Upgrading | ||
---|---|---|
Previous | ||
Planning the Upgrade |
This chapter describes the various steps of the upgrade process.
Before upgrading, you must stop all applications and user connections to Convergence for MDM. During the upgrade:
You should contact your database administrator and middleware administrator to make sure that the unavailability of Semarchy Convergence for MDM during the upgrade process is correctly managed.
Stop all Semarchy Convergence for MDM Applications. This is done either by:
Before upgrading, you should make sure that:
Important: Before going further, make sure that all the required backup are done, and that the entire Semarchy Convergence for MDM environment is stopped and not accessed by any user or application.
If you have decided to perform an out-of-place upgrade, you must replicate (Copy) the schemas containing the repositories and the data locations using the Oracle Database utilities.
The new product version, considered as a separate installation, will point to this copy of the schemas.
Tip: Use a clear naming convention for these new schemas to be able to identify them easily. For example, if the original schemas are called
SEM_REPOSITORY
,SEM_DLOC1
, etc., the new one may be calledSEM_2_2_REPOSITORY
,SEM_2_2_DLOC1
, etc.
Perform the following operation for every application server into which the Semarchy Convergence for MDM application was deployed.
To install the new application version for in-place upgrade:
Note: Refer to your application server documentation for more information about re-deploying applications on top of previous installations. The simple instructions for Apache Tomcat are provided below.
To perform an in-place upgrade for Apache Tomcat.
<tomcat>/conf/Catalina/localhost/semarchy.xml
file.
http://<tomcat_host>:<tomcat_port>/manager/
).
semarchy.war
file.
semarchy.xml
file in the
<tomcat>/conf/Catalina/localhost/
folder.
To install the new application version for out-of-place upgrade:
Warning: When performing an out-of-place update, make sure to deploy the new version as a new application. If this new deployment takes place in the application server that already contains the previous version, make sure to change the application name during the deployment.
Note: Refer to your application server documentation for more information about deploying new applications.
Perform the following operation for each deployment of the new Semarchy Convergence for MDM application version.
For in-place upgrade, the updated deployment reuses the configuration already in place. Check this configuration in the application server console or configuration files. The following points should be checked:
To configure the new application version in an out-of-place upgrade:
SEM_2_2_REPOSITORY
,
SEM_2_2_DLOC1
).
Note: Datasources for repositories and data locations should be configured locally for the application. Indeed, the repository datasource must be called
SEMARCHY_REPOSITORY
. Declaring this datasource at application-level avoids having multiple Semarchy applications (possibly in different versions) try to connect the same repository schema at the same time.
Important: By using datasources local to the new application, you make sure that the new application connects exclusively to the copy of the repository and data locations schemas. Similarly, the old version should use local datasources to connect only the original repository and data location schemas.
Perform this operation for a single new application version instance. If you have multiple repositories, you should repeat this operation for each repository.
Start your application server or connect to your application server and start the deployed application.
Note: Repository upgrade is required only for major and minor versions. For patches, repository upgrade is not needed and the Repository Upgrade dialog does not appear when you connect.
Important: The repository upgrade is an operation that cannot be undone. Make sure that you have made a backup of the repository schema before proceeding.
To upgrade the repository:
The repository upgrade starts. When it completes, the Overview window appears.
Warning: The repository upgrade process can only be triggered by a user with the semarchyAdmin role.
Note: Data locations upgrade is required only for major and minor versions. For patches, data location upgrade is not needed, and the Overview page will not show any data location requiring an update.
Important: The data location upgrade is an operation that cannot be undone. Make sure that you have made a backup of the data location schemas before proceeding.
Warning: Development data locations upgrade is possible only if the current model edition deployed is valid. Before upgrade a development data location make sure that the deployed model does not raise any design-time validation errors.
To upgrade the data locations:
The repository upgrade starts. When it completes, the Overview window appears.
Warning: The data location upgrade process can only be triggered by a user with the semarchyAdmin role.
The upgrade is now finished.
You can restart all the Semarchy instances in the new version, and open the access through the user interface, web services and database tables.
Previous | Top | |
Planning the Upgrade |