|
|
|
Armored3 is the application responsible for managing the configuration of multiple Essbase servers. It’s name refers to the secure and reliable transfer of metadata between Essbase servers. To date, metadata has been confined to a single server. Armored3 liberates metadata by allowing it to move freely in the enterprise. The free flow of metadata means an organization can gain control and enforce uniformity in the Essbase enterprise. Armored3 accomplishes it’s tasks by using the services of 3Sentry. Armored3 exposes the metadata management and filter manipulation capabilities of 3Sentry. |
||||||
|
The act of using metadata from one Essbase server to configure another is referred to as propagating metadata. |
|||||||
|
Metadata management in Armored3 is expanded from a single server perspective to encompass the entire enterprise. Given metadata information from a source, the Armored3 will configure the contents of it’s target Essbase server(s) accordingly. |
|||||||
|
Configuration data (metadata) can come from the following sources: |
|||||||
|
|||||||
|
|||||||
|
The definition of contents given for 3Sentry applies to its use here. Server settings, applications, databases, users, groups and database filters definitions are all portable across the enterprise. |
|||||||
|
The destination of a configuration propagation can be one or more running Esssbase servers. The user is presented with a list of Essbase servers in the organization to choose from. Selecting more than one instructs Armored3 to configure multiple Essbase servers in a single run. |
|||||||
|
In the same way that Armored3 expands metadata management to the enterprise level, database filters a liberated from the confines of a single server. Filter definitions as well as access settings can come from anywhere in the enterprise. |
|||||||