SOPERA Adapter 8.0 | webMethods SOPERA Adapter Documentation | webMethods SOPERA Adapter Installation and User’s Documentation | Adapter Notifications | Listener Notifications | Configuring Listener Notifications | SOPERA Request-Callback Provider
 
SOPERA Request-Callback Provider
You use the SOPERA Request-callback Provider template in one of the methods for creating a request-callback provider. With this method you first create an adapter notification that receives the request and publishes a document. Then using the SOPERA Callback Sender Provider template, you create an adapter service that sends a response to the request as described in SOPERA Callback Sender Provider. The following procedure describes how to create a request-callback provider listener notification.
*To create a SOPERA request-callback provider listener notification
1. Start Designer.
2. Right-click the package in which the notification should be contained and select New > Adapter Notification.
3. Select the parent namespace and type a name for the adapter notification.
4. Click Next.
5. Select SOPERA Adapter as the adapter type and click Next.
6. Select the SOPERA Request-callback Provider notification template and click Next.
7. Select the appropriate Notification Listener Name and click Next.
8. Click Finish.
Designer creates a listener notification and a publishable document type, and the editor for the adapter notification appears.
9. In the editor for adapter notifications, select the Adapter Settings tab to confirm notification properties such as the Adapter Name, Adapter Listener Name, and Adapter Notification Template as necessary.
10. In the editor for adapter notifications, select the SOPERA Request-callback Provider tab and specify the following fields:
Note:
This type of listener notification supports only the SDX-first approach. As a result, the services and their operations are populated on loading the listener notification.
Field
Description
SOPERA Service
The name of the SOPERA service. For example: {http://service.sopware.org/ExampleURI}ExampleService
SOPERA service operation
The name of the operation in the specified SOPERA service. For example: getUpper
Input document type
The fully qualified document type name for the input IS document. For example, doc.myservice.input:inDoc.
Important:
Specify a unique name for the input document type. If you specify an existing document type name, the IS document type will not be generated correctly.
Use HTTPS
Select this check box if you want to offer Integration Server services via HTTPS. The HTTP and HTTPS ports are configured in the SOPERA Adapter configuration file. See Set SOPERA Specific Properties in the SOPERA Adapter Configuration File for details.
11. From the File menu, select Save.