|
|
|
3Sentry is an application responsible for managing an Essbase server. For each Essbase server running on the network, a 3Sentry is assigned to stand guard. More than a security application, 3Sentry exposes an Essbase server to the network in a secure way. Client services are provided to enhance the use of Essbase in the enterprise. Capabilities provided by 3Sentry include; metadata management, scheduled execution of Essbase console commands (including "dump"), filter manipulation, statistical analysis and client messaging. 3Sentry compliments Essbase by working at the metadata level. These capabilities make 3Sentry alone a valuable product for customers who manage a single Essbase server. For multiple server sites, 3Sentry is a key component in coordinating a network of multiple Essbase servers. 3Sentry allows security data in an Essbase "security dump" file to be loaded into the server. Previously this data was locked within the "security dump" file. No tool existed to read it. 3Sentry brings this data to life by allowing it to be browsed and applied to the server. Furthermore, 3Sentry has the unique ability to move security data between applications and databases on a single server. A security dump file is the file produced by the Essbase console’s "dump" command. This file is essentially a snapshot of an Essbase configuration at a given point in time. It contains a rich set of metadata that essentially describes all of the allowed contents (see below). The data that is managed is referred to as metadata rather than simply security data because this information includes descriptions of servers, applications, and databases (data about data) as well as usernames, passwords and security filters. Metadata is also referred to as "configuration data". Essbase configurations can be browsed in 3Sentry’s user interface. The 3Sentry user is allowed to select an arbitrary subset of the source metadata to be loaded. This subset is referred to as the content of a metadata operation. The metadata elements that the user is allowed to select from include any or all of the following; Essbase server configuration parameters can be set in the target(s) according to those in the source. Applications and databases along with the full set of associated configuration parameters can be created or deleted. Applications or databases that already exist will have their configuration parameters changed if necessary. Users and groups at the server, application and database level can be created, updated or deleted. Propagating a user or group includes it’s definition as well as it’s access rights. Loading groups means that group lists can be maintained. Database filter definitions can be created, updated or deleted in their entirety. A scheduling component allows 3Sentry to execute any Essbase console command on a periodic basis. This can be a simple command or a complex batch defined in the scheduling user interface. 3Sentry can read the data in a security dump file and use it to recover an Essbase server configuration. Combine this with the periodic running of the "dump" command to produce the file and you have finer control of the security backup/recovery process. For example, instructing 3Sentry to issue a "dump" command every 15 minutes means you stand to loose at most 15 minutes of administrative work. Beyond the ability to copy or delete filters as a whole, the 3Sentry manages filter access rights in a unique way. This is useful when, for example, you want to temporarily prevent general users from changing data while the system administrator updates the database. Access rights can be toggled, for selected database filters, to one of the following modes;
This is the set of access levels supported by Essbase. A database can effectively be locked by setting a group of filters to read or none. Filter access rights are set according to the values in a propagation source. This can include a mixture of none, read and write. This is used to set the values back after temporarily locking a database by setting the filters to none or read access. An interface exists for sending all clients connected to 3Sentry an arbitrary message. This is a useful tool for communicating between the system administrator and users. Users are informed. The system administrator can send messages to all the connected clients; "Essbase server redwood will be down at 7:00 P.M. for maintenance." In such a case, while Essbase is "down", users are notified via a status bar, so they do not have to travel to the system console to confirm their suspicion. Trusted clients have access to the server’s console and can manipulate Essbase as if they where sitting at the system’s console.. System administrators will readily recognize the Essbase console. GUI tools are provided to make routine administration jobs easier. Essbase server load statistics are maintained by the 3Sentry. This data can be useful in determining how busy the server is at a given point in time. System administrators can use this data to determine configuration parameters. | ||||||