The Marketing Operations database must be on a machine that is accessible to all machines in the cluster, but it does not need to be on a machine in the cluster.

Share the top-level directory in which Marketing Operations is installed. For example, say that Marketing Operations is installed in C:\MktOpsCluster\IBM_EMM\MarketingOperations. In this case, you would share the entire MktOpsCluster directory.

Create and share a folder on the administration server to contain the upload files for Marketing Operations. This folder is known as the Shared_UMO_Artifacts folder. All cluster members must have full control (read, write, change, and delete) of this folder. Placing this folder below the IBM® home directory in the local file system hierarchy is optional.

-Dplan.local.log.dir=local_log_dir (where local_log_dir is the writeable folder on the physical machine where Marketing Operations creates logs)

To use a different plan_ehcache.xml file in place of the default file defined in the CONF directory for a node, set the -plan_ehcache parameter for that node to specify the location of the file.

For IBM® Marketing Operations to work effectively in a clustered environment, users must remain on a single node for their entire session. This option for session management and load balancing is known as session affinity. For more information on configuring your installation to use session affinity, refer to the documentation for your application server.

Log in to Marketing Operations, select Settings > Configuration, and configure the following URL parameters so that all references to the Marketing Operations server use the proxy host and port.