Installing WAS for ondemand batch

※ 1 : The use of WAS for ondemand batch is not recommended for the following reasons:

If an OOM(OutOfMemory) error occurs while a batch is running, it affects other batches that are running.
Since the Hot Deploy function is not provided, there are difficulties in startup and deployment.
It is executed by an Http Request, not by Shell execution, so it is difficult to link with a Job Scheduler.

※ 2 : When WAS for ondemand batch is used

When the resources of the batch server are insufficient

The installation location of Tomcat should be at the same level directory as $BXM_HOME, and use tomcat9_batch.
Example) If $BXM_HOME is /home/bxmv5/bxm, install it in /home/bxmv5/tomcat9_batch.
1. classpath settings
  1. Open tomcat9_batch/conf/catalina.properties.
  2. Find the common.loader entry and add the classpath for the BXM libraries as follows. At this time, modify BXM HOME to the path where BXM is installed.
    
    ... common.loader=${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jar,<<BXM_HOME>>/lib/bxm/*.jar,<<BXM_HOME>>/lib/deps/*.jar,<<BXM_HOME>>/lib/ext/*.jar ...
2. Datasource settings
  1. For ondemand batch, there is no need to configure a DataSource in Tomcat.
3. Service port settings
  1. Open tomcat9_batch/conf/server.xml.
  2. Find the Connector entry and change the port. The value specified in port is an example given in this document and can be modified to an appropriate value according to the user environment.
    
    ... <Connector port="8100" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" /> ...
  3. Since the AJP Connector is not used, find the AJP Connector entry and comment it out as shown below to prevent port conflicts.
    
    ...   ...
  4. Change the Tomcat shutdown port so that it does not conflict with other instances. The value specified in port is an example given in this document and can be modified according to the user environment.
    
    ... <Server port="8006" shutdown="SHUTDOWN"> <Listener className="org.apache.catalina.startup.VersionLoggerListener" /> ...
4. JVM option settings
  1. Open tomcat9_batch/bin/setenv.sh.
    
    If this file does not exist, create a new one.
  2. Add the following content. At this time, modify BXM HOME to the directory where BXM is installed. However, the value of bxm.node.name must be unique for each host where BXM is installed and must not be duplicated between servers. Also, bxm.instance.name must not be duplicated between Tomcat instances.
    
    if [ "$1" = "start" ] ; then JAVA_OPTS="$JAVA_OPTS -Dbxm.node.name=DFT1 -Dbxm.instance.name=ondbat1" JAVA_OPTS="$JAVA_OPTS -Dlog.level.layer.file=<<BXM HOME>>/batch/batchServiceEndpoint/WEB-INF/classes/logLayer.properties" JAVA_OPTS="$JAVA_OPTS -Dlogback.configurationFile=<<BXM HOME>>/batch/batchServiceEndpoint/WEB-INF/classes/logback.xml" #Add only when using Tomcat. JAVA_OPTS="$JAVA_OPTS -Xms1024m -XmX1024m -XX:MaxPermSize=256m" #OJDBC7 AutoCommit Error validate option false JAVA_OPTS="$JAVA_OPTS -Doracle.jdbc.autoCommitSpecCompliant=false" fi