> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flexagon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# odiDeploy

> Imports scenarios or LoadPlans generated by the operation into an ODI execution repository. This operation supports full deployment projects and packa

Imports scenarios or LoadPlans generated by the [odiBuild](https://docs.flexagon.com/flexdeploy-11-2-documentation/flexdeploy-plugin-guides/flexdeploy-oracle-data-integrator-plugin-guide/odibuild.md) operation into an ODI execution repository.

This operation supports full deployment projects and package-based projects of type Oracle Data Integrator. If you are using odiDeploy with the package-based model, then each file within the package will sequentially be processed. Multithreading will not apply in this case.

# Target Properties

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Property Name**</th><th>**Property Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>ODI Home</td><td>`FDODI_ODI_HOME`</td><td>Yes</td><td>Fully qualified path to the ODI installation directory.</td></tr><tr><td>ODI JDBC Driver Path</td><td>`FDODI_JDBC_DRIVER_PATH`</td><td>Yes</td><td>Class path for locating the JDBC Driver.</td></tr><tr><td>ODI JDBC URL</td><td>`FDODI_JDBC_URL`</td><td>Yes</td><td>JDBC Connect String for the ODI Master/Work repositories.</td></tr><tr><td>ODI JDBC Driver</td><td>`FDODI_JDBC_DRIVER`</td><td>Yes</td><td>JDBC Driver to use for connecting to the ODI Master/Work repositories.</td></tr><tr><td>ODI Master User</td><td>`FDODI_MASTER_USER`</td><td>Yes</td><td>Database schema owner of the ODI Master repository.</td></tr><tr><td>ODI Master Password</td><td>`FDODI_MASTER_PASSWORD`</td><td>Yes</td><td>Database password for ODI Master User.</td></tr><tr><td>ODI User</td><td>`FDODI_ODI_USER`</td><td>Yes</td><td>User to connect to ODI instance with (must have `SUPERVISOR` privileges).</td></tr><tr><td>ODI Password</td><td>`FDODI_ODI_PASSWORD`</td><td>Yes</td><td>Password for `ODI User`.</td></tr><tr><td>ODI Work Repository</td><td>`FDODI_WORK_REPOSITORY`</td><td>Yes</td><td>The name of the target ODI work repository.</td></tr><tr><td>ODI Thread Count</td><td>`FDODI_THREAD_COUNT`</td><td>Yes</td><td>Thread pool size used for exporting and importing scenarios (default is 5, max is 20).</td></tr></tbody></table>

# Inputs

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Input Name**</th><th>**Input Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>Scenario Audit Flag</td><td>`FDODI_INP_SCENARIO_AUDIT_FLAG`</td><td>No</td><td>When enabled, after importing a scenario FIRST\_USER and LAST\_USER are updated to FDODI\_ODI\_USER and LAST\_DATE is updated to time of deployment. If false, then FIRST\_DATE and LAST\_DATE are updated based on scenario file FIRST\_DATE and LAST\_DATE. FIRST\_USER and LAST\_USER would be unchanged.Defaults to false.</td></tr><tr><td>Loadplan Audit Flag</td><td>`FDODI_INP_LOADPLAN_AUDIT_FLAG`</td><td>No</td><td>When enabled, after importing a Loadplan FIRST\_USER and LAST\_USER are updated to FDODI\_ODI\_USER and LAST\_DATE is updated to time of deployment. If false, then FIRST\_DATE and LAST\_DATE are updated based on LoadPlan file FIRST\_DATE and LAST\_DATE. FIRST\_USER and LAST\_USER would be unchanged.Defaults to false.</td></tr></tbody></table>

# Artifacts

This operation consumes the artifacts produced from the [odiBuild](https://docs.flexagon.com/flexdeploy-11-2-documentation/flexdeploy-plugin-guides/flexdeploy-oracle-data-integrator-plugin-guide/odibuild.md) operation of this plugin, which consists of one or more XML files representing exported ODI scenarios or LoadPlans.

# 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

This deploy operation implements change detection by avoiding importing scenarios /LoadPlans which have not been modified, therefore providing increased throughput for builds containing a large number of scenarios/LoadPlan. This is accomplished by comparing the update date of source XML scenarios against the target repository and taking care to preserve the update dates from the source repository.

Note that a deployment request marked Force Deploy will deploy all scenarios/LoadPlans contained in the build independent of whether they match what is in the target repository.

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+.**