Option | Description | ||
Created on | Displays the date when the Integration was created. | ||
Created by | Displays the user who created the Integration. | ||
Stages tabs | Displays different stages of the Integration development. You can pull Integrations from all other stages except from the Development stage. | ||
Overview | Provides an overview of the Integration at each stage, that is, the components used to create the Integration, when the Integration was last modified, who last modified the Integration, when was the last execution, and whether the Integration is scheduled. You can also schedule, run, or expose the Integration as a REST service from this screen. | ||
Last 5 Execution Results | Click to view the last five execution results panel. This screen allows you to view the audit trail of the executions that happened in a stage. | ||
Edit | Click to modify the Integration. | ||
Delete | Click to delete the Integration from a stage. | ||
Uses | Displays the components used to create the Integration. | ||
Last modified/Last modified by | When and by whom was the Integration last modified. | ||
Status | If the Integration in a stage is scheduled, the status of the Integration displays Scheduled, else it appears as Not Scheduled. The Status appears as Schedule Paused if the Integration has been paused. | ||
Last execution | When was the Integration last executed. A warning message appears if the last execution was not successful. | ||
Next scheduled execution | When is the Integration scheduled to run again. | ||
Schedule | Click to schedule the Integration to run once immediately or at a specified date and time. You can also define a recurrence pattern if you want to run the Integration recurrently. Click Next to provide inputs to the Integration based on the defined input signature. | ||
Run Now | Click to submit the Integration for execution. You can provide inputs to the Integration based on the defined input signature. | ||
Resume | Click to start the Integration that was paused. | ||
Pull | Click to pull an Integration from a preceding stage into this stage. You can pull an Integration after you have configured the Accounts for each stage in the Account Configuration page. | ||
Remove | Click to remove an Integration from a stage. You can remove an Integration from all stages except from the Development stage. | ||
Expose as a REST service | Check this option if you want to trigger the execution of an Integration from an external system. By default, Integrations built in Integration Cloud are not accessible using REST. This feature provides you with one more option to trigger Integration executions from a software application, for example, a REST client, apart from manual and scheduled integrations from the user interface. Once the Integration is exposed as a REST service, the REST URL appears. Click the Show Advanced Options link to view the HTTP Method, sample JSON input, and the parameters that are required to invoke this Integration from an external system. Provide the usage URL, HTTP Method, modified or the sample JSON input, and necessary parameters in the external program, including the required security credentials (user name and password) while submitting the REST service. After the request is sent, the response will contain a status indicating whether the Integration has been submitted for execution. The response will also contain a reference to the execution result identifier so that a new REST call can be made later to get the execution results. Application Status Codes 0 - SUCCESS: Successfully submitted the Integration for execution. -1 - ERROR: Problem while submitting the Integration for execution. | ||
HTTP Status Codes 200 - OK 201 - Created 500 - Internal Server Error 401 - Unauthorized User Error To get the execution results, construct the URL of the new REST call from the URI field available in the Response section. To construct the URL of the new REST call, add the response URI obtained from resultReference in the Response section to: https://<sub-domain>.webMethodscloud.com/integration Example: https://<sub-domain>.webmethodscloud.com/integration/rest/assembly/ external/execution/result?resultReference= 76fb5733-6a21-4b02-864f-5e958f698373 | |||
Application Status Codes 0 - SUCCESS -1 - ERROR HTTP Status Codes 200 - OK 500 - Internal Server Error 401 - Unauthorized User Error 404 - Not Found
|