Deploying Distributed Marketing on WAS from an EAR file

You can deploy Distributed Marketing and Attribution Modeler by using an EAR file if you included Distributed Marketing and Attribution Modeler in an EAR file when you ran the IBM® Marketing Software installer.

Before you begin

  • Confirm that your version of WebSphere® meets the requirements in the Recommended Software Environments and Minimum System Requirements document, including any necessary fix packs or upgrades.
  • Confirm that you created the data sources and database provider in WebSphere.

Procedure

  1. Go to the WebSphere Integrated Solutions Console.
  2. Complete the following steps, if your system tables are in DB2®:
    1. Click the data source that you created. Go to the Custom Properties for the data source.
    2. Select the Custom properties link.
    3. Set the value for the resultSetHoldability property to 1.

      If you do not see the resultSetHoldability property, create the resultSetHoldability property and set its value to 1.

  3. Go to Applications > Application Types > WebSphere enterprise applications and click Install.
  4. In the Preparing for the application installation window, select the Detailed - Show all options and parameters check box and click Next.
  5. Click Continue to see the Install New Application wizard.
  6. Accept the default settings on the windows of the Install New Application wizard except the following windows:
    • In step 1 of the Install New Application wizard, select the Precompile JavaServer Pages files check box.
    • In step 3 of the installation wizard, set the JDK Source Level to 17.
    • In step 8 of the installation wizard, set the Context Root to /Campaign.
  7. In the left navigation panel of WebSphere Integrated Solutions Console, navigate to Applications > Application Types > WebSphere enterprise applications.
  8. In the Enterprise Applications window, select the EAR file that you want to deploy.
  9. In the Web Module Properties section, click Session Management and select the following check boxes:
    • Override session management
    • Enable Cookies
  10. Click Enable Cookies, and in the Cookie name field, enter a unique cookie name.
  11. If you are using version 8 of WebSphere Application Server, select Servers > WebSphere application server > server 1 > Session management > Enable Cookies and clear the check box for Set session cookies to HTTPOnly to help prevent cross-site scripting attacks.
  12. In the Detail Properties section, select Class loading and update detection.
  13. In the Class loader order section, select the Classes loaded with local class loader first (parent last) option.
  14. In campaign.ear, open the Manage Modules section and select the Classes loaded with local class loader first (parent last) option.
  15. In Websphere Enterprise Applications, select Your Application > Manage Modules > Your Application > Class Loader Order > Classes loaded with local class loader first (parent last).
  16. For WAR class loader policy, select the Single class loader for application option.
  17. Go to Application Servers > your server > Process definition > Java Virtual Machine.
  18. In the Generic JVM arguments section, enter the following JVM arguments:
    -Dcom.ibm.websphere.webservices.DisableIBMJAXWSEngine=true
-Dibm.cl.verbose=PersistenceProvider
-Dibm.cl.verbose=PersistenceProviderImpl
-agentlib:getClasses -verbose:dynload
-Dcom.ibm.xml.xlxp.jaxb.opti.level=3
  19. Start your deployment.

    For more information about WebSphere Application Server version 8.5, see Welcome to the WebSphere Application Server information center.