Considerations When Using REST Outbound in Siebel
From Siebel CRM 22.9 Update release, the following limitations apply to REST outbound:
-
Siebel REST API only supports OpenAPI 2.0 and OpenAPI 3.0 compatible JSON specifications.
-
Files must be in JSON format only.
-
You can import JSON files using the Web Service Wizard in Web tools.
-
The Siebel Web Tools OM makes a JBS call to the applicationcontainer_internal tomcat while importing the JSON specification which requires setting up the 64-bit Java subsystem with the CONTAINERURL parameter pointing to applicationcontainer_internal tomcat.
-
You can download the JSON specification files to your local machine, and save them in any folder. You can also save these files to any directory to which Web Tools has access.
-
You can also use the URL pointing to the JSON specification to import into Siebel, which requires setting up the proxy configuration for applicationcontainer_internal tomcat and importing certificates from the host server of the URL into the Trust Store of applicationcontainer_internal tomcat to enable the applicationcontainer_internal tomcat to connect to the host server and download the JSON specification to import.
-
When using Siebel REST API, you can use JSON files that refer to other JSON files for the definition which would be auto downloaded, provided, the proxy configuration is set for applicationcontainer_internal tomcat and certificates from the host server are imported into the Trust Store of applicationcontainer_internal tomcat.
-
Siebel REST outbound supports security of type basic authentication, and Siebel REST Outbound Request/Response Filter Services can be used to support other security authentication mechanisms to inject the required security parameters into the payload.
-
Siebel REST outbound is backward compatible, which means the JSON specification that was imported and being used after 20.8 Update release would continue to work seamlessly with this Update release.