Common troubleshooting techniques and self-help information
help you identify and solve problems quickly. For information about
configuring logging properties and changing the log and trace file
names, see Configuring logging and tracing.
Techniques for troubleshooting problems
Troubleshooting is a systematic approach to solving a problem.
The goal is to determine why something does not work as expected and
how to resolve the problem. Certain common techniques can help with
the task of troubleshooting.
Log and Trace Analyzer
The adapter creates log and trace files that can be viewed
with the Log and Trace Analyzer.
Detecting errors during outbound processing
To detect errors such as invalid data or invalid
state
that occur during outbound processing, you set up business-object
application-specific data.
Resolving errors during Query interface for SAP Software processing
To avoid data being wrongly truncated with a delimiter,
you must change the default function module used by the adapter to
retrieve data from SAP tables in the query interface for SAP Software,
which processes non-unicode systems for other than English languages.
Resolving memory-related issues
You can increase the IBM Business Process Manager or WebSphere Enterprise Service Bus memory
limit if you encounter memory-related issues.
Supported codepages for WebSphere Adapter for SAP Software
Since the adapter is based on Java™,
it automatically converts language characters to Unicode when sending
data to the broker. It also automatically converts Unicode characters
to the code page of the SAP system (if set to non-Unicode) and the
SAP JCo support when sending data to the SAP system (if set to non-Unicode).
First-failure data capture (FFDC) support
The adapter supports first-failure data capture (FFDC),
which provides persistent records of failures and significant software
incidents that occur during run time in IBM Business Process Manager or WebSphere Enterprise Service Bus.
Avoiding stale connection problems in the SAP adapter
Connection related problems can be resolved in WebSphere Adapter for SAP Software using
two new properties, connectionRetryLimit and connectionRetryInterval defined
in the Managed connection factory of the SAP adapter.
Resolving selector exception error
Selector exception errors can be resolved in WebSphere Adapter for SAP Software by
identifying the IDoc which has not been configured. Using the external service wizard,
configure the IDoc to resolve the error.
Resolving a service 'sapxxnn' unknown error
While deploying an inbound module to test environment, if you get an error message stating
that the "service 'sapxxnn' unknown" (where xx is two letters, and
nn is two numbers), you can resolve this by adding a missing entry
into the services file.
Resolving SAP JCo environment setup errors
When deploying a module (Inbound or Outbound)
using any
interface with the JCo3 jar, the module deployment may fail with the NoClassDefFoundError or
a ClassNotFoundException in the run time environment.
The error can be resolved by making sure the CWYAP_SAPAdapterExt.jar,
which is a mandatory JAR, is available in the IBM Business Process Manager or WebSphere Enterprise Service Bus run
time class path.
Unreleased IDoc segments cause exceptions
When running the external service wizard or at runtime,
unreleased segments in IDocs cause the following exception error messages:
Invalid meta data exception
Using Adapter for SAP Software,
you can either configure an outbound or an inbound module for the
adapter connections.
Frequently Asked Questions
This section provides you with answers to common questions
about WebSphere Adapter for SAP Software.