JCAPS 512 HL7 eWay
Hi All
I am trying to create an inbound TCP/IP HL7 connection. I am using the sample projects provided but am not sure how to configure the eWay connections type on the Connectivity map. I am trying to have JCAPS connect to my applications box and port and listen there which in previous versions was set as server. However it looks as if setting the config connection type value to server now only allows the port to be on the local machine as the machine name field is ignored. If you set the connection type to client it will allow you to connect to the other PC and port but it seems its not in listen mode. Surely we are able to listen on the remote port and not forsed to make all external applications send to the local JCAPS box.
Any ideas appriciated.
Joe
[789 byte] By [
JCAPS_Joea] at [2007-11-27 7:38:28]
# 1
The host on which the eWay will be listening is the one on which the Integration Server/logical host is running . . . and that's controlled by your environment configuration and deployment profile.
Even in eGate 4.x, the host name field was irrelevant in the stcdgwtcpiphl7 eWay's configuration when running as a server.
# 3
If I'm understanding you correctly, Machine A is running your Java CAPS logical host, and machine B is running the application that is the source of the HL7 messages.
You would configure the eWay as a server, on port 4400. The value in the eWay's host name field is not applicable.
You would configure the external application as a client, to connect to Machine A's IP address at port 4400.
# 5
Sorry, but what you're describing doesn't make any sense. When running as a "Server" configuration in 4.x, the eWay listens on whatever port you've configured, on your participating host, and waits for a connection from an external system. The external system is a client, and in that application's configuration you must specify which IP address and port number to connect to.
In that respect, Java CAPS isn't any different. If an eWay is set up as a server, it will listen on whatever port is configured, on whatever host the LH is running on, and wait for a connection to come in from an external application. The external app must be a "client" for this to work.
If you need CAPS to actually establish/initiate the connection to an external application, it needs to be configured as a client, with IP address (or hostname) and port number specified . . . the external application must then be configured as a server, listening on whatever port you've specified in the eWay config.
In other interface engines, the roles of server and client are sometimes referred to as "passive" and "active" configurations. Servers listen (passively). Clients initiate connections to servers (actively). That's how it works.
With all of the above said, however, I must point out that the roles of client and server really don't have anything to do with the direction of data flow. A client may establish a connection, but once it's established, the server may actually be the sender of the messages. In most healthcare interfaces the convention is to have the client function as the sender (the server responds with acknowledgments when messages are received), but it doesn't have to be that way.
Whether the JCAPS eWay functions as an inbound or outbound is controlled by its connection to the left or right side of a service in the connectivity map, and the configuration options for the eWay change accordingly . . . you can set an outbound eWay up as a server, or an inbound eWay up as a client.
