The deployOCC operation is a package-based project deploy operation for use with FlexDeploy's package-based deployment system. It deploys packages created by the buildOCC operation to a CX Commerce node using DCU and PLSU.

If the OCC Account and Source OCC Account are the same, page layouts will be skipped automatically. They will not show up in the deployment files tab.

If the node of the OCC Account matches the node in the .ccc/config.json node property, a dcu --put command will be used instead of a dcu --transfer. Note that dcu --put will check for modification before deployment. You can work around this by either checking in a modified config.json file with a different node (one that is not any of your actual nodes).

Target Properties

Property Name	Property Code	Required	Description

Property Name

Property Code

Required

Description

OCC Account

FDOCC_CLOUD_ACCOUNT_CODE

Yes

The Oracle CX Commerce account with all the required properties like URL, App Key etc.

The account will be different for each OCC environment.

The target node that is receiving the contents of the deployment package.

Source OCC Account

FDOCC_SOURCE_CLOUD_ACCOUNT_CODE

No

A link to an Oracle CX Commerce account with all the required properties like URL, App Key etc.

This account designates the source node for the PLSU command.

This is only used with Page Layout deployments. Page layout deployments transfer the page layouts directly from the source node to the target node.

Node Executable Path

FDOCC_NODE_PATH

No

Paths to both node and npm packages (where the dcu/plsu executables are stored). Used in populate, build and deploy operations when provided. If not provided dcu and plsu commands must be on PATH.

Windows example: C:\Program Files\nodejs\;C:\Users\developer\AppData\Roaming\npm

Unix example: /path/to/node:/path/to/npm

Inputs

Input Name	Input Code	Required	Description

Input Name

Input Code

Required

Description

Publish After Deploy

FDOOCC_INP_PUBLISH

No

Start and monitor a publish operation until complete as part of this deployment.

If checked, a publish operation will be started after the deployment is complete, and the plugin operation will block until the publish is complete.

Artifacts

This operation consumes a zip file artifact from the artifacts repository. The zip file may be empty if only Page Layouts are being transferred. Page Layouts are transferred directly from instance to instance.

Endpoint Selection

This operation will select all available endpoints associated to the Target. You can add any endpoint to Target as this operation does not depend on any external libraries or utilities.

Endpoint Execution

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