CONNECT 5.1 unable to invoke Adapter PD service

classic Classic list List threaded Threaded
40 messages Options
12
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
Sai, one thing we did notice:

In your AdapterMpiConfig.xml file, you have set mpi to secured:


<alias alias="mpi" name="mpiwssecured"/>

<bean lazy-init="true" class="gov.hhs.fha.nhinc.mpi.adapter.component.proxy.AdapterComponentMpiProxyNoOpImpl" id="mpinoop" name="mpinoop">
<meta key="impltype" value="noop"/>

Please set it to unsecured, restart your server, and see if that changes anything.
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti

Like this: I restarted the server, but still no output

 

    <!-- Beans defined: mpi -->

 

    <alias alias="mpi" name="mpiwsunsecured" />

 

    <!-- No-op Implementation -->

    <bean lazy-init="true" class="gov.hhs.fha.nhinc.mpi.adapter.component.proxy.AdapterComponentMpiProxyNoOpImpl" id="mpinoop" name="mpinoop">

        <meta key="impltype" value="noop"/>

    </bean>

 

    <!-- Java Implementation -->

    <bean lazy-init="true" class="gov.hhs.fha.nhinc.mpi.adapter.component.proxy.AdapterComponentMpiProxyJavaImpl" id="mpijava" name="mpijava">

        <meta key="impltype" value="java"/>

    </bean>

 

    <!-- Secured web service Implementation -->

    <bean lazy-init="true" class="gov.hhs.fha.nhinc.mpi.adapter.component.proxy.AdapterComponentMpiProxyWebServiceSecuredImpl" id="mpiwssecured" name="mpiwssecured">

        <meta key="impltype" value="wssecured"/>

       

    </bean>

 

    <!-- Unsecured web service Implementation -->

    <bean lazy-init="true" class="gov.hhs.fha.nhinc.mpi.adapter.component.proxy.AdapterComponentMpiProxyWebServiceUnsecuredImpl" id="mpiwsunsecured" name="mpiwsunsecured">

        <meta key="impltype" value="wsunsecured"/>

                                <meta key="default" value="true"/>

    </bean>

 

 

 

    <!-- Beans defined: adaptermpi -->

 

    <alias alias="adaptermpi" name="adaptermpiwssecured" />

 

    <!-- No-op Implementation -->

    <bean lazy-init="true" class="gov.hhs.fha.nhinc.mpi.adapter.proxy.AdapterMpiProxyNoOpImpl" id="adaptermpinoop" name="adaptermpinoop">

        <meta key="impltype" value="noop"/>

    </bean>

 

    <!-- Java Implementation -->

    <bean lazy-init="true" class="gov.hhs.fha.nhinc.mpi.adapter.proxy.AdapterMpiProxyJavaImpl" id="adaptermpijava" name="adaptermpijava">

        <meta key="impltype" value="java"/>

    </bean>

 

    <!-- Secured web service Implementation -->

    <bean lazy-init="true" class="gov.hhs.fha.nhinc.mpi.adapter.proxy.AdapterMpiProxyWebServiceSecuredImpl" id="adaptermpiwssecured" name="adaptermpiwssecured">

        <meta key="impltype" value="wssecured"/>

                                <meta key="default" value="true"/>       

    </bean>

 

    <!-- Unsecured web service Implementation -->

    <bean lazy-init="true" class="gov.hhs.fha.nhinc.mpi.adapter.proxy.AdapterMpiProxyWebServiceUnsecuredImpl" id="adaptermpiwsunsecured" name="adaptermpiwsunsecured">

        <meta key="impltype" value="wsunsecured"/>

 

 

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [mailto:[hidden email]]
Sent: 10 May 2018 00:06
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

Sai, one thing we did notice:

In your AdapterMpiConfig.xml file, you have set mpi to secured:


<alias alias="mpi" name="mpiwssecured"/>

<bean lazy-init="true" class="gov.hhs.fha.nhinc.mpi.adapter.component.proxy.AdapterComponentMpiProxyNoOpImpl" id="mpinoop" name="mpinoop">
<meta key="impltype" value="noop"/>

Please set it to unsecured, restart your server, and see if that changes anything.

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7581002.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
I see you bolded    <alias alias="adaptermpi" name="adaptermpiwssecured" />. Can you set that to unsecured as well?
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti

Updated it to unsecure and restarted the server too. But the error from the automatic response of CONNECT is

<detectedIssueEvent><code code="VALIDATION" codeSystem="2.16.578.1.34.5.3" displayName="The query parameters are wrong or insufficient."/></detectedIssueEvent>

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [mailto:[hidden email]]
Sent: 10 May 2018 01:04
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

I see you bolded    <alias alias="adaptermpi" name="adaptermpiwssecured" />. Can you set that to unsecured as well?

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7581004.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti
In reply to this post by Sovann Huynh

In the log is still says 400 bad request. But if we look at the log of our adapter service there is no call coming in.

 

Please let me know the flow of how the adapter service is invoked so that we can trace the problem with debugging.

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Saikrishna Vennelakanti [mailto:[hidden email]]
Sent: 10 May 2018 07:45
To: 'Sovann Huynh [via CONNECT Community Forum]'
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

Updated it to unsecure and restarted the server too. But the error from the automatic response of CONNECT is

<detectedIssueEvent><code code="VALIDATION" codeSystem="2.16.578.1.34.5.3" displayName="The query parameters are wrong or insufficient."/></detectedIssueEvent>

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [[hidden email]]
Sent: 10 May 2018 01:04
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

I see you bolded    <alias alias="adaptermpi" name="adaptermpiwssecured" />. Can you set that to unsecured as well?

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7581004.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
Please attach the full server log
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
Also, per my earlier message, are you using 5.1.1 instead of 5.1?
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti

We shifted to 5.1.1. We found the problem by using FIDDLER tool. The actual request is coming as follows to our service. You see there is a special character ff9 before the soap message. Infact we found out that this message was being sent to http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService which is a CONNECT service. Interestingly this service is accepting the below request but our webserver is rejecting the below request.

 

ff9

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Body><RespondingGateway_PRPA_IN201305UV02Request xmlns="urn:hl7-org:v3" xmlns:ns2="urn:hl7-org:sdtc" xmlns:ns3="urn:gov:hhs:fha:nhinc:common:nhinccommon" xmlns:ns4="urn:gov:hhs:fha:nhinc:common:patientcorrelationfacade" xmlns:ns5="http://www.w3.org/2005/08/addressing"><PRPA_IN201305UV02 ITSVersion="XML_1.0"><id root="2.16.840.1.113883.3.1259.10.1003" extension="-5a3e95b1:11d1fa33d45:-7f9b"/><creationTime value="20120618155123"/><interactionId root="2.16.840.1.113883.1.6" extension="PRPA_IN201305UV02"/><processingCode code="T"/><processingModeCode code="T"/><acceptAckCode code="AL"/><receiver typeCode="RCV"><device classCode="DEV" determinerCode="INSTANCE"><id root="2.16.840.1.113883.3.6810.23"/><asAgent classCode="AGNT"><representedOrganization classCode="ORG" determinerCode="INSTANCE"><id root="2.16.840.1.113883.3.6810.23"/></representedOrganization></asAgent></device></receiver><sender typeCode="SND"><device classCode="DEV" determinerCode="INSTANCE"><id root="2.16.840.1.113883.3.1259.10.1003"/><asAgent classCode="AGNT"><representedOrganization classCode="ORG" determinerCode="INSTANCE"><id root="2.16.840.1.113883.3.1259.10.1003"/></representedOrganization></asAgent></device></sender><controlActProcess classCode="CACT" moodCode="EVN"><code code="PRPA_TE201305UV02" codeSystem="2.16.840.1.113883.1.6"/><authorOrPerformer typeCode="AUT" contextControlCode="AP"><assignedDevice classCode="ASSIGNED"><id root="2.16.840.1.113883.3.1259.10.1003"/></assignedDevice></authorOrPerformer><queryByParameter><queryId root="2.16.840.1.113883.3.1259.10.1003" extension="-abd3453dcd24wkkks545"/><statusCode code="new"/><responseModalityCode code="R"/><responsePriorityCode code="I"/><parameterList><livingSubjectAdministrativeGender><value code="F"/><semanticsText>LivingSubject.administrativeGender</semanticsText></livingSubjectAdministrativeGender><livingSubjectBirthTime><value value="19831017" operator="I"/><semanticsText>LivingSubject.birthTime</semanticsText></livingSubjectBirthTime><livingSubjectId><value root="2.16.840.1.113883.4.1" extension="666660010"/><semanticsText>LivingSubject.id</semanticsText></livingSubjectId><livingSubjectId><value root="2.16.840.1.113883.3.1259.10.1003" extension="RI0004.000000010"/><semanticsText>LivingSubject.id</semanticsText></livingSubjectId><livingSubjectName><value><family partType="FAM">Davidson</family><given partType="GIV">Amy</given><given partType="GIV">C</given>

                                                                                   </value><semanticsText>LivingSubject.name</semanticsText></livingSubjectName><patientAddress><value><postBox partType="POB"></postBox><city partType="CTY">Springfield</city><state partType="STA">MO</state><postalCode partType="ZIP">65801</postalCode><country partType="CNT">USA</country><streetAddressLine partType="SAL">809 First Ave</streetAddressLine>

                                                                                   </value><semanticsText>Patient.addr</semanticsText></patientAddress></parameterList></queryByParameter></controlActProcess></PRPA_IN201305UV02><assertion><ns3:homeCommunity><ns3:homeCommunityId>urn:oid:2.16.840.1.113883.3.1259.10.1003</ns3:homeCommunityId></ns3:homeCommunity><ns3:uniquePatientId>RI0004.000000010^^^&amp;2.16.840.1.113883.3.1259.10.1003&amp;ISO</ns3:uniquePatientId><ns3:userInfo><ns3:personName><ns3:familyName>Testcase</ns3:familyName><ns3:givenName>Lab</ns3:givenName><ns3:secondNameOrInitials>IT</ns3:secondNameOrInitials><ns3:fullName>Lab IT Testcase</ns3:fullName></ns3:personName><ns3:userName>UID=TS: PRL-R-0000.0-2011 TC: PD-R-0000.0-2011</ns3:userName><ns3:org><ns3:homeCommunityId>urn:oid:2.16.840.1.113883.3.1259.10.1003</ns3:homeCommunityId><ns3:name>2.16.840.1.113883.3.1259.10.1003</ns3:name></ns3:org><ns3:roleCoded><ns3:code>46255001</ns3:code><ns3:codeSystem>2.16.840.1.113883.6.96</ns3:codeSystem><ns3:codeSystemName>SNOMED_CT</ns3:codeSystemName><ns3:displayName>Pharmacist</ns3:displayName></ns3:roleCoded></ns3:userInfo><ns3:authorized>false</ns3:authorized><ns3:purposeOfDisclosureCoded><ns3:code>TREATMENT</ns3:code><ns3:codeSystem>2.16.840.1.113883.3.18.7.1</ns3:codeSystem><n

46e

s3:codeSystemName>nhin-purpose</ns3:codeSystemName><ns3:displayName>Treatment</ns3:displayName></ns3:purposeOfDisclosureCoded><ns3:samlAuthnStatement><ns3:authInstant>2018-05-10T13:59:49.448Z</ns3:authInstant><ns3:authContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:X509</ns3:authContextClassRef></ns3:samlAuthnStatement><ns3:samlSignature><ns3:keyInfo><ns3:rsaKeyValueModulus></ns3:rsaKeyValueModulus><ns3:rsaKeyValueExponent></ns3:rsaKeyValueExponent></ns3:keyInfo><ns3:signatureValue></ns3:signatureValue></ns3:samlSignature><ns3:samlIssuer><ns3:issuer>C=US,O=AEGISnetInc,CN=dilhn003.dil.aegis.net</ns3:issuer><ns3:issuerFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName</ns3:issuerFormat></ns3:samlIssuer><ns3:samlSubjectConfirmations><ns3:method>urn:oasis:names:tc:SAML:2.0:cm:holder-of-key</ns3:method><ns3:subjectCondition/></ns3:samlSubjectConfirmations><ns3:messageId>urn:uuid:df9c7dfa-6ec6-499e-8e33-0f0c7fc724c6</ns3:messageId><ns3:relatesToList xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/></assertion></RespondingGateway_PRPA_IN201305UV02Request></soap:Body></soap:Envelope>

0

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [mailto:[hidden email]]
Sent: 10 May 2018 18:25
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

Also, per my earlier message, are you using 5.1.1 instead of 5.1?

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7581008.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
The ff9 and <RespondingGateway_PRPA_IN201305UV02Request is not coming from CONNECT. <RespondingGateway_PRPA_IN201305UV02Request is what you showed in the request from your SoapUI project.
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti

We are not running any soapui now. I took the request right out of fiddler when I ran my DIL test.

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [mailto:[hidden email]]
Sent: 10 May 2018 19:48
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

The ff9 and <RespondingGateway_PRPA_IN201305UV02Request is not coming from CONNECT. <RespondingGateway_PRPA_IN201305UV02Request is what you showed in the request from your SoapUI project.

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7581010.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
In reply to this post by Sovann Huynh
Also, what do you mean request is going to http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService? The server log you attached shows the request going to your custom adapter.
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti

Before calling our service in the fiddler we saw this url come up

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [mailto:[hidden email]]
Sent: 10 May 2018 19:52
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

Also, what do you mean request is going to http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService? The server log you attached shows the request going to your custom adapter.

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7581012.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
You previously attached a server log. Go into that log and do a find for http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService. Nothing shows up.
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti

Please see the server log. It is there twice before calling our service

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [mailto:[hidden email]]
Sent: 10 May 2018 19:58
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

You previously attached a server log. Go into that log and do a find for http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService. Nothing shows up.

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7581014.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML


server.log (1M) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
It's not in the server log you attached on April 27. I will be unable to assist further unless I can get a clear picture of what's happening when you use CONNECT as opposed to when you use SoapUI. Requests to our reference adapters are working as expected and your web server is rejecting that same message. However, there are no requests to the reference adapters in the logs you uploaded on April 27. We've narrowed it down to the request type. Undo the changes in the adapter config files and try updating your wsdl to allow for the request type used in the actual CONNECT adapter request.
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti

The current server log is after we have shifted to AdapterComponentMpiUnsecured in the AdapterMpiConfig.xml yesterday. But irrespective of that the error is same. We debugged CONNECT and found out that in the WebServiceProxyHelper.java -> InvokeMethod -> oMethod.invoke(…) is where an exception is coming. The exception that we caught using FIDDLER.

 

Do you want us to change the config to wssecured instead of wsunsecured in the AdapterMpiConfig.xml? with respect to wsdl changes, our service is accepting the actual CONNECT adapter request type only. What changes you are expecting?

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [mailto:[hidden email]]
Sent: 10 May 2018 20:20
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

It's not in the server log you attached on April 27. I will be unable to assist further unless I can get a clear picture of what's happening when you use CONNECT as opposed to when you use SoapUI. Requests to our reference adapters are working as expected and your web server is rejecting that same message. However, there are no requests to the reference adapters in the logs you uploaded on April 27. We've narrowed it down to the request type. Undo the changes in the adapter config files and try updating your wsdl to allow for the request type used in the actual CONNECT adapter request.

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7581016.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti
In reply to this post by Sovann Huynh

Please find attached the fiddler screenshots

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Saikrishna Vennelakanti [mailto:[hidden email]]
Sent: 10 May 2018 20:28
To: 'Sovann Huynh [via CONNECT Community Forum]'
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

The current server log is after we have shifted to AdapterComponentMpiUnsecured in the AdapterMpiConfig.xml yesterday. But irrespective of that the error is same. We debugged CONNECT and found out that in the WebServiceProxyHelper.java -> InvokeMethod -> oMethod.invoke(…) is where an exception is coming. The exception that we caught using FIDDLER.

 

Do you want us to change the config to wssecured instead of wsunsecured in the AdapterMpiConfig.xml? with respect to wsdl changes, our service is accepting the actual CONNECT adapter request type only. What changes you are expecting?

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [[hidden email]]
Sent: 10 May 2018 20:20
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

It's not in the server log you attached on April 27. I will be unable to assist further unless I can get a clear picture of what's happening when you use CONNECT as opposed to when you use SoapUI. Requests to our reference adapters are working as expected and your web server is rejecting that same message. However, there are no requests to the reference adapters in the logs you uploaded on April 27. We've narrowed it down to the request type. Undo the changes in the adapter config files and try updating your wsdl to allow for the request type used in the actual CONNECT adapter request.

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7581016.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML


GuardianAdapterInvokeError.png (388K) Download Attachment
ConnectPatientRequest.png (391K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

johnhd_at_zen
In reply to this post by SaiVennelakanti
Saikrishna,

I took some time to look over your issue. I compared the XCPD adapter request present in your logs against an XCPD adapter request (also for Amy Davidson, also from the DIL) in one of my active test rigs running CONNECT 5.1. It's integrated with our Adapters.

There are no differences between your message and ours except timestamp, deviceId, and messageId. Even the OIDs are the same because the originator was the DIL 1003 test system. :)

The only oddball issue I could see is that your message showed up as indented by TABs and mine show up as indented by SPACES but it's almost certainly attributable to the various copy/paste points involved in my comparison.

The issue lies outside of CONNECT from what I can tell. There may be some kind of networking issue, or your adapter is having a problem. Are you able to collect any information from the adapter itself to see what it's specifically complaining about?

I hope this helps.

Let us know! Thanks!
Ask The Experts! Free 15 minute live Q&A sessions with one of Zen's Expert Integrators @ https://consultzen.com/integration-service-desk-solutions/

www.consultzen.com
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti
I have analyzed it further by creating a log of my WCF service. the problem is SOAP action is missing from the message that is being sent to the Adapter(.NET Service).

at System.ServiceModel.Channels.HttpChannelListener`1.HttpContextReceivedAsyncResult`1.ProcessHttpContextAsync()</StackTrace><ExceptionString>System.ServiceModel.ActionMismatchAddressingException: The SOAP action specified on the message, '', does not match the HTTP SOAP Action, 'FindCandidates'.
   at System.ServiceModel.Channels.RequestContextBase.get_RequestMessage()
   at System.ServiceModel.Channels
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

johnhd_at_zen
I'm not sure I agree here. A SOAP action is a header component. While I expect these a SOAP header (and a SOAP action) to be present on the actual XCPD message that makes it to the gateway, I don't expect the same for an Adapter message. There aren't SOAP headers at all on the adapter message sent by the gateway to the adapter (at least when using the "unsecured" SPRING mechanism).

I checked through Adapter messages going back to CONNECT 4.6 and I see the same. No SOAP headers on Adapter messages that come out of the gateway. The MPI Adapter messages identify themselves by the "RespondingGateway_PRPA_IN201305UV02Request" element (Or I guess you could also check the "PRPA_IN201305UV02" sub element), and also by virtue of the endpoint it's being directed to in a sense.

To me this points to an issue with the Adapter. It's expecting a SOAP Action that it won't be getting. The correct path forward is to address it in the Adapter so it does not expect this (or any) SOAP action. If you don't have the means to do this, you may need to patch the gateway to meet your specific use case, or do something to capture these adapter messages on the fly and add the header before it gets to your adapter. (I've seen both ways work for similar needs.)

I hope this helps.
Ask The Experts! Free 15 minute live Q&A sessions with one of Zen's Expert Integrators @ https://consultzen.com/integration-service-desk-solutions/

www.consultzen.com
12