Announcement

Collapse

Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Problem with SOAP Sender Channel

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problem with SOAP Sender Channel

    Hello,

    I got Mirth 1.6.1.2750 and I am unable to save my channel after clicking on Get Methods for a SOAP Sender connector type, in Destinations.

    When i click on Save Changes I can see Saving Channel message, and nothing more, my channel is not saved and Save Changes button is still here.

    My WSDL URL is http://172.x.x.x:8080/ideopass/servicedef/Identite.wsdl
    This is an IdeoPass Webservice (http://sourceforge.net/projects/ideopass).

    IdeoPass : Provide a OSS component to manage the identity of the patients in healthcare organizations. Compliant with HL7, IHE and the study of the agency governemental French GMSIH.

    Thanks !

    -----------------------------------------------------------------------------

    SOAP Envelope for creationIdentite Method :

    <?xml version="1.0" encoding="utf-16"?>
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <creationIdentite xmlns="http://identification.services.sip.org">
    <in0 xmlns="http://hl7messages.sip.org">
    <MSH xmlns="">
    <MSH.1/>
    <MSH.2/>
    <MSH.3>
    <HD.1/>
    <HD.2/>
    <HD.3/>
    </MSH.3>
    <MSH.5>
    <HD.1/>
    <HD.2/>
    <HD.3/>
    </MSH.5>
    <MSH.7>
    <TS.1/>
    </MSH.7>
    <MSH.8/>
    <MSH.9/>
    <MSH.10/>
    <MSH.11>
    <PT.1/>
    </MSH.11>
    <MSH.12>
    <VID.1/>
    </MSH.12>
    <MSH.17/>
    <MSH.18/>
    </MSH>
    <EVN xmlns="">
    <EVN.2>
    <TS.1/>
    </EVN.2>
    <EVN.5>
    <XCN.1/>
    <XCN.3/>
    </EVN.5>
    <EVN.7>
    <HD.1/>
    <HD.2/>
    <HD.3/>
    </EVN.7>
    </EVN>
    <PID xmlns="">
    <PID.1/>
    <PID.3>
    <CX.1/>
    <CX.4>
    <HD.1/>
    <HD.2/>
    <HD.3/>
    </CX.4>
    <CX.5/>
    <CX.6>
    <HD.1/>
    <HD.2/>
    <HD.3/>
    </CX.6>
    <CX.7/>
    <CX.8/>
    </PID.3>
    <PID.5>
    <XPN.1>
    <FN.1/>
    </XPN.1>
    <XPN.2/>
    <XPN.3/>
    <XPN.7/>
    </PID.5>
    <PID.7>
    <TS.1/>
    </PID.7>
    <PID.8/>
    <PID.11>
    <XAD.1>
    <SAD.1/>
    <SAD.2/>
    <SAD.3/>
    </XAD.1>
    <XAD.2/>
    <XAD.3/>
    <XAD.5/>
    <XAD.6/>
    <XAD.7/>
    <XAD.9/>
    </PID.11>
    </PID>
    <ZPI xmlns="">
    <ZPI.1/>
    <ZPI.2>
    <CX.1/>
    <CX.4>
    <HD.1/>
    <HD.2/>
    <HD.3/>
    </CX.4>
    <CX.5/>
    <CX.6>
    <HD.1/>
    <HD.2/>
    <HD.3/>
    </CX.6>
    <CX.7/>
    <CX.8/>
    </ZPI.2>
    <ZPI.3/>
    <ZPI.4/>
    <ZPI.5/>
    <ZPI.6/>
    <ZPI.7/>
    <ZPI.8/>
    <ZPI.9/>
    </ZPI>
    <ZPC xmlns="">
    <ZPC.1/>
    <ZPC.2>
    <CX.1/>
    <CX.4>
    <HD.1/>
    <HD.2/>
    <HD.3/>
    </CX.4>
    <CX.5/>
    <CX.6>
    <HD.1/>
    <HD.2/>
    <HD.3/>
    </CX.6>
    <CX.7/>
    <CX.8/>
    </ZPC.2>
    <ZPC.3>
    <XTN.2/>
    <XTN.3/>
    <XTN.5/>
    <XTN.7/>
    </ZPC.3>
    <ZPC.4>
    <XTN.2/>
    <XTN.3/>
    <XTN.5/>
    <XTN.7/>
    </ZPC.4>
    <ZPC.5>
    <CE.1/>
    <CE.2/>
    <CE.3/>
    </ZPC.5>
    <ZPC.6>
    <CE.1/>
    <CE.2/>
    <CE.3/>
    </ZPC.6>
    <ZPC.7>
    <CX.1/>
    <CX.4>
    <HD.1/>
    <HD.2/>
    <HD.3/>
    </CX.4>
    <CX.5/>
    <CX.6>
    <HD.1/>
    <HD.2/>
    <HD.3/>
    </CX.6>
    <CX.7/>
    <CX.8/>
    </ZPC.7>
    <ZPC.8/>
    <ZPC.9/>
    <ZPC.10>
    <CE.1/>
    <CE.2/>
    <CE.3/>
    </ZPC.10>
    <ZPC.11>
    <TS.1/>
    </ZPC.11>
    <ZPC.12/>
    <ZPC.13/>
    <ZPC.14>
    <CE.1/>
    <CE.2/>
    <CE.3/>
    </ZPC.14>
    <ZPC.15>
    <TS.1/>
    </ZPC.15>
    <ZPC.16>
    <TS.1/>
    </ZPC.16>
    <ZPC.17>
    <TS.1/>
    </ZPC.17>
    <ZPC.18>
    <TS.1/>
    </ZPC.18>
    <ZPC.19>
    <TS.1/>
    </ZPC.19>
    </ZPC>
    </in0>
    </creationIdentite>
    </soap:Body>
    </soap:Envelope>

    Post edited by: magikbanana, at: 12/19/2007 07:56

    Post edited by: magikbanana, at: 12/21/2007 07:37

  • #2
    Same for me. I've used the wsdl example here:
    http://devzone.zend.com/article/689

    The webservice works when I invoke directly from browser but Mirth doesn't do anything when I click "get methods" and won't let me save it.

    I try another webservice like:
    http://webservices.amazon.com/AWSECo...ceService.wsdl

    and it works and it pulls the methods.

    Comment


    • #3
      I have noticed that Mirth doesn't like some subtleties of WSDL files. Sometimes when referencing a .NET web service's WSDL, the URL cannot be:
      Code:
      http://mywebservice/blah.asmx?WSDL
      However, if I have access to the web service, I'll explicitly copy/paste the WSDL XML into a new file, and save as blah.wsdl on the web server. THEN reference the new URL as
      Code:
      http://mywebservice/blah.wsdl
      , and Mirth will pickup the WSDL properly. Careful that you don't have any whitespaces in the first character of the file, otherwise Mirth will complain.

      I realize you aren't working with a .NET web service, and this may not help you.

      Perhaps create a .wsdl file on your local machine. Copy/paste the path to that .wsdl - (i.e. c:\mywebservice.wsdl), and paste that into Mirth's WSDL textbox.

      Comment


      • #4
        I have this same problem. The save never happens! The Mirth Connect Administrator cannot be exited. In order to re-start it I have to reboot to insure that all the Mirth processes are dead (I can't seem to recognize them all).

        I can lookup the wsdl in a web browser no problem, if I ask Mirth to read the same WSDL it takes forever just to come back and say "No methods found". Then I cannot perform a save nor can I exit the administrator cleanly. This is a significant bug.
        Reed Haslam
        Northrop Grumman Information Services
        Health & Human Services

        Comment

        Working...
        X