Copying a Pipeline

The Copy Pipeline feature enables you to create a Pipeline identical to another Pipeline but with a different name within the same environment or to a remote environment. .

Use the copy Pipeline feature to create a new copy of a Pipeline definition with identical connections and job type information. You might use this feature when you want to copy a Pipeline definition in a test environment or you want to copy a source Pipeline as a model for another Pipeline.

To copy a Pipeline:

  1. From the Data Integration home page, click ... next to the Pipeline to copy and then from the Actions drop-down, select Copy.

  2. From the Copy Pipeline page, then in New Pipeline Name, specify the new Pipeline name.

    The new name of the copied Pipeline is a concatenation of the source Pipeline name and the suffix:" -1" by default. Optionally, you can assign a unique name to the copied Pipeline.

  3. From the New Pipeline Code, specify the new Pipeline code.

    The new Pipeline code is a concatenation of the existing Pipeline code and the suffix "1." Optionally, you can assign a unique Pipeline code, which can only include alphanumeric characters.

    The code can contain up to 25 alphanumeric characters with a minimum of 3 characters and a maximum of 25 characters. This code cannot be updated after a Pipeline is created.

  4. From Connections, select the connection to use when copying the integration.

    Select Local to copy the integration in the same instance. You can also select the connection of another instance to copy the integration to the other instance. The connections must be defined in Oracle Fusion Cloud EPM Connections. For more information, see About Connecting Cloud EPM Environments in Administering Planning and Creating, Editing, and Deleting Connections to Other Cloud EPM Environments in Administering Planning.

    Select a remote connection to copy an Pipeline to a remote environment.

    If you specify a remote connection, all jobs and connections used in your Pipeline must already exist in the remote environment. The system validates connections and integrations only. If connections and integrations don’t exist, then the copied Pipeline fails. Other job parameters are not validated. If any referenced job parameters do not exist, the user interface shows a blank value. For example, when a Business Rule does not exist, the system does not validate the referenced job parameters and the user interface shows a blank value.

  5. Click Save.