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 | ![]() ![]() |
Send request only | ![]() ![]() |
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 | ![]() 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. ![]() 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. |