Guidelines for deploying IBM® Campaign on WebSphere®

Follow these guidelines to deploy IBM® Campaign application files on WebSphere® Application Server.

For complete information about WebSphere®, see the following links:

For WebSphere® Application Server version 8, see Welcome to the WebSphere® Application Server information center.

For WebSphere® Application Server version 7, see the WebSphere® Application Server Version 7.0 Information Center.

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®.

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.

Deploy the IBM® WAR orEAR file as an enterprise application.

Follow the guidelines below. Unless otherwise noted, you can accept the default settings.

In the form where you browse to and select the WAR or EAR file, select Show me all installation options and parameters so the Select Installation Options or Install New Application wizard runs.

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. If you deployed an EAR file, set the JDK Source Level for each web module (.war file).

In the server's Web Container Settings > Session Management section, enable cookies.

Specify a different session cookie name for each deployed application:

If you deployed a WAR file:

In the WebSphere® console, in the server's Applications > Enterprise Applications > [deployed_application] > Session Management > Enable Cookies > Cookie Name section, specify a session cookie name that is unique.

Select the Override session management check box in Session Management.

If you deployed an EAR file:

In the WebSphere® console, in the server's Applications > Enterprise Applications > [deployed_application] > Module Management > [deployed_module] > Session Management > Enable Cookies > Cookie Name section, specify a session cookie name that is unique.

Select the Override session management check box in Session Management.

In the server's Applications > Enterprise Applications section, select the WAR file or EAR file that you deployed, then select Class loading and update detection and set the following General Properties on the Configuration tab:

If you deployed a WAR file:

For Class loader order, select Classes loaded with local class loader first (parent last).

For WAR class loader policy, select Single class loader for application.

If you deployed an EAR file:

For Class loader order, select Classes loaded with local class loader first (parent last).

For WAR class loader policy, select Class loader for each WAR file in application.

Select Enterprise Applications > [deployed_application] >Manage Modules > [module name] and set Class loader order to Classes loaded with local class loader first (parent last).

Start your deployment.