@Since 5.0.0.4 - for Oracle Data Integrator 12.2.1+ only.
...
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| ODI Home |
| Yes | Fully qualified path to the ODI installation directory. |
| ODI JDBC Driver Path |
| Yes | Classpath for locating the JDBC Driver. |
| ODI JDBC URL |
| Yes | JDBC Connect String for the ODI Master/Work repositories. |
| ODI JDBC Driver |
| Yes | JDBC Driver to use for connecting to the ODI Master/Work repositories. |
| ODI Master User |
| Yes | Database schema owner of the ODI Master repository. |
| ODI Master Password |
| Yes | Database password for ODI Master User. |
| ODI User |
| Yes | User to connect to ODI instance with (must have |
| ODI Password |
| Yes | Password for |
| ODI Work Repository |
| Yes | The name of the target ODI work repository. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Deployment Archive Name | FDODI_DEPLOY_ARCHIVE_NAME | No | The name of the Deployment Archive file. The plugin input will take precedence if provided. |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Deployment Archive Folder | FDODI_INP_DEPLOY_ARCHIVE_FOLDER | No | The folder from which to source the archive file. Defaults to the artifacts directory if not provided. |
| Deployment Archive Name | FDODI_DEPLOY_ARCHIVE_NAME | No | The name of the Deployment Archive file. This value will override the project property, and be used for every project. |
...
| Tip | ||
|---|---|---|
| ||
The properties and inputs for this operation are used according to the following rules:
|
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation consumes the artifacts produced from the a build workflow.
Endpoint Selection
This operation will select all available endpoints associated to the environment/instance.
...
Special Considerations
This deploy operation implements change detection by avoiding importing scenarios which have not been modified, therefore providing increased throughput for builds containing a large number of scenarios. This is accomplished by comparing the update date of source XML scenarios against the target repository, and taking care to preserve the update dates from the source repository.
Note that a deployment request marked Force Deploy will deploy all scenarios contained in the build independent of whether they match what is in the target repository.
operation was added @Since 5.0.3 If scenarios identified during build are linked to scenario folders, those folders are automatically exported (without children) and stored as part of the build artifacts. During deployment, any scenario folders in the build artifacts are imported (insert only) into the target folder. In order for scenarios to be linked correctly in the target repository, any existing scenario folders in the target must have the same global id as the the same folder on the source. If the folder was created manually on the target, but with the same name as the source, the deployment will not create the scenario folder and the scenario will be imported without being linked. This feature is only available for ODI 12.2+0.4, and is available for Oracle Data Integrator 12.2.1+ only.