Deploying Interact and Attribution Modeler on WAS from a WAR file

You can deploy the Interact and Attribution Modeler application from a WAR file on WAS.

Before you begin

Complete the following tasks before you deploy Interact and Attribution Modeler:

  • 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 9 of the installation wizard, set the Context Root to /Campaign.
    • In step 8 of the installation wizard, set the Context Root to /interact.
  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, click the unica.war file.
  9. In the Enterprise Applications window, click the collaborate.war file.
  10. In the Enterprise Applications window, click the Campaign.war file.
  11. In the Enterprise Applications window, click the detect.war file.
  12. In the Enterprise Applications window, click the InteractRT.war file.
  13. In the Enterprise Applications window, click the ih.war file to deploy Interaction History, and click the am.war file to deploy Attribution Modeler.
  14. In the Enterprise Applications window, click the plan.war file.
  15. In the Web Module Properties section, click Session Management and select the following check boxes:
    • Override session management
    • Enable Cookies
  16. Click Enable Cookies, and in the Cookie name field, enter a unique cookie name.
  17. 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.
  18. In the Applications > Enterprise Applications section of the server, select the WAR file that you deployed.
  19. In the Detail Properties section, select Class loading and update detection.
  20. In the Class loader order section, select the Classes loaded with local class loader first (parent last) option.
  21. In the Modules section, select Manage modules > detect, and under Class loader order select the Classes loaded with local class loader first (parent last) option.
  22. Enter the context root for the application as /collaborate.
  23. In the WAR class loader policy section, select the Single class loader for application option.
  24. To deploy Interact, select ih > Manage Modules > ih.war > Class loader order. For Class loader order, select Classes loaded with local class loader first (parent last) in Manage Modules. To deploy Attribution Modeler, select am > Manage Modules > am.war > Class loader order. For Class loader order, select Classes loaded with local class loader first (parent last) in Manage Modules.
  25. For WAR class loader policy, select Single class loader for application.
  26. Go to Application Servers > your server > Process definition > Java Virtual Machine.
  27. 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
  28. Start your deployment.