Guidelines for deploying Unica Journey on WebSphere
You must follow a set of guidelines when you deploy Unica Journey on WebSphere.
Make sure that the version of WebSphere® meets the requirements as described in the Recommended Software Environments and Minimum System Requirements document, including fix packs (if necessary). Following are the guidelines for deploying Unica Journey on WebSphere®:
- Deploy the journey.war File as an enterprise application. When you deploy the
journey.war file, ensure that the JDK source level of the JSP compiler is set to
Java 18 for SDK 1.8 and the JSP pages are precompiled as per the following
information:
- In the form where you browse and select the WAR file, select Show me all installation options and parameters, so that the Select Installation Options wizard runs.
- In step 1 of the Select Installation Options wizard, select Precompile JavaServer Page files.
- In step 3 of the Select Installation Options wizard, ensure that the JDK Source Level is set to 18 for SDK 1.8.
- In step 8 of the Select Installation Options wizard, select JourneyDS as the matching Target Resource.
- In step 10 of the Select Installation Options
wizard, the context root must be set to /journey,
(all lower case).
- Click on Finish and wait for the Application to be installed.
- In WebSphere Enterprise Applications, select Your Application ex: journey.war
- 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 under Applications > Enterprise Applications > [deployed_application] > Session Management > Enable Cookies > Cookie Name section of the server, then 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
Add the Journey Web Home path variable like below where we used to put properties & config folder:
-Djourney.web.home=<Journeys_Home>/Web/
In case of a production setup, this Java option must be removed or set to
false
.Navigation tip: Select
.
Additional Details:
- In the Class loading and update detection and specify the following properties. section of the server, select the WAR file that you deployed, then select
- In the 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.
section of the server, select the EAR file or WAR file that you
deployed, then select - If you are deploying a WAR file:
- In WebSphere Enterprise Applications, select .
- 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:
- In WebSphere® Enterprise Applications, select .
- Set the initial heap size to 512.
- Set the maximum heap size to 1024
- Click Servers > Server Types > Application Servers, and select the server initially created.
- Click Web Container Settings > Web container.
- Click Custom properties.
- Click New.
- Enter the property values:
Property Value Name com.ibm.ws.webcontainer.invokeFlushAfterService Value False Description See http://www.ibm.com/support/docview.wss?uid=swg1PM50111 - Click OK.
- Click Save.
In case if need how to import SSL certificate then following URL will help: https://www.ibm.com/support/knowledgecenter/en/SSEKCU_1.1.2.1/com.ibm.psc.doc/rs_original/installer/rs_t_import_client_cert_was.html
- Go to WAS profile location used for Journey installation. For example /data/webservers/IBM/WebSphere85_ND/profiles/UMP9111
- There you will see two folders tmp and wstemp.
- Delete the contents of these two folders.
- Restart WebSphereNote: Once platform starts successfully then we need to start Journey application manually in Websphere server.
- Start your deployment for journey.war (Journey Application).