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 > Flat Files
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.- Adapter returns version conflict exception message
- Log and Trace Analyzer
The adapter creates log and trace files that can be viewed with the Log and Trace Analyzer.- Known issues in editing the Rule Table
When configuring the adapter to filter event files based on a set of rules, some known issues can occur while editing the Rule Table in the Properties view. To correct the problem follow the solutions described here for each of these issues.- Support for global elements without wrapper
When global element without wrapper is used as input type, you need to take care of using the correct configuration described for the below listed scenarios to get the expected result.- Global elements in SDOX mode throw exceptions
In SDOX (Service Data Objects - XML Cursor Interface) mode, the adapter throws the DataBindingException or IllegalArgumentException exception when the global element feature is used in the business object structure.- 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.- Incomplete file processing in UNIX environments
In UNIX environments, such as AIX , the files being copied to the event directory are made available to the adapter for processing even before the files are completely copied. This leads to incorrect business data being sent to the downstream components.- Out of memory exception
- XAResourceNotAvailableException
When the IBM Process Server log contains repeated reports of the com.ibm.ws.Transaction.XAResourceNotAvailableException exception, remove transaction logs to correct the problem.- Unable to invoke adapter through webservices
- org.xml.sax.SAXParseException
When the adapter is configured with the XML data handler, an org.xml.sax.SAXParseException exception is generated if the content is not in the specified business object format. To correct the problem, make sure the file content matches the business object structure. If the file contains multiple business objects, make sure the delimiter is specified correctly.- Disabling end point applications of the passive adapter
- Solutions to common problems
Some of the problems you might encounter while running WebSphere Adapter for Flat Files with your database are described along with solutions and workaround. These problems and solutions are in addition to those documented as technotes on the software support website.- Frequently Asked Questions
This section provides you with answers to common questions about WebSphere Adapter for Flat Files.- Support
WebSphere Adapter for Flat Files documentation
Related tasks:
Related reference: