Setting General Application Connection Options in Essbase Native Security Mode

The following application settings are available:

The following settings are available for various levels of application security:

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

Disabled Application Setting

When the Disabled Setting Takes Effect

Which Users are Affected by the Disabled Setting

Persistence of the Disabled Setting

Allow Users to Start Application

Immediately

All users, including administrators.

Users currently logged on and users who log on later.

The application cannot be started until an administrator re-enables the startup setting.

Start Application When Essbase Server Starts

Immediately

All users.

The application will not start with Essbase Server unless an administrator enables it.

Allow Commands

Immediately

All users, including administrators.

Users currently logged on and users who log on later.

Commands are disabled until any of the following actions occur:

  • The administrator who disabled commands logs off.

  • The application is stopped and restarted.

  • An administrator re-enables commands.

Allow Connects

Immediately, except that disabling connections does not affect users who already have databases loaded.

Users with permissions lower than Application Manager.

Users currently logged on and users who log on later.

Users already connected to the database are not affected.

Connections are disabled until any of the following actions occur:

  • The application is stopped and restarted.

  • An administrator re-enables connections.

Allow Updates

Immediately

All users, including administrators.

Users currently logged on and users who log on later.

Updates are disabled until any of the following actions occur:

  • The administrator who disabled updates logs off.

  • The application is stopped and restarted.

  • An administrator re-enables updates.

Enable Security

Immediately

All users, including administrators.

Users currently logged on and users who log on later.

Security is disabled until a user re-enables security.

  To change application settings, use a tool:

Tool

Topic

Location

Administration Services

Setting Application Properties

Oracle Essbase Administration Services Online Help

MaxL

alter application

Oracle Essbase Technical Reference

Note:

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.

Caution!

Never power down or reboot your client computer when you have cleared any Allow settings. Always log off from the server correctly. Improper shutdown can cause the application to become inaccessible, which requires a full application shutdown and restart.

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.