Installing Web Admin Instance
Install $BXM_HOME/admin/bxmAdmin 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/admin/bxmAdmin $BXM_HOME/../tomcat9_admin/webapps/bxmAdmin
-
Or copy $BXM_HOME/admin/bxmAdmin
|
If you copy the directory, you must modify the configuration path defined in this guide to the copied path. |
cp -R $BXM_HOME/admin/bxmAdmin $BXM_HOME/../tomcat9_admin/webapps/bxmAdmin
| File name | Location | Remarks |
|---|---|---|
web.xml |
bxmAdmin/WEB-INF/ |
Web context configuration file |
bxm-management-instance.xml |
bxmAdmin/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) |
-
Open the $BXM_HOME/admin/bxmAdmin/WEB-INF/classes/bxm-management-instance.xml file.
-
Find the environment item and modify system-properties upload dir and loader application-home. At this time, set BXM HOME to the path where BXM is installed.
... <environment> <system-properties>beantype.usemetadata=true accrue.data.accesstime=true accrue.beanfactory.accesstime=true admin.system.main.key=AC admin.system.domain.id=DEFAULT <!-- used by dni--> admin.use.trx.cd=true admin.image.log.system.header=bxm.dft.context.DefaultSystemHeader admin.batch.type.no.select=false admin.locale.no.select=false file.upload.dir=<<BXM HOME>>/upload <!-- mysql supports. NullPointerException may occur without the option below --> multidb.dbio.configuration=true </system-properties> <system-mode>D</system-mode> <datasource> <jndi-datasource jndi-name="java:/comp/env/BXMNXA" /> </datasource> <loader mode="hot" autodeploy="true" interval-millis="8000" lazy-init="true" deferred-init="true" deferred-init-interval="1000" registry="off" sessionfactory-lazyinit="true" use-lastmodified-cache="true"> <application-home><<BXM HOME>>/apps/admin</application-home> </loader> </environment> ... -
Find the data-access item and modify jndi-datasource-aliases as shown below. In this case, the alias name follows the Datasource name configured earlier in server.xml.
... <data-access max-resultset="10000" fetch-size="10" min-fetch-size="100" limit-exceeded-action="Error" forced-logging="false"> <jndi-datasource-aliases> <alias name="java:/comp/env/APPNXA" alias="DSNXA" /> <alias name="java:/comp/env/APPXA" alias="DSXA" /> </jndi-datasource-aliases> </data-access> ...