Versions Compared

Old Version 1

changes.mady.by.user Copy Page Tree

Saved on

compared with

New Version 2

changes.mady.by.user Karl Henselin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Environment/Instance Properties

Property Name

Property Code

Required

Description

ODI Home

FDODI_ODI_HOME

Yes

Fully qualified path to the ODI installation directory.

ODI JDBC Driver Path

FDODI_JDBC_DRIVER_PATH

Yes

Classpath for locating the JDBC Driver.

ODI JDBC URL

FDODI_JDBC_URL

Yes

JDBC Connect String for the ODI Master/Work repositories.

ODI JDBC Driver

FDODI_JDBC_DRIVER

Yes

JDBC Driver to use for connecting to the ODI Master/Work repositories.

ODI Master User

FDODI_MASTER_USER

Yes

Database schema owner of the ODI Master repository.

ODI Master Password

FDODI_MASTER_PASSWORD

Yes

Database password for FDODI_MASTER_USER.

ODI User

FDODI_ODI_USER

Yes

User to connect to ODI instance with (must have SUPERVISOR privileges).

ODI Password

FDODI_ODI_PASSWORD

Yes

Password for FDODI_ODI_USER.

ODI Work Repository

FDODI_WORK_REPOSITORY

Yes

The name of the target ODI work repository.

ODI Thread Count

FDODI_THREAD_COUNT

Yes

Thread pool size used for exporting and importing scenarios (default is 5, max is 20).

ODI Marker Group Code

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

Property Code

Required

Description

ODI Project Code

FDODI_PROJECT_CODE

Yes

The code of the target ODI project.

ODI Marker Code

FDODI_MARKER_CODE

No

The code of the Marker within the defined Marker Group for this build.

ODI Include Pattern

FDODI_INCLUDE_PATTERN

No

Regular expression which identifies scenario name patterns to include in the build.

ODI Exclude Pattern

FDODI_EXCLUDE_PATTERN

No

Regular expression which identifies scenario name patterns to exclude from the build.

ODI Versions

FDODI_VERSIONS

No

List of scenario version numbers (coma comma-separated) to include in the build.

Inputs

Input Name

Input Code

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.

...

  • 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_EXCULDE_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.

...