Deploying Unica Plan on WebLogic

Use the following guidelines for deploying Unica Plan on WebLogic.

About this task

  • Unica products customize the JVM used by WebLogic. You might create a WebLogic instance dedicated to Unica products if you encounter JVM-related errors.
  • Do not install more than one Unica Plan 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 Unica Plan to WebLogic:

Procedure

  1. If your operating system is AIX®, extract the Unica Plan 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.
  2. If you are configuring WebLogic to use the IIS plug-in, review the WebLogic documentation to determine whether you have additional requirements.
  3. 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_Unica_Home>\<Plan_Home>

      Where <HCL_Unica_Home> is the path to the top-level irectory and <Plan_Home> is the path to the directory where you installed Unica Plan. Typically this directory is HCL_Unica/Plan.

    • -Dfile.encoding=UTF-8
    • Make sure that the following JVM parameters are present. If not add them:
      • For version 12.1.0, 12.1.0.1, 12.1.0.2, and 12.1.0.3, add the following parameters:
        • -Dlog4j2.contextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector
        • -Dlog4j2.configurationFile=file:///<Plan_home>\conf\plan_log4j.xml (in case of fresh install of 12.1)
        • -Dlog4j.configurationFile=file:///<Plan_home>\conf\plan_log4j.xml (in case of fresh install of 12.1)
      • For version 12.1.0.4 or later, if you are installing, add the following parameters. If you are upgrading from version 12.1.0 or later, remove the parameters mentioned earlier, and add the following parameters:
        • -Dlog4j.configuration=file:///<Plan_home>\conf\plan_log4j_1x.xml
        • -Dplan.log4j.config=<Plan_home>\conf\plan_log4j.xml
        • -Dplan.log4j.async=true (If not set, deafults to true)
      Note:
      • For version 12.1.0, 12.1.0.1, 12.1.0.2, and 12.1.0.3, 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 and the -Dlog4j.configurationFile that has been deployed.
      • For version 12.1.0.4 or later, 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 -Dplan.log4j.config file that has been deployed.
      • For version 12.1.0, 12.1.0.1, 12.1.0.2, and 12.1.0.3, ensure that the xml file pointed by log4j2.configurationFile and log4j.configurationFile is the same and follows the log4j2 syntax. The file should contain the following two lines at the top:
         <?xml version="1.0" encoding="UTF-8"?>
<Configuration packages="com.unica.afc.logger" monitorInterval="60">
      • For version 12.1.0.4 or later, ensure that the xml file pointed by -Dplan.log4j.config file follows the log4j2 syntax. The file should contain the following two lines at the top:
         <?xml version="1.0" encoding="UTF-8"?>
<Configuration packages="com.unica.afc.logger" monitorInterval="60">
      • See the log4j2 documentation for details by referring to the link: https://logging.apache.org/log4j/2.0/manual/configuration.html
      • 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.
      Note:
      • 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.
  4. In the <Plan_home>/conf/ location, the 12.1.2 installer creates a back up of the existing files:
    File name before backup File name after backup
    plan_log4j.xml plan_log4j.xml_pre_12.1.2
    plan_log4j_client.xml plan_log4j_client.xml_pre_12.1.2
    plan_log4j_socket_server.xml plan_log4j_socket_server.xml_pre_12.1.2

    If the backed up files contain custom settings, you must ensure that the custom settings are copied to the newly added configuration files by the 12.1.2 installer.

  5. Save and close the file.
  6. Restart WebLogic.
  7. Deploy Unica Plan as a web application module: select plan.war.
  8. Start the deployed web application.

What to do next

WebLogic 12.2.1.3 blocks a few HTTP methods, for example DELETE and PATCH, which are used by REST API for the newly added Enhanced workflow. To resolve this issue, apply a WebLogic patch (if it is not applied).

For details about the patch, access https://support.oracle.com/knowledge/Middleware/2331453_1.html. You need to be a registered user to access the link. After sucessful authentication, search for the patch number 26923558.

Note: The information provided about the patch belongs to a third-party website. HCL Unica will not be responsible if the information is inaccurate.