This section describes problems that you may encounter when starting up or running any module of the . It covers three troubleshooting areas:
The following subsections provide suggestions for startup problems.
If you encounter difficulties when trying to start the connector:
If the connector cannot log on to the SAP application:
If the connector successfully logs on to the SAP application and then the session closes immediately, there may be a database problem. Check that PSAPUSER1D and PSAPUSER1I tablespaces have sufficient space allocated to them. By default, the SAP system provides minimal space for these two tablespaces. The connector requires more than the default amount of space. For more information, see Increasing log tablespace size.
If the connector dies with a message "connection to the SAP application is lost"or you get an RFC system exception, then you may have a network problem. Check the short dump for the connector user or the time when the error occurred. Use the IBM CrossWorlds Station tool or go to transaction ST22. If you still need more information, check the system log by going to transaction SM21.
If a collaboration is not subscribing to a particular business object on a specified InterChange Server, then:
For fields with binary data (RAW data type in an SAP system), the adapter will encode the value for the fields in hexadecimal rather than the more typical base64 encoding in the XML MQ message. As well, the adapter also expects data from a service call request to be in hexadecimal encoding in the XML MQ message.