packageBuild (OIC)

Builds OIC artifacts which includes Integration, Connection and Lookup components placed in a Source Control Management or source from a OIC cloud instance. Creates a zip artifact to be used with packageDeploy operation. If populated from backend (source OIC instance) the components will be exported. Also, will manage connections if manage connections is set to true for the integration object.

This plugin can work with iar, connections.json and .csv files populated from anywhere in a source system.

Either FDOIC_CLOUD_ACCOUNT_CODE Target property value or FDOIC_INP_CLOUD_ACCOUNT_CODE plugin input value should exist. When both exist, the plugin input will take precedence. See Creating/Editing a Cloud Account and Provider for details on how to setup Cloud Account for OIC.

Target Properties

Property Name

Property Code

Required

Description

Property Name

Property Code

Required

Description

OIC Account

FDOIC_CLOUD_ACCOUNT_CODE

No

The OIC account with all the required properties like Base URI, Username and Password for running OIC Instance.

Inputs

Input Name

Input Code

Required

Description

Input Name

Input Code

Required

Description

OIC Account

FDOIC_INP_CLOUD_ACCOUNT_CODE

No

The OIC account with all the required properties like Base URI, Username and Password for running OIC Instance.

Artifacts

This operation produces artifacts that will be stored in the artifacts repository.

Endpoint Selection

This operation will select all available endpoints associated to the Target.

Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.

Recommended Folder Structure

This folder structure is considered to be best practice.

image-20240207-082911.png
  • Connections - Connections that are exported using exportConnection operation follows this folder structure. The folder name must be the connection id which contains the connections.json file.

  • Integrations - Each integration (compressed as an IAR or uncompressed) is stored in its own folder in SCM. This matches the format of the exportIntegration operation outputs, so you can use that operation to setup your source control if you don't already have one or wish to migrate to the recommended structure.

  • Lookups - The .csv files that are exported using exportLookup operation. The file name will be the lookup name with a .csv extension.

The following macros are not currently supported in the footer:
  • style