WebSphere® guidelines

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

For complete information about WebSphere, see the links below:

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

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

Confirm that your version of WebSphere® meets the requirements that are described in the Recommended Software Environments and Minimum System Requirements document, including any necessary fix packs or upgrades.

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 find a field named resultSetHoldability, add a custom property with that name and set its value to 1.

Deploy the IBM® EAR file or 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 the correct version of Java™ and the 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, ensure that the JDK Source Level is set to 16. If 16 is not available, select 15.

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

Specify a different session cookie name for each deployed application. Use the procedure that is appropriate for your deployment, as follows.

If you deployed separate WAR files:

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 EAR files:

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 EAR file or WAR file that you deployed, then select Class loading and update detection and set the following General Properties on the Configuration tab:

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.

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.