Справочник Пользователя для Sun Microsystems TCP
At the end of each action, the state is set for the next execution of the Collaboration. There are
three main states:
three main states:
■
To Establish:
A new or reset connection needs to have an HL7 session established. If
sequence numbering is used, the sequence numbers need to be negotiated.
■
Messaging:
This is where the exchange of messages and ACKs takes place.
■
Shutdown:
This is where any cleanup can happen before the connection is closed, or to
close the connection.
Additional Collaborations can be added to a Project to increase message flow.
Note –
The TCP/IP HL7 V2 inbound Collaboration publishes received data as a Byte message in
JMS using the sendBytes() method. However, the HL7 V2 outbound Collaboration expects a
Text message from JMS. The adapter is not designed for the HL7 V2 outbound Collaboration to
subscribe to a JMS data queue created by the HL7 V2 inbound Collaboration directly. HL7 V2
inbound and outbound Collaborations are designed to communicate through an HL7 V2
TCP/IP adapter connection.
Text message from JMS. The adapter is not designed for the HL7 V2 outbound Collaboration to
subscribe to a JMS data queue created by the HL7 V2 inbound Collaboration directly. HL7 V2
inbound and outbound Collaborations are designed to communicate through an HL7 V2
TCP/IP adapter connection.
Inbound HL7 V2 Collaboration Overview
The inbound HL7 V2 Collaboration, jcdHL7inbound, contains Message Libraries for the HL7
Resource Adapter, JMS Data, HL7 ACK, JMS Journal, and JMS Error, as well as the Generic
HL7 Event. The Collaboration works with its own internal code and the properties
configuration files.
Resource Adapter, JMS Data, HL7 ACK, JMS Journal, and JMS Error, as well as the Generic
HL7 Event. The Collaboration works with its own internal code and the properties
configuration files.
This following topics describe the business logic defined in the jcdHL7Inbound Collaboration:
■
■
■
Inbound HL7 V2 Collaboration - Part 1
The inbound Collaboration is triggered by an HL7 V2 message received from an external
system or an outbound HL7 V2 client. The Collaboration calls the HL7 V2 user Collaboration
rule by executing receive().
system or an outbound HL7 V2 client. The Collaboration calls the HL7 V2 user Collaboration
rule by executing receive().
The receive method is the entry point to the HL7 V2 user Collaboration, with the following
signature:
signature:
public void
receive(com.stc.connector.appconn.tcpip.hl7.HL7ServerApplication input,
com.stc.connectors.jms.JMS otdJMS_DATA,
com.stc.SeeBeyond.OTD_Library.HL7.Generic.HL7_GENERIC_EVT.GENERIC_EVT
About TCP/IP HL7 V2 Collaborations
Sun Adapter for TCP/IP HL7 User's Guide
109