Guidelines for deploying Unica Journey on JBoss
V12.1 Fixpack 4 onwards we can deploy Unica Journey on JBoss. You must follow a set of guidelines when you deploy Unica Journey on JBoss.
Make sure that the version of JBoss meets the requirements that are described in the HCL Enterprise Products Recommended Software Environments and Minimum System Requirements document. Use the following guidelines when you deploy Unica Journey on JBoss:
Use the following guidelines when you deploy the Unica Journey products on any supported version of JBoss:
- Deploy the HCL EAR file or the unica.war file as an enterprise
application.
For example: deploy <Journey_Install>\unica.war
See https://docs.jboss.org/jbossweb/3.0.x/deployer-howto.html for instructions on Deploying Web Server Application in JBoss.
- Complete the following tasks if your installation must support non-ASCII
characters, for example for Portuguese or for locales that require multi-byte
characters:
- Edit the
standalone.conf
script in the bin directory under your JBOSS /bin directory to add-Dfile.encoding=UTF-8
-Dclient.encoding.override=UTF-8
to-Djboss.as.management.blocking.timeout=3600
JAVA_VENDOR
.In case you are deploying a non-production setup, add
-DENABLE_NON_PROD_MODE=true
In case of a production setup, this Java option must be removed or set to
false
. - Restart JBoss server.
- Edit the
- To ensure that the Scheduler works correctly, complete the following
substeps.
- Take a backup of <JBOSS_HOME>/standalone/configuration/standalone.xml file.
- In <JBOSS_HOME>/standalone/configuration/standalone.xml, search the
module name for
driver.
<driver name="oracledriver" module="oracle.jdbc"> <xa-datasource-class>oracle.jdbc.OracleDriver</xa-datasource-class> </driver>
- Installer will not update the datasources, so you need to manually configure the datasources.
- Add the following statement underneath
<subsystem xmlns="urn:jboss:domain:ee:4.0">
to make the module name global.<global-modules> <module name="oracle.jdbc"/> </global-modules>
- Edit the
standalone.conf
script in the bin directory under your JBOSS /bin directory to addDlog4j.configuration
=file:///<Drive_loc>\Campaign_git_repo\AffiniumWebApps\Campaign\conf\campaign_log4j.properties - Restart JBOSS server.
- The log file name for log4j 1.x related to Journey logging in Campaign
is
"
log4j.appender.FILE.File=${CAMPAIGN_HOME}/logs/campaignweb_unicacommon_1x.log
" in campaign_log4j.properties.