SOPERA Adapter 8.0 | webMethods SOPERA Adapter Documentation | webMethods SOPERA Adapter Installation and User’s Documentation | Adapter Services | Configuring Adapter Services | SOPERA Generic Consumer | Configuring a Service for a Specific SOPERA Service and Operation | Configuring Request-Response Consumer Services
 
Configuring Request-Response Consumer Services
When you want to create a request-response consumer, you configure a request-response 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. The following table describes the required fields and the values you provide for a request-response consumer service:
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
The name of the operation the adapter service must perform. For example. Select RequestResponseOperation
Callback Operation Name
Leave  empty.
Send request only
Do not select.
Interaction style
The way in which the adapter service interacts with the SOPERA infrastructure.
When you select the request-response operation in the Operation name field, the value in this field changes automatically to REQUEST_RESPONSE.
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.
Output document type
The fully qualified document type name for the output IS document. For example, doc.myservice.output:inDoc
Important:
Specify a unique name for the output document type. If you specify an existing document type name, the IS document type will not be generated correctly.
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
Determines the invocation style of the adapter service:
*When selected, the adapter service is configured as blocking and it waits for the actual service result. By default, blocking is selected.
*When not selected, the adapter service is configured as non-blocking and returns a response message handler. This message handler can be passed to the pub.wmsopera.service:getNonBlockingServiceResponse utility service, using a flow service that gets the actual result. This allows a complex service to start as soon as all of its input parameters are available and to only block when the output of the service is needed.
Return the actual message object
Determines how the service provider returns the response message to the service consumer.
*When not selected, the response message is transformed into Integration Server data structures. This is the default.
*When selected, the response message returns as an actual message object. This is useful when a response message contains attachments or is very large, because an actual message object enables you to retrieve the attachments or the message content in a stream-based manner.
Note:
If the response contains attachments, then the response is returned as an object whether you select this option or not. Ensure that the adapter services are configured appropriately.