Troubleshooting options for debugging end-to-end processing problems
using a JCo connection to an SAP datasource and Web service to expose SAP BAPIs.
High-level Process Flow
This section describes high-level process flow when using SAP as a
datasource.
SAP JCo Connection Process Flow
Troubleshooting Options
This section describes the options available for diagnosing process flow problems.
SAP-side Debugging
- Verify the SAP datasource is running.
- Verify the SAP datasource privileges have been granted properly.
- Ensure the SAP BAPIs are exposed properly as Web services.
- Verify credentials are correct.
- Check for error messages.
Search Troubleshooting for the topic Verifying SAP Prerequisites.
SAP JCO Connection Debugging
- Verify the JCo connection is configured properly and is
operational.
- Check for error messages.
- If you experience an unresponsive
RFC connection, consult with the SAP administrator for a resolution.
SAP Mobile Platform-side Debugging
- Verify SAP Mobile Server is up and running.
- Turn on JCo tracing in the SAP Mobile Server
system properties. If your SAP-based MBOs fail, tracing can help determine
the cause. To turn on tracing:
- In SAP Control Center for SAP Mobile Platform, select Server Configuration > User Options for your SAP Mobile Server. You can configure JVM
parameters in the form -Dxxx=xxx. Add the following JVM
parameters:
-Djco.trace_level=[0-10]
-Djco.trace_path=[defined_path]
The jco.trace_level
determines the level of detail of tracing you get from the JCo
libraries. The jco.trace_path
determines a directory where trace files get stored(if the
jco.trace_path value specifies a file, JCo tracing
fails silently, so only specify the directory).
For
example:
-Djco.trace_level=5
-Djco.trace_path=SMP_HOME\Servers\UnwiredServer\logs
- Verify the JCo connection is configured properly.
For SAP Mobile Server JCo connections, see the topic Preparing SAP Mobile Server to Connect to SAP
using Java Connectors in System
Administration.