Overview of ALE technology

The ALE Module is best used for objects such as batch objects, that are asynchronous in nature. It uses push technology that requires that there be a server listening for events. Processes called registering and installing notify the server what to listen to and from whom to expect information. Registering involves using a program itendifier to give the SAP Gateway a communication point with listener threads (servers). Function module definitions within the server interpret data that is pushed out of SAP by providing a template for this data.

The ALE module uses the RFC Server module for event handling. The ALE module uses MQ Series queues for Transaction ID (TID)and IDocs management. The connector checks for subscriptions when processing the data from SAP to the connector, resulting in transactions remaining in SAP until the collaboration is started.

Important:
In releases of the connector prior to version 4.8.2, the connector used collaborations, business objects, and maps to store Transaction IDs (TIDs) and their status in the repository, and used the local file system to store IDoc data. Version 4.8.2 of the connector replaces the previous management of TIDs and IDoc data with the use of MQSeries queues.
Note:
Because the ALE Module uses asynchronous communication, it cannot be used when cross-referencing is required.

Copyright IBM Corp. 1997, 2004