JNDI Migration Script Warnings
Warning | Ignoring Broker property "SSLEncrypted" with value "true" |
Cause | The migration script does not migrate the authentication related properties of the Broker connection factory. The SSLEncrypted property of the Broker connection factory is set to true. |
Action | Configure the SSL encryption on the corresponding connection factory in Universal Messaging. |
Warning | Ignoring Broker property "SSLKeystore" with value <ssl_keystore_value> |
Cause | The migration script does not migrate the authentication related properties of the Broker connection factory. The SSLKeystore property of the connection factory is set in Broker. |
Action | Configure the SSL keystore on the corresponding connection factory in Universal Messaging. |
Warning | Ignoring Broker property "SSLTruststore" with value <value> |
Cause | The migration script does not migrate the connection factory properties that are related to Broker authentication. The SSLTruststore property of the connection factory is set in Broker. |
Action | Configure the SSL truststore on the corresponding connection factory in Universal Messaging. |
Warning | Ignoring Broker property "MarshalInClassName" with value <value> |
Cause | Universal Messaging does not support marshalling. The Broker-specific MarshalInClassName property of the connection factory is not migrated from the Broker. The MarshalInClassName property of the connection factory is set in Broker. |
Action | Check the marshaling functionality in Broker and configure Universal Messaging as per your requirement for interoperability. |
Warning | Ignoring Broker property "MarshalOutClassName" with value <marshaloutclasname_value> |
Cause | Universal Messaging does not support marshaling. The Broker-specific MarshalOutClassName property of the connection factory is not migrated from the Broker. The MarshalOutClassName property of the connection factory is set in Broker. |
Action | Check the marshaling functionality in Broker and configure Universal Messaging as per your requirement for interoperability. |
Warning | Ignoring cluster Brokers "[[<list_of_comma_separated_ cluster_Brokers>]]" as migrating to standalone UM |
Cause | The ClusterBrokers property of the Broker cluster connection factory is not migrated because it is difficult to identify:  Whether the number of Brokers and Universal Messaging servers are equal. How load balancing is done using the cluster policy. |
Action | Note the list of cluster Brokers in the warning message and make the required changes in the migrated cluster connection factory in Universal Messaging. |
Warning | Migrating to UM cluster in <Failover or Random> mode. Broker cluster policy is <policy_name> |
Cause | There is a mismatch due to one of these reasons: The Broker cluster policy is not STICKY and the Universal Messaging server is in Failover mode. The Broker cluster policy is STICKY and the Universal Messaging server is in RANDOM mode. |
Action | Configure the Universal Messaging cluster to specify the list of servers in the cluster. Specify the list of server URLs separated by ";" or ",". |
Warning | Ignoring cluster connection factories "[< ClusterConnectionFactory_1, ClusterConnectionFactory_2>]" as migrating to standalone UM |
Cause | Universal Messaging does not support composite connection factory. |
Action | Understand the usage of the composite cluster connection factory in Broker and configure Universal Messaging as per your requirement. |
Warning | Ignoring Broker property "SharedState" with value "false" |
Cause | The SharedState property of the Broker destination is disabled. The corresponding SharedDurable property in the Universal Messaging connection factory is enabled by default. |
Action | Make sure you use this destination with a non-shared durable connection factory in Universal Messaging. |
Warning | Ignoring Broker property "SharedState" with value " false" |
Cause | The SharedState property of the Broker destination is disabled. The corresponding SharedDurable property in the Universal Messaging connection factory is enabled by default. |
Action | Configure the SharedDurable property in Universal Messaging as per your requirement. Universal Messaging does not support shared state ordering. |
Warning | Ignoring Broker property "PriorityOrdering" with value "true" |
Cause | The PriorityOrdering property of a Broker destination is enabled. The corresponding SharedPriority property in the Universal Messaging connection factory is disabled by default. |
Action | If the PriorityOrdering property is enabled in the Broker destination, enable the SharedPriority property in the Universal Messaging connection factory. |
Warning | Ignoring Broker property "LocalOnly" with value "true" |
Cause | The migration script does not migrate the LocalOnly property of the Broker topic. The LocalOnly property is enabled in Broker. |
Action | Configure Universal Messaging to receive only the messages published by the local publisher, if required. |
Warning | Ignoring Broker property "DeadLetterOnly" with value " true" |
Cause | The migration script does not migrate the DeadLetterOnly property of the Broker topic. The DeadLetterOnly property is enabled in Broker. |
Action | Configure Universal Messaging to subscribe to dead letters, if required. |
Warning | Migration not done for <sub_context_name> with value <subcontext_value> |
Cause | The migration script does not migrate the subcontext JNDI entries of Broker. |
Action | Create the folders manually and move your destinations to the target Universal Messaging to achieve the required structure. |
Warning | Migration not done for String <string_name> with value <string_value> |
Cause | The migration script does not migrate the string JNDI entries of Broker. |