Field | Description |
SOPERA Service | The name of the SOPERA service under which the specified Integration Server service will be registered. For example: {http://service.sopware.org/ExampleURI}ExampleService |
SOPERA Operation Name | The name of the operation in the specified SOPERA service. For example: NotificationFS |
Callback operation name | Leave empty. Used only in the request-callback communication style. |
Integration Server Service | To use the SDX-first approach, specify the qualified name of the IS service that will be generated. Note: In this case SOPERA Adapter creates both the IS service and its corresponding IS document types. To use the IS document-first approach, specify the qualified name of the Integration Server service that will be exposed through the SOPERA infrastructure. For example: test.string:concat Note: The input and output parameters of the specified Integration Server service must be document references. The input parameter is required, but the output parameter is optional. If no output parameter is found, the adapter creates a ONEWAY operation. |
Use Existing SOPERA Service | To use the SDX-first approach, select this check box to use an existing SOPERA service specification. The SOPERA service and operation will be loaded from the SOPERA Service Registry. You can then select the service and operation you require in the SOPERA Service Name and SOPERA Operation Name fields. Important: When this option is selected, the Integration Server service will overwrite the current provider definition stored in the registry. Do not select when you want to generate the SDX from an existing IS document type. In this case, you must specify a name for the SOPERA service and its operation in the SOPERA Service Name and SOPERA Operation Name fields respectively. |
Is Req-callback operation | Do not select. Used only in the request-callback communication style. |
Use HTTPS | Select this check box if you want to use HTTPS as the underlying transport for this provider. The HTTP and HTTPS ports are configured in the SOPERA Adapter configuration file. See
Set
SOPERA Specific Properties in the
SOPERA Adapter Configuration File for details. |
Use Plain XML | When selected, the service description will not contain any of the data structure given in the signature. Note: Selecting this option works for services with one requestMessage input parameter and one responseMessage output parameter, and is recommended when conversion to IData is not necessary or should be avoided for performance reasons. |
Field | Description |
Callback Operation name | Specify a callback operation that corresponds to the operation specified in the Operation name field. For example, if the value in the Operation name field is inOut, the value in this field could be inOutResponse. |
Is Req-callback operation | Select this check box. |