Troubleshooting options for debugging end-to-end processing problems using a JCo connection to an SAP data source and Web service to expose SAP BAPIs.
High-level Process Flow
This section describes high-level process flow when using SAP as a data source.
Troubleshooting Options
This section describes the options available for diagnosing process flow problems.
SAP-side Debugging
- Verify the SAP data source is running.
- Verify the SAP data source 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:
- In SAP Control Center for
SAP Mobile Platform, select Performance
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 your SAP-based MBOs fail, turning on tracing can help determine the cause.
- In SAP Control Center for
SAP Mobile Platform, select Performance
Configuration > User
Options for your SAP Mobile Server.
You can configure JVM parameters in the form
-Dxxx=xxx. Add the following JVM
parameters:
- 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.