Exports scenarios identified by configurable build criteria from an ODI development repository.

Environment/Instance Properties

Property Name	Required	Description
`FDODI_ODI_HOME`	Yes	Fully qualified path to the ODI installation directory.
`FDODI_JDBC_DRIVER_PATH`	Yes	Classpath for locating the JDBC Driver.
`FDODI_JDBC_URL`	Yes	JDBC Connect String for the ODI Master/Work repositories.
`FDODI_JDBC_DRIVER`	Yes	JDBC Driver to use for connecting to the ODI Master/Work repositories.
`FDODI_MASTER_USER`	Yes	Database schema owner of the ODI Master repository.
`FDODI_MASTER_PASSWORD`	Yes	Database password for `FDODI_MASTER_USER`.
`FDODI_ODI_USER`	Yes	User to connect to ODI instance with (must have `SUPERVISOR` privileges).
`FDODI_ODI_PASSWORD`	Yes	Password for `FDODI_ODI_USER`.
`FDODI_WORK_REPOSITORY`	Yes	The name of the target ODI work repository.
`FDODI_THREAD_COUNT`	Yes	Thread pool size used for exporting and importing scenarios (default is 5, max is 20).
`FDODI_MARKER_GROUP_CODE`	No	The code of the ODI Marker Group used for selecting scenarios within a build (default is `FLEXDEPLOY`).

Project Properties

Property Name	Required	Description
`FDODI_PROJECT_CODE`	Yes	The code of the target ODI project.
`FDODI_MARKER_CODE`	No	The code of the Marker within the defined Marker Group for this build.
`FDODI_INCLUDE_PATTERN`	No	Regular expression which identifies scenario name patterns to include in the build.
`FDODI_EXCLUDE_PATTERN`	No	Regular expression which identifies scenario name patterns to exclude from the build.
`FDODI_VERSIONS`	No	List of scenario version numbers (coma separated) to include in the build.

Inputs

Input Name	Required	Description

Outputs

Output Name	Required	Description

Artifacts

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.

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

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, packages, procedures, and variables) can be identified by tagging them with the ODI Marker (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.
Include/Exclude Patterns – Java regular expressions can be used within the 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).
Scenario Version – You have the option to identify the specify version numbers of the scenarios to include in the build by using the 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.