Webservice Deployment failure : Could not find Web services engine

Dear All,

We are using TeamSite 6.7.1 SP1 with OpenDeploy 6.2.0.

We are deploying Editions through Custom PortalDeliveryadaptors.

It is failing with the below error. Issue is not resolved even after restarting Opendeploy services. Can anybody help on this issue?

AxisFault faultCode: 
{http://xml.apache.org/axis/}HTTP 
faultSubcode: 
faultString: (500)Internal Server Error faultActor: 
faultNode: faultDetail: {}:return code: 500 Error 500: 
WSWS3142E: Error: Could not find Web services engine. {http://xml.apache.org/axis/}HttpErrorCode:500 (500)
Internal Server Error 
at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:744) 
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)

Find more posts tagged with

Comments

nipper

Did you turn on web services in odbase.xml ?

What port ? Typically people use 11111 or 9273

galex

Hello Nipper,

Thanks for response. In our odbase.xml, webservices were never enabled.

In our Custom Portal delivery adaptor, we are invoking a Portal Content Repository through defining a Apache Axis stub.

So does this mean that issue is with the Portal Content Repository Web Service engine? Please correct me if my understanding is wrong?

ISCBorisB

Hello Nipper,

Thanks for response. In our odbase.xml, webservices were never enabled.

In our Custom Portal delivery adaptor, we are invoking a Portal Content Repository through defining a Apache Axis stub.

So does this mean that issue is with the Portal Content Repository Web Service engine? Please correct me if my understanding is wrong?

- Have it ever worked?
- If it did, what changed?

In addition to what Andy already mentioned, take a look at OD Administration Guide.
Read Chapter "Server and Host Configuration", Section "Access Service Management",
paragraphs "Access Service Management" and "Web Services Clients". Make sure you
follow recommendations and properly allocate CSF Key File (default name's passphrase).

Also, check this article: Enabling an EAR file for Web services

galex

Hello Boris,

Thanks for the details and references. But our deployments were working till today without enabling the webservices in odbase.xml.

And I have checked our CustomPortalDelivery Adaptor and I could see that it is calling the WebServices of PortalContentRepository.

I will check with our Portal team further on the status of the Webservices in their Content Repository and update the thread.

The link on the run time changes in the WebServices EAR will be helpful for them. Thanks for that info as well.