Configuration Manager - Commerce - Transport - Connection Specifications/Interaction Specifications

The Configuration Manager can only be used to configure the connection specifications for inbound transports.

Inbound connection specifications

Inbound connectors connection specifications - serial
Requests are processed from the Inbound Serial JMS Queue in the order in which they are received.
Inbound connectors connection specifications - parallel
Request are processed from the Inbound Parallel JMS Queue simultaneously. The order in which the requests are processed is not predictable. There is a "number of thread" value associated with the inbound parallel connector. This is the number of threads used to process inbound requests concurrently. For example, if the user enters 5 as the number of threads here, there will be 5 concurrent threads started to read from the inbound parallel queue.

On the advanced tab of the inbound ConnectionSpec pages, you can modify the following parameters:

AIXi5/OSiSeriesLinuxSun Solaris Operating EnvironmentWindows Connection Factory
This is the JMS Connection Factory - which maps to a WebSphere MQ Queue Manager
AIXi5/OSiSeriesLinuxSun Solaris Operating EnvironmentWindowsInbound Queue
JMS queue name of the queue from which requests from the WebSphere MQ adapter are accepted.
AIXiSeriesLinuxSun Solaris Operating EnvironmentWindows Error Queue
JMS Queue Name of the queue where requests are placed in the event of an error. When an error occurs, the original message content is placed on the error queue, with the correlation ID equal to the message ID of the original message.

Inbound interaction specifications

You should not modify the interaction specifications for inbound connectors.

Outbound connection and interaction specifications

The Configuration Manager cannot be used to configure outbound transports.

Feedback