Deploy Application Server

This section describes how to deploy the engine (on Linux) on the following application
servers:
• Oracle Application Server
• Web Logic
• Tomcat

Deploying on Oracle Application Server (OAS)

Perform the steps in this section only if you are deploying the engine on OAS.
Generally, <INSTALL_ROOT>/lib/engineManager.war is installed with pack
Oracle_Demantra_Linux_Engine.tar.gz. If you need to create it manually, use the following
command:
cd <INSTALL_ROOT>/lib jar cvf engineManager.war WEB-INF conf
Open the Oracle Application Server administration page in your browser (example,
http://<server>:7778/em).
Perform the following steps to deploy <INSTALL_ROOT>/lib/engineManager.war:
1. In the list of Application Servers, click ‘home’ (type = OC4J).
2. Click Administration.
3. Go to the Configure Server Properties task.
4. In the Server Properties section, define environment variables as described below:
• Set LD_LIBRARY_PATH to <INSTALL_ROOT>\lib
• Set PATH to <INSTALL_ROOT>\lib
• Set ENGINE_ROOT to <INSTALL_ROOT>
* Make sure to uncheck the Append checkbox to the right, if any other paths are required
add them directly following the engine required paths
Note: If your database instance is configured in a different language, also define the following
environment variable:
Set NLS_LANG to AMERICAN_AMERICA.AL32UTF8S
5. Save the changes, and then deploy the EngineManager.war file. For example, click Deploy,
browse to select the EngineManager.war file, click Next, and then click Deploy.
6. Verify that engineManager was deployed successfully. For example, the following message
appears: “application “engineManager” has been deployed successfully”.
7. Restart Oracle Application Server.
<INSTALL_ROOT>/bin/shutdownOAS.sh <INSTALL_ROOT>/bin/startallOAS.sh
Note: Verify that a tnsnames.ora file is not automatically deployed with OAS. If it is, delete it.
 Note: Verify that engine path definitions are appended to the LD_LIBRARY_PATH and PATH
environment variables.

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.

Configure the Engine

The engine works as an operating system service, similar to telnet and FTP.
Perform the following to configure the engine to run on Linux.
Update the following system parameters:
• EnginePlatform: The operating system platform on which the engine is executed. (Set to 1
for Linux.)
• EngineBaseUrl: The base URL to be used to execute the engine.
You can update these parameters either in Business Modeler (Parameters > System Parameters,
System tab), OR by performing the following update statements:
UPDATE SYS_PARAMS SET pval = '1' WHERE lower(pname) = 'engineplatform' UPDATE
SYS_PARAMS SET pval = '#URL#' WHERE lower(pname) = 'enginebaseurl'
Note: Be sure to replace the #URL# token with the actual URL of the engine manager.
Example:
http://server.us.oracle.com:9999/engineManager/
where 'server.us.oracle.com' is the URL part of the environment server and '9999' is the correct
port.