Configuring application servers for Cloud Native Unica

You must perform additional configurations on JBoss and WebLogic.

Configuring JBoss for Cloud Native Unica

To use JBoss with Cloud Native Unica, complete the following steps:

Procedure

  1. Open the file common-configMap.yaml. To locate the file, access the JBOSSOracle/unica/templates/ location.
  2. For the _JBOSS_ZIP_LOCATION parameter, provide the folder name, residing within the HOME folder, containing the JBoss installation ZIP file. For example, /docker/unica/JBossZip/JBOSS.Zip.
  3. For the _JBOSS_ZIP_NAME_ parameter, provide the name of the JBoss installer ZIP file. For example, jboss-eap-7.1.0.zip.
  4. For the _DEST_JBOSS_UNZIP_LOCATION_ parameter, provide the absolute directory location where you want to install JBoss. For example, if you want to install JBoss inside the container, provide the value /opt. If you want to install JBoss in a mapped shared folder, provide the value /docker/unica.
  5. For the _DEST_UNZIP_FOLDER_ parameter, provide a folder name that contains the unzipped contents of the JBoss installer ZIP file. For example, if the ZIP file is jboss-eap-7.1.0.zip and the folder within the ZIP file is jBoss710, provide the value jBoss710.

Results

Completing the earlier mentioned configuration will automatically install JBoss and the required Unica component.

Configuring WebLogic for Cloud Native Unica

Your system should have WebLogic installed to use it with Cloud Native Unica. Cloud Native Unica uses the utilities from WebLogic to create a domain for the required Unica component.

About this task

To use WebLogic with Cloud Native Unica, complete the following steps:

Procedure

  1. For the JAVA_HOME_WEBLOGIC parameter, WebLogic requires Oracle JDK. The value of this setting is the HOME location of the JDK used for the existing WebLogic installation. For example, /docker/unica/jdk18_oracle.
  2. For the WLS_HOME_DIR parameter, provide the home directory of the WebLogic server installation. For example, /docker/unica/oracle_products/middleware/wlse.
  3. For the WLS_DOMAIN_LOCATION parameter, provide the fully qualified path of the directory under which the domains for the products will be created. For example, /docker/unica/wlsdomains.
    CAUTION: The creation of a new pod creates a directory for the domain of that Pod. If you discard a pod, the directory is not deleted automatically. You should delete such directories as they consume a lot of disk space.