WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Exceptions

A set of OneAPI widgets can receive exceptions from errors emanating out of Access Gateway mediation primitives as well as out of the service layer.

As part of the exception handling, the OneAPI widgets can receive exceptions from two different layers:

All of the interfaces can generate the exceptions listed in the following table. Whatever error information is issued by the mediation flow or service layer is available as part of the error XML tag. In the event that the exception contains messageId and text elements, they are concatenated and presented within this error tag.

Table 1. Exceptions
Exception type When it occurs Exception
Service Service-related error has occurred as a result of a client invocation on the service
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml

<error>Internal platform error occurred/<error>
Service Operator's service is unavailable
HTTP/1.1 502 Bad Gateway
Content-Type: text/xml

<error>ServiceException: Error Code – Error Text </error>
Policy exception Fault relating to a policy associated with the service
HTTP/1.1 402 Forbidden
Content-Type: text/xml

<error>PolicyException: Error Code - Error Text  </error>
General Parameter is specified incorrectly or is missing
HTTP/1.1 400 Bad Request
Content-Type: text/xml

<error>Message not present</error>
General Authorization credentials are incorrect or not present
HTTP/1.1 401 Unauthorized



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.