To deploy IBM® Campaign on WebSphere® Application Server from an EAR file
Follow this procedure to deploy the IBM® Campaign application on WebSphere® Application Server when Campaign is a module (.war file) within an EAR file.
These instructions pertain if you included IBM® Campaign in an EAR file when you ran the IBM® EMM installer. If you are deploying an EAR file, you must follow all of the deployment guidelines detailed in the individual installation guides for the products included in the EAR file.
Before you deploy IBM® Campaign:
*
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.
*
Confirm that you created the data sources and database provider in WebSphere®.
See Preparing data sources for IBM Campaign.
1.
To deploy IBM® Campaign from an EAR file onto WebSphere® Application Server, complete the following steps.
2.
If your system tables are in DB2®, go to the Custom Properties for the data source. Set the value for resultSetHoldability to 1.
If you do not see a field named resultSetHoldability, add a custom property with that name and set its value to 1.
3.
Follow the guidelines below to deploy the IBM® EAR file as an enterprise application.
Unless otherwise noted, you can accept the default settings.
*
In the form where you browse to and select the EAR file, select Show me all installation options and parameters to start the Select Installation Options or Install New Application wizard.
*
In step 1 of the installation wizard, select Precompile JavaServer Pages files.
*
In step 3 of the installation wizard, set the JDK Source Level to 16. If 16 is not available, select 15. Be sure to set the JDK Source Level for each web module (.war file).
*
In step 10 of the installation wizard, confirm that the Context Root value is set to /Campaign. The correct Context Root values are supplied for you in the wizard. For example, unica.war is set to /unica and Campaign.war is set to /Campaign.
4.
In the server's Web Container Settings > Session Management section, enable cookies.
5.
If you are using version 8 of WebSphere® Application Server, choose Servers > WebSphere application server > server 1 > Session management > Cookies and clear the check box for Set session cookies to HTTPOnly to help prevent cross-site scripting attacks.
6.
In the WebSphere® console, open the server's Applications > Enterprise Applications > UnicaApp > Module Management > [deployed_module] > Session Management > Enable Cookies > Cookie Name section, and specify a unique session cookie name.
7.
Select the Override session management check box in Session Management.
8.
In the server's Applications > Enterprise Applications section, select the EAR file that you deployed, select Class loading and update detection and set the following General Properties on the Configuration tab:
*
Class loader order: Select Classes loaded with local class loader first (parent last).
*
WAR class loader policy: Select Single class loader for application.
9.
Specify the following settings for the Campaign.war module that is in the EAR file that you deployed:
a.
Go to Enterprise Applications and select the EAR file (UnicaApp).
b.
On the Manage Modules page, select the Campaign.war file.
c.
On the Enterprise Applications > EAR > Manage Modules > WAR page:
*
Set Starting weight to 10000.
*
Set Class loader order to Classes loaded with local class loader first (parent last).
d.
On the Enterprise Applications > EAR > Manage Modules > WAR > Session management page, select Enable cookies.
e.
On the Enterprise Applications > EAR > Manage Modules > WAR > Session management > Cookies page:
*
Set the Cookie name to CMPJSESSIONID.
*
For the Cookie maximum age, select Current browser session.
f.
On the Enterprise Applications > EAR > Manage Modules > WAR > Session management page
*
Select Allow overflow.
*
For Maximum in-memory sessions, enter 1000.
*
For Session timeout, select Set timeout and enter 30.
g.
Define the same settings for each of the other .war files that you want to deploy from the EAR file.
10.
Start your deployment.
Copyright IBM Corporation 2015. All Rights Reserved.