Deploying Unica Centralized Offer Management on WebSphere

You can deploy the Unica Centralized Offer Management application from a WAR file or an EAR file on the WebSphere® Application Server (WAS).

Before you begin

Consider the following points before you deploy Unica Centralized Offer Management 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.
Note: Different versions of WebSphere® Application Server present user interface controls in varying sequences and with alternative labels.

About this task

Complete the following steps to set up the environment for deploying Unica Centralized Offer Management:

Procedure

  1. 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:
    • -DOFFER_HOME=<UNICA_HOME>\<Offer_Home>

      where <Unica_Home> is the path to the top-level HCL directory and <Offer_Home> is the path to the directory where you installed Unica Centralized Offer Management. Typically, this path is <UNICA_HOME>/CentralizedOffer.

    • For your installation to support non-ASCII characters, 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
    • For the Oracle database, set the following system property:
      -Doracle.jdbc.J2EE13Compliant=true
  2. Set the JSP Compilation level in the WebSphere application server to 18.

Deploying the WAR 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.

About this task

Complete the following steps to deploy the WAR or EAR file:

Procedure

  1. Select Applications > New Application > New Enterprise Application.
  2. On the initial form, select Remote file system and then Browse to the Offer.war file or your EAR file.
  3. On the next Preparing for the Application Installation window:
    • Select Detailed.
    • Select Generate Default Bindings.
    • Select Override existing bindings.
  4. On the Select Installation Options window, complete the following actions:
    • Select Precompile JavaServer Pages files.
    • For Application name, enter offer.
    • 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 window, select the Module. If you deployed an EAR, select every WAR file.
  6. On the Provide Options to Compile JSPs window, select the Web module. If you deployed an EAR, select every WAR file.
  7. Set the JDK Source Level to 18.
  8. On the JSP reloading options for Web modules form, select JSP enable class reloading and for JSP reload interval in seconds enter 5.
  9. On the Map shared libraries window, select the Application and the Module.
  10. On the Map shared library relationships window, select the Application and the Module.
  11. On the Map resource references to resources window, select the module and for Target Resource JNDI Name enter campaignPartition1DS.
  12. On the Map context roots for Web modules window, for Context Root enter /offer.
  13. Review and save your settings.

Defining class loader policy

Class loader policy defines how the application is configured on WAS. You must change some of the default settings on WAS before you deploy Unica Centralized Offer Management.

About this task

Complete the following steps to define the class loader policy:

Procedure

  1. On the Enterprise Applications > offer > Class loader, select Override class reloading settings for Web and EJB modules and provide an appropriate value for the Polling interval for updated files field.
  2. For Class loader order, select Classes loaded with local class loader first (parent last).
  3. Perform one of the following options depending on the file:
    • WAR: For WAR class loader policy, select Single class loader for application.
    • EAR: For WAR class loader policy, select Class loader for each WAR file in application.
  4. Click Apply and Save Settings.

Defining settings for cookies

You must define and set settings for cookies by using Session Management option on the Websphere Enterprise Applications.

About this task

Complete the following steps to define the settings for cookies:

Procedure

  1. Go to the Enterprise Applications > offer > Session management.
  2. Select Override session management.
  3. Select Enable cookies.
  4. Click Apply, then go to the Enterprise Applications > offer > Session management > Cookies.
  5. Change the Unica Centralized Offer Management Cookie name from JSESSIONID to OMSESSIONID.
  6. Click Apply and Save Settings.

Defining EAR module settings

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

About this task

Complete the following steps to define EAR file module settings:

Procedure

  1. Go to Enterprise Applications and select the EAR file.
  2. On the Manage Modules form, select one of the WAR files; for example, Offer.war.
  3. On the Enterprise Applications > EAR > Manage Modules > WAR form, complete the following sub-steps:
    1. Set Starting weight to 10000.
    2. For Class loader order, select Classes loaded with application class loader first.
  4. On the Enterprise Applications > EAR > Manage Modules > WAR > Session management, select Enable cookies.
  5. On the Enterprise Applications > EAR > Manage Modules > WAR > Session Management > Cookies, complete the following steps:
    1. Set the Cookie name to CMPJSESSIONID.
    2. For the Cookie maximum age, select Current browser session.
  6. On the Enterprise Applications > EAR > Manage Modules > WAR > Session management, enter the following information:
    1. Select Allow overflow.
    2. For Maximum in-memory sessions, enter 1000.
    3. 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 Offer.war.
    Note: If the Campaign.war file also exists in the EAR file and you plan to integrate Unica Centralized Offer Management with Unica Campaign, define the same settings for the Campaign.war file.