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.
-
Please follow the below steps while deploying Campaign.war file on
HCL Websphere Application Server 8.5.5.x Fix Pack 9 or below versions
a) Go to <app_server_install_directory>/properties location
Example: /data/webservers/HCL/WebSphere8.5.5/properties
b) Edit "amm.filter.properties" file to include "com.thoughtworks.xstream"
Example:
Ignore-Scanning-Packages = javassist, \
org.antlr, \
org.apache.avalon, \
org.apache.batik, \
org.apache.bcel, \
org.apache.commons, \
org.apache.log4j, \
org.apache.poi, \
org.apache.regexp, \
org.apache.xalan, \
org.apache.xerces, \
org.apache.xml, \
org.apache.xpath, \
org.ajax4jsf, \
org.dbunit, \
org.richfaces, \
org.jboss.el, \
org.jchrontab, \
org.omg, \
org.seasar, \
org.slf4j, \
com.thoughtworks.xstream
By doing this, WebSphere will disable the annotation scanning for the xstream jar
and allow the application deployed properly.
This is also mentioned in here http://x-stream.github.io/faq.html
This steps are not required for Websphere version 8.5.0.x or 8.5.5 Fix Pack 10 or higher.
Procedure
-
Go to the WebSphere Integrated Solutions
Console.
-
Complete the following steps if your system tables are in DB2®:
-
Click the data source that you created. Go to the Custom Properties for the data source.
-
Select the Custom properties link.
-
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.
-
Go to and click Install.
-
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
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.
-
In the left navigation panel of WebSphere
Integrated Solutions Console, navigate to .
-
In the Enterprise Applications window, click the unica.war file.
-
In the Enterprise Applications window, click the collaborate.war
file.
-
In the Enterprise Applications window, click the Campaign.war file.
-
In the Enterprise Applications window, click the detect.war file.
-
In the Enterprise Applications window, click the InteractRT.war
file.
-
In the Enterprise Applications window, click the ih.war file to deploy
Interaction History, and click the
am.war file to deploy Attribution Modeler.
-
In the Enterprise Applications window, click the plan.war file.
-
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 Applications > Enterprise Applications section of the server,
select the WAR file that you deployed.
-
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 the Modules section, select Manage modules > detect, and under Class loader order select the Classes loaded with local class loader first (parent last) option.
-
Enter the context root for the application as /collaborate.
-
In the WAR class loader policy section, select the Single
class loader for application option.
-
To deploy Interact, select . For Class loader order, select Classes loaded with
local class loader first (parent last) in Manage Modules. To
deploy Attribution Modeler, select . For Class loader order, select Classes loaded with
local class loader first (parent last) in Manage Modules.
-
For WAR class loader policy, select Single class loader for application.
-
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
-
Start your deployment.