Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 5 Configuring Adapter Services : Common Configuration Options for Adapter Services

Common Configuration Options for Adapter Services
This section explains the following common configuration options for adapter services:
The transport type (Rendezvous or JMS) you select for the runtime adapter determines transport specific service options. Only options that are compatible with a service’s transport type will be available in the Configuration Panel.
Transport Type
There are two transport types available for the runtime adapter, namely JMS and Rendezvous. After selecting the transport type, you can configure the transport specific options. Only options that are compatible with the service’s transport type appear in the Configuration Panel.
The transport can be configured to use a trusted store and identity resource for use in SSL (Secure Sockets Layer) configurations. TIBCO Rendezvous sessions and JMS topics have an SSL configuration field which uses a dialog to perform SSL configuration.
To enable and configure SSL:
1.
2.
Expand Advanced > Sessions, and then select the TIBCO Rendezvous session or JMS session.
3.
Check the Use SSL? checkbox in the Configuration Panel.
4.
Click the Configure SSL... button to do further configuration.
The SSL configuration options are explained in the online help associated with the session dialog.
Quality of Service
If you have selected Rendezvous as the transport type, then select Quality of Service.
Certified
Guarantees that every certified message reaches its intended recipient in the order sent. The message can be sent across network boundaries and, if a network fails, delivery attempts continue until it succeeds or the message times out. This is called certified message delivery.
If certified message delivery is used, data is stored in a ledger file. The size of the ledger depends on several factors, the most important one is the retention rate of stored data. That is, the ledger grows fastest in response to the cumulative length of undeliverable messages. Ensure that sufficient disk space is available for the expected size of the ledger.
Reliable
Ensures that each multicast or broadcast message is received as long as the physical network and packet recipients are working. It also ensures that the loss of a message is detected.
This option can compensate for brief network failures because it can retransmit a message on request if the first attempt failed. This choice is appropriate when message delivery is expected but some loss can be tolerated.
Distributed Queue
Distributed Queue delivers a message to one-of-many service listeners (workers). It contains features of both Certified Messaging and Fault Tolerance.
Wire Format
XML Message
The XML Message wire format conforms to specifically constructed and fully compliant XML Schema (XSD) based on the existing definition of the ActiveEnterprise schema.
ActiveEnterprise Message
The ActiveEnterprise Message is available only for the Rendezvous transport.
Control information for validation is sent in the message. If no control information is included, an exception is returned to the subscription service. ActiveEnterprise standard wire format provides class information and packing rules for the TIBCO Adapter SDK set of data types. This format allows ActiveEnterprise components to perform extra validation on messages sent or received.
See TIBCO Adapter SDK Programmer’s Guide for details about the control information generated and sent with ActiveEnterprise messages.
Connection Factory Type
For JMS transport, there are two kinds of connection factories.
Topic
A message published to a topic is broadcast to one or more subscribers. All messages published to the topic are received by all services that have subscribed to the topic. This messaging model is known as publish-subscribe.
Queue
A message sent to a queue is consumed by one and only one receiver. Each message has only one receiver though multiple receivers may connect to the queue. The first receiver to access the queue gets the message. The other receivers do not. This messaging model is known as point-to-point.
Delivery Mode
For JMS transport, there are two groups of delivery modes.
CI Publication Service, IB Publication Service, and Request-Response Invocation Service
Messages sent with the persistent delivery mode are always written to persistent storage, except when they are published to a topic that has no durable subscribers. When a topic has no durable subscribers, there are no subscribers that need messages resent in the event of a server failure. Therefore, messages do not need to be saved, and performance is improved because disk I/O is not required.
Subscription Service, Message Subscription Service, and Request-Response Service
See TIBCO Enterprise Message Service User’s Guide for more information about the semantics for this field.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved