Skip to main content
Export connection metadata and any attachments from the given OIC instance.  Each connection found will be exported under its own connection folder with its contents consisting of a ‘connections.json’ file as well as attachments. This operation is designed to be used with our browser extension, which collects a list of IDs from the OIC Integrations page and triggers a webhook. The webhook then initiates a utility workflow that exports the projects and commits the resulting files to your source control management (SCM) system. Following plugin operation in workflow image-20250508-151653.png exports as shown below. Note that you can use absolute path in Export Folder to export in a folder other than artifacts (FD_ARTIFACTS_DIR). image-20250508-151752.png
Either FDOIC_CLOUD_ACCOUNT_CODE Target 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.

Target Properties

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.

Project Properties

Property Name

Property Code

Required

Description

Connection List

FDOIC_CONNECTION_LIST

No

CSV list of connection ids to export.  Leave blank to export all non-project connections found on the server.

Inputs

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.

OIC Connection List

FDOIC_INP_CONNECTION_LIST

No

Optional List of non-project Connection Ids to export. This input should only be used in a utility fashion, otherwise the Connection List project property should be used.

Export Folder

FDOIC_INP_EXPORT_SUBFOLDER

No

Optional subfolder within artifacts directory for exporting connections, or specify an absolute path. If you are using standard project for build and deploy using export and import operations, it is recommended to leave this blank. Since 9.0.0.6.

e.g.: FD_TEMP_DIR + “connections” (specified as Groovy Expression to allow for dynamic value for temporary directory)

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.

Special Considerations

Attachments

This operation will also export any relevant attachments for the connections and save them in the artifacts repository.

Example Artifacts Dir After Export

12343/2312/artifacts/HR_SOAP_CONNECTION/connections.json12343/2312/artifacts/HR_SOAP_CONNECTION/attachments/HR_SOAP_CONNECTION/targetWSDLURL/hr.wsdl12343/2312/artifacts/MY_REST_ENDPOINT_INTERFAC/connections.json