This operation will create a template connection plan file using all the connections found on the current OIC environment instance. This connection plan can be applied during the importConnections operation or importIntegration operation updateConnections, importIntegration, or partialDeploy operation.
Its purpose is to allow environment-specific properties to be replaced for connections prior to deployment. This prevents manual updates of the connections artifacts in between deployments to different environments.
| Info |
|---|
Either FDOIC_CLOUD_ACCOUNT_CODE environment-instance property value or FDOIC_INP_CLOUD_ACCOUNT_CODE plugin input value should exist. When both existsexist, the 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
| 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 connecting to an OIC Instance. |
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
FDOIC_INP_CLOUD_ACCOUNT_CODE | No | The OIC account with all the required properties like Base URI, Username and Password for runningconnecting to an OIC Instance. Typically this will not be used because the value will come from the property FDOIC_CLOUD_ACCOUNT_CODE instead. | |
| Connection List | FDOIC_INP_CONNECTION_LIST | No | CSV list of connection ids to use during creation. Leave blank to use allcreate a connection plan for all connections on in the OIC environment. |
| OIC Connection Plan File | FDOIC_INP_CONNECTION_PLAN | No | Optional input to specify a different connection plan file name. Default If not specified, it defaults to 'connectionPlan.properties'. An absolute path can be specified otherwise . Otherwise the location is relative to the temp directory. |
...
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
#Add values for any properties you wish to change when updating connections.
#FlexDeploy properties or plain text are allowed
SAMPLE_FTP_CONNECTION.connection.FTP Server Host Address=${{FD_OIC_FTP_HOST}}
SAMPLE_FTP_CONNECTION.connection.FTP Server Port=
SAMPLE_FTP_CONNECTION.connection.SFTP Connection=
SAMPLE_FTP_CONNECTION.connection.Host Key=
SAMPLE_FTP_CONNECTION.connection.SSL Certificate=
SAMPLE_FTP_CONNECTION.connection.FTP Server Time Zone=
SAMPLE_FTP_CONNECTION.secure.User Name=albundy
SAMPLE_FTP_CONNECTION.secure.Password=${{FD_OIC_FTP_PASSWORD}}
SAMPLE_FTP_CONNECTION.secure.SSL Certificate Password=
SAMPLE_FTP_CONNECTION.secure.PGP Public Key=
SAMPLE_FTP_CONNECTION.secure.ASCII-Armor Encryption Format=
SAMPLE_FTP_CONNECTION.secure.Cipher Algorithm=
SAMPLE_FTP_CONNECTION.secure.PGP Private Key=
SAMPLE_FTP_CONNECTION.secure.PGP Private Key Password=
TEST_SOAP_CONNECTION.connection.WSDL URL=
TEST_SOAP_CONNECTION.connection.Service WSDL=
TEST_SOAP_CONNECTION.connection.Target Server's TLS version (Optional)=
TEST_SOAP_CONNECTION.connection.Suppress insertion of timestamp into the request (Optional)=
TEST_SOAP_CONNECTION.connection.Ignore timestamp in the response message (Optional)=
TEST_SOAP_CONNECTION.connection.Enable two way SSL for outbound connections (Optional)=
TEST_SOAP_CONNECTION.connection.Identity keystore alias name (Optional)=
|
...
In the sample above we can see we are replacing the FTP Server Host on the SAMPLE_FTP_CONNECTION with ${{FD_OIC_FTP_HOST}}. This means that FD_OIC_FTP_HOST is configured as a FlexDeploy property(most likely an environment instance property) and has a different value for each OIC environment we have. This allows us to dynamically set the FTP Server Host based on environment without ever changing our artifacts. The properties should be added to a deploy workflow that is used to deploy the integrations or update the connections. Then the workflow must be connected to the OIC target group using the topology screens.
| Info | ||
|---|---|---|
| ||
| Only properties that need to be replaced should be in the connection plan file. If there are lines without a value (as seen above), this the property will be treated as updating the property set to null. |