Deploying Opportunity Detection on WAS from an EAR file
You can deploy the Opportunity Detection application on WAS when Opportunity Detection is a module within an EAR file.
You can deploy Opportunity Detection by using an EAR file if you included Opportunity Detection in an EAR file when you ran the IBM® EMM installer.
Before you deploy Opportunity Detection:
*
Confirm that your version of WebSphere® meets the requirements in the Recommended Software Environments and Minimum System Requirements document, including any necessary fix packs or upgrades.
*
To deploy Opportunity Detection from an EAR file onto WebSphere® Application Server, complete the following steps:
1.
Go to the WebSphere® Integrated Solutions Console.
2.
If your system tables are in DB2®, click the data source that you created. go to the Custom Properties for the data source. .
3.
4.
Set the value for the resultSetHoldability property to 1.
If you do not see the resultSetHoldability property, create the resultSetHoldability property and set its value to 1.
5.
Go to Applications > Application Types > WebSphere enterprise applications and click Install.
6.
In the Preparing for the application installation window, select the Detailed - Show all options and parameters check box and click Next.
7.
Click Continue to see the Install New Application wizard.
8.
*
In step 1 of the Install New Application wizard, select the Precompile JavaServer Pages files check box.
*
9.
In the left navigation panel of WebSphere® Integrated Solutions Console, navigate to Applications > Application Types > WebSphere enterprise applications.
10.
11.
In the Web Module Properties section, click Session Management and select the following check boxes:
*
*
12.
Click Enable Cookies, and in the Cookie name field, enter a unique cookie name.
13.
In the Detail Properties section, select Class loading and update detection.
14.
In the Class loader order section, select the Classes loaded with local class loader first (parent last) option.
15.
In the WAR class loader policy section, select the Class loader for each WAR file in application option.
16.
Go to Application Servers > your server > Process definition > Java Virtual Machine.
17.
In the Generic JVM arguments section, enter the following JVM arguments:
-Dcom.ibm.websphere.webservices.DisableIBMJAXWSEngine=true
-Dibm.cl.verbose=PersistenceProvider
-Dibm.cl.verbose=PersistenceProviderImpl
-agentlib:getClasses -verbose:dynload
-Dcom.ibm.xml.xlxp.jaxb.opti.level=3
18.
For more information about WebSphere® Application Server version 8, see Welcome to the WebSphere® Application Server information center.