IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Oracle E-Business Suite
Troubleshooting and support
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 Configure 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.- 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 BPM or WebSphere Enterprise Service Bus.- Tracing the XML Gateway web Service status
Use Oracle E-Business Suite administrative console to find the XML Gateway web Service status.- Resolving namespace conflict in Web Service/JMS interface
When using the Web Service/JMS interface to connect to two different Oracle E-Business Suite servers, if the selected root DTD and the root Element are similar, the generated artifacts will have the same namespace in the top BO, which results in a naming conflict.- Resolving connection information lost during EMD
When using different interfaces of WebSphere Adapter for Oracle E-Business Suite and accessing the EMD several times, the connection information may be lost at the Specify the Service Generation and Deployment Properties window.For example, when you are configuring the module for the first time, and choose the XML Gateway JMS processing option, to reach the Specify the Service Generation and Deployment Properties window, and then go back to the Specify the Discovery Properties window, to choose Advanced Queue for processing, and reach the Specify the Service Generation and Deployment Properties window again, you may find that the "Database URL" is empty, when you choose "Specify XA database connection information" as "Database connection information".
- Disabling end point applications of the passive adapter
- Limitations of JMS dequeue mechanism
- Known issues in advanced queue inbound
- Solutions to common problems
Some of the problems you encounter while running WebSphere Adapter for Oracle E-Business Suite with your database are described, along with solutions and workaround. These problems and solutions are in addition to technotes documented on the software support website.- Support