Deploying Collaborate on WAS from an EAR file
You can deploy Collaborate by using an EAR file if you included Collaborate in an EAR file when you ran the HCL Unica 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
- Go to the WebSphere® Integrated Solutions Console.
-
Complete the following steps, if your system tables are in DB2®:
- Go to Install. and click
- In the Preparing for the application installation window, select the Detailed - Show all options and parameters check box and click Next.
- Click Continue to see the Install New Application wizard.
- 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 8 of the installation wizard, set the Context Root to /collaborate.
- In the left navigation panel of WebSphere® Integrated Solutions Console, navigate to .
- In the Enterprise Applications window, select the EAR file that you want to deploy.
- In the Web Module Properties section,
click Session Management and select the following
check boxes:
- Override session management
- Enable Cookies
- Click Enable Cookies, and in the Cookie name field, enter a unique cookie name.
- If you are using version 8 of WebSphere® Application Server, select and clear the check box for Set session cookies to HTTPOnly to help prevent cross-site scripting attacks.
- In the Detail Properties section, select Class loading and update detection.
- In the Class loader order section, select the Classes loaded with local class loader first (parent last) option.
- In Collaborate.ear, open the Manage Modules section and select the Classes loaded with local class loader first (parent last) option.
- For WAR class loader policy, select the Class loader for each WAR file in application option.
- In Websphere Enterprise Applications, select .
- Go to .
-
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
For more information about WebSphere® Application Server version 8.5, see Welcome to the WebSphere® Application Server information center.