Web Service Operations

Connect comes pre-configured with all baseline Web Service Names and their operations. However, some configuration changes are allowed to change the behavior of a Web Service Operation if the request comes from a specific Source Application.

The Web Service Operations (CWSOBSP) page allows administrators to view existing web service operations and allows them to configure the Web Service Operations by Source Application.

The following table provides the description of various fields for the Web Service Operations by Source Application entity:

Field	Description
Web Service Name	Indicates the Web Service Name.
Operation Name	Indicates the Web Service Operation Name.
Source Application	It is mandatory and must be a valid Source Application for current tenant. If set to Active, a client corresponding to the Source Application can invoke this web service operation. If set to Inactive, a client corresponding to the Source Application cannot invoke this web service operation.
Orchestration Service Name	Orchestration Service Name that processes service requests for this Web Service operation. When configuring Web Service Operation by Source Application, set this field to the same value configured for the WS Operation in baseline. Note: A different orchestration service name can be entered but that usually involves development effort to develop a new Orchestration Service.
Processing Pattern	It is set to Request Response for all Web Service operations in baseline. You can change this behavior by setting a different processing pattern. For example, you may want to use ONEWAY processing pattern for a specific WS Operation if a request comes from a specific Source Application. Usually, ONEWAY processing pattern is applicable only for POST/PATCH operation types.

Please refer to the CGI Advantage Connect - Configuration & Management Guide for more information on this page.