- style
odiDeploy
- Kari Draheim (Unlicensed)
- Jack Reynebeau
- Dan Reynebeau
Imports scenarios generated by the odiBuild operation into an ODI execution repository.
Environment/Instance Properties
Property Name | Required | Description |
|---|---|---|
| Yes | Fully qualified path to the ODI installation directory. |
| Yes | Classpath for locating the JDBC Driver. |
| Yes | JDBC Connect String for the ODI Master/Work repositories. |
| Yes | JDBC Driver to use for connecting to the ODI Master/Work repositories. |
| Yes | Database schema owner of the ODI Master repository. |
| Yes | Database password for |
| Yes | User to connect to ODI instance with (must have |
| Yes | Password for |
| Yes | The name of the target ODI work repository. |
| Yes | Thread pool size used for exporting and importing scenarios (default is 5, max is 20). |
Project Properties
Property Name | Required | Description |
|---|---|---|
|
|
|
Inputs
Input Name | Required | Description |
|---|---|---|
|
|
|
Outputs
Output Name | Required | Description |
|---|---|---|
|
|
|
Artifacts
This operation consumes the artifacts produced from the odiBuild operation of this plugin, which consists of one or more XML files representing exported ODI scenarios.
Endpoint Selection
This operation will select all available endpoints associated to the environment/instance.
Endpoint Execution
This operation will randomly execute on one of the endpoints identified during selection.
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.
- style