Merging 3.0.2HF-4 Configurations to 4.0 Configurations
The application's configuration and log4j configuration properties used by TIBCO Fulfillment Order Management 3.0.2 HF-4 must be migrated into the corresponding files in the TIBCO Fulfillment Order Management 4.0 installation.
This can be done by running a Java based command line utility which can be launched using
$AF_HOME/migration/bin/migrateConfigProperties.sh. This utility requires all
.jar files present in the
$AF_HOME/migration/lib directory. The utility refers to the following two files from the
$AF_HOME/migration/config directory:
- migrationIgnore.properties - This file contains the property name of the configuration properties which are ignored during the migration. By default, there are only two configuration properties which are ignored.
- MigrationLog4j.xml - This file contains the log4j configurations for the utility with the default log level set at
INFO level. It can be changed to
DEBUG for more granular logging.
This utility migrates the application's configuration properties for the following components in the mentioned files:
- OmsServer and Orchestrator - $AF_HOME/roles/configurator/standalone/config/ConfigValues_OMS.xml
- AOPD - $AF_HOME/roles/configurator/standalone/config/ConfigValues_AOPD.xml
- JEOMS - $AF_HOME/roles/configurator/standalone/config/ConfigValues_JEOMS.xml
- OPE - $AF_HOME/roles/configurator/standalone/config/ConfigValues_OPE.xml
It also migrates the log4j configuration properties for the following components in the mentioned files:- OmsServer, Orchestrator and JEOMS - $AF_HOME/roles/configurator/standalone/config/OMSServerLog4j.xml
- AOPD - $AF_HOME/roles/configurator/standalone/config/AOPDLog4j.xml
- OMSUI - $AF_HOME/roles/configurator/standalone/config/OMSUILog4j.xml
- OPE - $AF_HOME/roles/configurator/standalone/config/OPELog4j.xml
The utility writes the logs in the $AF_HOME/migration/logs/fom-property-migration.log file.
Procedure
Copyright © Cloud Software Group, Inc. All rights reserved.