SOPERA Adapter 8.0 | webMethods SOPERA Adapter Documentation | webMethods SOPERA Adapter Installation and User’s Documentation | Adapter Notifications | Listener Notifications | Configuring Listener Notifications | SOPERA Generic Provider
 
SOPERA Generic Provider
The following procedure describes the steps to configure a SOPERA Generic Provider listener notification using the SOPERA Generic Provider template. You use this type of listener notification to create:
*Request-response service providers
*One-way service providers
*Request-callback service providers that consist of a listener notification that calls an IS service and returns the output of that service as the callback.
*To configure a Generic 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 Generic 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 Generic Provider tab and specify the following fields:
a. To create a one-way or request-response service provider:
Field
Description
SOPERA Service
The name of the SOPERA service under which the specified Integration Server service will be registered. For example: {http://service.sopware.org/ExampleURI}ExampleService
SOPERA Operation Name
The name of the operation in the specified SOPERA service. For example: NotificationFS
Callback operation name
Leave empty.
Used only in the request-callback communication style.
Integration Server Service
*To use the SDX-first approach, specify the qualified name of the IS service that will be generated.
Note:
In this case SOPERA Adapter creates both the IS service and its corresponding IS document types.
*To use the IS document-first approach, specify the qualified name of the Integration Server service that will be exposed through the SOPERA infrastructure. For example: test.string:concat
Note:
The input and output parameters of the specified Integration Server service must be document references. The input parameter is required, but the output parameter is optional. If no output parameter is found, the adapter creates a ONEWAY operation.
Use Existing SOPERA Service
*To use the SDX-first approach, select this check box to use an existing SOPERA service specification.
The SOPERA service and operation will be loaded from the SOPERA Service Registry. You can then select the service and operation you require in the SOPERA Service Name and SOPERA Operation Name fields.
Important:
When this option is selected, the Integration Server service will overwrite the current provider definition stored in the registry.
*Do not select when you want to generate the SDX from an existing IS document type.
In this case, you must specify a name for the SOPERA service and its operation in the SOPERA Service Name and SOPERA Operation Name fields respectively.
Is Req-callback operation
Do not select.
Used only in the request-callback communication style.
Use HTTPS
Select this check box if you want to use HTTPS as the underlying transport for this provider. 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.
Use Plain XML
When selected, the service description will not contain any of the data structure given in the signature.
Note:
Selecting this option works for services with one requestMessage input parameter and one responseMessage output parameter, and is recommended when conversion to IData is not necessary or should be avoided for performance reasons.
b. To create a request-callback service provider, you specify the same values as for request-response and one-way service providers, except for the following fields:
Field
Description
Callback Operation name
Specify a callback operation that corresponds to the operation specified in the Operation name field. For example, if the value in the Operation name field is inOut, the value in this field could be inOutResponse.
Is Req-callback operation
Select this check box.
11. From the File menu, select Save.