WebSphere® guidelines

Follow the guidelines in this section when deploying IBM® Unica Marketing application files on WebSphere®.

Be sure that the version of WebSphere® meets the requirements described in the IBM® Unica® Enterprise Products Recommended Software Environments and Minimum System Requirements document, including any necessary fix packs or upgrades.

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

In step 1 of the Select Installation Options wizard, select Precompile JavaServer Pages files.

In step 3 of the Select Installation Options wizard, ensure that the JDK Source Level is set to 15.

1.	Deploy the IBM® Unica® application file as an enterprise application.

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

3.	If you are using WAS 8, choose Applications > Websphere Enterprise applications > Campaign > Session management > Cookies, and disable the following setting: Set session cookies to HTTPOnly to help prevent cross-site scripting attacks. (The setting is enabled by default.)

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

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.

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.

5.	If your system tables are in DB2®, go to the data source's Custom Properties. Set the value for resultSetHoldability to 1.

If you do not find a field named resultSetHoldability, add a custom property with that name and with the value set to 1.

6.	If you are deploying multiple IBM® Unica® applications, modify the session cookie name for each deployed application to ensure that it is unique, as follows:

In the server's Applications > Enterprise Applications > [deployed_application] > Session Management > Enable Cookies > Cookie Name section, specify the session cookie name.