ODI Master: Working with a Scenario from a Different Repository

A scenario may need to be operated from a different work repository than the one where it was created. Examples include:

Multiple Agencies: A company with multiple agencies using the same software develops scenarios in the IT headquarters to be executed identically in each agency.
Multiple Environments: A company with distinct environments for development, qualification, and production that require complete separation, meaning they cannot share the repository.

Ensure that each environment (site, agency, or environment) has a work repository installed.
The master repository linked to the work repository should have a compatible logical architecture (same logical schema names).
The physical architecture (connection settings) can differ between repositories.
If any procedures or mappings explicitly specify a context code, ensure the target repository has the same context codes.
You can export and import the topology (logical and physical architecture) from the development master repository to the target repositories using the Topology module.

Export and Import Process to Operate a Scenario from a Different Repository:

1. Export the Scenario:

In the original repository, right-click the scenario and select Export to create an export file.

2. Forward the Scenario Export File:

Send the exported scenario file to the target environment (agency, site, or repository).

3. Connect to the Target Environment:

Open Designer Navigator in the target environment and connect to the target repository.

4. Import the Scenario:

In the target environment, use Import to load the scenario from the export file into the repository.

If the physical topology differs, make sure to adjust server addresses in the target environment after importing the topology.
Importing the topology references the new data servers without changing existing ones in the target repository.

ODI Master