Debugging message flows that contain WebSphere Adapters nodes

You can use various methods to monitor message flows that include WebSphere® Adapters nodes.

About this task

Before you use any of the methods listed in this section, ensure that the appropriate JAR files and shared libraries are available to the WebSphere Adapters nodes. For more information, see Preparing the environment for WebSphere Adapters nodes.

Also, check for the latest information about WebSphere Adapters; see WebSphere Adapters technotes.

User and service trace: You can use user and service trace to trace a message flow that contains WebSphere Adapters nodes. For more information, see Using trace.
Flow debugger: Use the flow debugger in the normal way to debug a message flow that contains WebSphere Adapters nodes. For more information, see Testing your message flow by using the flow debugger.
Adapter event table: The WebSphere Adapters nodes use an event table to communicate the outcome of operations asynchronously to a calling application. For more information, see Creating a custom event project in PeopleTools.

Handling exceptions that are raised by a WebSphere Adapters request node

The WebSphere Adapters request nodes raise exceptions that indicate the following Enterprise Information System (EIS) failures.

Message number	Exception type	Explanation
BIP3511	`RecordNotFound`	The requested record could not be found in the EIS.
BIP3512	`DuplicateRecord`	An attempt was made to create a record that already exists in the EIS.
BIP3513	`MultipleMatchingRecords`	A retrieve request matched more than one record. To retrieve multiple records, perform a `retrieveall` operation.
BIP3515	`MatchesExceededLimit`	A `retrieveall` exception returned more entries than the maximum allowed number.
BIP3516	`MissingData`	The message tree that was sent to the adapter request node does not have all the required fields set.

If an exception occurs that does not fit into the categories in the table, the node raises a general BIP3450 message that describes the problem.

You can use these exceptions to perform special processing when you do not want the exceptions to be treated as errors. For example:

If a create operation fails because the record already exists, you could modify the request to an update.
If a retrieve operation fails because the request matches more than one record, you could try a retrieveall operation instead.
If a retrieve operation fails because the record could not be found, an empty record could be returned.

To handle these exceptions, you can connect a message routing node, Compute node, or JavaCompute node to the Failure terminal of the WebSphere Adapters request node, and route the exception to other processing nodes based on the exception message number.

XSD Schema Validation problem

When you configure an SAP adapter in the IBM App Connect Enterprise Toolkit, you might see the following warning, referring to an unresolvable IBM XML schema:

CTDX1101W : XSD: The location '' has not been resolved 
example1.xsd /EAI_ESB_LIB line 2 
example2.xsd /EAI_ESB_LIB line 2 
XSD Schema Validation Problem

This warning is caused by the following namespace reference in an <xsd:import> element:

<xsd:import namespace="http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/metadata"/>

No types or elements from this namespace are referenced in the logical structure of the XSD. An XML schema that references this namespace is in the referenced connector project, and is pointed to from the XML catalog. The XML catalog entry is populated when the SAP connector project is brought into the workspace.

This warning is benign and can be safely ignored, because it does not affect the structural content of your schema definition.

Tuning the SAP adapter for scalability and performance

You can monitor the performance of a message flow that contains SAP nodes by using user trace, and accounting and statistics data, then use that information to tune your flow by configuring an appropriate number of listeners and additional instances for the message flow.