In This Section:
Requirements for Using Administration Services Java Plug-ins
This chapter provides an overview of Oracle Essbase Administration Services.
Administration Services is the cross-platform framework for managing and maintaining Oracle Essbase. Administration Services provides a single point of access for viewing, managing, and maintaining Essbase Servers, Essbase Administration Servers, and Oracle Hyperion Provider Services.
Administration Services works with Essbase Servers in a three-tiered system that consists of a client user interface, a middle-tier server, and one or more database servers (Essbase Servers). The middle tier coordinates interactions and resources between the user interface and Essbase Servers. The three tiers may or may not be on the same computer or platform. For more information about deployment scenarios, see Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
The three tiers include the following:
Client tier: Administration Services Console—A Java client console enabling administrators to manage the Essbase environment from a robust graphical user interface.
Middle tier: Essbase Administration Server—A Java middle-tier server that communicates with Administration Services Console and Essbase Servers. Essbase Administration Server maintains communication and session information for each connection to Essbase Servers. Essbase Administration Server also stores documentation files so that console users can access documentation without having to install it locally.
Database tier: Essbase Server—One or more Essbase Server that store and process multidimensional database information. Essbase Servers are installed separately from Administration Services.
Essbase Administration Server serves as the middle tier between Administration Services Console and Essbase Servers, as shown in Figure 1, Administration Services Architecture.
Administration Services Java plug-ins are installable components. They provide the following benefits to users:
Enable the Administration Services development team to easily provide additional functionality to end users
Allow other Oracle internal development groups to easily integrate their products withAdministration Services
Enable partners and customers to easily integrate their processes into Administration Services
Allow customers to accomplish more because they are not launching several applications at once
The following list describes how you can use Administration Services plug-ins:
For each of these tasks, there are a set of classes, interfaces, and methods that must be implemented by a plug-in author. There are also a set of guidelines to follow when implementing plug-ins.
For information about performing the preceding tasks, see Writing Client Plug-ins.
The following list describes the requirements necessary to use Administration Services Java plug-in components:
Developers using this guide must have the following prerequisite knowledge:
Swing is a graphical user interface (GUI) component kit, part of the Java Foundation Classes (JFC) integrated into Java 2 platform, Standard Edition (J2SE). Swing simplifies deployment of applications by providing a complete set of user-interface elements written entirely in the Java programming language. Swing components permit a customizable look and feel without relying on any specific windowing system.
Because Swing is incorporated in the Java 2 platform, there is no need to download or install it.
The code snippets and examples contained in this guide are intended to demonstrate how plug-ins interact with the Administration Services framework. They are intended to show how to get an aspect of the interaction to work and, in some cases, omit details that are not relevant to the topic being discussed. In addition, while the techniques shown will work, the Java techniques shown may in some cases not be the best implementation method when scaling up to a production quality product.
For example, in the section on context menu items, Adding Context Menu Items To Tree Nodes, the example creates new menu items and action listeners each time the getContextMenuItems() method is called; this might not be the best mechanism for handling this task. Please consult the appropriate Java resources (books, Web pages, documentation) for other techniques; in particular, when dealing with Swing objects, the Swing event model, and associating Swing event listeners to objects.