SOAP UI test results: No bean named 'xxx' is defined

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

SOAP UI test results: No bean named 'xxx' is defined

kalanui
I noticed the community forum had posted errors of this type while deploying a CONNECT bundle.  We are running a very basic test using SOAP UI by sending a message through CONNECT and back to SOAP UI.  CONNECT-WL-4.5.0 is deployed within our test environment.  We've restarted our server and redeployed CONNECT with unsuccessful results.  This is the response we received:

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
   <soap:Header/>
   <soap:Body>
      <ns3:AdhocQueryResponse status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure" xmlns:ns10="urn:ihe:iti:xds-b:2007" xmlns:ns11="http://docs.oasis-open.org/wsn/b-2" xmlns:ns12="urn:gov:hhs:fha:nhinc:common:subscriptionb2overridefordocuments" xmlns:ns13="http://docs.oasis-open.org/wsrf/bf-2" xmlns:ns14="http://docs.oasis-open.org/wsn/t-1" xmlns:ns15="urn:oasis:names:tc:emergency:EDXL:DE:1.0" xmlns:ns16="http://nhinc.services.com/schema/auditmessage" xmlns:ns17="http://www.hhs.gov/healthit/nhin/cdc" xmlns:ns18="urn:gov:hhs:fha:nhinc:common:subscriptionb2overrideforcdc" xmlns:ns2="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0" xmlns:ns4="urn:gov:hhs:fha:nhinc:common:nhinccommon" xmlns:ns5="urn:gov:hhs:fha:nhinc:common:nhinccommonentity" xmlns:ns6="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0" xmlns:ns7="http://www.w3.org/2005/08/addressing" xmlns:ns8="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" xmlns:ns9="http://www.caqh.org/SOAP/WSDL/CORERule2.2.0.xsd">
         <ns2:RegistryErrorList highestSeverity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error">
            <ns2:RegistryError codeContext="EXCEPTION: org.springframework.beans.factory.NoSuchBeanDefinitionException
EXCEPTION Cause Message: No bean named 'nhindocquerywsunsecured' is defined
" errorCode="XDSRepositoryError" severity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error"/>
         </ns2:RegistryErrorList>
         <ns8:RegistryObjectList/>
      </ns3:AdhocQueryResponse>
   </soap:Body>
</soap:Envelope>

Anything anyone can do to shed some light on this issue would be most helpful.
Reply | Threaded
Open this post in threaded view
|

Re: SOAP UI test results: No bean named 'xxx' is defined

johnhd_at_zen
Looking at this I'd say your WS endpoints aren't up. I've seen this caused by CONNECT's MYSQL DB not available or issues with the MYSQL drivers.

Can you restart your application server (which one are you using?) and capture the startup logs?

I've also run into something like this when playing with the SPRING config files. I'll see what context I can dig up on this...
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: SOAP UI test results: No bean named 'xxx' is defined

kalanui
Thanks "johnhd"

I'm working with our sys admin on doing a restart and capturing startup logs.  Our app server we're using is weblogic.
Reply | Threaded
Open this post in threaded view
|

Re: SOAP UI test results: No bean named 'xxx' is defined

johnhd_at_zen
In reply to this post by kalanui
Ok I took a moment to jog my memory a little bit.

It looks like you've been working with the DocumentQueryProxyConfig.xml file on a recent version of CONNECT (4.7 or so?), is this correct?

I have just a working familiarity with how these SPRING configurations work but I'll share what I've experienced.

The section you appear to have been working with comes out of the box looking like this:

    
  <!--
        Beans defined for nhindocquery
    -->

<alias alias="nhindocquery" name="nhindocquerywssecured" />

    <!-- No-op Implementation -->
    <bean lazy-init="true" class="gov.hhs.fha.nhinc.docquery.nhin.proxy.NhinDocQueryProxyNoOpImpl" id="nhindocquerynoop" name="nhindocquerynoop">
        <meta key="impltype" value="noop"/>
    </bean>

    <!-- Secured web service Implementation -->
    <bean lazy-init="true" class="gov.hhs.fha.nhinc.docquery.nhin.proxy.NhinDocQueryProxyWebServiceSecuredImpl" id="nhindocquerywssecured" name="nhindocquerywssecured">
        <meta key="impltype" value="wssecured"/>
        <meta key="default" value="true"/>
    </bean>

Note the "alias" element points to one of the two options below it by literal "name". In my case it's using "nhindocquerywssecured". The other option available is "noop" which I believe is shorthand for "Non-operational" (in other words "disable this service").

Note that "nhindocquerywsunsecured", which you appear to be using, is not an option. That's what CONNECT is calling out in the error message you posted- it doesn't have a hook for an "unsecured" endpoint here.

What this particular endpoint/service does is listen externally for NWHIN Document Query calls from the outside world. The CONNECT designers are effectively requiring you to use HTTPS on this endpoint and eliminated HTTP as an option.

To the root of your issue, the SOAP UI tests should "just work" with the stock configuration of all these sservices- because they hit the EntityDocQueryUnsecured endpoint which is an internal/HTTP endpoint anyway. e.g. http://connect.gateway.ip.address:8080/Gateway/DocumentQuery/2_0/EntityService/EntityDocQueryUnsecured

Anyway, check the value in DocumentQueryProxyConfig.xml, and if you change it, restart CONNECT, try again, and let us know what your results are!

Side note:

I know that when I was working in this file at one point it was because I was trying to figure out how to "point" CONNECT to my ADAPTERS appropriately. If this is what you (or someone who stumbles on this answer) are trying to do, you change the "name" in the "adapterdocquery" section to hit your DQ adapters. In my case, I wound up using the "adapterdocquerywsunsecured" option at the time because in that particular scenario my adapters were on the same server as the CONNECT application, so HTTP (vs HTTPS) was feasible. Disclaimer: Proceed with caution anytime you're considering purposefully removing any security features!
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: SOAP UI test results: No bean named 'xxx' is defined

johnhd_at_zen
In reply to this post by kalanui
Hi kalanui, did my answer help get you past this issue?
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: SOAP UI test results: No bean named 'xxx' is defined

kalanui
Hello johnhd at zen,

Many apologies for not getting back sooner.  I'm new to this gig and my intellect is constantly challenged.  I work for the VA and our sys admin's project plate is always overflowing and due to security concerns, we can't leave caution to the wind.  As we search for the experienced and smart guys within VA, I'm reaching outward within this forum for answers as a second choice.  Once again thank you for hanging in there with me.  

Yes, we've installed CONNECT 4.5 on our WebLogic server.  Due to our test infrastructure we're filtering through the information you've provided that may apply.    

To ensure I understand you correctly, our endpoint, nhindocquerywsunsecured, is not a viable endpoint that CONNECT relates to and a change to our config.xml is required.  Specifically, are you suggesting we should update the "id=nhindocquerywssecured" value to "id=nhindocquerywsunsecured"?  
Reply | Threaded
Open this post in threaded view
|

Re: SOAP UI test results: No bean named 'xxx' is defined

johnhd_at_zen
VA is a big player- maybe our paths will cross on an implementation someday soon. :)

kalanui wrote
To ensure I understand you correctly, our endpoint, nhindocquerywsunsecured, is not a viable endpoint that CONNECT relates to and a change to our config.xml is required.  Specifically, are you suggesting we should update the "id=nhindocquerywssecured" value to "id=nhindocquerywsunsecured"?
Other way around.. Kind of.

(What I think you're getting at is that the value in this file links to values in internalConnectionInfo.xml for the internal endpoints for various services, and we can follow that path next if we need to.)

Currently in your DocumentQueryProxyConfig.xml I expect you have the <alias> element with a name @attribute of "nhindocquerywsunsecured". If you could kindly confirm this is the case first, the next steps might help things fall into place.

What would help establish this is if you could post your DocumentQueryProxyConfig.xml or at least the section under the comment that says   "Beans defined for nhindocquery" (You can see mine above. It's possible this is different in CONNECT 4.5 but I have a hunch they're nearly identical)
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: SOAP UI test results: No bean named 'xxx' is defined

kalanui
Hello johnhd at zen,

You're right VA is a big player and paths often do cross at some point in time.

I believe your suspicions were right on.  This is the entry from our DocumentQueryProxyConfig.xml file under the comment "Beans defined : nhindocquery" -
       
        <alias alias="nhindocquery" name="nhindocquerywsunsecured" />

Is the next step updating this entry to "nhindocquerywssecured" and see what happens?
Reply | Threaded
Open this post in threaded view
|

Re: SOAP UI test results: No bean named 'xxx' is defined

johnhd_at_zen
It *might* be that simple. I want to dig in to who changed that and why to help figure out the bigger picture, but in short, that should get you through this phase of the SOAP UI test, or at the very least past this error and onto something new. Won't hurt to try it.

You'll need to restart CONNECT for the change to kick in.

From there you might be in the territory of needing to implement adapters to get the gateway past the basic smoke tests and into more dynamic tests and/or production use. (You guys likely already have adapters developed that you can deploy, but I'm just guessing.)
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: SOAP UI test results: No bean named 'xxx' is defined

kalanui
Hello johnhd at zen,

It's been a while.  Last month sys admins made the change, restarted the server, and the error cleared.  Still not sure why the unsecured value was there and sys admins did not have a clear answer either.  One thing they noticed, they've seen this unsecured value in other environments that may be causing some issues so the assistance is greatly appreciated!
Reply | Threaded
Open this post in threaded view
|

Re: SOAP UI test results: No bean named 'xxx' is defined

johnhd_at_zen
Glad that solved it.

My hunch here is that someone was trying to figure out how to get the gateway to listen on an unsecured endpoint for basic testing and had tried changing this setting in that course of events. I tried the same thing once. :)

Remember, this gets you past the smoke tests using the internal "stub" MPI and test values. There's more configuration that'll need to happen to install and make use of your adapters (I assume you guys have a set of them you've developed).

Have fun!

JH
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