Error calling EBusiness Suite Public API's from SOA

Question

Hi, I'm doing some proof of concept work with SOA Suite v 10.1.3.10. When I try to call any of the EBiz suite public API's that have user defined types for records and tables passed as parameters I get the following error when the Oracle Application Adaptor tries to create the WSDL and necessary sql scripts:
Error while writing wsdl file C:\Program
Files\jDeveloper\jdev\mywork\CRMTest\CRMTest\CRMOut3.wsdl.
Exception:
The wrapper procedure, CS_SERVICEREQUEST_PUB$CREATE_,
could not be found in the package, XX_BPEL_CRMOUT3, for the schema, APPS.
To move beyond this I created a skeleton stored procedure containing a declaration for the
CS_SERVICEREQUEST_PUB$CREATE_ function (and selected overwrite script in the wizard) and am now getting the following error:
Error while writing wsdl file C:\Program
Files\jDeveloper\jdev\mywork\CRMTest\CRMTest\CRMOut3.wsdl.
Exception:
Unable to expand a user defined type definition.
An unexpected exception occurred while trying to analyze teh user defined type definition of parameter .
Check to ensure that the user defined type is defined correctly in the database. Contact oracle support if
error is not fixable.
This works fine for the API's that just use basic types. I've also tried this with the Database Adapter and this seems to work OK too, just not with the Oracle Application Adapter.
Thanks for any help you can provide
Mike
Edited by: user2554089 on Jan 5, 2009 1:38 PM

Answer 1

Hi Christine,
It looks like a couple of the Application Servers aren't starting when OC4J starts, I need to hunt through the logs to identify the source of the problem but in the meantime I'm starting them manually from the Application Server Control. To do this expand the OC4J server and check that all the services are running (green up arrow) any that are down, click on them and start them manually. I had to manually start hw_services and deploy_service but the Worklist now runs fine.
It's possible that you won't see this problem yourself as you're upgrading from a later release than I started from but from a brief google session it looks like others have seen the same problem for different reasons. I've seen some posts that refer to the default port of the Worklist changing so that it needs starting with http://host:8988/integration/worklistapp/Login instead of http://host:8888/integration/worklistapp/Login.
Because I'm also having problems shutting down SOA suite I suspect that the patch has mangled one of the configuration scripts and I'll post the root cause when I've had chance to pore over the logs.
Regards
Mike
Edited by: Mike Ronson on Jan 19, 2009 3:28 PM