Packages an integration into an iar file and saves it to artifacts. This operation is intended as an alternative for exportIntegration with the difference being exportIntegration exports directly from OIC, whereas this operation is intending the integration source code to be managed in an SCM.
...
Like exportIntegration, this operation also allows the ability to manage connections and lookups along with the integration. In this case, only the .iar file needs to be in source control. The connections and lookups are pulled from the server
@since 5.4.0.1 The connections are determined from the IAR extract at build time.
@pre 5.4.0.1 The connections are determined from the live integration on the OIC Instance at build time.
This operation should be used in a build workflow. The artifact will contain the exported .iar file and optionally the connections.json file. You can also store the connection replacement properties in SCM and they will be ready to go for your deploy workflow as well.
@since 5.3.0.4 - If the Manage Connections input is false this operation will save any connections included in the source control export. See Special Considerations for more information.
| Info |
|---|
Either FDOIC_CLOUD_ACCOUNT_CODE environment instance property value or FDOIC_INP_CLOUD_ACCOUNT_CODE plugin input value should exist. When both exists, plugin input value will take precedence. See Creating/Editing a Cloud Account and Provider for details on how to setup Cloud Account for OIC. |
Environment/Instance Properties
...