Adapter for SAP 10.1 | webMethods Adapter for SAP Documentation | webMethods Adapter for SAP Installation and User’s Guide Documentation | Adapter Notifications | Listener Notifications | Configuring Listener Notifications | ALE Listener Notification (Asynchronous) | Configuring an Asynchronous ALE Listener Notification
 
Configuring an Asynchronous ALE Listener Notification
*To configure an asynchronous ALE listener notification
1. In the adapter notification service editor for the notification you just created, select the Adapter Settings tab.
2. In the Adapter Properties area, confirm the adapter name, adapter notification name, and adapter notification template.
3. In the Publish Document to area, do one of the following:
*To publish to the Broker connected to the local Integration Server:
1. Select webMethods Broker/Local.
This option publishes documents to the local Integration Server or to the Broker connected to that Integration Server, if one is configured. This is the default.
*To publish to JMS:
1. Select JMS Provider.
This option publishes documents in the form of messages to a JMS provider.
2. Click the Browse button next to Connection alias name.
3. Select the name of the connection alias as it is configured on Integration Server and then click OK.
If the connection alias is a Broker Cluster configured with Multisend Guaranteed policy, you must add the watt property watt.art.notification.jmsSend.usePublicService and set it to true.
Adapter Runtime does not support LOCAL_TRANSACTION and XA_TRANSACTION type JMS connection alias.
4. Type the destination name defined in the JMS provider to specify the target of messages the client produces and the source of messages it consumes.
5. Specify whether the destination is a Queue or a Topic. The default is Queue.
4. Create a matching Broker/local or JMS trigger to process the request document locally, at a remote Integration Server connected to this Integration Server by way of a Broker, or to a JMS provider, depending on the "publish to" destination you selected in the previous step. Configure the trigger to ensure that the matching reply document is returned to this adapter notification.
5. Select the IDoc tab to verify or modify the following:
Property
Description
IDoc type
Identifies the type of IDoc expected by the listener notification.
Cim type
The IDoc type extension (CIM type / customer extension type).
SAP system release
The IDoc release.
Old IDoc type 2
The IDoc version; unchecked for a new version 3 IDoc, checked for old version 2 IDocs (like in 3.1 SAP systems).
Monitor IDocs
Set to "On" to have Adapter for SAP link the IDoc packet's TID with the DOCNUMs of the IDocs in that packet so that later ALE IDoc Monitoring will be possible. Set to "Off" to prevent linking the TID with the DOCNUMS.
6. Select the Request Field Selection tab to specify which IDoc fields to include in the publishable document. The request fields are available for mapping steps at design time.
Note:
By default, irrespective of the selection you make at design time, the adapter publishes all fields available to the Broker at run time.
7. In the Use column on the Request Field Selection tab, select the boxes for the required request fields. You can also select all fields by using the icon or unselect all fields by using the icon.
8. Select the Permissions tab to manage the access control list (ACL) information. Use the drop-down menu to select each of the ACL types. For general information about assigning and managing ACLs, see the webMethods Service Development Help for your release.
9. From the File menu, select Save (or Save All).