Troubleshooting for the ALE Module

This section describes problems that you may encounter when starting up or running the ALE Module. It covers the following areas:

Startup problems

The following subsections provide suggestions for startup problems.

Connector cannot log on to or register with the SAP application

If the connector cannot log on to or register with the SAP application:

Connector is not picking up events

If your connector is not picking up events from the SAP application:

Connector appears to be polling but events are not being picked up

Event handling

The connector logs information about successfully processed IDocs in a JMS-MQ event message (in the queue specified in the SAPALE_Event_Queue configuration property) to the EventState.log file. This file is located in the directory specified in the AleEventDir configuration property.

Note:
Each event message can contain multiple IDocs, each of which represents a business object.

If the connector goes down before it processes all IDocs in the current event message, it uses the EventState.log file during recovery to ensure that it sends each IDoc only once to the integration broker.

Important:
The connector does not create the log file automatically the first time it processes an event. You must create this file for before you run the connector for the first time.

The format of the log file is:

TID: OS, 1S, 2F, 3U

where <TID> is the the current transaction ID being processed, and each number represents the sequence number of all work units in the event message.

For example, assume that the connector has successfully processed three of the first four IDocs in the current event message, and that the second IDoc failed processing. Assume also that the connector has not yet finished processing the current event message. In this case, the EventState.log file might look like the following:

<TID> :: OS, 1F, 2S, 3S

If the connector went down before processing the entire event message, at startup the connector uses the information in the log file to resume processing the events in the message at the point where it had stopped processing. The connector reads the log to get the transaction ID of the event to be recovered, the latest work unit and the status of each work unit. Then the connector begins sending to the integration broker the business objects that represent all IDocs in the event message whose sequence number is greater than the last number in the log file. For example, given the log file above, the connector begins processing the fifth IDoc in the current event message.

The connector keeps the contents of the log file in memory to enhance performance. It accesses the file on disk only to update it with a new entry. The connector reads the log file only at recovery time.

For information on how the connector uses the EventState.log file in the recovery process, see Failure recovery.

Failure recovery

Note:
The following recovery steps do not apply if a disk failure occurs or a disk is full.

To recover from failures during event notification, the connector does the following:

  1. The connector processes IDocs from the JMS-MQ message in the event queue (specified in the SAPALE_Event_Queue configuration property). When it successfully processes a IDoc, the connector logs an entry in the EventState.log file.
  2. After the connector processes all IDocs in an event message, it clears the EventState.log file and begins writing entries to it from the next event message.
  3. If the connector goes down before it processes all IDocs in an event message, it uses the information in EventState.log to determine where to begin processing during the recovery process. When it comes back up, the connector checks whether there are any entries in the log file.

Recovery from business object creation errors

The connector has created only the header portion of the message in the Wip queue but not the data portion. To handle recovery for such a failure, do the following:

  1. Examine the SAP connector log for error messages pertaining to the business object's name, message type, or verb.
  2. Make the appropriate corrections to the business object definition or the connector configuration.
    Note:
    Configuration changes may include changes to MQSeries queues. For more information, see Prerequisites to running the ALE Module.
  3. Restart the connector.

Request processing

If a subscribing business object is not being processed by the ALE Module, then:

Copyright IBM Corp. 1997, 2003