The adapter for the
DTS protocol conforms to the following communication characteristics of the
protocol:
- DTS messaging is bi-directional, so a request may be sent from either VME
or the message broker.
- Each DTS link handles either text messages or binary messages, not a
combination of both.
- Each configured VJC service uses a particular DTS link, and thus each
service handles either text messages or binary messages, not a combination of
both.
- Each VJC service is associated with a single DTS link.
- A Java client establishes a connection, or session, to a particular VJC
service. Thus, each connection handles either text messages or binary
messages, but not a combination of both.
- All messages of a particular Message Tag or Message Type on a particular
service must be either normal or transparent, not a combination of
both.
- Each VJC service may have multiple concurrent connections.
- Each connection established can be used either as an initiator or as a
responder, and each connection can handle only a single conversation at a
time.
- A DTS reply must be sent back on the same VJC connection, VJC service, and
DTS link on which the request was received. Because of this, the data
type (text or binary) of each reply message must match that of the request,
and if a connection terminates, any in-progress conversation becomes
invalid.
- Each DTS message must not exceed a maximum size of approximately
6K.
- DTS requests must be contained in a single DTS message.
- DTS replies may have 0 or more intermediate reply messages.
- DTS Conversation IDs are unique only to a VJC service.
- If a transaction-processing application times out waiting for a response,
the VJC and the adapter are not notified.
