Guidelines for deploying Unica Platform on WebSphere

Make sure that the version of WebSphere® meets the requirements that are described in the Recommended Software Environments and Minimum System Requirements document, including any necessary fix packs. Use the following guidelines when you deploy Unica Platform on WebSphere®:

• Specify the following custom property in the server:
  • Name: com.ibm.ws.webcontainer.invokefilterscompatibility
  • Value: true
• Set a custom property in WebSphere®.
• Deploy the EAR file or unica.war file as an enterprise application. When you deploy the EAR file or the unica.war file, ensure that the JDK source level of the JSP compiler is set to Java™ 17 for SDK 1.7 and 18 for SDK 1.8, and that JSP pages are precompiled according to the following information:
  • 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 17 for SDK 1.7 and set to 18 for SDK 1.8.

    If you deployed an EAR, set the JDK Source Level for each WAR file.

  • In step 8 of the Select Installation Options wizard, select UnicaPlatformDS as the matching Target Resource.
  • In step 10 of the Select Installation Options wizard, the context root must be set to /unica, all lower case.
• In the Web Container Settings > Web Container > Session Management section of the server, enable cookies. Specify a different session cookie name for each application that is deployed. Use one of the following procedures to specify a cookie name:
  • Select the Override session management check box under Session Management.

    If you deployed separate WAR files for your Unica products, in the WebSphere® console, in the Applications > Enterprise Applications > [deployed_application] > Session Management > Enable Cookies > Cookie Name section of the server, specify a unique session cookie name.

    If you deployed EAR files for your Unica products, in the WebSphere® console, in the Applications > Enterprise Applications > [deployed_application] > Module Management > [deployed_module] > Session Management > Enable Cookies > Cookie Name section of the server, specify a unique session cookie name.

  • If your installation must support non-ASCII characters, for example for Portuguese or for locales that require multi-byte characters, add the following arguments to Generic JVM Arguments at the server level:

    -Dfile.encoding=UTF-8

    -Dclient.encoding.override=UTF-8

    In case you are deploying a non-production setup, add

    -DENABLE_NON_PROD_MODE=true

    In case of a production setup, this Java option must be removed or set to false.

    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.

• In the Applications > Enterprise Applications section of the server, select the EAR file or WAR file that you deployed, then select Class loading and update detection and specify the following properties.
  • If you are deploying 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 are deploying 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.
• Start your deployment. If your instance of WebSphere® is configured to use a JVM version 1.7 or newer, complete the following steps to work around an issue with the time zone database.
  1. Stop WebSphere®.
  2. Download the Time Zone Update Utility for Java™ (JTZU).
  3. Follow the steps provided by the IBM® (JTZU) to update the time zone data in your JVM.
  4. Restart WebSphere®.
• In WebSphere Enterprise Applications, select Your Application > Manage Modules > Your Application > Class Loader Order > Classes loaded with local class loader first (parent last).
• The recommended minimum heap size for the basic functioning of the application is 512 and the recommended maximum heap size is 1024.
  Complete the following tasks to specify the heap size:

  1. In WebSphere® Enterprise Applications, select Servers > WebSphere application servers > server1 > Server Infrastructure > Java and Process Management > Process definition > Java Virtual Machine.
  2. Set the initial heap size to 512.
  3. Set the maximum heap size to 1024

  See the WebSphere® documentation for more information about sizing.

  For DB2, set progressiveStreaming = 2 in WebSphere console at following path: JDBC >Data sources > UnicaPlatformDS > Custom properties.