Configuring the Administration Services Console Launch File

A default EASLaunch.properties file is created during installation and contains the configuration setting necessary to launch Administration Services Console directly from the Essbase Studio Console Tools menu or from deployed cubes.

Note:

In order to launch Administration Services Console from Essbase Studio Console, the Administration Services Console must be installed on the same machine as Essbase Studio Console. If the consoles are installed on different machines, a message is displayed when attempting to launch Administration Services Console.

After installation and configuration, you may edit EASLaunch.properties manually to add the remaining optional Essbase Administration Server properties.

Note:

You can configure only one Oracle Essbase Administration Services instance in EASLaunch.properties.

  To configure the EASLaunch.properties file:

  1. Locate and open the EASLaunch.properties file in the Essbase Studio installation in the \Console\eas directory.

    Note:

    Edit the file in text format with any text editor, such as Windows Notepad. Enter each setting on a separate line in the file. You do not need to end each line with a semicolon.

  2. Verify the setting already written in this file, EASHome.

    During the installation process, EASHome is populated with the location of your Administration Services installation on the client machine. Note that this is not the same as the location of the Administration Services client executable, but is equal to the value of the EAS_HOME environment variable. For example:

    EASHome=C:\Oracle\Middleware\EPMSystem11R1\products\Essbase\eas\server

    Note:

    This is the only required setting and assumes you are connecting to an instance of Essbase Administration Server on the local machine.

    Including only the EASHome setting in EASLaunch.properties means that, when launching Administration Services Console from Essbase Studio Console, the Essbase Administration Services Logon window is displayed with the Essbase Administration Server field already populated with the server name of the local machine. To log in, you need only provide a valid user name and password.

  3. Optional: If you want to connect to an instance of Essbase Administration Server on a different computer, add a line for EASServer and provide the machine name where Essbase Administration Server is installed.

    For example:

    EASServer=spruce1

    Including only the EASHome and EASServer settings in EASLaunch.properties means that, when launching Administration Services Console from a deployed cube in Essbase Studio Console, the Essbase Administration Services Logon window is displayed with the Essbase Administration Server field already populated with the server name you provided in this step. To log in, you need only provide a valid user name and password.

    Note:

    You can change the Essbase Administration Server setting (EASServer) at any time and relaunch Administration Services Console without stopping and restarting Essbase Studio Server.

  4. Optional: Add a line for the user name setting.

    EASUser—A valid Administration Services user name. This setting can be overwritten at the console login screen with a valid user name. For example:

    EASUser=admin

    Including the optional user name setting in EASLaunch.properties means that, when launching Administration Services Console from Essbase Studio Console, the Essbase Administration Services Logon window is already populated with user name you have specified.

  5. Save EASLaunch.properties.