This section describes problems that you may encounter when starting up or running the ALE Module. It covers the following areas:
The following subsections provide suggestions for startup problems.
If the connector cannot log on to or register with the SAP application:
For more information, see Configuring the connector and Appendix D, Troubleshooting the connector.
If your connector is not picking up events from the SAP application:
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.
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.
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.
To recover from failures during event notification, the connector does the following:
Using the log file prevents the connector from sending the same IDoc multiple times to the integration broker. The connector keeps the log file in memory to enhance performance. The connector accesses the file on disk only to update it with a new entry, and reads the log file only at recovery time.
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:
If a subscribing business object is not being processed by the ALE Module, then: