Exports scenarios identified by configurable build criteria from an ODI development repository.
This operation supports full deployment projects and package based projects of type Oracle Data Integrator, only if the scenarios are sourced from SCM (GIT, Subversion, etc..). Alternatively, you could use a partial shell operation to source from SCM.
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
ODI Home |
| Yes | Fully qualified path to the ODI installation directory which contains the odi folder. |
ODI JDBC Driver Path |
| Yes | Class path for locating the JDBC Driver. This is the complete path to the jar file which contains 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. (e.g. oracle.jdbc.driver.OracleDriver) |
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 User. |
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). |
ODI Marker Group Code |
| No | The code of the ODI Marker Group used for selecting scenarios within a build (default is |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
ODI Project Code |
| Yes | The code of the target ODI project. |
ODI Marker Code |
| No | The code of the Marker within the defined Marker Group for this build. |
ODI Include Pattern |
| No | Regular expression which identifies scenario name patterns to include in the build (e.g. .*_Order.*). |
ODI Exclude Pattern |
| No | Regular expression which identifies scenario name patterns to exclude from the build (e.g. .*_Old.*). |
ODI Versions |
| No | List of scenario version numbers (comma-separated) to include in the build. |
...
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+.