BEA WebLogic Server, User Manual

Page: 188 / 294

Error Messages in JCA
9-6 BEA Systems, Inc.
Error Messages in JCA
The following table lists an error and a solution when using JCA.
Error Messages in iBSE
The following topics discuss the different types of errors that can occur when processing
Web services through the Integration Business Services Engine (iBSE).
General Error Handling in iBSE
The Integration Business Services Engine (iBSE) serves as both a SOAP gateway into the
adapter framework and as the engine for some of the adapters. At design time and run
time, various conditions can cause errors in iBSE when Web services that use adapters are
running. Some conditions and resulting errors are exposed the same way, regardless of the
specific adapter; others are exposed differently, based on the adapter being used. This topic
explains what to expect when you encounter the more common error conditions on an
adapter-specific basis.
Usually, the SOAP gateway ( agent ) inside iBSE passes a SOAP request message to the
adapter required for the Web service. If an error occurs, the way it is exposed depends on
the adapter and the API or interfaces that the adapter uses. A few scenarios cause the SOAP
gateway to generate a SOAP fault. In general, when the SOAP agent inside iBSE receives an
invalid SOAP request, a SOAP fault element is generated in the SOAP response. The SOAP
fault element contains fault string and fault code elements. The fault code contains a
description of the SOAP agent error.
Error Solution
In Application Explorer, the following
error message appears when you attempt
to connect to a JCA configuration:
Could not initialize JCA
In the Details tab in the right pane, ensure
that the directory specified in the Home
field points to the correct directory, for
example,
iway_home /lib