odiBuild
- Karl Henselin
Exports scenarios or LoadPlan 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 or LoadPlan are sourced from SCM (GIT, Subversion, etc..). Alternatively, you could use a 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 |
| No | The code of the target ODI project. |
ODI LoadPlanName |
| No | ODI Load plan Name to include in the build(More than one Name can be configured as comma separated list). |
ODI ObjectType |
| No | Select the ODI Object Type to include in the Build( by default scenarios will included in the Build). |
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. |
Artifacts
This operation produces artifacts that will be stored in the artifacts repository. The artifacts consist of one XML file per scenario/LoadPlan that was exported during the build operation.
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
In addition to the required ODI project code (FDODI_PROJECT_CODE) there are several options to further filter the scenarios that are included in the build:
ODI Markers – Folders or objects (interfaces, mappings, packages, procedures, and variables) can be identified by tagging them with the ODI Marker (ODI Marker Code) within the ODI Marker Group (ODI Marker Group Code). Marking a folder will result in all scenarios within that folder being included in the build. See Oracle Data Integrator documentation for instructions on creating and using Markers and Marker Groups.
Include/Exclude Patterns – Java regular expressions can be used within the ODI Include Pattern and ODI Exclude Pattern to identify which scenarios/loadPlan should be included or excluded in the build. In both cases the expressions are matched against the scenario/LoadPlan name (not the owning object's name).
Scenario Version – You have the option to identify the specify version numbers of the scenarios to include in the build by using the
FDODI_VERSIONproperty. Multiple version numbers can be specified by comma separating them. If no versions are specified, all versions of selected scenarios will be included. Specify -1 to only export the latest version.
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 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+.Â
Note: The export of a Load Plan does not include the scenarios referenced by the Load Plan. Scenarios used in a Load Plan need to be exported separatelyÂ
- style