Databases Reference
In-Depth Information
Startup section
This property is used to tell Essbase how to automatically start the application.
There are two ways you can start an Essbase application:
•
Allow users to start application
•
Start application when Essbase Server starts
By default,
Allow users to start application
is selected and we advise you to leave
it as it is. Only select the second option when it is absolutely necessary for the
Essbase server to start your application. As you have previously learned, if an
inactive application is started it will unnecessarily consume system memory.
One of the only times it may be necessary to have an application start (when the
Essbase server is started) is if you have an automated batch process which starts
immediately following a server restart. This might be performed during routine
server maintenance or housekeeping.
Security
There are several different types of security commands. They are listed as follows:
•
Allow commands
:
If checked, this allows users to run commands on the
database in the application. This option is selected by default.
•
Allow connects
:
If checked, this allows all users with proper access to connect
to the application. When unchecked, only the Application Designer, or higher
users, are allowed to connect to the database. This option is selected by default.
•
Allow updates
:
If checked, this allows the users with appropriate access
to update the data in the databases. This option is selected by default.
•
Enable security
:
If this option is unchecked, then Essbase ignores all of the
security settings and gives Application Designer access to all of the users.
This option is selected by default and we recommend you keep it that way.
Minimum access level
This setting sets the minimum access level for all databases within an application,
and grants this access level to all valid IDs created on the server. The setting can
be overridden at the database level, but it's really a good idea to leave it set to none
at the application level. This property will be discussed further, in detail, in the
database properties section of this chapter.
