This section describes how to create and configure an asynchronous RFC listener notification.
Creating an Asynchronous RFC Listener Notification
To create an asynchronous RFC listener notification
1 Start webMethods Developer or Software AG Designer.
2 Select New > Adapter Notification and do one of the following:
If you are using Developer, click Next.
If you are using Designer, be sure the parent namespace is selected and type a
name for the adapter notification. Click Next.
3 Select SAP Adapter as the adapter type and click Next.
4 From the list of templates, select RFC Listener Notification (asynchronous) and click Next.
5 Select the appropriate Notification Listener Name and click Next.
6 If you are using Developer, type a unique name for the asynchronous listener
notification and select the appropriate folder. Click Next.
7 Click Finish.
The Adapter Notification template creates the following items:
An RFC asynchronous listener notification
Configuring an Asynchronous RFC Listener Notification
To configure an asynchronous RFC 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:
i 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:
i Select JMS Provider.
This option publishes documents in the form of messages to a JMS provider.
ii Click the Browse button next to Connection alias name.
iii Select the name of the connection alias as it is configured on Integration Server
and then click OK.
iv 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.
v 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 Function Search tab to verify or modify the following:
Property Description
Function Pattern All or part of the name of the function module on the SAP system.
Enter a wildcard-like pattern for the function module for which you want create the notification. You can use exact patterns, or patterns with single or multiple wildcard characters.
6 Select the Request Field Selection tab to specify which fields should match the arriving message to run the notification.
7 Select the fields by selecting the appropriate boxes in the Use column. You can also
select all fields by using the icon or de-select 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 Developer user’s guide or Designer Service Development online help for your release. See “About this Guide” for specific document titles.
9 From the File menu, select Save (or Save All).
ALE Listener Notification (Asynchronous)
This section describes how to create and configure an asynchronous ALE listener notification.
Creating an Asynchronous ALE Listener Notification
To create an asynchronous ALE listener notification
1 Start webMethods Developer or Software AG Designer.
2 Select New\>Adapter Notification and do one of the following:
If you are using Developer, click Next.
If you are using Designer, be sure the parent namespace is selected and type a
name for the adapter notification. Click Next.
Group Pattern All or part of the name of the Function Group on the SAP system.
Enter a wildcard-like pattern for the Function Group for which you want create the notification. You can use exact patterns, or patterns with single or multiple wildcard characters.
Function Name The resulting function module name matching the provided pattern.
Function Description The function module description, if it is available for that function module.
Group Name The group name the function module belongs to.
5 Select the appropriate Notification Listener Name and click Next.
6 If you are using Developer, type a unique name for the ALE asynchronous listener
notification and select the appropriate folder. Click Next.
7 Click Finish.
The Adapter Notification template creates the following items:
An ALE asynchronous listener notification
A Publish Document Type
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:
i 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:
i Select JMS Provider.
This option publishes documents in the form of messages to a JMS provider.
ii Click the Browse button next to Connection alias name.
iii Select the name of the connection alias as it is configured on Integration Server
and then click OK.
iv 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.
v 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
5 Select the IDoc tab to verify or modify the following:
6 Select theRequest Field Selection tab to specify which fields should match the arriving message to run the notification.
Select the fields by selecting the appropriate boxes in the Use column. You can also select all fields by using the icon or de-select all fields by using the icon.
7 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 Developer user’s guide or Designer Service Development online help for your release. See “About this Guide” for specific document titles.
8 From the Filemenu, select Save(or Save All).