IBM 4.6.x User Manual page 108

DeliveryTransport
The DeliveryTransport property 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.
v If the value of the RepositoryDirectory property is set to <REMOTE>, the value
v If the value of the RepositoryDirectory property is a local directory, the value
The connector sends service-call requests and administrative messages over
CORBA IIOP if the value of the RepositoryDirectory property is MQ or IDL.
The default value is JMS.
WebSphere MQ and 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:
v Asynchronous communication:
v Server side performance:
v Agent side performance:
JMS
The JMS transport mechanism 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
are listed in Connector Configurator. The properties jms.MessageBrokerName and
jms.FactoryClassName are required for this transport.
There may be a memory limitation if you use the JMS transport mechanism for a
connector in the following environment:
v AIX 5.0
v WebSphere MQ 5.3.0.1
v ICS is the integration broker
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. If your installation uses less than 768MB of
process heap size, set the following variable and property:
v Set the LDR_CNTRL environment variable in the CWSharedEnv.sh script.
96
Adapter for Siebel eBusiness Applications User Guide
of the DeliveryTransport property can be MQ, IDL, or JMS, and the default is IDL.
can be only JMS.
WebSphere MQ allows the application-specific component to poll and
persistently store events even when the server is not available.
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
prevents writing potentially large events to the repository database.
WebSphere MQ provides faster performance on the application-specific
component side. Using WebSphere MQ, the connector polling thread picks up an
event, places it in the connector queue, then picks up the next event. This is
faster than IDL, which requires the connector polling thread to pick up an event,
go across the network into the server process, store the event persistently in the
repository database, then pick up the next event.