Deploying Marketing Operations on Websphere
You can deploy the Marketing Operations application from a WAR file or an EAR file on the WebSphere® Application Server (WAS).
Consider the following points before you deploy Marketing Operations on Websphere:
*
Verify 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.
*
You use the WebSphere® Integrated Solutions console to configure your WebSphere® Application Server. The steps that follow provide guidance for setting specific controls.
*
Different versions of WebSphere® Application Server present user interface controls in varying sequences and with alternative labels.
Complete the following steps to set up the environment for deploying Marketing Operations:
1.
Define a custom property: On the Application servers > <servers> > Web container > Custom properties form, click New and enter following values:
*
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 fields:
a.
For Implementation type, select Connection pool data source.
b.
Specify the native library path of the database driver JAR file on your server.
For example, db2jcc4.jar/ojdbc6.jar/sqljdbc4.jar.
3.
Create the data source: On the Resources > JDBC > Data sources form, click New. Complete the Create a data source wizard by completing the following actions:
a.
Specify a data source name.
b.
For JNDI name, enter plands.
c.
Select the JDBC provider that you created in step 2.
d.
Specify the database name and server name.
e.
For Mapping-configuration alias select WSLogin.
4.
Define custom properties for the data source: On the JDBC providers > <database provider> > Data sources > 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
Copyright IBM Corporation 2014. All Rights Reserved.