14 min read
Privacy Management with PowerShell – Let's look at the core features of Priva!
All you need to know about Privacy Management, privacy management policies, rules, and subject rights requests.
In ScriptRunner this mainly concerns the corresponding reports for the execution of scripts as well as the corresponding metadata. ScriptRunner uses the integrated SQL Compact database to store reports in the runtime environment. This has limits in capacity, especially for long-term storage.
In ScriptRunner 2016 a function for long-term storage will be available in the form of the Report/Audit DB Connector.
It allows the parallel storage of report and metadata on a SQL server. The implementation also has failure and restart functions. If, for example, the SQL server is not accessible, the transactions are stored locally on the ScriptRunner service backend. Once the database is accessible again, all outstanding reports are written to the long-term database. This ensures that all results of script executions are stored in the long-term memory at all times.
The configuration of the database connection is done by creating a specific registry key; the configuration for the credentials for the database access is done in the ScriptRunner UI.
Related posts
About the author:
Frank Kresse is Head of Product and CEO of ScriptRunner. As the inventor of the automation and delegation solution for PowerShell, he advises clients on use case scenarios and develops solutions for the automation and the digitalization of their processes. He is also involved in technology start-ups.
Latest posts:
- Privacy Management with PowerShell – Let's look at the core features of Priva!
- Let's celebrate System Administrator Appreciation Day!
- PowerShell 7: What are the pros and cons of switching from Windows PowerShell 5.1?
- Azure Arc & integration in VMware vSphere
- PowerShell Secrets – Bulletproof password management