CBORD / NetMenu SOAP Setup

[Rodney Howell]

We are upgrading our CBORD application to NetMenu and will be using a SOAP connection. I am not familiar with this type of setup and have been walking through the Cloverleaf 19.1.2 Protocol and Properties menu trying to get it to work. The vendor has given me a URL, a Key and a WDSL file that I have been using to setup this configuration. Also, they suggest we use TLS. If you have done this or understand how this should work, please comment. All thoughtful comments will be appreciated.

Sr. Integration Analyst
Houston Methodist

Topic

[Arkadiy.K]

LOL Literarily started the same setup today!

[Jim Kosloskey]

Here is a link for an old post that may be of use: Web Service Set Up For Dummies – Clovertech

The attached files in part of that discussion includes a Word Doc that takes you by the hand.

Tell Clinton to reach out if he wants a second set of eyes.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.

[James Cobane]

We converted from on-prem CBORD to NetMenu a few years back.  It was a bit of a struggle to get it working and the NetMenu side had some issues with volume, so we had to split up into multiple connections to them.  We have the threads configured with the Netmenu endpoint info and we have an outbound tps proc which base-64 encodes the HL7 message and applies the xml wrapper around the base-64 encoded HL7 message with the APIKEY that they specified.  We also have a reply handling proc that receives/checks the http response and decodes the base-64 encoded HL7 ACK to determine if they ACK’d or NAK’d us.  I’ll box one of the connections and the respective procs for reference.  Stay tuned….

Jim Cobane – Henry Ford Health

[James Cobane]

Attached is the BOX containing one of our configured threads and the associated procs.  You would replace the xxxxxxxx on in the {APIKEY xxxxxxxx} argument on the outbound tps_cbord_SOAP_env proc with your api key that NetMenu supplied.

Hope this helps.

Jim Cobane – Henry Ford Health

• This reply was modified 3 weeks, 3 days ago by James Cobane.
• This reply was modified 3 weeks, 3 days ago by James Cobane.

Attachments:

You must be logged in to view attached files.

[James Cobane]

FYI – The APIKEY argument on the proc in the thread has an actual numeric value and not xxxxxxxx like I thought.  Please don’t use that value, replace it with yours.  I can’t delete and re-upload the BOX for some reason.  It is not letting me edit my post 🙁

[Rodney Howell]

When I go through the Cloverleaf java/ws-client properties menu, I set the following, however, I don’t see a place to add the supplied KEY. Also, I have nothing in the TLS (TAB). Is this where the KEY string goes? I am trying to do this without using the procs that James provided for now.

Below:

I am generating a HL7 message in outbound SMAT but no Acknowledgement and the vendor did not receive the message.

I was given the following from the Vendor:

1. WSDL File:

2. URL: https://hcis-staging.cbord.com/houstonmethodist/services/Mirth

3. Key: XXXXXXXXXXX

Cloverleaf:

PROTOCOL = java/ws-client

Properties:

BUS:

General (Tab)

(BOX NOT CHECKED) – WS-Addressing Enabled (applies to SOAP clients/providers)

(BOX CHECKED) – Message Logging Enabled

(BOX CHECKED) – Message Validation Check Mode Enabled

Conduit(*.http-conduit):

Client (Tab)

*Name: *.http-conduit

TLS (Tab)

(BOX CHECKED) – TLS Secured

SoapConsumer(MySOAPDispatch): [Read in from WSDL file]

General (Tab)

Name (required if more than one client) – MySOAPDispatch

*Sevice Mode – PAYLOAD

“WSDL Location: – /cloverleaf/cis19.1/integrator/t_ob_anc2/data/CBORDHL7W7WSS.wsdl

*Service: – {http://www.cbord.com/msg/}CBORDHL7WSService

*Port: – {http://www.cbord.com/msg/}CBORDHL7Port

*Address: = https://hcis-staging.cbord.com/houstonmethodist/services/Mirth

Enable WS-Addressing = (BOX NOT CHECKED)

Enable Message Logging = (BOX CHECKED)

Enable Schema Validation = (BOX CHECKED)

Enable MTOM = (BOX NOT CHECKED)

SMAT:

MSH|^~\&|EPIC|AMMM|CBORD|NetMenu|20260715163936||ADT^A05|4675177|T|2.5.1

EVN|A05|20260715163936||ADT_EVENT

PID|1||100485063^^^^MRN||DIEKMAN^SHELBY||19950317|F||||||||||3000000133714

PV1|1|I|MADM^^^MMM|L|||003309^ROBBEN^CHRISTOPHER||||||||||003309^ROBBEN^CHRISTOPHER|I

OBX|1||HAR_CSN^HAR PRIMARY CSN^HARCSN||3000000133714

No Acknowledgement Message:

SMAT Error:

msg: 0x3012803c

    msgType           : DATA

    msgClass          : PROTOCOL

    msgState          : Disp Error process in IB data TPS (201)

    msgPriority       : 5120

    msgRecoveryDbState: Log:update (3)

    msgFlags          : 0x8006

    msgMid            : [0.0.3062595]

    msgSrcMid         : [0.0.3062541]

    msgSrcMidGroup    : midNULL

    msgHostId         : 1503854647

    msgOrigSrcThread  : hr_cbr_adt

    msgOrigDestThread : t_cbr_ug_ao_tmh

    msgSrcThread      : hr_cbr_adt

    msgDestThread     : t_cbr_ug_ao_tmh

    msgXlateThread    :

    msgSkipXlate      : 0

    msgSepChars       :

    msgNumRetries     : 0

    msgGroupId        : 0

    msgDriverControl  : {CONNID 0} {IPVERSION 4} {CLIENTIP 127.0.0.1} {CLIENTPORT 54115} {_TRXID_ _HCI_static_route_}

    msgRecordFormat   :

    msgRoutes         :

    msgUserData       : t_cbr_ug_ao_tmh/check_ack_cbord_notify : Received Invalid Ack Response of

    msgStaticIsDirty  : 0

    msgVariableIsDirty: 0

    msgRetryTimes     :

    msgTimeStartIb    : 1784152873.960(Wed Jul 15 17:01:13 2026)

    msgTimeStartOb    : 1784152873.977(Wed Jul 15 17:01:13 2026)

    msgTimeCurQueStart: 0.000(Wed Dec 31 18:00:00 1969)

    msgTimeTotalQue   : 0.007

    msgTimeRecovery   : 1784152873.972(Wed Jul 15 17:01:13 2026)

    msgEoConfig       : 0x0

    msgData (BO)      : 0x30128144

    message           : ‘MSH|^~\&|EPIC|AMMM|CBORD|NetMenu|20260715163936||ADT^A05|4675177|T|2.5.1\x0dEVN|A05|20260715163936||ADT_EVENT\x0dPID|1||100485063^^^^MRN||DIEKMAN^SHELBY||19950317|F||||||||||3000000133714\x0dPV1|1|I|MADM^^^MMM|L|||003309^ROBBEN^CHRISTOPHER||||||||||003309^ROBBEN^CHRISTOPHER|I\x0dOBX|1||HAR_CSN^HAR PRIMARY CSN^HARCSN||3000000133714\x0d’

Log:

[java:java:ERR /1:t_cbr_ug_ao_tmh_0:07/15/2026 17:00:03] com.sun.xml.internal.messaging.saaj.soap.ver1_1.Fault1_1Impl getFaultNode:SEVERE: SAAJ0303: Operation getFaultNode not supported by SOAP 1.1

[java:java:ERR /1:t_cbr_ug_ao_tmh_0:07/15/2026 17:01:13] com.infor.cloverleaf.gjdws.validation.MessageValidation getXMLStreamReaderToFirstElement:SEVERE: XML message is broken:org.w3c.dom.ls.LSException: Content is not allowed in prolog.

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:07/15/2026 17:01:13] com.infor.cloverleaf.gjdws.validation.MessageValidation printWarnings:WARNING: Message validation has detected 1 warning

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:07/15/2026 17:01:13] com.infor.cloverleaf.gjdws.validation.MessageValidation printWarnings:WARNING: failed to verify message content due to exception: type ‘com.ctc.wstx.exc.WstxUnexpectedCharException’ with message: Unexpected character ‘M’ (code 77) in prolog; expected ‘<‘

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–]  at javax.xml.stream.SerializableLocation@d5d5de3e

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:07/15/2026 17:01:14] org.apache.cxf.phase.PhaseInterceptorChain doDefaultLogging:WARNING: Interceptor for {http://www.cbord.com/msg/}CBORDHL7WSService#{http://cxf.apache.org/jaxws/dispatch}Invoke has thrown exception, unwinding now

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] Catch Execption:

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] org.apache.cxf.binding.soap.SoapFault: Error writing to XMLStreamWriter.

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor$SoapOutEndingInterceptor.handleMessage(SoapOutInterceptor.java:318)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor$SoapOutEndingInterceptor.handleMessage(SoapOutInterceptor.java:294)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:531)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:440)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:355)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.endpoint.ClientImpl.invokeWrapped(ClientImpl.java:348)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:322)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:241)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.infor.cloverleaf.gjdws.WSClient.processMessageFromCloverleaf(WSClient.java:360)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.lawson.cloverleaf.driver.FromCloverleafLink.doMsg(FromCloverleafLink.java:46)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] Caused by: com.ctc.wstx.exc.WstxIOException: com.ibm.jsse2.util.h: PKIX path building failed: com.ibm.security.cert.IBMCertPathBuilderException: unable to find valid certification path to requested target

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ctc.wstx.sw.BaseStreamWriter._finishDocument(BaseStreamWriter.java:1468)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ctc.wstx.sw.BaseStreamWriter.writeEndDocument(BaseStreamWriter.java:552)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor$SoapOutEndingInterceptor.handleMessage(SoapOutInterceptor.java:307)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] … 11 more

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] Caused by: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: PKIX path building failed: com.ibm.security.cert.IBMCertPathBuilderException: unable to find valid certification path to requested target

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.k.a(k.java:41)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.av.a(av.java:147)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.D.a(D.java:103)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.D.a(D.java:432)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.E.a(E.java:248)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.E.a(E.java:620)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.D.r(D.java:628)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.D.a(D.java:518)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.av.a(av.java:288)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.av.i(av.java:136)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.av.a(av.java:1001)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.av.startHandshake(av.java:991)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.net.ssl.www2.protocol.https.c.afterConnect(c.java:186)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:14)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1352)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1327)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.net.ssl.www2.protocol.https.b.getOutputStream(b.java:82)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.setupWrappedStream(URLConnectionHTTPConduit.java:274)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleHeadersTrustCaching(HTTPConduit.java:1345)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.onFirstWrite(HTTPConduit.java:1306)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.onFirstWrite(URLConnectionHTTPConduit.java:307)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.io.AbstractWrappedOutputStream.write(AbstractWrappedOutputStream.java:47)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.io.AbstractThresholdOutputStream.write(AbstractThresholdOutputStream.java:69)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.io.CacheAndWriteOutputStream.write(CacheAndWriteOutputStream.java:80)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at org.apache.cxf.io.AbstractWrappedOutputStream.write(AbstractWrappedOutputStream.java:51)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:100)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:242)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ctc.wstx.sw.BufferingXmlWriter.close(BufferingXmlWriter.java:215)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ctc.wstx.sw.BaseStreamWriter._finishDocument(BaseStreamWriter.java:1466)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] … 13 more

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] Caused by: com.ibm.jsse2.util.h: PKIX path building failed: com.ibm.security.cert.IBMCertPathBuilderException: unable to find valid certification path to requested target

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.util.f.a(f.java:71)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.util.f.b(f.java:10)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.util.e.a(e.java:19)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.aD.a(aD.java:7)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.aD.a(aD.java:151)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.aD.checkServerTrusted(aD.java:39)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.E.a(E.java:848)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] … 37 more

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] Caused by: com.ibm.security.cert.IBMCertPathBuilderException: unable to find valid certification path to requested target

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.security.cert.SunCertPathBuilder.build(SunCertPathBuilder.java:139)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.security.cert.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:124)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:292)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] at com.ibm.jsse2.util.f.a(f.java:118)

[java:java:WARN/1:t_cbr_ug_ao_tmh_0:–/–/—- –:–:–] … 43 more

[java:java:ERR /1:t_cbr_ug_ao_tmh_0:07/15/2026 17:01:14] com.sun.xml.internal.messaging.saaj.soap.ver1_1.Fault1_1Impl getFaultNode:SEVERE: SAAJ0303: Operation getFaultNode not supported by SOAP 1.1

Sr. Integration Analyst
Houston Methodist

[Robert Kersemakers]

Rodney, you are trying to send an HL7 message with java/ws-client; this protocol expects an XML message. I think you need to use either java/ws-rawclient or http-client to send HL7 messages over a webservice. The http-client is easier to setup, just don’t forget to put set Driver Mode on ‘Message Driven’ and set script ‘httpQuery’ in Query TPS.

About the key: you need to ask the receiving application how they want to receive this key. Could be X-API-KEY or X-functions-key. You can then add the key to Headers as a keyed list, something like this:
{Content-Type “text/plain; charset=utf-8”} {X-functions-key “<put your key here>”}

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Rodney Howell]

Thanks Robert for looking at this issue.

Below is a example message and how they want to receive the Key. Even though the wrapper is XML, you think that I should not use java/ws-client?

Sample Message:

MSH|^~\&|SendingApp|SendFac|CBORD|FacId|20160102113332.477-0400||ADT^A01|1008||2.5||||
PID|||MRN123||Doe^John^|||M||||||||||
PV1||I|NusingUnitId^Room1^Bed1||||Joe^Doctor|||||||||Y||||||||||||||||||||||||||||20160102095636.005-0400|
AL1||FA|GLUTFREE|

 

Encoding of Sample Message:

<?xml version=”1.0″ encoding=”utf-8″?>

<s:Envelope xmlns:s=http://www.w3.org/2003/05/soap-envelope>

          <s:Body>

               <SendMessage xmlns:i=”http://www.w3.org/2001/XMLSchema-instance&#8221; xmlns=”http://www.cbord.com/msg/”&gt;

                    <key>123456789</key>

<encodedMessage>TVNIfF5+XCZ8U2VuZGluZ0FwcHxTZW5kRmFjfENCT1JEfEZhY0lkfDIwMTYwMTAyMTEzMzMyLjQ3Ny0wNDAwfHxBRFReQTAxf

DEwMDl8fDIuNXx8fHwNClBJRHx8fE1STjEyM3x8RG9lXkpvaG5efHx8TXx8fHx8fHx8fHwNClBWMXx8SXxOdXNpbmdVbml0SWReUm9vbTFeQmVkMX

x8fHxKb2VeRG9jdG9yfHx8fHx8fHx8WXx8fHx8fHx8fHx8fHx8fHx8fHx8fHx8fHx8fHwyMDE2MDEwMjA5NTYzNi4wMDUtMDQwMHwNCkFMMXx8RkF

8R0xVVEZSRUV8DQo=</encodedMessage>

              </SendMessage>

       </s:Body>

</s:Envelope>

Sr. Integration Analyst
Houston Methodist

[Robert Kersemakers]

Your error log showed: Unexpected character ‘M’ (code 77) in prolog; expected ‘<‘.
So I assumed you were sending a real HL7 message (starting with MSH) through java/ws-client. Are you sure the XML wrapper works? It’s not standard functionality, as far as I know.

You could at least try the rawclient to see if it gives you a better result. We mostly use rawclient.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Arkadiy.K]

How are you all handing the certificate? they gave us a URL for an auto renewing SSL from AWS.

[Author]

Replies