Deploying Campaign on WAS from an EAR file

You can deploy the product by using an EAR file if you included Campaign.

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. Go to Applications > Application Types > WebSphere enterprise applications and click Install.
  3. In the Preparing for the application installation window, select the Detailed - Show all options and parameters check box and click Next.
  4. Click Continue to see the Install New Application wizard.
  5. 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 18.
    • In step 9 of the installation wizard, set the Context Root to /Campaign.
  6. In the left navigation panel of WebSphere® Integrated Solutions Console, navigate to Applications > Application Types > WebSphere enterprise applications.
  7. In the Enterprise Applications window, select the EAR file that you want to deploy.
  8. In the Web Module Properties section, click Session Management and select the following check boxes:
    • Override session management
    • Enable Cookies
  9. Click Enable Cookies, and in the Cookie name field, enter a unique cookie name.
  10. 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.
  11. In the Detail Properties section, select Class loading and update detection.
  12. In the Class loader order section, select the Classes loaded with parent class loader first option.
  13. In campaign.ear, open the Manage Modules section and select the Classes loaded with local class loader first (parent last) option.
  14. For WAR class loader policy, select the Class loader for each WAR file in application option.
  15. Go to Application Servers > your server > Process definition > Java Virtual Machine.
  16. Users can add the following JVM arguments to enable unicode support with this JVM.
    • -Dfile.encoding=UTF-8
    • -Dclient.encoding.override=UTF-8
  17. Start your deployment.
    Note: For Unica Campaign Websphere on HTTP and Unica Link (for native installation) on HTTPS, user need to set below parameters in Websphere JVM, SSL configuration and retrieve SSL certificates. To avoid problem "javax.net.ssl.SSLException: Received fatal alert: protocol_version"

    *JVM Arguments: -Dhttps.protocols=TLSv1.2 -Djdk.tls.client.protocols=TLSv1.2*

    **

    Set the protocol to TLSv1.2 from WAS admin console in below mentioned path and restart your Websphere Application Server.

    _SSL Certificate and Key management -> SSL configurations ->NodeDefaultSSLSetings ->Quality of protection(Qop) settings_

    *protocol: TLSv1.2*

    Retrieve the signer certificates from hip-rest server and add into NodeDefaultKeyStore and NodeDefaultTrustStore

    _*path: SSL certificate and key management > Key stores and certificates > NodeDefaultKeyStore > Signer certificates > Retrieve from port*_