BX Framework(BXM) Center-Cut Processing Service Instance WAS Environment Configuration

Install a dedicated tomcat for the BX Framework(BXM) Center-Cut processing service instance.
For the tomcat installation location, use a directory named tomcat9_centercut02 at the same level as $BXM_HOME.

To use the Center-Cut of BX Framework(BXM), configure the classpath, Datasource, Service port, and Context for the BXM library in Tomcat.

Configure the classpath for the BXM library.
- Move to the tomcat9_centercut02/conf directory.
  
  Add the classpath for the BXM library to the common.loader entry in catalina.properties.
  
  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,<<BXM_HOME>>/lib/jta/*.jar
Modify BXM_HOME to the path where BX Framework(BXM) is installed.

Configure the Datasource to be used by BX Framework Center-Cut and the Application.

Move to the tomcat9_centercut02/conf directory.
Modify server.xml and add the datasource configuration.

Two types of Datasource are required for BXM Framework and the Application: NonXA and XA.

BXMNXA : NonXA Datasource name used by BXM Framework

APPNXA : NonXA Datasource name used by the Application

APPXA : XA Datasource name used by the Application

The added configuration is as follows:

<GlobalNamingResources>
    <Resource type="javax.sql.DataSource"
                name="BXMNXA"
                auth="Container"
                maxActive="20"
                minIdle="1"
                maxIdle="1"
                maxWait="10000"
                factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
                driverClassName="oracle.jdbc.OracleDriver"
                url="<<DB JDBC URL>>"
                username="bxm"
                password="<<bxm account password>>"
         />
    <Resource type="javax.sql.DataSource"
                name="APPNXA"
                auth="Container"
                maxActive="20"
                minIdle="1"
                maxIdle="1"
                maxWait="10000"
                factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
                driverClassName="oracle.jdbc.OracleDriver"
                url="<<DB JDBC URL>>"
                username="bxm"
                password="<<bxm account password>>"
         />
    <Resource
                name="APPXA"
                auth="Container"
                type="com.atomikos.jdbc.AtomikosDataSourceBean"
                factory="com.atomikos.tomcat.EnhancedTomcatAtomikosBeanFactory"
                uniqueResourceName="APPXA"
                maxPoolSize="20"
                minPoolSize="1"
                xaDataSourceClassName="oracle.jdbc.xa.client.OracleXADataSource"
                xaProperties.databaseName="<<oracle sid>>"
                xaProperties.serverName="<<db server ip>>"
                xaProperties.portNumber="<<oracle port>>"
                xaProperties.user="bxm"
                xaProperties.password="<<bxm account password>>"
                xaProperties.URL="<<DB JDBC URL>>"
        />
</GlobalNamingResources>

Modify the <<…>> parts and the pool configuration values (such as maxActive, minIdle) to appropriate values for the user environment.

Configure the HTTP service port used by the cc service endpoint.
- Move to the tomcat9_centercut02/conf directory.
Modify server.xml to adjust the service port settings.
- The added configuration is as follows:
  
  <Connector port="28081" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" />
  
  The value specified in port is an example in this document and can be modified to an appropriate value for the user environment.

Configure the cc service endpoint web application context environment.

Move to the tomcat9_centercut02/conf directory.

Modify context.xml.

The added configuration is as follows:

<Context reloadable = "false">
    <ResourceLink global="BXMNXA" name="BXMNXA" type="javax.sql.DataSource"/>
    <ResourceLink global="APPNXA" name="APPNXA" type="javax.sql.DataSource"/>
    <ResourceLink global="APPXA" name="APPXA" type="com.atomikos.jdbc.AtomikosDataSourceBean"/>

    <Transaction factory="com.atomikos.icatch.jta.UserTransactionFactory" />
    <Resource name="TransactionManager"
            auth="Container"
            type="com.atomikos.icatch.jta.UserTransactionManager"
            factory="org.apache.naming.factory.BeanFactory"
            />
</Context>

The values specified in ResourceLink are examples in this document and can be modified to appropriate values for the user environment.

Use the values specified for Transaction and Resource as they are, and only users familiar with the Transaction Manager (atomikos) may modify them to appropriate values for the user environment.

Configure the JVM options for the cc service endpoint tomcat instance.
- Move to the tomcat9_centercut02/bin directory.
  
  Modify setenv.sh.
- The added configuration is as follows:
  
  if [ "$1" = "start" ] ; then JAVA_OPTS="$JAVA_OPTS -Dbxm.node.name=DFT1 -Dbxm.instance.name=Emerald_ccProc01" #Add only when using Tomcat. JAVA_OPTS="$JAVA_OPTS -Dcom.atomikos.icatch.file=<<BXM_HOME>>/lib/deps/jta.properties" JAVA_OPTS="$JAVA_OPTS –Xms1024m –Xmx1024m -XX:MaxPermSize=256m" fi
  
  Assign a unique value for each host where BX Framework(BXM) is installed to the bxm.node.name value. When multiple servers exist, configure it so that it does not overlap.
  
  Ensure that the bxm.instance.name value does not overlap between tomcat instances.
  
  JVM memory settings (Xms, Xmx, MaxPermSize) must be modified to appropriate values for the user environment.
  
  << BXM_HOME >> must be modified to the directory where BX Framework(BXM) is installed.