Use the following guidelines for deploying Marketing Operations on
WebLogic.
About this task
- HCL® Marketing
Software products
customize the JVM used by WebLogic. You might create a WebLogic instance
dedicated to HCL Marketing
Software products
if you encounter JVM-related errors.
- Do not install more than one Marketing Operations application
under the same WebLogic domain.
- Verify that the Software Developement Kit (SDK) selected for the
WebLogic domain you are using is the Sun SDK by looking in the startup
script (startWebLogic.cmd) for the JAVA_VENDOR
variable. It should be set to JAVA_VENDOR=Sun.
If it is set to JAVA_VENDOR=BEA, JRockit has
been selected. JRockit is not supported. To change the selected SDK,
refer to the WebLogic documentation.
Complete the following steps to deploy Marketing Operations to
WebLogic:
Procedure
- If your operating system is AIX®,
extract the Marketing Operations WAR file,
delete the xercesImpl.jar file from WEB_INF/lib directory,
and recreate the WAR file.
If the
installer combined products in an EAR file,
you must first extract that file to obtain the WAR file,
and you must recreate the EAR file.
- If you are configuring WebLogic to use the IIS plug-in,
review the WebLogic documentation to determine whether you have additional
requirements.
- From the bin directory under your
WebLogic domain directory, locate and open the setDomainEnv script
in a text editor. Scroll to the JAVA_OPTIONS property,
and add the following entries. Use a space to separate entries.
-Dplan.home=<HCL_IMS_Home>\<MarketingOperations_Home>
Where <HCL_IMS_Home> is the path to the top-level
HCL
directory and
<MarketingOperations_Home> is the path to the directory
where you installed Marketing Operations. Typically
this directory is HCL_IMS/MarketingOperations.
- -Dfile.encoding=UTF-8
- Make sure that the following JVM parameters are present. If not add them:
- -Dlog4j2.contextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector
- -Dlog4j2.configurationFile=file:///<Plan_home>\conf\plan_log4j_11.1.xml
- -Dlog4j.configuration=file:/// <Plan_home>\conf\plan_log4j_1x.xml
Note:
- In case of upgrade and fast upgrade, if there is a plan_log4j_11.1.0.0.xml file apart from the
plan_log4j.xml, use the plan_log4j_11.1.0.0.xml.
- In the -Dlog4j2.configurationFile=file:///<Plan_home>\conf\plan_log4j_11.1.xml setting, if you
have customized the plan_log4j.xml and made some changes to suit your organization, then ensure that
you make those settings in the plan_log4j.xml specified here as per the -Dlog4j2.configurationFile
that we have deployed to you now. If you have used the plan_log4j_11.1.0.0.xml file, make your changes in
that file.
- In Windows, the file path contains a back slash. Whereas, in UNIX, it must contain a forward
slash.
- The path separator in the log4j configuration file name should be set as Windows style() or UNIX
(/ ) style based on the underlying operating system.
- Save and close the file.
- Restart WebLogic.
- Deploy Marketing Operations as
a web application module: select plan.war.
- Start the deployed web application.