Post-migration
The following steps are required following a QXtend migration:
1 Update the source application database details to ensure that the qxevents database points to the new version’s qxevents database. This action applies when migrating the QXtend Outbound configuration. During an in-place conversion, the existing qxevents database specified in the source application connection details is converted to the version.
To update the source application database details, go to the QXtend Outbound UI, select the Configuration tab, and make the necessary changes in the Databases pane.
2 Verify the QXtend Web Service subscribers in QXtend Outbound. For each QXtend Web Service subscriber, verify that the entries in the Tomcat Host, Tomcat Port, and WebApp Name fields point to the new version’s web application.
3 Verify the license manager details for QXtend Outbound. You can set them in QXO by selecting Configuration|Outbound Settings|License Manager.
4 Additional work can be required depending on the QXtend version. The work is described in a reminder the installer displays after a successful migration.
5 You must manually validate all business objects before an event message can be extracted. To validate business objects, select the Business Objects tab, and click Validate All. This action regenerates the schema definition for the business objects.
Note: Since QXtend 1.8.4, QXtend only allows alphanumeric characters, dashes, and underscores in BO or profile names. During upgrade and migration, if a BO or Profile name contains unsupported characters from a previous QXtend installation, the installer raises warning messages and writes them to the install log file. After upgrade or migration, a BO with unsupported characters is not validated. You must change the BO or Profile name to make it available.