After comparing and validating the configuration metadata and changes, you
can migrate the changes to the current deployment environment or system.
When you import the configuration changes from the previous deployment, the configuration objects
in the IBM
OpenPages® with Watson™ repository of the current
deployment are updated with those changes.
Note: The source and target environments must have the same version and patch level of OpenPages with Watson.
An alternative to using the command-line interface (CLI) tool in ObjectManager is to use to import the XML file. For information, see Importing a migration file.
Procedure
- Verify that the OpenPages with Watson application is running.
-
Open a command or shell window and change to the
<OP_HOME>/bin directory of your OpenPages with Watson installation.
- From the command or shell window, run an ObjectManager command on a single line:
- On a computer running a Microsoft
Windows operating system:
ObjectManager load config <admin-user> <password> <config-folder-path> <prefix>
- On a computer running a Linux® operating
system:
./ObjectManager.sh load config <admin-user> <password> <config-folder-path> <prefix>
Where:
<admin-user> is the user name of the Super Administrator
account (for example, OpenPagesAdministrator).
<password> is the password of the Super Administrator
account.
<config-folder-path> is the file path to the folder where
the exported file will reside. If the folder does not already exist, ObjectManager will create it.
<prefix> is the prefix for the file name that will be
used by ObjectManager.
For example, on a Windows operating system:
ObjectManager load config OpenPagesAdministrator password c:\temp myconfig
- To see the configuration changes in the application, stop and then restart
the OpenPages with Watson application services.
-
To validate that the newly updated OpenPages with Watson repository matches the configuration changes from the export
file, see the topic Validating configuration changes.
- To export the configuration data to a file,
see the topic Exporting configuration changes.
What to do next
If you loaded profiles, update the reporting schema. For more information, see Updating the reporting schema.