odiDeploy
- Copy Page Tree
- Ben Hoffman
- Karl Henselin
- Erick Jones
Imports scenarios generated by the odiBuild operation into an ODI execution repository.
Environment/Instance Properties
| 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. |
| ODI Thread Count |
| Yes | Thread pool size used for exporting and importing scenarios (default is 5, max is 20). |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Inputs
Input Name | Input Code | 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