Configuring Request-Callback Consumer Services

When you want to create a request-callback consumer, you configure a request-callback consumer service using the SOPERA Generic Consumer template. For the steps to configure the service, see Configuring a Service for a Specific SOPERA Service and Operation. However, there are two ways two create a request-callback consumer as described in Creating Service Consumers. Based on the method you use, you provide different values in the Operation name, Send request only, and Output document type template fields. The values in the remaining fields are the same for both methods:

Field	Description
Service name	The name and the path to the SOPERA service to invoke. For example, {http://services.sopware.org/ExampleURI}ExampleService
Operation name	When you want to create an adapter consumer service that uses one of the request-callback operations, select the respective request-callback operation.
Callback Operation name	The name of the callback operation that corresponds to the request-callback operation selected in the Operation name field. When the Send request only checkbox is selected, leave this field empty.
Send request only	When you want to create an adapter service that only submits a request and has a listener for receiving the callback, select this box. When you want to receive the response as part of the consumer service, do not select this box.
Interaction style	When you select one of the request-callback operations in the Operation name field, the value in this field changes automatically to REQUEST_CALLBACK.
Input document type	The fully qualified document type name for the input IS document. For example, doc.myservice.input:inDoc
Output document type	When you want to create a consumer service that uses one of the request-callback operations, provide the fully qualified document type name for the output IS document. For example, doc.myservice.output:inDoc. In this case, the signature of the adapter service will contain only one output parameter: responseMessageHandler. You can use the responseMessageHandler parameter as input to the pub.wmsopera.service:getNonBlockingServiceResponse service that will wait and block for the actual result. The consumer service and the getNonBlockingServiceResponse service function together in much the same way as for a non-blocking request-response style. For more information about the getNonBlockingServiceResponse service, see pub:wmsopera.service:getNonBlockingServiceResponse. When you want to create an adapter service that only submits a request, leave this field empty. In this case, the consumer service does not have any output parameters. You must configure an adapter notification to receive the callback. For information about how to configure a consumer adapter notification, see SOPERA Callback Consumer.
Policy	The conditions under which the adapter service invokes a SOPERA service. SOPERA Adapter retrieves policies from the SOPERA Service Registry based on the location configured in the Connection Settings. For information about configuring the adapter connection settings, see Configuring Adapter Connections.
Blocking	Do not select.
Return the actual message object:	Do not select.