Following steps describes how to update(migrate) WSO2 products to newer versions
Step 1 - Deploying existing artifacts
Copy the deployed artifacts to WSO2 ESB old version to WSO2 ESB new version by copying wso2esb-4.0.0/repository/deployment/server folder to wso2esb-4.0.3/repository/deployment/server Also Copy all the content of repository/component/lib {wso2esb-4.0.0} to the new installation {wso2esb-4.0.3} (this will help you install the existing drivers and additional plug-ins used in your earlier installation)
Step 2 - Apply Patches
Most of the patches are applied when we release newer versions however, some patches can be not applied such as a custom patches or patches which were given after the release. Therefore you need to check the needed patches and apply them
Step 3 - Allocate proper memory numbers (if applicable).
If you have allocated memory numbers don't forget to allocate them to the new installation as well.
Step 3 - Change the configuration files
Apply the same changes you have done to configurations files inside OldVersion/repository/conf to NewVersion/repository/conf (if you have done any such to any configuration files)
Note
Apply the security measures taken as before. such as Encrypting passwords {as done previously}, Changing key stores etc
Step 1 - Deploying existing artifacts
Copy the deployed artifacts to WSO2 ESB old version to WSO2 ESB new version by copying wso2esb-4.0.0/repository/deployment/server folder to wso2esb-4.0.3/repository/deployment/server Also Copy all the content of repository/component/lib {wso2esb-4.0.0} to the new installation {wso2esb-4.0.3} (this will help you install the existing drivers and additional plug-ins used in your earlier installation)
Step 2 - Apply Patches
Most of the patches are applied when we release newer versions however, some patches can be not applied such as a custom patches or patches which were given after the release. Therefore you need to check the needed patches and apply them
Step 3 - Allocate proper memory numbers (if applicable).
If you have allocated memory numbers don't forget to allocate them to the new installation as well.
Step 3 - Change the configuration files
Apply the same changes you have done to configurations files inside OldVersion/repository/conf to NewVersion/repository/conf (if you have done any such to any configuration files)
Note
- If you have done registry mounting make sure you apply to the new installation as done before by changing relevant configuration files such as carbon.xml,axis2.xml,user-mgt.xml,mgt-transports.xml
- If you have created external data sources (Carbon data sources) make sure you copy datasources.properties file from repository/conf to the newer version repository conf
Apply the security measures taken as before. such as Encrypting passwords {as done previously}, Changing key stores etc
No comments:
Post a Comment