SOPERA Adapter 8.0 | webMethods SOPERA Adapter Documentation | webMethods SOPERA Adapter Installation and User’s Documentation | Adapter Services | Configuring Adapter Services | SOPERA Notification Provider
 
SOPERA Notification Provider
You use the SOPERA Notification Provider service template to create an adapter service that functions as a service provider when using the SOPERA notification communication style. For more information about the SOPERA notification style and service providers, see Communication Styles Support and Creating Service Providers.
*To create a SOPERA notification provider adapter service
1. Start Designer.
2. Right-click the package in which the service should be contained and select New > Adapter Service.
3. Select the parent namespace and type a name for the adapter service.
4. Click Next.
5. Select SOPERA Adapter as the adapter type and click Next.
6. Select the appropriate Adapter Connection Name and click Next.
7. Select the SOPERA Notification Provider adapter template and click Finish.
The adapter service editor for the notification service appears.
8. In the service editor, select the Adapter Settings tab at any time to confirm adapter service properties such as Adapter Name, Adapter Connection Name, and Adapter Service Template, as necessary.
9. In the service editor, select the SOPERA Notification Provider tab and specify values in the following fields based on the method for creating a provider that you want to use:
a. Using an existing IS document type:
Field
Description
Service name
The name and the path to the new SOPERA notification service. For example, {http://services.sopware.org/ExampleURI}ExampleService
Operation name
The name of the operation for the SOPERA service. For example, notify
Input document type
The fully qualified document type name for an existing IS document. For example, doc.myservice.output:notificationDoc
Use existing SOPERA service
Do not select.
Based on the IS document type that you specify, SOPERA Adapter creates the notification operation in the service registry.
b. Using the SDX-first approach:
Field
Description
Service name
The name of the SOPERA service. For example, {http://services.sopware.org/ExampleURI}ExampleService
Operation name
The name of one of the notification operations for the SOPERA service. For example, notifyForArrival
Input document type
The fully qualified document type name for the IS document that will be generated. For example, doc.myservice.input:notifyDoc
Use existing SOPERA service:
Select this box.
SOPERA Adapter creates an IS document type that matches the signature of the notification operation in the existing SOPERA service.
10. On the JMS Provider Settings tab, provide values for the following fields:
Field
Description
JMS Provider
The name of the JMS MOM Provider. Select ActiveMQ.
JMS Communication Style
The JMS communication style. Select topic.
JNDI URL
Location of the JNDI. For example, tcp://dewm:61616
11. From the File menu, click Save.