text
stringlengths 65
20k
|
|---|
This message type is for client encoding of existing message formats.Durable Subscriber (Is displayed if you selected Topic on the Basic Info page.)This field is optional.If you are setting up a durable subscriber, a durable subscriber ID is required.A subscriber generally loses messages if it becomes disconnected.However, a durable subscriber downloads stored messages when it reconnects.This ensures that consumers receive messages that were published even when the subscribers were not running.These messages are persisted by the JMS provider and are either sent to the consumer when it becomes active again or purged from storage if the message expires.Subscription Name (Is displayed if you selected Topic on the Basic Info page.)Enter the durable subscriber ID.This field is displayed if you selected Yes for Durable Subscriber .Time to Live (Is displayed if you selected Queue on the Basic Info page.)Specify the time to live (the amount of time before a message expires and is no longer available for consumption).Chapter 3 Configuration for Queue or Topic Page 3-2Element Description Delivery Mode (Is displayed if you selected Queue on the Basic Info page.)Persistent : Specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber.A durable subscriber is a consumed message with a durable subscriber ID. |
Durable Subscriber (Is displayed if you selected Topic on the Basic Info page.)This field is optional.If you are setting up a durable subscriber, a durable subscriber ID is required.A subscriber generally loses messages if it becomes disconnected.However, a durable subscriber downloads stored messages when it reconnects.This ensures that consumers receive messages that were published even when the subscribers were not running.These messages are persisted by the JMS provider and are either sent to the consumer when it becomes active again or purged from storage if the message expires.Subscription Name (Is displayed if you selected Topic on the Basic Info page.)Enter the durable subscriber ID.This field is displayed if you selected Yes for Durable Subscriber .Time to Live (Is displayed if you selected Queue on the Basic Info page.)Specify the time to live (the amount of time before a message expires and is no longer available for consumption).Chapter 3 Configuration for Queue or Topic Page 3-2Element Description Delivery Mode (Is displayed if you selected Queue on the Basic Info page.)Persistent : Specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber.A durable subscriber is a consumed message with a durable subscriber ID.A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages. |
)This field is optional.If you are setting up a durable subscriber, a durable subscriber ID is required.A subscriber generally loses messages if it becomes disconnected.However, a durable subscriber downloads stored messages when it reconnects.This ensures that consumers receive messages that were published even when the subscribers were not running.These messages are persisted by the JMS provider and are either sent to the consumer when it becomes active again or purged from storage if the message expires.Subscription Name (Is displayed if you selected Topic on the Basic Info page.)Enter the durable subscriber ID.This field is displayed if you selected Yes for Durable Subscriber .Time to Live (Is displayed if you selected Queue on the Basic Info page.)Specify the time to live (the amount of time before a message expires and is no longer available for consumption).Chapter 3 Configuration for Queue or Topic Page 3-2Element Description Delivery Mode (Is displayed if you selected Queue on the Basic Info page.)Persistent : Specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber.A durable subscriber is a consumed message with a durable subscriber ID.A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages.Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active. |
If you are setting up a durable subscriber, a durable subscriber ID is required.A subscriber generally loses messages if it becomes disconnected.However, a durable subscriber downloads stored messages when it reconnects.This ensures that consumers receive messages that were published even when the subscribers were not running.These messages are persisted by the JMS provider and are either sent to the consumer when it becomes active again or purged from storage if the message expires.Subscription Name (Is displayed if you selected Topic on the Basic Info page.)Enter the durable subscriber ID.This field is displayed if you selected Yes for Durable Subscriber .Time to Live (Is displayed if you selected Queue on the Basic Info page.)Specify the time to live (the amount of time before a message expires and is no longer available for consumption).Chapter 3 Configuration for Queue or Topic Page 3-2Element Description Delivery Mode (Is displayed if you selected Queue on the Basic Info page.)Persistent : Specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber.A durable subscriber is a consumed message with a durable subscriber ID.A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages.Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active.Select one of the patterns of Message SelectorSelect the pattern to use. |
A subscriber generally loses messages if it becomes disconnected.However, a durable subscriber downloads stored messages when it reconnects.This ensures that consumers receive messages that were published even when the subscribers were not running.These messages are persisted by the JMS provider and are either sent to the consumer when it becomes active again or purged from storage if the message expires.Subscription Name (Is displayed if you selected Topic on the Basic Info page.)Enter the durable subscriber ID.This field is displayed if you selected Yes for Durable Subscriber .Time to Live (Is displayed if you selected Queue on the Basic Info page.)Specify the time to live (the amount of time before a message expires and is no longer available for consumption).Chapter 3 Configuration for Queue or Topic Page 3-2Element Description Delivery Mode (Is displayed if you selected Queue on the Basic Info page.)Persistent : Specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber.A durable subscriber is a consumed message with a durable subscriber ID.A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages.Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active.Select one of the patterns of Message SelectorSelect the pattern to use.After selecting a pattern, you can manually edit the value, if necessary. |
However, a durable subscriber downloads stored messages when it reconnects.This ensures that consumers receive messages that were published even when the subscribers were not running.These messages are persisted by the JMS provider and are either sent to the consumer when it becomes active again or purged from storage if the message expires.Subscription Name (Is displayed if you selected Topic on the Basic Info page.)Enter the durable subscriber ID.This field is displayed if you selected Yes for Durable Subscriber .Time to Live (Is displayed if you selected Queue on the Basic Info page.)Specify the time to live (the amount of time before a message expires and is no longer available for consumption).Chapter 3 Configuration for Queue or Topic Page 3-2Element Description Delivery Mode (Is displayed if you selected Queue on the Basic Info page.)Persistent : Specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber.A durable subscriber is a consumed message with a durable subscriber ID.A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages.Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active.Select one of the patterns of Message SelectorSelect the pattern to use.After selecting a pattern, you can manually edit the value, if necessary.The pattern filters messages based on header and property information. |
This ensures that consumers receive messages that were published even when the subscribers were not running.These messages are persisted by the JMS provider and are either sent to the consumer when it becomes active again or purged from storage if the message expires.Subscription Name (Is displayed if you selected Topic on the Basic Info page.)Enter the durable subscriber ID.This field is displayed if you selected Yes for Durable Subscriber .Time to Live (Is displayed if you selected Queue on the Basic Info page.)Specify the time to live (the amount of time before a message expires and is no longer available for consumption).Chapter 3 Configuration for Queue or Topic Page 3-2Element Description Delivery Mode (Is displayed if you selected Queue on the Basic Info page.)Persistent : Specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber.A durable subscriber is a consumed message with a durable subscriber ID.A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages.Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active.Select one of the patterns of Message SelectorSelect the pattern to use.After selecting a pattern, you can manually edit the value, if necessary.The pattern filters messages based on header and property information.The message selector rule is a boolean expression. |
These messages are persisted by the JMS provider and are either sent to the consumer when it becomes active again or purged from storage if the message expires.Subscription Name (Is displayed if you selected Topic on the Basic Info page.)Enter the durable subscriber ID.This field is displayed if you selected Yes for Durable Subscriber .Time to Live (Is displayed if you selected Queue on the Basic Info page.)Specify the time to live (the amount of time before a message expires and is no longer available for consumption).Chapter 3 Configuration for Queue or Topic Page 3-2Element Description Delivery Mode (Is displayed if you selected Queue on the Basic Info page.)Persistent : Specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber.A durable subscriber is a consumed message with a durable subscriber ID.A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages.Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active.Select one of the patterns of Message SelectorSelect the pattern to use.After selecting a pattern, you can manually edit the value, if necessary.The pattern filters messages based on header and property information.The message selector rule is a boolean expression.If the expression is true, the message is consumed. |
Subscription Name (Is displayed if you selected Topic on the Basic Info page.)Enter the durable subscriber ID.This field is displayed if you selected Yes for Durable Subscriber .Time to Live (Is displayed if you selected Queue on the Basic Info page.)Specify the time to live (the amount of time before a message expires and is no longer available for consumption).Chapter 3 Configuration for Queue or Topic Page 3-2Element Description Delivery Mode (Is displayed if you selected Queue on the Basic Info page.)Persistent : Specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber.A durable subscriber is a consumed message with a durable subscriber ID.A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages.Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active.Select one of the patterns of Message SelectorSelect the pattern to use.After selecting a pattern, you can manually edit the value, if necessary.The pattern filters messages based on header and property information.The message selector rule is a boolean expression.If the expression is true, the message is consumed.If the expression is false, the message is rejected. |
)Enter the durable subscriber ID.This field is displayed if you selected Yes for Durable Subscriber .Time to Live (Is displayed if you selected Queue on the Basic Info page.)Specify the time to live (the amount of time before a message expires and is no longer available for consumption).Chapter 3 Configuration for Queue or Topic Page 3-2Element Description Delivery Mode (Is displayed if you selected Queue on the Basic Info page.)Persistent : Specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber.A durable subscriber is a consumed message with a durable subscriber ID.A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages.Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active.Select one of the patterns of Message SelectorSelect the pattern to use.After selecting a pattern, you can manually edit the value, if necessary.The pattern filters messages based on header and property information.The message selector rule is a boolean expression.If the expression is true, the message is consumed.If the expression is false, the message is rejected.Do you want to define a schema for this endpoint?Select whether to define a schema. |
This field is displayed if you selected Yes for Durable Subscriber .Time to Live (Is displayed if you selected Queue on the Basic Info page.)Specify the time to live (the amount of time before a message expires and is no longer available for consumption).Chapter 3 Configuration for Queue or Topic Page 3-2Element Description Delivery Mode (Is displayed if you selected Queue on the Basic Info page.)Persistent : Specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber.A durable subscriber is a consumed message with a durable subscriber ID.A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages.Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active.Select one of the patterns of Message SelectorSelect the pattern to use.After selecting a pattern, you can manually edit the value, if necessary.The pattern filters messages based on header and property information.The message selector rule is a boolean expression.If the expression is true, the message is consumed.If the expression is false, the message is rejected.Do you want to define a schema for this endpoint?Select whether to define a schema.This field is only applicable if you selected TextMessage as the Message Type . |
Time to Live (Is displayed if you selected Queue on the Basic Info page.)Specify the time to live (the amount of time before a message expires and is no longer available for consumption).Chapter 3 Configuration for Queue or Topic Page 3-2Element Description Delivery Mode (Is displayed if you selected Queue on the Basic Info page.)Persistent : Specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber.A durable subscriber is a consumed message with a durable subscriber ID.A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages.Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active.Select one of the patterns of Message SelectorSelect the pattern to use.After selecting a pattern, you can manually edit the value, if necessary.The pattern filters messages based on header and property information.The message selector rule is a boolean expression.If the expression is true, the message is consumed.If the expression is false, the message is rejected.Do you want to define a schema for this endpoint?Select whether to define a schema.This field is only applicable if you selected TextMessage as the Message Type .If you select Yes, a field is displayed for selecting a schema file. |
)Specify the time to live (the amount of time before a message expires and is no longer available for consumption).Chapter 3 Configuration for Queue or Topic Page 3-2Element Description Delivery Mode (Is displayed if you selected Queue on the Basic Info page.)Persistent : Specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber.A durable subscriber is a consumed message with a durable subscriber ID.A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages.Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active.Select one of the patterns of Message SelectorSelect the pattern to use.After selecting a pattern, you can manually edit the value, if necessary.The pattern filters messages based on header and property information.The message selector rule is a boolean expression.If the expression is true, the message is consumed.If the expression is false, the message is rejected.Do you want to define a schema for this endpoint?Select whether to define a schema.This field is only applicable if you selected TextMessage as the Message Type .If you select Yes, a field is displayed for selecting a schema file.Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter. |
)Persistent : Specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber.A durable subscriber is a consumed message with a durable subscriber ID.A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages.Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active.Select one of the patterns of Message SelectorSelect the pattern to use.After selecting a pattern, you can manually edit the value, if necessary.The pattern filters messages based on header and property information.The message selector rule is a boolean expression.If the expression is true, the message is consumed.If the expression is false, the message is rejected.Do you want to define a schema for this endpoint?Select whether to define a schema.This field is only applicable if you selected TextMessage as the Message Type .If you select Yes, a field is displayed for selecting a schema file.Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter.You can also specify custom headers. |
A durable subscriber is a consumed message with a durable subscriber ID.A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages.Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active.Select one of the patterns of Message SelectorSelect the pattern to use.After selecting a pattern, you can manually edit the value, if necessary.The pattern filters messages based on header and property information.The message selector rule is a boolean expression.If the expression is true, the message is consumed.If the expression is false, the message is rejected.Do you want to define a schema for this endpoint?Select whether to define a schema.This field is only applicable if you selected TextMessage as the Message Type .If you select Yes, a field is displayed for selecting a schema file.Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter.You can also specify custom headers.Element Description Select Headers Begin typing the name to filter the display of standard headers. |
A durable subscriber downloads messages that have been stored in the persistent publisher, and does not have to remain active at all times to receive all the messages.Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active.Select one of the patterns of Message SelectorSelect the pattern to use.After selecting a pattern, you can manually edit the value, if necessary.The pattern filters messages based on header and property information.The message selector rule is a boolean expression.If the expression is true, the message is consumed.If the expression is false, the message is rejected.Do you want to define a schema for this endpoint?Select whether to define a schema.This field is only applicable if you selected TextMessage as the Message Type .If you select Yes, a field is displayed for selecting a schema file.Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter.You can also specify custom headers.Element Description Select Headers Begin typing the name to filter the display of standard headers.Available Headers Select the headers to use. |
Nonpersistent : A nondurable subscriber loses any messages that are produced when the adapter is not active.Select one of the patterns of Message SelectorSelect the pattern to use.After selecting a pattern, you can manually edit the value, if necessary.The pattern filters messages based on header and property information.The message selector rule is a boolean expression.If the expression is true, the message is consumed.If the expression is false, the message is rejected.Do you want to define a schema for this endpoint?Select whether to define a schema.This field is only applicable if you selected TextMessage as the Message Type .If you select Yes, a field is displayed for selecting a schema file.Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter.You can also specify custom headers.Element Description Select Headers Begin typing the name to filter the display of standard headers.Available Headers Select the headers to use.Selected Headers Displays the selected headers. |
Select one of the patterns of Message SelectorSelect the pattern to use.After selecting a pattern, you can manually edit the value, if necessary.The pattern filters messages based on header and property information.The message selector rule is a boolean expression.If the expression is true, the message is consumed.If the expression is false, the message is rejected.Do you want to define a schema for this endpoint?Select whether to define a schema.This field is only applicable if you selected TextMessage as the Message Type .If you select Yes, a field is displayed for selecting a schema file.Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter.You can also specify custom headers.Element Description Select Headers Begin typing the name to filter the display of standard headers.Available Headers Select the headers to use.Selected Headers Displays the selected headers.Custom JMS Header Name Add custom headers, if required. |
After selecting a pattern, you can manually edit the value, if necessary.The pattern filters messages based on header and property information.The message selector rule is a boolean expression.If the expression is true, the message is consumed.If the expression is false, the message is rejected.Do you want to define a schema for this endpoint?Select whether to define a schema.This field is only applicable if you selected TextMessage as the Message Type .If you select Yes, a field is displayed for selecting a schema file.Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter.You can also specify custom headers.Element Description Select Headers Begin typing the name to filter the display of standard headers.Available Headers Select the headers to use.Selected Headers Displays the selected headers.Custom JMS Header Name Add custom headers, if required.Summary Page You can review the specified adapter configuration values on the Summary page. |
The pattern filters messages based on header and property information.The message selector rule is a boolean expression.If the expression is true, the message is consumed.If the expression is false, the message is rejected.Do you want to define a schema for this endpoint?Select whether to define a schema.This field is only applicable if you selected TextMessage as the Message Type .If you select Yes, a field is displayed for selecting a schema file.Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter.You can also specify custom headers.Element Description Select Headers Begin typing the name to filter the display of standard headers.Available Headers Select the headers to use.Selected Headers Displays the selected headers.Custom JMS Header Name Add custom headers, if required.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard. |
The message selector rule is a boolean expression.If the expression is true, the message is consumed.If the expression is false, the message is rejected.Do you want to define a schema for this endpoint?Select whether to define a schema.This field is only applicable if you selected TextMessage as the Message Type .If you select Yes, a field is displayed for selecting a schema file.Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter.You can also specify custom headers.Element Description Select Headers Begin typing the name to filter the display of standard headers.Available Headers Select the headers to use.Selected Headers Displays the selected headers.Custom JMS Header Name Add custom headers, if required.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter. |
If the expression is true, the message is consumed.If the expression is false, the message is rejected.Do you want to define a schema for this endpoint?Select whether to define a schema.This field is only applicable if you selected TextMessage as the Message Type .If you select Yes, a field is displayed for selecting a schema file.Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter.You can also specify custom headers.Element Description Select Headers Begin typing the name to filter the display of standard headers.Available Headers Select the headers to use.Selected Headers Displays the selected headers.Custom JMS Header Name Add custom headers, if required.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed. |
If the expression is false, the message is rejected.Do you want to define a schema for this endpoint?Select whether to define a schema.This field is only applicable if you selected TextMessage as the Message Type .If you select Yes, a field is displayed for selecting a schema file.Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter.You can also specify custom headers.Element Description Select Headers Begin typing the name to filter the display of standard headers.Available Headers Select the headers to use.Selected Headers Displays the selected headers.Custom JMS Header Name Add custom headers, if required.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file. |
Do you want to define a schema for this endpoint?Select whether to define a schema.This field is only applicable if you selected TextMessage as the Message Type .If you select Yes, a field is displayed for selecting a schema file.Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter.You can also specify custom headers.Element Description Select Headers Begin typing the name to filter the display of standard headers.Available Headers Select the headers to use.Selected Headers Displays the selected headers.Custom JMS Header Name Add custom headers, if required.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back. |
This field is only applicable if you selected TextMessage as the Message Type .If you select Yes, a field is displayed for selecting a schema file.Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter.You can also specify custom headers.Element Description Select Headers Begin typing the name to filter the display of standard headers.Available Headers Select the headers to use.Selected Headers Displays the selected headers.Custom JMS Header Name Add custom headers, if required.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns. |
If you select Yes, a field is displayed for selecting a schema file.Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter.You can also specify custom headers.Element Description Select Headers Begin typing the name to filter the display of standard headers.Available Headers Select the headers to use.Selected Headers Displays the selected headers.Custom JMS Header Name Add custom headers, if required.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns.Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ). |
Headers Page Select the standard (predefined) headers to use for the operation with the IBM MQ Series JMS Adapter.You can also specify custom headers.Element Description Select Headers Begin typing the name to filter the display of standard headers.Available Headers Select the headers to use.Selected Headers Displays the selected headers.Custom JMS Header Name Add custom headers, if required.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns.Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ).From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ). |
You can also specify custom headers.Element Description Select Headers Begin typing the name to filter the display of standard headers.Available Headers Select the headers to use.Selected Headers Displays the selected headers.Custom JMS Header Name Add custom headers, if required.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns.Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ).From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ).1.Configure the IBM MQ Series JMS Adapter on the Connections page. |
Element Description Select Headers Begin typing the name to filter the display of standard headers.Available Headers Select the headers to use.Selected Headers Displays the selected headers.Custom JMS Header Name Add custom headers, if required.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns.Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ).From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.2.Create the an application-driven integration. |
Available Headers Select the headers to use.Selected Headers Displays the selected headers.Custom JMS Header Name Add custom headers, if required.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns.Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ).From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.2.Create the an application-driven integration.This is the first of two integrations you create. |
Selected Headers Displays the selected headers.Custom JMS Header Name Add custom headers, if required.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns.Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ).From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.2.Create the an application-driven integration.This is the first of two integrations you create.The second is described in the second use case. |
Custom JMS Header Name Add custom headers, if required.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns.Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ).From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.2.Create the an application-driven integration.This is the first of two integrations you create.The second is described in the second use case.See Use a Topic to Subscribe to a Message . |
Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns.Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ).From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.2.Create the an application-driven integration.This is the first of two integrations you create.The second is described in the second use case.See Use a Topic to Subscribe to a Message .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration. |
Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns.Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ).From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.2.Create the an application-driven integration.This is the first of two integrations you create.The second is described in the second use case.See Use a Topic to Subscribe to a Message .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed. |
The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns.Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ).From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.2.Create the an application-driven integration.This is the first of two integrations you create.The second is described in the second use case.See Use a Topic to Subscribe to a Message .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Queue for the Destination Type is selected. |
For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns.Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ).From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.2.Create the an application-driven integration.This is the first of two integrations you create.The second is described in the second use case.See Use a Topic to Subscribe to a Message .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Queue for the Destination Type is selected.5.On the Configuration page, the following details are specified for this use case. |
For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns.Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ).From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.2.Create the an application-driven integration.This is the first of two integrations you create.The second is described in the second use case.See Use a Topic to Subscribe to a Message .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Queue for the Destination Type is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary. |
To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns.Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ).From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.2.Create the an application-driven integration.This is the first of two integrations you create.The second is described in the second use case.See Use a Topic to Subscribe to a Message .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Queue for the Destination Type is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A queue of your choice for the Destination Name (for this example, INQ is selected). |
To cancel your configuration details, click Cancel.Chapter 3 Headers Page 3-34 Implement Common Patterns Using the IBM MQ Series JMS Adapter You can use the IBM MQ Series JMS Adapter to implement the following common patterns.Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ).From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.2.Create the an application-driven integration.This is the first of two integrations you create.The second is described in the second use case.See Use a Topic to Subscribe to a Message .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Queue for the Destination Type is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A queue of your choice for the Destination Name (for this example, INQ is selected).TextMessage for the Message Type value. |
Topics: Put a Message in an Inbound Queue Use a Topic to Subscribe to a Message Put a Message in an Inbound Queue This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ).From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.2.Create the an application-driven integration.This is the first of two integrations you create.The second is described in the second use case.See Use a Topic to Subscribe to a Message .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Queue for the Destination Type is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A queue of your choice for the Destination Name (for this example, INQ is selected).TextMessage for the Message Type value.JMSPriority=8 for the Message Selector value. |
From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.2.Create the an application-driven integration.This is the first of two integrations you create.The second is described in the second use case.See Use a Topic to Subscribe to a Message .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Queue for the Destination Type is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A queue of your choice for the Destination Name (for this example, INQ is selected).TextMessage for the Message Type value.JMSPriority=8 for the Message Selector value.This means that only messages with a priority of 8 are consumed. |
1.Configure the IBM MQ Series JMS Adapter on the Connections page.2.Create the an application-driven integration.This is the first of two integrations you create.The second is described in the second use case.See Use a Topic to Subscribe to a Message .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Queue for the Destination Type is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A queue of your choice for the Destination Name (for this example, INQ is selected).TextMessage for the Message Type value.JMSPriority=8 for the Message Selector value.This means that only messages with a priority of 8 are consumed.Yes for the Do you want to specify the structure for the payload value. |
2.Create the an application-driven integration.This is the first of two integrations you create.The second is described in the second use case.See Use a Topic to Subscribe to a Message .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Queue for the Destination Type is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A queue of your choice for the Destination Name (for this example, INQ is selected).TextMessage for the Message Type value.JMSPriority=8 for the Message Selector value.This means that only messages with a priority of 8 are consumed.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected). |
This is the first of two integrations you create.The second is described in the second use case.See Use a Topic to Subscribe to a Message .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Queue for the Destination Type is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A queue of your choice for the Destination Name (for this example, INQ is selected).TextMessage for the Message Type value.JMSPriority=8 for the Message Selector value.This means that only messages with a priority of 8 are consumed.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).6.On the Headers page, JMSType for the standard header and department for the custom header are selected. |
The second is described in the second use case.See Use a Topic to Subscribe to a Message .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Queue for the Destination Type is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A queue of your choice for the Destination Name (for this example, INQ is selected).TextMessage for the Message Type value.JMSPriority=8 for the Message Selector value.This means that only messages with a priority of 8 are consumed.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).6.On the Headers page, JMSType for the standard header and department for the custom header are selected.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration. |
See Use a Topic to Subscribe to a Message .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Queue for the Destination Type is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A queue of your choice for the Destination Name (for this example, INQ is selected).TextMessage for the Message Type value.JMSPriority=8 for the Message Selector value.This means that only messages with a priority of 8 are consumed.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).6.On the Headers page, JMSType for the standard header and department for the custom header are selected.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Topic for the Destination Type value is selected. |
3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Queue for the Destination Type is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A queue of your choice for the Destination Name (for this example, INQ is selected).TextMessage for the Message Type value.JMSPriority=8 for the Message Selector value.This means that only messages with a priority of 8 are consumed.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).6.On the Headers page, JMSType for the standard header and department for the custom header are selected.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Topic for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value. |
The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Queue for the Destination Type is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A queue of your choice for the Destination Name (for this example, INQ is selected).TextMessage for the Message Type value.JMSPriority=8 for the Message Selector value.This means that only messages with a priority of 8 are consumed.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).6.On the Headers page, JMSType for the standard header and department for the custom header are selected.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Topic for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value.4-1TextMessage for the Message Type value. |
4.On the Basic Info page, Queue for the Destination Type is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A queue of your choice for the Destination Name (for this example, INQ is selected).TextMessage for the Message Type value.JMSPriority=8 for the Message Selector value.This means that only messages with a priority of 8 are consumed.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).6.On the Headers page, JMSType for the standard header and department for the custom header are selected.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Topic for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value.4-1TextMessage for the Message Type value.Priority [0 - 9] for the Message Selector value. |
5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A queue of your choice for the Destination Name (for this example, INQ is selected).TextMessage for the Message Type value.JMSPriority=8 for the Message Selector value.This means that only messages with a priority of 8 are consumed.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).6.On the Headers page, JMSType for the standard header and department for the custom header are selected.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Topic for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value.4-1TextMessage for the Message Type value.Priority [0 - 9] for the Message Selector value.Yes for the Do you want to specify the structure for the payload value. |
Your selections can vary.A queue of your choice for the Destination Name (for this example, INQ is selected).TextMessage for the Message Type value.JMSPriority=8 for the Message Selector value.This means that only messages with a priority of 8 are consumed.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).6.On the Headers page, JMSType for the standard header and department for the custom header are selected.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Topic for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value.4-1TextMessage for the Message Type value.Priority [0 - 9] for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.singleString.xsd for the Schema File value. |
A queue of your choice for the Destination Name (for this example, INQ is selected).TextMessage for the Message Type value.JMSPriority=8 for the Message Selector value.This means that only messages with a priority of 8 are consumed.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).6.On the Headers page, JMSType for the standard header and department for the custom header are selected.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Topic for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value.4-1TextMessage for the Message Type value.Priority [0 - 9] for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.singleString.xsd for the Schema File value.10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected. |
TextMessage for the Message Type value.JMSPriority=8 for the Message Selector value.This means that only messages with a priority of 8 are consumed.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).6.On the Headers page, JMSType for the standard header and department for the custom header are selected.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Topic for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value.4-1TextMessage for the Message Type value.Priority [0 - 9] for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.singleString.xsd for the Schema File value.10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound queue and assigned to the outbound topic. |
JMSPriority=8 for the Message Selector value.This means that only messages with a priority of 8 are consumed.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).6.On the Headers page, JMSType for the standard header and department for the custom header are selected.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Topic for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value.4-1TextMessage for the Message Type value.Priority [0 - 9] for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.singleString.xsd for the Schema File value.10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound queue and assigned to the outbound topic.11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element. |
This means that only messages with a priority of 8 are consumed.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).6.On the Headers page, JMSType for the standard header and department for the custom header are selected.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Topic for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value.4-1TextMessage for the Message Type value.Priority [0 - 9] for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.singleString.xsd for the Schema File value.10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound queue and assigned to the outbound topic.11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element. |
Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).6.On the Headers page, JMSType for the standard header and department for the custom header are selected.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Topic for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value.4-1TextMessage for the Message Type value.Priority [0 - 9] for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.singleString.xsd for the Schema File value.10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound queue and assigned to the outbound topic.11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is manually set to 4. |
A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).6.On the Headers page, JMSType for the standard header and department for the custom header are selected.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Topic for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value.4-1TextMessage for the Message Type value.Priority [0 - 9] for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.singleString.xsd for the Schema File value.10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound queue and assigned to the outbound topic.11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is manually set to 4.When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8. |
6.On the Headers page, JMSType for the standard header and department for the custom header are selected.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Topic for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value.4-1TextMessage for the Message Type value.Priority [0 - 9] for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.singleString.xsd for the Schema File value.10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound queue and assigned to the outbound topic.11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is manually set to 4.When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8.If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic. |
7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Topic for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value.4-1TextMessage for the Message Type value.Priority [0 - 9] for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.singleString.xsd for the Schema File value.10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound queue and assigned to the outbound topic.11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is manually set to 4.When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8.If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration. |
8.On the Basic Info page, Topic for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value.4-1TextMessage for the Message Type value.Priority [0 - 9] for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.singleString.xsd for the Schema File value.10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound queue and assigned to the outbound topic.11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is manually set to 4.When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8.If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration.Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ). |
9.On the Configuration page, the following details are specified for this use case: TOPIN for the Destination Name value.4-1TextMessage for the Message Type value.Priority [0 - 9] for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.singleString.xsd for the Schema File value.10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound queue and assigned to the outbound topic.11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is manually set to 4.When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8.If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration.Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ).1.Configure the IBM MQ Series JMS Adapter on the Connections page. |
4-1TextMessage for the Message Type value.Priority [0 - 9] for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.singleString.xsd for the Schema File value.10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound queue and assigned to the outbound topic.11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is manually set to 4.When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8.If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration.Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.See Create a Connection . |
Priority [0 - 9] for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.singleString.xsd for the Schema File value.10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound queue and assigned to the outbound topic.11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is manually set to 4.When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8.If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration.Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.See Create a Connection .2.Create an application-driven integration. |
Yes for the Do you want to specify the structure for the payload value.singleString.xsd for the Schema File value.10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound queue and assigned to the outbound topic.11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is manually set to 4.When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8.If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration.Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.See Create a Connection .2.Create an application-driven integration.This is the second of two integrations that you create. |
singleString.xsd for the Schema File value.10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound queue and assigned to the outbound topic.11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is manually set to 4.When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8.If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration.Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.See Create a Connection .2.Create an application-driven integration.This is the second of two integrations that you create.The first is described in the first use case. |
10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound queue and assigned to the outbound topic.11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is manually set to 4.When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8.If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration.Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.See Create a Connection .2.Create an application-driven integration.This is the second of two integrations that you create.The first is described in the first use case.See Put a Message in an Inbound Queue . |
These headers are captured from the inbound queue and assigned to the outbound topic.11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is manually set to 4.When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8.If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration.Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.See Create a Connection .2.Create an application-driven integration.This is the second of two integrations that you create.The first is described in the first use case.See Put a Message in an Inbound Queue .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration. |
11.In the mapper, the following mappings are specified: Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is manually set to 4.When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8.If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration.Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.See Create a Connection .2.Create an application-driven integration.This is the second of two integrations that you create.The first is described in the first use case.See Put a Message in an Inbound Queue .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed. |
Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is manually set to 4.When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8.If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration.Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.See Create a Connection .2.Create an application-driven integration.This is the second of two integrations that you create.The first is described in the first use case.See Put a Message in an Inbound Queue .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Topic for the Destination Type value is selected. |
Target JMSPriority element is manually set to 4.When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8.If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration.Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.See Create a Connection .2.Create an application-driven integration.This is the second of two integrations that you create.The first is described in the first use case.See Put a Message in an Inbound Queue .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Topic for the Destination Type value is selected.5.On the Configuration page, the following details are specified for this use case. |
When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8.If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration.Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.See Create a Connection .2.Create an application-driven integration.This is the second of two integrations that you create.The first is described in the first use case.See Put a Message in an Inbound Queue .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Topic for the Destination Type value is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary. |
If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration.Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.See Create a Connection .2.Create an application-driven integration.This is the second of two integrations that you create.The first is described in the first use case.See Put a Message in an Inbound Queue .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Topic for the Destination Type value is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A topic of your choice for the Destination Name value (for this example, TOPIN is selected). |
Use a Topic to Subscribe to a Message This use case describes how to create an integration that uses the same topic (for this example, named TOPIN ) used in the first integration to subscribe to a message that was published from that integration.Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.See Create a Connection .2.Create an application-driven integration.This is the second of two integrations that you create.The first is described in the first use case.See Put a Message in an Inbound Queue .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Topic for the Destination Type value is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A topic of your choice for the Destination Name value (for this example, TOPIN is selected).TextMessage for the Message Type value. |
Once the message has been subscribed, the same message is consumed and delivered to the outbound queue (for this example, named OUTQ ).1.Configure the IBM MQ Series JMS Adapter on the Connections page.See Create a Connection .2.Create an application-driven integration.This is the second of two integrations that you create.The first is described in the first use case.See Put a Message in an Inbound Queue .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Topic for the Destination Type value is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A topic of your choice for the Destination Name value (for this example, TOPIN is selected).TextMessage for the Message Type value.No for the Durable Subscriber value. |
1.Configure the IBM MQ Series JMS Adapter on the Connections page.See Create a Connection .2.Create an application-driven integration.This is the second of two integrations that you create.The first is described in the first use case.See Put a Message in an Inbound Queue .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Topic for the Destination Type value is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A topic of your choice for the Destination Name value (for this example, TOPIN is selected).TextMessage for the Message Type value.No for the Durable Subscriber value.No value is set for the Message Selector value. |
See Create a Connection .2.Create an application-driven integration.This is the second of two integrations that you create.The first is described in the first use case.See Put a Message in an Inbound Queue .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Topic for the Destination Type value is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A topic of your choice for the Destination Name value (for this example, TOPIN is selected).TextMessage for the Message Type value.No for the Durable Subscriber value.No value is set for the Message Selector value.Yes for the Do you want to specify the structure for the payload value. |
2.Create an application-driven integration.This is the second of two integrations that you create.The first is described in the first use case.See Put a Message in an Inbound Queue .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Topic for the Destination Type value is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A topic of your choice for the Destination Name value (for this example, TOPIN is selected).TextMessage for the Message Type value.No for the Durable Subscriber value.No value is set for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected. |
This is the second of two integrations that you create.The first is described in the first use case.See Put a Message in an Inbound Queue .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Topic for the Destination Type value is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A topic of your choice for the Destination Name value (for this example, TOPIN is selected).TextMessage for the Message Type value.No for the Durable Subscriber value.No value is set for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are sent to the outbound queue. |
The first is described in the first use case.See Put a Message in an Inbound Queue .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Topic for the Destination Type value is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A topic of your choice for the Destination Name value (for this example, TOPIN is selected).TextMessage for the Message Type value.No for the Durable Subscriber value.No value is set for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are sent to the outbound queue.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration. |
See Put a Message in an Inbound Queue .3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Topic for the Destination Type value is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A topic of your choice for the Destination Name value (for this example, TOPIN is selected).TextMessage for the Message Type value.No for the Durable Subscriber value.No value is set for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are sent to the outbound queue.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Queue for the Destination Type value is selected. |
3.Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Topic for the Destination Type value is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A topic of your choice for the Destination Name value (for this example, TOPIN is selected).TextMessage for the Message Type value.No for the Durable Subscriber value.No value is set for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are sent to the outbound queue.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Queue for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value. |
The Adapter Endpoint Configuration Wizard is displayed.4.On the Basic Info page, Topic for the Destination Type value is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A topic of your choice for the Destination Name value (for this example, TOPIN is selected).TextMessage for the Message Type value.No for the Durable Subscriber value.No value is set for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are sent to the outbound queue.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Queue for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value.TextMessage for the Message Type value. |
4.On the Basic Info page, Topic for the Destination Type value is selected.5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A topic of your choice for the Destination Name value (for this example, TOPIN is selected).TextMessage for the Message Type value.No for the Durable Subscriber value.No value is set for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are sent to the outbound queue.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Queue for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value.TextMessage for the Message Type value.Persistent for the Delivery Mode value. |
5.On the Configuration page, the following details are specified for this use case.Your selections can vary.A topic of your choice for the Destination Name value (for this example, TOPIN is selected).TextMessage for the Message Type value.No for the Durable Subscriber value.No value is set for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are sent to the outbound queue.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Queue for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value.TextMessage for the Message Type value.Persistent for the Delivery Mode value.Priority=[0 - 9] for the Message Selector value. |
Your selections can vary.A topic of your choice for the Destination Name value (for this example, TOPIN is selected).TextMessage for the Message Type value.No for the Durable Subscriber value.No value is set for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are sent to the outbound queue.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Queue for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value.TextMessage for the Message Type value.Persistent for the Delivery Mode value.Priority=[0 - 9] for the Message Selector value.Seconds for the Time to Live value. |
A topic of your choice for the Destination Name value (for this example, TOPIN is selected).TextMessage for the Message Type value.No for the Durable Subscriber value.No value is set for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are sent to the outbound queue.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Queue for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value.TextMessage for the Message Type value.Persistent for the Delivery Mode value.Priority=[0 - 9] for the Message Selector value.Seconds for the Time to Live value.Yes for the Do you want to specify the structure for the payload value. |
TextMessage for the Message Type value.No for the Durable Subscriber value.No value is set for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are sent to the outbound queue.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Queue for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value.TextMessage for the Message Type value.Persistent for the Delivery Mode value.Priority=[0 - 9] for the Message Selector value.Seconds for the Time to Live value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected). |
No for the Durable Subscriber value.No value is set for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are sent to the outbound queue.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Queue for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value.TextMessage for the Message Type value.Persistent for the Delivery Mode value.Priority=[0 - 9] for the Message Selector value.Seconds for the Time to Live value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected. |
No value is set for the Message Selector value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are sent to the outbound queue.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Queue for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value.TextMessage for the Message Type value.Persistent for the Delivery Mode value.Priority=[0 - 9] for the Message Selector value.Seconds for the Time to Live value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound topic and assigned to the outbound queue. |
Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are sent to the outbound queue.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Queue for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value.TextMessage for the Message Type value.Persistent for the Delivery Mode value.Priority=[0 - 9] for the Message Selector value.Seconds for the Time to Live value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound topic and assigned to the outbound queue.11.In the mapper, the messages coming from the inbound topic are mapped to the outbound queue. |
A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).Chapter 4 Use a Topic to Subscribe to a Message 4-26.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are sent to the outbound queue.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Queue for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value.TextMessage for the Message Type value.Persistent for the Delivery Mode value.Priority=[0 - 9] for the Message Selector value.Seconds for the Time to Live value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound topic and assigned to the outbound queue.11.In the mapper, the messages coming from the inbound topic are mapped to the outbound queue.Source JMSType element is mapped to the target JMSType element. |
These headers are sent to the outbound queue.7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Queue for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value.TextMessage for the Message Type value.Persistent for the Delivery Mode value.Priority=[0 - 9] for the Message Selector value.Seconds for the Time to Live value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound topic and assigned to the outbound queue.11.In the mapper, the messages coming from the inbound topic are mapped to the outbound queue.Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element. |
7.Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.8.On the Basic Info page, Queue for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value.TextMessage for the Message Type value.Persistent for the Delivery Mode value.Priority=[0 - 9] for the Message Selector value.Seconds for the Time to Live value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound topic and assigned to the outbound queue.11.In the mapper, the messages coming from the inbound topic are mapped to the outbound queue.Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is mapped to the target JMSPriority . |
8.On the Basic Info page, Queue for the Destination Type value is selected.9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value.TextMessage for the Message Type value.Persistent for the Delivery Mode value.Priority=[0 - 9] for the Message Selector value.Seconds for the Time to Live value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound topic and assigned to the outbound queue.11.In the mapper, the messages coming from the inbound topic are mapped to the outbound queue.Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is mapped to the target JMSPriority .12.Activate both integrations. |
9.On the Configuration page, the following details are specified for this use case: OUTQ for the Destination Name value.TextMessage for the Message Type value.Persistent for the Delivery Mode value.Priority=[0 - 9] for the Message Selector value.Seconds for the Time to Live value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound topic and assigned to the outbound queue.11.In the mapper, the messages coming from the inbound topic are mapped to the outbound queue.Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is mapped to the target JMSPriority .12.Activate both integrations.13.Put an XML message in the inbound queue ( INQ) to be consumed by this integration. |
TextMessage for the Message Type value.Persistent for the Delivery Mode value.Priority=[0 - 9] for the Message Selector value.Seconds for the Time to Live value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound topic and assigned to the outbound queue.11.In the mapper, the messages coming from the inbound topic are mapped to the outbound queue.Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is mapped to the target JMSPriority .12.Activate both integrations.13.Put an XML message in the inbound queue ( INQ) to be consumed by this integration.In the first integration, the message is dequeued and published to the outbound topic (TOPIN ). |
Persistent for the Delivery Mode value.Priority=[0 - 9] for the Message Selector value.Seconds for the Time to Live value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound topic and assigned to the outbound queue.11.In the mapper, the messages coming from the inbound topic are mapped to the outbound queue.Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is mapped to the target JMSPriority .12.Activate both integrations.13.Put an XML message in the inbound queue ( INQ) to be consumed by this integration.In the first integration, the message is dequeued and published to the outbound topic (TOPIN ).In the second integration, the TOPIN topic is subscribed to any message that arrives on it. |
Priority=[0 - 9] for the Message Selector value.Seconds for the Time to Live value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound topic and assigned to the outbound queue.11.In the mapper, the messages coming from the inbound topic are mapped to the outbound queue.Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is mapped to the target JMSPriority .12.Activate both integrations.13.Put an XML message in the inbound queue ( INQ) to be consumed by this integration.In the first integration, the message is dequeued and published to the outbound topic (TOPIN ).In the second integration, the TOPIN topic is subscribed to any message that arrives on it.TOPIN consumes the message and delivers it to the OUTQ queue. |
Seconds for the Time to Live value.Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound topic and assigned to the outbound queue.11.In the mapper, the messages coming from the inbound topic are mapped to the outbound queue.Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is mapped to the target JMSPriority .12.Activate both integrations.13.Put an XML message in the inbound queue ( INQ) to be consumed by this integration.In the first integration, the message is dequeued and published to the outbound topic (TOPIN ).In the second integration, the TOPIN topic is subscribed to any message that arrives on it.TOPIN consumes the message and delivers it to the OUTQ queue.14.Check for the message and the headers such as JMSType and JMSPriority in the OUTQ queue.Chapter 4 Use a Topic to Subscribe to a Message 4-35 Troubleshoot the IBM MQ Series JMS Adapter Review the following topics to learn about troubleshooting issues with the IBM MQ Series JMS Adapter. |
Yes for the Do you want to specify the structure for the payload value.A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).10.On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected.These headers are captured from the inbound topic and assigned to the outbound queue.11.In the mapper, the messages coming from the inbound topic are mapped to the outbound queue.Source JMSType element is mapped to the target JMSType element.Source JMSProperty department element is mapped to the target JMSProperty department element.Target JMSPriority element is mapped to the target JMSPriority .12.Activate both integrations.13.Put an XML message in the inbound queue ( INQ) to be consumed by this integration.In the first integration, the message is dequeued and published to the outbound topic (TOPIN ).In the second integration, the TOPIN topic is subscribed to any message that arrives on it.TOPIN consumes the message and delivers it to the OUTQ queue.14.Check for the message and the headers such as JMSType and JMSPriority in the OUTQ queue.Chapter 4 Use a Topic to Subscribe to a Message 4-35 Troubleshoot the IBM MQ Series JMS Adapter Review the following topics to learn about troubleshooting issues with the IBM MQ Series JMS Adapter.Topics: Troubleshoot Connection Errors Additional integration troubleshooting information is provided. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.