Warning | Ignoring Broker client group "JMSClient" property required_encryption" with value "ENCRYPT_LEVEL_ENCRYPTION" |
Cause | The migration script does not migrate any authentication related information from Broker. Encryption is enabled for the client group in Broker. |
Action | Configure authentication as per your requirement in Universal Messaging. |
Warning | Ignoring Broker client group "JMSClient" property "access_label_required" with value "true" |
Cause | The migration script does not migrate any authentication related information from Broker. Access label, an advanced security feature of Broker is enabled for the client group. |
Action | Configure authentication as per your requirement in Universal Messaging. |
Warning | Ignoring Broker client group "JMSClient" property "ClientGroupACL" with value "Users: [CN=brokerserver,O=webM,ST= CA,C=US], AuthNames: [emailAddress=dtung@webmethods.com,CN= webMCA,O=webM,ST=CA,C=US]" |
Cause | The migration script does not migrate any authentication related information from Broker. ACL is set for the client group in Broker. |
Action | Configure authentication as per your requirement in Universal Messaging. |
Warning | Ignoring Broker document type property "Validation" with value "FULL or OPEN" |
Cause | The validation property of the document type specifies whether Broker must validate the document type instances. The validation property set to "FULL" or "OPEN" specifies that Broker must validate even the fields that are not defined in the document type. |
Action | Universal Messaging does not support message validation at the server side. Configure message validation as per your requirement in your messaging solution. |
Warning | Ignoring Broker document type property "Storage type" with value "VOLATILE" |
Cause | The storage type property of the document type in Broker determines whether the instances of the document type are stored in memory or disk. The channel type is Mixed in Universal Messaging by default, whereas the storage type of the document type in Broker is set to VOLATILE. |
Action | If the Broker storage type is set to VOLATILE, configure the channel type to transient in Universal Messaging. |
Warning | Ignoring Broker document type field(s) "[name, host, type, version, client group, info]" |
Cause | The Fields property of the Broker document type is not migrated. The Fields property contains data that client applications use to exchange information. The Fields property might contain a single value, a sequence of values of the same type, or a structure containing values of different types. |
Action | If the document fields configured in Broker have functional implications on Universal Messaging, configure Universal Messaging as per your requirement. |