Online Instance Installation

Install $BXM_HOME/online/serviceEndpoint on WAS by choosing one of the two methods below.

Create a symbolic link

This guide proceeds under the assumption that a symbolic link is configured.
```
ln -s $BXM_HOME/online/serviceEndpoint $BXM_HOME/../tomcat9_online/webapps/serviceEndpoint
```

Or copy $BXM_HOME/online/serviceEndpoint

If you copy it, you must modify the configuration path defined in the guide to the copied path.

cp -R $BXM_HOME/online/serviceEndpoint $BXM_HOME/../tomcat9_online/webapps/serviceEndpoint

BXM online instance environment file list
File name	File location	Remarks
web.xml	serviceEndpoint/WEB-INF/	web context configuration file
bxm-management-instance.xml	serviceEndpoint/WEB-INF/ classes	BXM instance configuration file
logback.xml		logback configuration file (used by BXM)
commons-logging.properties		common logging configuration file (used by Spring)
logLayer.properties		File for configuring system, DB, and job log level
module.properties		Module test configuration file

BXM online instance configuration

Open tomcat9_online/webapps/serviceEndpoint/WEB-INF/classes/logback.xml.

Find the property item below and change BXM_HOME to the BXM installation directory. For the log level, it is recommended to use debug in development and info in production.

...

<property name="LOGS_ABSOLUTE_PATH" value="<<BXM HOME>>/bxm/logs" />

...

Since the applogdb appender stores logs in the Database, it is recommended to use it only on development servers where the log volume is low. If the log volume is high, it may degrade Application performance, so use it with caution.

Open tomcat9_online/webapps/serviceEndpoint/WEB-INF/classes/bxm-management-instance.xml.

Find the environment item and change application-home under the loader item. At this time, modify BXM HOME to the directory where BXM is installed.

...

<environment>
    <system-properties>
        beantype.usemetadata=true
        accrue.data.accesstime=true
        accrue.beanfactory.accesstime=true
    </system-properties>
    <system-mode>D</system-mode>
    <datasource>
        <jndi-datasource jndi-name="java:/comp/env/BXMNXA">
        </jndi-datasource>
    </datasource>
    <loader mode="hot" autodeploy="true" interval-millis="8000" registry="off"
        lazy-init="true" deferred-init="true" deferred-init-interval="1000" sessionfactory-lazyinit="true"
        use-lastmodified-cache="true">
        <application-home><<BXM HOME>>/apps/online</application-home>
        <instrument>
            <cn:transformer classname="bxm.dft.transform.PrintServiceLogTagTransformer" order="1">
                <cn:typefilter rule="include" type="regex" expression="bxm.*.bean.*"/>
            </cn:transformer>
        </instrument>
    </loader>
</environment>

...

Find the data-access item and change the alias as shown below. The alias names follow the entries added to server.xml in the earlier WAS configuration.

...

<data-access trace-inject="false" monitor-inject="false" identify-inject="true"
    max-resultset="5000" fetch-size="100" min-fetch-size="100"
    limit-exceeded-action="Error" forced-logging="false">
    <jndi-datasource-aliases>
        <alias name="java:/comp/env/APPNXA" alias="BXMNXA" />
        <alias name="java:/comp/env/APPXA" alias="BXMXA" />
    </jndi-datasource-aliases>
</data-access>

...