...
Check the configurations in the following files in BRS 2.1.0, and apply same configurations in BRS 2.2.0 manually.
Note Configurations should not be copied directly from BRS 2.1.0 to BRS 2.2.0 because the configuration files have new properties added to them as well as obsolete properties removed from them between the two releases.
Configuration File Location axis2.xml
<BRS_HOME>/repository/conf/axis2
axis2_client.xml
<BRS_HOME>/repository/conf/axis2
carbon.xml
<BRS_HOME>/repository/conf
master-datasources.xml
<BRS_HOME>/repository/conf/datasources
identity.xml
<BRS_HOME>/repository/conf
log4j.properties
<BRS_HOME>/repository/conf
registry.xml
<BRS_HOME>/repository/conf
catalina-server.xml
<BRS_HOME>/repository/conf/tomcat
web.xml
<BRS_HOME>/repository/conf/tomcat
If the Cipher too tool was configured for BRS 2.1.0, check the configurations in the following files and apply the same changes in BRS 2.2.0 manually.
Configuration File Location cipher-text.properties
<BRS_HOME>/repository/conf/security
cipher-tool.properties
<BRS_HOME>/repository/conf/security
- Check the configurations in the other files located in the
<BRS 2.1.0_HOME>/repository/conf
directory and apply the same changes to BRS 2.2.0 manually. - If there are any third party libraries used with BRS 2.1.0 that you want to migrate, copy the following directories as applicable from BRS 2.1.0 to BRS 2.2.0:
- If you have used JMS libraries, JDBC libraries etc, copy
<BRS_HOME>/repository/components/lib
. - If you have used OSGi bundles such as SVN kit etc, copy
<BRS_HOME>/repository/components/dropins
.
- If you have used JMS libraries, JDBC libraries etc, copy
- Start the BRS 2.2.0 server. For more information, see Running the Product.
...