The instructions on this page takes you through the steps for upgrading from AS 5.1.0 to AS 5.2.1. This includes upgrading the database changes as well as the configurations that should follow the upgrade.
You cannot rollback the upgrade process. However, It is possible to restore a backup of the previous database and restart the upgrade progress.
Preparing to upgrade
The following prerequisites must be completed before upgrading:
Take a backup of the user and registry databases of AS 126.96.36.199 database and copy the
Take a backup of <AS_HOME_5.1.0> directory in order
2.1> folder to backup the product configurations.
Download WSO2 Application Server 5.2
0 from http://wso2.com/products/application-server/.
The downtime is limited to the time taken for switching databases when in the production environment.
Upgrading the databaseBefore you upgrade to
There are no registry and user database schema changes between AS 5.2.1 and 5.3.0. Therefore, you do not need to do any database schema migration. However, you should create a new database and restore the
backup of the old database in this new database.
existing database, and create a duplicate database to use with a newer product version. This is described below.
You should NOT connect a new version of WSO2 AS to an older database that has not been upgraded.
Select the relevant script for the upgrade from here and run it on the new database. Running this script will ensure that the database is upgraded with the additional tables and schemas that are required for AS 5.2.1.
There are three migration scripts available:
migration.sql. However, note that only the migration.sql script is required to be executed for AS 5.2.1.
Once you run the migration scripts on the new database, it becomes the upgraded database for AS 5.2.1.
Migrating the configurations
Once Before you have completed the database upgrade as explained in the previous steps, you must migrate the configurations from start updating the configuration files in AS 5.1.0 to AS 5.2.1 as explained below3.0, create a new database and restore the backup of the old database in this new database.
Updating the configuration files
The following are the updates that need to be done to the configuration files in AS 5.23.10.
Note that configuration files should not be copied directly between servers.
- Create a new database for AS 5.3.0 and restore the backup of the old database in this new database.
- To connect AS 5.23.1 0 to the upgraded database, configure the following files:
<AS_HOME_5.2.1>/repository/conf/datasources/masterdatasources.xml file as shown in the following example:
<description>The datasource used for registry and
Go to the
<AS _HOME_5.2.1>/repository/conf/ directory and update the datasource references in the
registry.xml files to match the updated configurations in the
masterdatasources.xml file. The following are sample configurations if the datasource is “jdbc/WSO2CarbonDB”:
- The SaaS application configuration in webapps has been changed. So, if you are using SaaS features, you need to update your web applications. Previously, users have configured the SaaS configuration via web.xml by adding a context-param called carbon.enable.saas. In the new version, SaaS is configured via the context.xml configuration file that needs to be placed under the META-INF/ folder of the webapp. See the following documentation for more details -https://docs.wso2.com/display/AS530/Configuring+Applications+for+AS
- KeyStore configuration in AS 5.2.1 has been converged into the carbon.xml. But users wanted to configure different keystore for SSL communication, and so on. Hence, in AS 5.3.0, users should separately configure the transport keystores through catalina-server.xml. The “RegistryKeyStore” configuration in carbon.xml has been removed. This is not really there in the AS 5.2.1, but was added later in a patch. This has been reverted in AS 5.3.0.
- Check for any other configurations that were done for AS 5.1.0 (based on your solutions), and update the configuration files in AS 5.2.1 accordingly. For example, external user stores, caching, mounting, etc.
Note that the following configuration files have changed in
Migrating third party libraries
If there are any third party libraries used with AS 5.2.1 :
The following configuration files are newly added to AS 5.2.1:
Migrating the tenant settings and applications
that you want to migrate, copy them to the following directories as applicable to AS 5.3.0.
- If you have used JDBC drivers etc, copy them into <AS_HOME>/repository/components/lib
- If you have used OSGi bundles such as SVNKit etc, copy them into <AS_HOME>/repository/components/dropins
Migrating the services and artifacts
You can migrate all artifacts etc. relevant to super-tenant and ordinary tenants by copying the following directories from the old server to the new server.
To migrate the deployment
super-tenant’s artifacts, copy the <AS_HOME>/repository/deployment/server/ directory from AS 5.2.1 .0
to AS 5.2
If multitenancy is used
you are using multi-tenancy, copy the <AS_HOME>/repository/tenants/ directory from AS 5.1.0 to
AS 5.2.1 .
- If axis based services are included in the directories that were copied above, you must do the following:
- Open the metadata files corresponding to the axis services from the following locations:
- The metadata files of axis services for the super tenant are stored in the
- The metadata files of axis services for each tenant can be found in the
When you open each metadata file, remove all occurrences of the following:
<module name="activation" version="2.1.0" type="engagedModules"/
- If any JAXRS and JAXWS applications were copied from the old server (in step 1 and step 2), they must be moved as follows:
- For the super tenant, these applications should be moved from the
<AS_HOME_5.2.1>/repository/deployment/server/jaxwebapps/ folder to the
- For other tenants, these applications should be moved from the
<AS_HOME_5.2.1>/repository/tenants/<Tenant_No>/jaxwebapps/ folder to the
- Start WSO2 Application Server 5.2.1.
If you have a Composite Application Archive (CAR) file in AS 5.1.0, you can manually deploy using the management console of AS 5.2.1. See the topic on Creating and Deploying Carbon Applications for instructions. Alternatively, without using the management console of AS 5.2.1, you can directly copy the following directories:
For super tenant, copy the
<AS_HOME_5.1.0>/repository/carbonapps/0/ directory to the
For other tenants, copy the
<AS_HOME_5.1.0>/repository/carbonapps/<Tenant_No> directory to the
Testing the upgrade
- When the database upgrade scripts are executed, the following are some of the new tables that will be created in the database:
- Verify that all the required scenarios are working as expected. This confirms that the upgrade is successful.