Generic troubleshooting

This section describes problems that you may encounter when starting up or running any module of the . It covers three troubleshooting areas:

Startup problems

The following subsections provide suggestions for common startup problems.

Connector fails to start

If you encounter difficulties when trying to start the connector:

Connector cannot log on to the SAP application

If the connector cannot log on to the SAP application:

Connector logs on and the session closes

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..

Note:
This problem is relevant to all connector modules except the RFC Server Module.

Connector dies

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.

Default values are not being set

Default values have been set in a business object but the connector is not picking up the values. This is a configuration issue. For default values to be used, the UseDefaults connector property needs to be set to true and each attribute requiring a default value needs to be marked as required in the business object definition.

Collaborations not subscribing to business objects (WebSphere InterChange Server only)

If a collaboration is not subscribing to a particular business object on a specified WebSphere InterChange Server, then:

Encoding of binary data (MQ Integrator Broker only)

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.

Copyright IBM Corp. 2003, 2004