Other Actions Performed as Part of the Migration
Old configuration files are deleted, and old properties that are not used by the new installation are deleted from the new configuration files.
If the old installation used the embedded database, the database tables from the old installation are copied to the new installation and the tables are upgraded to the new format, if the format has changed.
The SERVER ID stored in database tables and configuration files is updated to reflect the new host machine.
A new property named "Validate schemas using Xerces" is added to existing Web service descriptors, and the new property is set to the same value to which the watt.server.wsdl.validateWSDLSchemaUsingXerces parameter was set in the old installation. The new property replaces the functionality provided by that parameter. For information about the new property, see
webMethods Service Development Help.
Keystore aliases of type PKCS12 whose keystore provider name is SunJSSE are updated to use Bouncy Castle as a provider.
If you are migrating Business Rules data, Business Rule projects are upgraded. You might see XML parsing messages due to a Java bug; you can ignore these messages.
If you are upgrading
CloudStreams, configuration artifacts related to administering
CloudStreams Server are migrated.