Planning your queue connectors

Consider the following points when you create and map queue data source connectors.

• Opportunity Detect supports SSL communication only with the WebSphere MQ queue server. If you are using another type of queue server, your queue server must not be configured to use SSL.
• Ensure that at least one queue is created on your queue server for each queue connector that you plan to use.
• A workspace has only one Outcome data source, regardless of how many Action components it contains.
• You must map one queue connector to each transaction and Outcome data source. Optionally, you can map more than one queue connector to the transaction and Outcome data sources.
• A non-shared queue connector can be used by only one deployment. The system enforces this constraint.
• A non-shared connector cannot be mapped to a data source when you configure a server group. It can be mapped in a deployment configuration only.
• A shared queue connector can be used across multiple deployment configurations.
• Shared connectors are mapped when you configure a server group. You can change this mapping in a deployment configuration.
• For Outcomes, you would typically use multiple non-shared queues if you have multiple consumers of the Outcomes, and use a shared queue if you have only a single consumer of the Outcomes.
• For testing, it is typical to use shared data source connectors for your transaction data, to reduce the time required to set up separate queues. Because the message includes the configuration ID, the transaction data is sent to the appropriate queue. For production, you should generally use non-shared connectors for your transaction data.