Exports scenarios identified by configurable build criteria from an ODI development repository.
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). |
| No | The code of the ODI Marker Group used for selecting scenarios within a build (default is |
Property Name | Required | Description |
---|---|---|
| Yes | The code of the target ODI project. |
| No | The code of the Marker within the defined Marker Group for this build. |
| No | Regular expression which identifies scenario name patterns to include in the build. |
| No | Regular expression which identifies scenario name patterns to exclude from the build. |
| No | List of scenario version numbers (coma separated) to include in the build. |
Input Name | Required | Description |
---|---|---|
|
|
|
Output Name | Required | Description |
---|---|---|
|
|
|
This operation produces artifacts that will be stored in the artifacts repository. The artifacts consist of one XML file per scenario that was exported during the build operation.
This operation will select all available endpoints associated to the environment/instance.
This operation will randomly execute on one of the endpoints identified during selection.
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:
FDODI_MARKER_CODE
) within the ODI Marker Group (FDODI_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.FDODI_INCLUDE_PATTERN
and FDODI_EXCLUDE_PATTERN
to identify which scenarios should be included or excluded in the build. In both cases the expressions are matched against the scenario name (not the owning object's name).FDODI_VERSION
property. Multiple version numbers can be specified by comma separating them. If no versions are specified, all versions of selected scenarios will be included.