Instances, Configurations, Data, and Assets that Can be Migrated

Edit online

You can choose to migrate the following:

  • Server instances, with this exception: Starting in My webMethods Server 10.3, My webMethods Server no longer offers an embedded database, so the IBM My webMethods Server migration utility will not migrate instances that used an embedded database. Instead you can create a new instance, and then transfer applications and content from the old instance to the new instance using Deployer or the content import/export functionality of IBM My webMethods Server. For instructions, see IBM webMethods Deployer User’s Guide or Administering IBM My webMethods Server, respectively.
  • JAAS configuration files.
  • Java Service Wrapper customizations you made in the old custom_wrapper.conf files, including #include directives and comments (but not associated properties).
  • If you specified a URL for Universal Messaging, the existing JNDI URL parameter is updated or a new JNDI URL parameter is added to the cluster.xml file, as appropriate.

After migrating, the utility deletes old configuration files, and deletes old properties that are not used by the new IBM My webMethods Server from the new configuration files. The utility also synchronizes the IBM My webMethods Server installation directory with the database.