Document Type and Trigger Migration

The pub.utils.messaging:migrateDocTypesTriggersToUM service can be found in the WmPublic folder in Designer. Run this service to migrate publishable document types and the subscribing triggers to use Universal Messaging as the messaging provider.

Note:
This service works only with Universal Messaging 9.8 and later.

The pub.utils.messaging:migrateDocTypesTriggersToUM service can be used to perform one or more of the following:

Change the messaging connection alias assigned to the publishable document types to Universal Messaging.

Note:
This step is required only if you choose to have Broker as your default messaging provider and migrate to Universal Messaging in phases.

Set the encoding type of the publishable document type to protocol buffers.

Synchronize the updated publishable document types with Universal Messaging.

Convert the filters used by the webMethods messaging triggers that subscribe to the publishable document types. Specifically, the service migrates the filter expressions that can be evaluated by the Universal Messaging server from the Filter field for a trigger condition to the Provider Filter (UM) field.

Ensure that Integration Server is connected to Broker.

Ensure that the document types are in sync with their associated Broker document types in the target Integration Server.

Determine the list of publishable document types to be migrated. Migrate all document types subscribed by a group of webMethods messaging triggers at one time.

Ensure that if a trigger subscribes to more than one publishable document type, all the publishable document types use the same messaging connection alias. Otherwise,Integration Server considers the trigger to be invalid.

Ensure that the webMethods messaging triggers are not locked for edit by another user when running this service.

Ensure that you have Write access to the publishable document types and webMethods messaging triggers.

Decide if you want to use packageNames or documentTypeNames input parameters. If you specify a value for both parameters, the service will fail with an exception.

Run the service in report only mode by setting the reportOnly input parameter to true. Use the service output to find potential problems in the migration.

Before using this service to migrate document types and triggers, see the information and usage notes in webMethods Integration Server Built-In Services Reference.