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 Any SOPERA Service and Operation
 
Configuring a Service for Any SOPERA Service and Operation
In this configuration the SOPERA service and operation are parameters of the adapter service. The benefits of this approach are increased flexibility (run-time selection of SOPERA service is possible) and less configuration overhead (only one adapter service can be used for multiple SOPERA service invocation).
To configure a generic invocation adapter service, use the same procedure as described in the Configuring a Service for a Specific SOPERA Service and Operation section, but leave the fields on the SOPERA Generic Consumer tab blank. Specify configuration values as input values for the adapter service parameters that you can view on the Input/Output tab of the adapter service template:
Input Parameters
serviceName
The name of the SOPERA service.
operationName
The name of the operation to perform for the adapter service.
policyId
The policy identifier for the SOPERA service.
requestMessageString
The request that the adapter service sends as an XML String.
Output Parameters
responseMessageString
The response message as an XML String, when the Return the actual message object field on the SOPERA Generic Consumer tab is set to false.
responseMessageObject
The response message as an Object, when the Return the actual message object field on the SOPERA Generic Consumer tab is set to true.
When the response contains attachments, the response always returns as a responseMessageObject.
responseMessageHandler
The message handler passed to the pub.wmsopera.service:getNonBlockingServiceResponse utility service when the communication style is request-response non-blocking.