Specifies the transport mechanism for the delivery of events.
Possible values are MQ for WebSphere MQ, IDL for CORBA
IIOP, or JMS for Java Messaging Service. The default is
IDL.
The connector sends service call requests and administrative messages over
CORBA IIOP if the value configured for the DeliveryTransport
property is MQ or IDL.
Use WebSphere MQ rather than IDL for event delivery transport, unless you
must have only one product. WebSphere MQ offers the following
advantages over IDL:
- Asynchronous communication:
WebSphere MQ allows the application-specific component to poll and
persistently store events even when the server is not available.
- Server side performance:
WebSphere MQ provides faster performance on the server side. In
optimized mode, WebSphere MQ stores only the pointer to an event in the
repository database, while the actual event remains in the WebSphere MQ
queue. This saves having to write potentially large events to the
repository database.
- Agent side performance:
WebSphere MQ provides faster performance on the application-specific
component side. Using WebSphere MQ, the connector's polling thread
picks up an event, places it in the connector's queue, then picks up the
next event. This is faster than IDL, which requires the connector's
polling thread to pick up an event, go over the network into the server
process, store the event persistently in the repository database, then pick up
the next event.
Enables communication between the connector and client connector framework
using Java Messaging Service (JMS).
If you select JMS as the delivery transport, additional JMS properties such
as jms.MessageBrokerName,
jms.FactoryClassName, jms.Password, and
jms.UserName, appear in Connector Configurator
Express. The first two of these properties are required for this
transport.
- Important:
- There may be a memory limitation if you use the JMS transport mechanism for a
connector running on InterChange Server Express.
In this environment, you may experience difficulty starting both the
connector controller (on the server side) and the connector (on the client
side) due to memory use within the WebSphere MQ client.
