If there is an existing MCS installation, you may need to migrate the MCS policies to the new version before developing or modifying existing policies. There are differences in the XML and database schema structures in the new version.
When migrating policies to the new version, use the mcsMigrate
command. The syntax for mcsMigrate
is as follows:
option defines the directory to migrate, which must exist. The -output
option specifies the output file or directory, which must not exist. The -verbose
option specifies that you want to display detailed (verbose) messages.
For migration purposes, MCS policies fall into four categories:
- Device repository policies
- XDIME aggregator policies
- Global policies
- Portlet policies
When you finish migrating the Mobile Portal Accelerator database tables, proceed to the next topic: Completing the migration.
Migrating device repository policiesParent topic: Migrating
Overview of Migrating from Mobile Portal Accelerator version 6.1 or 7.0.x
Verifying the migration
Migrating preload notice data
Completing the migration from version 6.1
Migrating the XDIME aggregator policies
When you install IBM
Mobile Portal Accelerator version 8.0, the device repository supplied with the product is imported into the MCS database that is used with your version 8.0 installation.
Migrating global policies
If you created new policies for this project in your previous IBM
Mobile Portal Accelerator installation or modified the policies that were provided with this project, follow these steps.
Migrating portlet policies
If you developed your own portlets, you must migrate the Multi-Channel Server policies before you install those portlets.
Migrating a portlet
If you need to migrate a portlet, you must prepare the source node and the target node first.