Essbase XTD Deployment Services Release 6.5.3

Configuring Application Servers

This document describes what you need to do to deploy and configure Essbase XTD Deployment Services within the Apache Tomcat Application server or other supported application servers.

There are three steps to the configuration:

Making Configuration Changes
Setting ARBORPATH and PATH on Windows or on Unix
Configuring Application Servers

The following topics explain how to deploy and configure the supported application servers:

Configuring the Apache Tomcat Server
Configuring the BEA WebLogic Server
Configuring the IBM WebSphere Enterprise Server
Configuring the Sun ONE Application Server

Top

Making Configuration Changes

Open the essbase.properties file present in the $EDS_HOME\bin folder and replace all the relative path references (..\essolap) to the full path of the location of Essbase XTD Deployment Services.
For example, system.dataDir=../data should be changed to system.dataDir=c:/Hyperion/Essbase/ees/data.
Disable starting of the Essbase Deployment Services command shell in the Deployment Server console by setting system.cmdShell.start property to false in essbase.properties file.
For example,
```
# Embedded Command console.
system.cmdShell.start=false
```

Top

Setting ARBORPATH and PATH on Windows

Before configuring the application server to host Deployment Services, the ARBORPATH and PATH environment variables have to be configured properly.

Set the ARBORPATH variable to $EDS_HOME\essolap.
Add $EDS_HOME\bin and $ARBORPATH\bin to the system path.

Examples:

If Deployment Services is installed in c:\hyperion\essbase\ees add the following environment variables:

SET ARBORPATH=c:\hyperion\essbase\ees\essolap
SET PATH=%ARBORPATH%\bin;c:\hyperion\essbase\ees\bin;%PATH

Top

Setting ARBORPATH and PATH on Unix

Before configuring the application server to host Deployment Services, the ARBORPATH and Library path environment variables have to be configured properly. You can set these parameters through your .bashrc, .cshrc, or .profile depending on the shell you are using.

Make sure these parameters are set before starting the application server configuration. The following examples are for bash shell.

AIX

Set the ARBORPATH variable to $EDS_HOME/essolap
Set LIBPATH to $EDS_HOME/bin:$EDS_HOME/essolap/bin

Examples:

For Deployment Services installed in /export/home/ees, add the following environment variables:

export ARBORPATH=/export/home/ees/essolap
export  LIBPATH=/export/home/ees/bin:/export/home/ees/essolap/bin:$LD_LIBRARY_PATH

HP-UX

Set the ARBORPATH variable to $EDS_HOME/essolap
Set SHLIB_PATH to $EDS_HOME/bin:$EDS_HOME/essolap/bin

Examples:

For Deployment Services installed in /export/home/ees, add the following environment variables:

export ARBORPATH=/export/home/ees/essolap
export SHLIB_PATH=/export/home/ees/bin:/export/home/ees/essolap/bin:$LD_LIBRARY_PATH

Solaris

Set the ARBORPATH variable to $EDS_HOME/essolap
Set LD_LIBRARY_PATH to $EDS_HOME/bin:$EDS_HOME/essolap/bin

Examples:

For Deployment Services installed in /export/home/ees, add the following environment variables:

export ARBORPATH=/export/home/ees/essolap
export LD_LIBRARY_PATH=/export/home/ees/bin:/export/home/ees/essolap/bin:$LD_LIBRARY_PATH

Top

Configuring Application Servers

The following topics explain how to deploy and configure the supported application servers:

Configuring the Apache Tomcat Server
Configuring the BEA WebLogic Server
Configuring the IBM WebSphere Enterprise Server
Configuring the Sun ONE Application Server

Top

Configuring the Apache Tomcat Server 4.1

The Apache Tomcat application server can be downloaded from the Apache Foundation website:
http://jakarta.apache.org/tomcat/index.html

If you have an existing installation of Apache Tomcat perform the following steps to deploy and configure it for use with Deployment Services.

To deploy the Deployment Services Release 6.5 server file to Apache Tomcat:

If Apache Tomcat is already running, stop the application server.
Copy C:\Hyperion\ees\redist\eds.war file from $EDS_HOME\redist to the \tomcat webapps directory.
Copy the Essbase.properties file to the /bin folder of Tomcat.
Start Apache Tomcat to complete the deployment process.

Note:
To validate that you have installed and deployed the application server that you are using, go to http://<hostname>:<port number>/eds/EssbaseEnterprise to verify that Deployment Server is up and running.

Top

Configuring the BEA WebLogic Server 6.1

If you plan to use the BEA WebLogic application server with Deployment Services, start the WebLogic server and perform the following steps to deploy and configure WebLogic for use with Deployment Service.

To deploy the Deployment Services server file to WebLogic, complete the following steps:

In the WebLogic Server Console navigation frame click mydomain, then click Application.
From the menu displayed, select Install a new Application and select Browse to navigate to the .war file. This will enable you to upload the Essbase Deployment Server .war file to be deployed to the WebLogic server.
Navigate to $EDS_HOME\redist\eds.war.
Click on Web Applications in the navigation view. In the Web Applications page you will see a table that has Name, Application and URI columns. The name EDS must show in that table.
In the navigation frame, navigate to Deployment > Web Applications > and click the name eds. In the configuration window, click on the Targets tab, click on the Server tab, and choose the server name. Click the arrow to place your selection under the Chosen list. Click Apply.
Copy the Essbase.properties file from $EDS_HOME\bin to the location where the startweblogic.cmd (startWebLogic.sh for Unix) resides. For example, if you are using the default domain, mydomain, the startweblogic.cmd is present in c:\bea\user_projects\mydomain.

Top

Configuring the IBM WebSphere Enterprise Server 4.x

If you plan to use the IBM WebSphere application server with Deployment Services, start the WebSphere server, and perform the following steps to deploy and configure WebSphere for use with Deployment Server.

To deploy the Objects server file to WebSphere, complete the following steps:

In the navigation frame of the WebSphere Administrative Console, click Applications, then click Install New Application.
On the Preparing for the application installation page, click Browse and navigate to the $EDS_HOME\redist\eds.war file.
In the Context Root box, enter /eds and click Next.
In the Generate Default Bindings box, click Next to accept the default values.
In the Step 1 Provide options to perform the installation box, click Next to accept the default values shown in the AppDeployment Options box.
In the Step 2 Map virtual hosts for web modules box, click EDSWebModule to select it as the default host, then click Next.
In the Step 3 Map Modules to application servers box, check EDSWebModule, to indicate eds.war is the module to map to WebSphere (the server, and then click Next.
In the Step 4 Summary box, click Finish to initiate the installation.
When the installation is completed, a message advises you that the eds_war application is successfully installed.
Click the Save to Master Configuration option to enable startup of Deployment Server, then click Save.
When the Enterprise Applications page is displayed, click eds.war, and then click Start to start Deployment Server.
Copy the Essbase.properties file from $EDS_HOME\bin to AppServer\Bin folder of your WebSphere installation.
Restart WebSphere for the settings to take effect.

Top

Configuring the Sun™ ONE Application Server 7.0

If you plan to use the Sun ONE application server 7.0 with Essbase XTD Deployment Services, start the Sun ONE Application server, and perform the following steps to deploy and configure the Essbase XTD Deployment Services server with Sun ONE 7.0.

To deploy the Essbase XTD Deployment Services files to Sun ONE, complete the following steps:

In the navigation frame of the Sun ONE Administrative Console, Navigate to Web Apps under server1->applications.
On the Applications page, click on Deploy.
On the Upload WAR File page click Browse and navigate to $EDS_HOME\redist\eds.war file. Click OK.
In the Server1:Applications:Web:Deploy page, click OK accept the default values.
Copy the Essbase.properties file from $EDS_HOME\bin to the config folder of your application server domain. For example, for default installation, copy essbase.properties file to AppServer\domains\domain1\server1\config folder of your Sun ONE installation.
Modify the policy of your virtual server to allow reading and writing of properties.
Open the server.policy file located in the AppServer\domains\domain1\server1\config folder and search for the string permission java.util.PropertyPermission "*", "read ". Change it to permission java.util.PropertyPermission "*", "read,write";
Restart Sun ONE application server for the settings to take effect.

Top