|
|
|
3Director is an intermediary application between and Essbase client and server. It’s purpose is to serve as a traffic mediator for the Essbase enterprise. Clients request access to the data they require rather than it’s location in the form of a specific server name. 3Director maintains a repository of data location information and connects the client to the appropriate server. Once this level of indirection has been established, it can be used for several purposes. Data can be moved unbeknownst to it’s users. This allows the system administrator swap out a server for maintenance. Similarly, an automated fault tolerant architecture can be supported. . There is no restriction on the client, it can be any application that normally connects to the Essbase server via the Essbase API. These include, but are not limited to, Excel, Wired for OLAP, even the Essbase Application Manager. For added functionality, 3Director can be connected to a 3Sentry (which, in turn, manages an Essbase server). In this configuration, the 3Director is able to provide a site wide view of an Essbase intranet. 3Director will connect a user to an instance of Essbase that is currently running and hosts the requested data. Users are connected accordingly. This provides for the existence of redundant servers for critical data. 3Director uses statistical data maintained by 3Sentry to determine which server containing the requested data is least busy. 3Client users can connect to the 3Director and view the entire network of Essbase servers. Which servers are up/down, what users are connected where, relative load on each server. Just as the 3Sentry can message it’s clients, 3Director can message all connected 3Clients. | ||||||