The DeliveryTransport property specifies the transport mechanism for the delivery of events. For Java Messaging Service, the value is JMS.
The connector sends service-call requests and administrative messages over CORBA IIOP if the value of the RepositoryDirectory property is IDL.
The default value is 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 Express. 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 when InterChange Server Espress (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:
This script is located in the \bin directory below the product directory (<ProductDir>). Using a text editor, add the following line as the first line in the CWSharedEnv.sh script:
export LDR_CNTRL=MAXDATA=0x30000000
This line restricts heap memory usage to a maximum of 768 MB (3 segments * 256 MB). If the process memory grows larger than this limit, page swapping can occur, which can adversely affect the performance of your system.