Error getting API Level by Service Name

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

Error getting API Level by Service Name

earla12
When running the DIL Responding Gateway test I am receiving an error 'Getting API by Servicename'
has anyone encountered this issue before?  If so, what was the solution.

I have included by Server.log file below to assist in the diagnosis.
server.log

Any help is greatly appreciated.
Reply | Threaded
Open this post in threaded view
|

Re: Error getting API Level by Service Name

Sovann Huynh
Administrator


2018-09-19 12:32:12,243 ERROR [gov.hhs.fha.nhinc.mpi.adapter.proxy.AdapterMpiProxyWebServiceSecuredImpl] (default task-1) Failed to call the web service (mpisecured).  The URL is null.

Check your internalConnectionoInfo.xml to make sure you have the correct adapter endpoint. Also make sure you have the correct local HCID configured.
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

Re: Error getting API Level by Service Name

earla12
Well, I have validated the HCID, the internalConnections file and even copied and pasted the URL for
the MPISecuredService in my browser, adding the ?wsdl and it came us fine.

https://test.semhie.org:8181/Adapter/PatientDiscovery/A_0/AdapterMpiSecuredService

Additionally I thought eh internalConnections file might have been corrupted so I copied over a
fresh version of it, but I get the same results.

Any ideas?

internalConnectionInfo.xml
Reply | Threaded
Open this post in threaded view
|

Re: Error getting API Level by Service Name

Sovann Huynh
Administrator
I did a quick search for https://test.semhie.org:8181/Adapter/PatientDiscovery/A_0/AdapterMpiSecuredService in your file and it's not there. Also, at the bottom of your file:

<identifierBag>
<keyedReference tModelKey="uddi:nhin:nhie:homecommunityid" keyName="" keyValue="urn:oid:1.1"/>
</identifierBag>

Is 1.1 what you're using for local HCID?
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

Re: Error getting API Level by Service Name

earla12
Good catch on the bottom file entry, I have changed it now to the proper OID.

Getting ready to go back through the internalConnections file and check the entries
again.

Thank you for you help :)
Reply | Threaded
Open this post in threaded view
|

Re: Error getting API Level by Service Name

earla12
I found the issue.  In the 'internalConnectionInfo.xml' file, the entries for each service contained
'localhost' instead of the domain name.

Thank you again for you help.