Guidelines for deploying the Marketing Platform on all versions of WebSphere®
Follow the guidelines in this section when deploying the Marketing Platform on IBM® WebSphere®.
1.
Be sure that the version of WebSphere® meets the requirements described in the IBM® Enterprise Products Recommended Software Environments and Minimum System Requirements document, including any necessary fix packs or upgrades.
2.
*
Name: com.ibm.ws.webcontainer.invokefilterscompatibility
*
See http://www-01.ibm.com/support/docview.wss?uid=swg21284395 for instructions on setting a custom property in WebSphere®.
3.
Deploy the IBM® EAR file or unica.war file as an enterprise application.
Follow the guidelines below. Unless otherwise noted below, you can accept the default settings.
Ensure that the JDK source level of the JSP compiler is set to Java 16 and that JSP pages are precompiled, as follows.
*
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, do the following.
*
In step 3 of the Select Installation Options wizard, ensure that the JDK Source Level is set to 16. If 16 is not available, select 15.
*
The context root must be the it /unica, all lower case.
4.
In the server’s Web Container Settings > Web Container > Session Management section, enable cookies.
5.
*
Select the Override session management checkbox under Session Management.
*
If you deployed separate WAR files for your IBM® EMM products, 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 checkbox under Session Management.
*
If you deployed EAR files for your IBM® EMM products, 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.
6.
Only if your installation must support non-ASCII characters, for example for Portuguese or for locales that require multi-byte characters, add the following to Generic JVM Arguments at the server level.
-Dfile.encoding=UTF-8
-Dclient.encoding.override=UTF-8
Navigation tip: select Servers > Application Servers > Java and Process Management > Process Definition > Java Virtual Machine > Generic JVM Arguments. See the WebSphere® documentation for additional details.
7.
In the server's Applications > Enterprise Applications section, select the EAR file or WAR file 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.
8.
9.
Only if your instance of WebSphere® is configured to use a JVM version 1.6 or newer, do the following to work around an issue with the time zone database.
*
Stop WebSphere®.
*
Download the IBM® Time Zone Update Utility for Java (JTZU) from the IBM® web site:
*
*
Follow the steps provided by the IBM® (JTZU) to update the time zone data in your JVM.
10.
Restart WebSphere®.