Deploy Integration Step

Type	Description

Type

Description

deploy-integration

The last step which executes deployment of a template.

If there are objects (mappers, filters, resources or routes) in the repo folder, this step deploys them to the IM instance.

Attribute Name	Description	Example	Required

Attribute Name

Description

Example

Required

urlEncodedProperties

Specifies how to handle characters not valid in XML – they are converted into XML or another URL-safe form to prevent issues with sending unescaped characters (e.g. tab) to IM.

"urlEncodedProperties": [ "pfx-csv.settings" ]

where

pfx:ftp-separ-test.pfx-csv.settings = 'delimiter%3D%09%26quoteCharacter%3D%22%26escapeCharacter%3D%5C'

dynamicProperties

Defines how dynamic properties should be handled on templates.

name – Name of the original dynamic property.
strategy – Defines how the property should be used on the template. Possible values are "header", "placeholder" and "replace".
required – Indicates if the property is required or not.
rename – Specifies the new name under which the property will be used.
includeExpression – Uses SPEL to decide if the value should be used on the template. This is only applied when the strategy is "header."

false

Example:

{
      "type": "deploy-integration",
      "name": "deploy-integration",
      "urlEncodedProperties": [
        "pfx-csv.settings"
      ],
      "dynamicProperties": [
        {
          "name": "pfx-connection",
          "strategy": "header",
          "required": false,
          "rename": "partitionPfxApi"
        },
        {
          "name": "virtualHeaders",
          "strategy": "header",
          "required": false
        },
        {
          "name": "useVirtualHeaders",
          "strategy": "header",
          "required": false,
          "includeExpression": "#useVirtualHeaders == true"
        }
      ]
}