Guidelines for deploying Marketing Operations on WebSphere®

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

You use the WebSphere® Integrated Solutions Console to configure your WebSphere® application server. The steps that follow provide guidance for setting specific controls.

Different WebSphere® versions present user interface controls in varying sequences and with alternative labels.

Set up the environment

1.	Define a custom property: On the Application servers > <server> > Web container > Custom properties form, click New and enter:

Name: com.ibm.ws.webcontainer.invokefilterscompatibility

Value: true

2.	Create the JDBC provider: On the Resources > JDBC > JDBC providers form, click New. Complete the Create a new JDBC provider wizard, including the following.

For Implementation type, select Connection pool data source.

Specify the location of the ojdbc6.jar file on your server.

Specify the Native library path on your server.

3.	Create the data source: On the Resources > JDBC > Data sources form, click New. Complete the Create a data source wizard, including the following.

Specify a Data source name.

For JNDI name, enter plands.

Select the JDBC provider that you created in step 2.

Specify the Database name and Server name.

For Mapping-configuration alias select WSLogin.

4.	Define custom properties for the data source: On the JDBC providers > <database provider> > Data sources > <plan> > Custom properties form, click New to add two properties:

Name: User

Value: <user name>

Name: Password

Value: <password>

If your Marketing Operations system tables are in DB2®, locate the resultSetHoldability property and set its value to 1. If this property does not exist, add it.

5.	Configure the JVM: On the Application servers > <server> > Process definition > Java Virtual Machine form, identify the Classpath then add the following entries as Generic JVM arguments, separated by a space:

-Dplan.home=<IBM_EMM_Home>\<MarketingOperations_Home>

where <IBM_EMM_Home> is the path to the top-level IBM® directory and <MarketingOperations_Home> is the path to the directory where you installed Marketing Operations. Typically this path is IBM_EMM/MarketingOperations.

-Dclient.encoding.override=UTF-8

Deploy the WAR or EAR file

When you deploy a new enterprise application, the WebSphere® Integrated Solutions Console presents a series of forms. The steps that follow provide guidance for setting specific controls on these forms. Different versions of WebSphere® can present controls in another sequence or with other labels.

1.	Select Applications > New Application > New Enterprise Application.

2.	On the initial form, select Remote file system and then Browse to the plan.war file or your EAR file.

3.	On the next Preparing for the application installation form:

Select Detailed.

Select Generate Default Bindings.

Select Override existing bindings.

4.	On the Select installation options form:

Select Precompile JavaServer Pages files.

For Application name, enter plan.

Select Override class reloading settings for Web and EJB modules.

For Reload interval in seconds, enter an integer such as 4.

5.	On the Map modules to servers form, select the Module. If you deployed an EAR, select every WAR file.

6.	On the Provide options to compile JSPs form, select the Web module. If you deployed an EAR, select every WAR file.

If you are using WebSphere® 7.5, set the JDK Source Level to 15.

If you are using WebSphere® 8, set the JDK Source Level to 16.

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

7.	On the JSP reloading options for Web modules form, select JSP enable class reloading and for JSP reload interval in seconds enter 5.

8.	On the Map shared libraries form, select the Application and the Module.

9.	On the Map shared library relationships form, select the Application and the Module.

10.	On the Map resource references to resources form, for Target Resource JNDI Name enter plands.

11.	On the Map context roots for Web modules form, for Context Root enter /plan.

12.	Review and save your settings.

Define the class loader policy

1.	On the Enterprise Applications > plan > Class loader form, select Override class reloading settings for Web and EJB modules.

2.	For Class loader order, select Classes loaded with local class loader first (parent last).

3.	For WAR class loader policy, select Single class loader for application.

4.	Click Apply.

Define settings for cookies

1.	Go to the Enterprise Applications > plan > Session management form.

2.	Select Override session management.

3.	Select Enable cookies.

4.	Click Apply, then go to the Enterprise Applications > plan > Session management > Cookies form.

5.	Change the Marketing Operations Cookie name from JSESSIONID to UMOSESSIONID.

6.	Click Apply.

Define EAR module settings (optional)

If you deployed an EAR, you must define settings for the individual WAR files contained by the EAR.

1.	Go to Enterprise Applications and select the EAR file.

2.	On the Manage Modules form, select one of the WAR files; for example, Campaign.war.

3.	On the Enterprise Applications > EAR > Manage Modules > WAR form:

Set Starting weight to 10000.

For Class loader order, select Classes loaded with application class loader first.

4.	On the Enterprise Applications > EAR > Manage Modules > WAR > Session management form, select Enable cookies.

5.	On the Enterprise Applications > EAR > Manage Modules > WAR > Session management > Cookies form:

Set the Cookie name to CMPJSESSIONID.

For the Cookie maximum age, select Current browser session.

6.	On the Enterprise Applications > EAR > Manage Modules > WAR > Session management form:

Select Allow overflow.

For Maximum in-memory sessions, enter 1000.

For Session timeout, select Set timeout and enter 30.

7.	Define the same settings for each of the other WAR files, including unica.war and plan.war.