HTTP and HTTPS

You can create a client that uses the HTTP or HTTPS transport to send an HL7 version 2.x message to Integration Server. When using HTTP, the client must include the following logic:

Address the request to the URL of the service that is to process the HL7 message (for example, http://localhost:5555/invoke/wm.ip.hl7.tn.service/receive)

Put the HL7 document to process in the body of the message. The document must be the only text that appears in the body of the request.

Because most browsers do not allow you to modify the content type header field, they are not suitable clients for this type of submission. Clients that you might use to submit an HL7 message in this manner include PERL scripts (which allow you to build and issue HTTP requests) and the webMethods pub.client:http service. The following table describes the values that you provide for the pub.client:http service to POST an HL7 version 2.x message to Integration Server:

Parameter	Description
url	A string that contains the URL of the service that you want to invoke to process the HL7 message. For example, http://localhost:5555/invoke/wm.ip.hl7.tn.service/receive
method	Specify post.
loadAs	A string that contains the data type of the input data source. Specify either bytes or stream. bytes if the document data source is a byte[]. stream if the document data source is an InputStream.
data/string	A string that contains the HL7 message that you want to post.
headers	An IData object that contains the following: NameSpecifyContent-type Value The content type for the document, for example, text/plain.

The client can also set other optional HTTP variables, such as authorization information, that are required by your application. For a complete description of the pub.client.http service, see the webMethods Integration Server Built-In Services Reference for your release.