调用Oracle EBS SOA服务时常见的几个错误

1. Before usage of a Oracle E-Business Suite (EBS) Integrated SOA Gateway (ISG) service, it should be generated and deployed. See, page “TroubleShooting Service Generation” for errors on service generation and deployment.

2. Any third party Web Service Client can be used to test ISG Services.

3. Common errors in Service Invocations are:-

Fault from server : Missing wsse:Security in SOAP Header.
Cause: This error is thrown by server if SOAP request does not contain a Web Service Security Header in SOAPHeader section of SOAPEnvelope.
Resolution: Pass a valid Web Service Security Header, containing valid Username token, in SOAPHeader.

Fault from server : Policy requires authentication token.
Cause: This error is thrown by server when either Web Service Security Username Token in Security header is missing or is invalid.
Resolution: Pass a valid Web Service Security Username Token in Security header.

Fault from server : The security token could not be authenticated or authorized
Cause: This error is thrown by server when username or(/and) password in Web Service Security Username Token is invalid.
Resolution: Pass valid oracle applications username and password in Web Service Security Username Token.

Fault from server : User not authorized to execute service
Cause: This error is thrown by server when user given in Web Service Security Username Token is not authorized to execute the Web Service function being invoked in SOAP Request.
Resolution: Create grant at user, role or global level from Integration Repository UI to authorize the the user to execute Web Service function. Clear cache from Functional Administrator Responsibility.

Fault from server : Responsibility key is not valid
Cause: This error is thrown by server when Responsibility Key passed in Responsibility Header in SOAHeader is invalid.
Resolution: Server expects a valid Responsibility Key in Responsibility Header in SOAHeader.
Use this query to find valid Responsibility Keys for a particular user:-
Select resp.RESPONSIBILITY_KEY, grp.SECURITY_GROUP_KEY,
APP.APPLICATION_SHORT_NAME
From FND_USER_RESP_GROUPS furg, FND_USER usr, fnd_responsibility_vl
resp,FND_SECURITY_GROUPS grp,FND_APPLICATION APP
where furg.user_id=usr.user_id
and furg.RESPONSIBILITY_ID=resp.RESPONSIBILITY_ID
and furg.SECURITY_GROUP_ID=grp.SECURITY_GROUP_ID
and furg.RESPONSIBILITY_APPLICATION_ID=APP.APPLICATION_ID
and usr.user_name=

Fault from server: Responsibility Application Short name is not valid.
Cause: This error is thrown by server when Application Short name in RespApplication Header in SOAHeader is invalid.
Resolution: Server expects a valid Application short name in RespApplication Header in SOAHeader. Use query given above to find a valid Application short name.

Fault from server: Security Group Key is not valid.
Cause: This error is thrown by server when Security Group Key in SecurityGroup Header in SOAHeader is invalid.
Resolution: Server expects a valid Security Group Key in SecurityGroup Header in SOAHeader. Use query given above to find a valid Security Group Key.

Fault from server: NLS Language is not valid.
Cause: This error is thrown by server when NLS Language in NLSLanguage Header in SOAHeader is invalid.
Resolution: Server expects a valid NLSLanguage value in NLSLanguage Header in SOAHeader. Use the following query to find a valid NLSLanguage:
SELECT NLS_LANGUAGE
FROM FND_LANGUAGES
WHERE INSTALLED_FLAG in (‘B’,'I’);

Fault from server: Service is not deployed.
Cause: This error is thrown by server when invoked service is generated but not deployed.
Resolution: Deploy this service from Integration Repository UI.

Fault from server: Error occured while service was processing.
Cause: This error is thrown by server when a internal error happens in Service Provider.
Resolution: View SOAP Response via SOA Monitor UI. It has a error trace of the error happened in server. This should give a fair idea of what went wrong.

source:http://aabhishek.wordpress.com/about/oracle-ebs-integrated-soa-gateway-isg/troubleshooting-service-invocation/