API Endpoints are either characterized as either Consumer or Provider Endpoints. Both types of Endpoints are automatically generated in the CIC Cockpit when Web Service Consumer or Provider objects are created in CIC Studio and deployed to the Integration Server.
Both types of Endpoint reflect API requests and responses in your integration. The details of these messages and responses can be viewed from the CIC Cockpit.
Changes to API Endpoints in the CIC Cockpit are limited to renaming only. Endpoints can not be created or deleted directly from the CIC Cockpit.
Any integration using these Endpoints is driven by the Integration Engine and CIC Studio. API Endpoints are not available to be used in Data Flows in the CIC Cockpit. They are, however, used by CIC Cockpit to display Job information on the Job List page and Job Details page.
API Consumer Endpoints (shown below) are auto-generated in the CIC Cockpit when Web Service (WS) Consumer objects are created in CIC Studio and deployed to the Integration Server. Multiple WS Consumer objects referencing the same host and vault alias value (if applicable) are combined into a single API Consumer Endpoint, which can be viewed from the Jobs page.
API Provider Endpoints are auto-generated in the CIC Cockpit when Web Service (WS) Provider objects are created in CIC Studio and deployed to the Integration Server.
Related Topics: