IBM E02HMLL-I Implementation Guide - Page 151
ControllerTraceLevel, DeliveryQueue, DeliveryTransport, DuplicateEventElimination
View all IBM E02HMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 151 highlights
However, if the destination application's application-specific component becomes unavailable after the connector controller forwards a service call request to it, the connector controller fails the request. If this property is set to false, the connector controller begins failing all service call requests as soon as it detects that the destination application-specific component is unavailable. The default is true. ControllerTraceLevel Level of trace messages for the connector controller. The default is 0. DeliveryQueue Applicable only if DeliveryTransport is JMS. The queue that is used by the connector to send business objects to InterChange Server Express. The default value is CONNECTORNAME/DELIVERYQUEUE. DeliveryTransport Specifies the transport mechanism for the delivery of events. Possible values are 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 IDL. JMS: 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. DuplicateEventElimination When you set this property to true, a JMS-enabled connector can ensure that duplicate events are not delivered to the delivery queue. To use this feature, the connector must have a unique event identifier set as the business object's ObjectEventId attribute in the application-specific code. This is done during connector development. This property can also be set to false. Note: When DuplicateEventElimination is set to true, you must also configure the MonitorQueue property to enable guaranteed event delivery. Chapter 7. Configuring connectors 139