About the Repository Objects Generated by the JSON Import

The import of OpenAPI Specification generates two objects in the Siebel repository: a proxy outbound REST business service with methods and arguments, and if necessary, a set of integration objects.

Use this JSON file extract as an example in the following topics:

• About the REST Outbound Service Created by the JSON Import

• Overview of the REST Outbound Proxy Business Service

• Overview of Generated Repository Integration Objects

• Overview of Custom Headers in REST Outbound Proxy Business Service Methods

• Adding Custom Headers in REST Outbound Proxy Business Service Methods

Note: As of this release, the definitions having keywords such as "allOf", "anyOf", "oneOf" are not supported yet. To import JSON having such keywords, you need to resolve the definitions manually and import the modified JSON. For better understanding on how to resolve these definitions manually, refer to OpenAPI 3.0 specification. Any schema which has these key words/terms would need to substitute/include the properties/objects/items from $ref or the schema provided under them as per these rules:

• oneOf – validates the value against exactly one of the subschemas
• allOf – validates the value against all the subschemas
• anyOf – validates the value against any (one or more) of the subschemas

You can also use existing Siebel Integration Objects, instead of those created by the Web Services Import Wizard, when creating a Siebel-to-Siebel outbound REST integration, as explained in the following topic:

• Using Existing Integration Objects in Outbound REST Services