odiDeploy
Imports scenarios generated by the odiBuild operation into an ODI execution repository.
This operation supports full deployment projects and package based projects of type Oracle Data Integrator. If you are using odiDeploy with the package based model, then each file within the package will sequentially be processed. Multithreading will not apply in this case.
Target Properties
Property Name | Property Code | Required | Description |
---|---|---|---|
ODI Home |
| Yes | Fully qualified path to the ODI installation directory. |
ODI JDBC Driver Path |
| Yes | Class path 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). |
Target Properties
Input Name | Input Code | Required | Description |
---|---|---|---|
Scenario Audit Flag |
| No | @since6.0.0.2 When enabled, after importing a scenario FIRST_USER and LAST_USER are updated to FDODI_ODI_USER and LAST_DATE is updated to time of deployment. If false, then FIRST_DATE and LAST_DATE are updated based on scenario file FIRST_DATE and LAST_DATE. FIRST_USER and LAST_USER would be unchanged. Defaults to false. |
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 Target.
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.
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+.Â
- style