AMS 1.5.0 and higher support migrating data from one AMS-supported database to another (for example, from AMS's default embedded H2 database to an AMS-supported PostgreSQL database or vice-versa).
The AMS data source is defined in the database section of your configuration file. When migrating data, the following criteria apply:
An AMS server can be connected to only one data source
A data source can be connected to only one AMS server
To migrate AMS data from one data source to another, do the following:
Update the AMS server to the required version. AMS manages the schema and data migration, so both the backup and restore must be performed on the same version of AMS (for example, AMS 1.5.0).
ams server --upgrade
Back up the existing AMS data. See Backing Up Data for more information.
ams-server --backup
Change the database section of the AMS configuration file to define the new AMS data destination.
Restore the AMS data to the AMS data destination defined in the database section of the AMS configuration file.
ams-server --restore
While not required, TIBCO recommends you perform a restore on an empty/new AMS data source.
Start the AMS server. Once started, the AMS data will contain the users, roles, permission, artifacts, and so on, from the previous data source.
ams-server –-run