The following application settings are available:
Options that control application loading, command processing, connections, updates, and security
Settings that define the minimum permissions to the application (see Setting Application and Database Minimum Permissions in Essbase Native Security Mode)
The following settings are available for various levels of application security:
When disabled, prevents all users from starting the application directly or as a result of operations that would start the application; for example, attempting to change application settings or create databases. By default, the application is not prevented from starting.
Start When Essbase Server Starts.
When enabled, the application starts automatically whenever the Essbase Server starts. By default, the application does not start when the Essbase Server starts.
When unchecked, prevents users from making requests to databases in the application, including non-data-specific requests such as viewing database information or changing database settings. Administrators are affected by this setting as a safety mechanism to prevent accidental changes to databases during maintenance operations. By default, commands are enabled.
When unchecked, prevents users with a permission lower than Application Manager for that application from making connections to databases within the application which require the databases to be started. By default, connections to databases are allowed.
When unchecked, prevents modification to on-disk database structures; for example, any operation that might have an effect on the data. This restriction does not include outline operations. To block metadata updates, set the database to read-only mode or uncheck Allow Commands and/or Allow Connects. By default, updates are enabled.
When unchecked, Essbase ignores all security settings in the application and treats all users as Application Managers. By default, security is enabled.
Table 123 describes when the implementation of protective application settings takes effect, how long the effects last, and which users are affected.
Table 123. Scope and Persistence of Application-Protection Settings
If performing maintenance operations that require disabling commands or updates, make those maintenance operations within the same session as the one in which the setting was disabled. |
If you disable commands or updates in a MaxL script, be aware that the end of the script constitutes the end of the session. Calling a nested MaxL or ESSCMD script from the current MaxL script also constitutes the end of the session.
If you disable commands or updates in an ESSCMD script, the end of the script constitutes the end of the session, but calling a nested ESSCMD script from the current ESSCMD script does not constitute the end of the session.
If a power failure or system problem causes Essbase Server to improperly disconnect from the Essbase client, and the application is no longer accessible, you must shut down and restart the application. See Starting and Stopping Applications.