Professional Documents
Culture Documents
Deploy Application Server PDF
Deploy Application Server PDF
This section describes how to deploy the engine (on Linux) on the following application
servers:
• Oracle Application Server
• Web Logic
• Tomcat
Deploying on WebLogic
Perform the steps in this section only if you are deploying the engine on the Web Logic application
server.
1. Open the Web Logic Server administration page in a Web browser.
2. Click Start the Administration Console
3. Navigate to base_domain > Configuration > Web Applications.
4. Verify that “Archived Real Path” is enabled, and then save any changes.
5. Activate the changes, e.g. in the Admin console, click Activate Changes.
6. In Domain Structure, navigate to Deployments, then click Lock & Edit.
7. Choose to install a new application or module, e.g. click Install.
8. Enter the full directory path to engineManager.war.
9. Select engineManager.war, and then click Next.
10. Choose to install the deployment as an application, and then click Next.
11. Enter a name for the deployment, e.g. “engineManager”, and then click Finish.
12. Activate the changes, e.g. in the Admin console, click Activate Changes.
13. In Domain Structure, navigate to Deployments, then click Lock & Edit.
14. Select the engineManager Web application from the list of available deployments, then
select Start > Servicing All Requests.
15. Start the deployment, e.g. click Yes, and then release the configuration. e.g. click Release
Configuration.
16. When the application status = Active, engineManager is ready for use. Refer to the steps
below to complete the deployment.
Perform the following to complete the deployment on Web Logic:
Update the file $WL_HOME/user_projects/domains/base_domain/bin/-setDomainEnv.sh. Append
ENGINE_ROOT,PATH and LD_LIBRARY_PATH definitions, as in the following example:
ENGINE_ROOT=/home/oracle/demantra
PATH=/home/oracle/demantra/lib:$PATH
LD_LIBRARY_PATH=/home/oracle/demantra/lib:$LD_LIBRARY_PATH
ORACLE_HOME=/home/oracle/demantra/lib/ORACLE_HOME
export ENGINE_ROOT PATH LD_LIBRARY_PATH ORACLE_HOME
Please be aware that application server configurations can impact Demantra performance, both
positively and negatively. For example, if parameters relating to connection timeout or stuck
threads are set incorrectly, they can cause issues. Please review the configuration guide for
your application server version.
Deploying on Tomcat
Perform the steps in this section only if you are deploying the engine on the Tomcat application
server.
To deploy the engine on Tomcat, run the following script:
<INSTALL_ROOT>/bin/deployEngineManagerIntoTomcat.sh
Note: The following useful scripts are also available in this directory:
• TomcatRun.sh - Starts tomcat
• TomcatEnd.sh - Stops tomcat
• startBatchTomcat.sh - Starts engine in batch mode
• startSimulationTomcat.sh - Starts the engine in simulation mode
• stopEngineTomcat.sh - Stops the engine
Note: User needs to deploy only one Application Server.
Engine Configuration
1. Download and deploy additional library or RPM (standard C++ library for RedHat 7.x) from
the following URL:
http://rpm.pbone.net/index.php3/stat/2/simple/2
2. Select the check box for RedHat 7.x, and then enter the following in the Search field:
compat-libstdc++-rh62-1.i386
3. Click Search.
4. Download then manually copy/move the library libstdc++-libc6.1-2.so.3 to the /usr/lib or
<ENGINE_ROOT>/lib directory. Oracle recommends this method because installing older
compatible RPM versions can be problematic.
Alternatively, download the library and install it as ROOT compat-libstdc++-rh62-
1.i386.rpm package.
5. Change to the <ROOT DIRECTORY>/bin and make all scripts executable:
cd bin
chmod +x *.sh
6. Set up system
The engine manager configuration consists of the following:
o Configure environment variables
o Configure the Engine
Configure Environment Variables
As you did previously, run a script that prompts you for input and sets up configurations:
<INSTALL_ROOT>/bin/configureVarables.sh
* Note that every path provided to configureVarables.sh should NOT include a trailing "/"
<INSTALL_ROOT>/bin/source $HOME/.bash_profile.
Note, if your Engine is on the same machine as EngineManager you don’t need to run script twice.