ESCI install problem

Folks.

Have just set up ESCI in our new place, having used it just fine in the older clinic.  Git this error message, so I have missed something I imagine!

 

No unique bean of type [org.openvpms.esci.adapter.client.OrderServiceAdapter] is defined: expected single bean but found 0:

 

HELP

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: ESCI install problem

It sounds like the OpenVPMS webapp hasn't deployed correctly.

The OrderServiceAdapter is defined in <TOMCAT_HOME>/webapps/openvpms/WEB-INF/openvpms-esci.xml as:

<bean id="orderService" class="org.openvpms.esci.adapter.client.impl.OrderServiceAdapterImpl">
    <property name="factory" ref="imObjectBeanFactory"/>
    <property name="orderMapper" ref="orderMapper"/>
    <property name="supplierServiceLocator" ref="supplierServiceLocator"/>
</bean>

If this exists, then verify that openvpms-esci.xml is included in WEB-INF/applicationContext.xml:

<import resource="openvpms-framework.xml"/>
<import resource="openvpms-archetypes.xml"/>
<import resource="openvpms-reports.xml"/>
<import resource="openvpms-esci.xml"/>  <-- here -->
<import resource="openvpms-sms.xml"/>

 

Re: ESCI install problem

Greenwood runs remotely from the same server as Wembley. Wembley would use the same setting for what you describe above???  Wembley works fine.

Re: ESCI install problem

Are Greenwood and Wembley set up as practice locations running in the one OpenVPMS instance, or are they running separately?

If the former, then I can't think what the issue would be. Ordering should work regardless of which practice location is selected.

If the latter, you may need to redeploy your OpenVPMS application as per http://www.openvpms.org/documentation/csh/1.8/topics/installing-openvpms...

Re: ESCI install problem

The two databases are on the same Tomcat instance so one of th edatbases has had its esci disabled so not to cause authentication issues with te main database.

Options ar eto move second site datbase to another server/VM or install a second tomcat instance on the server.  The later may be simpler but will require some changes at the sit eend to change the connection URL (will need to configurd on a different port) 

Cheers

Tony

Syndicate content