In this article you will be able to successfully import pipelines into the DQ+ application. For additional information, there can also be more information found in help section of your DQ+ screen.
Within Environments, Data Stages are organized and associated in Pipelines. A Pipeline may contain any combination of Data Stages, and the contents/structure of any given Pipeline will be determined by your Infogix Data360 Administrator, with the help of some users. Pipelines will typically contain an organization's "curated content" - in the form of dashboards that serve as official reports and the multiple types of Data Stages underlying these dashboards.
Administering Pipelines Across Multiple Instances -For organizations using Infogix Data360 across multiple instances, Infogix Data360 also includes Import/Export Definitions functionality, to move Data Stages into and out of the platform. Like Promote, this feature is available by way of the More button.
Exporting Definitions - When Exporting, you are exporting your Data Stage Definitions - i.e., the rules that make them what they are, behind the scenes of Infogix Data360. You are not exporting any data associated with them. For example, if you export a Data Store and then Import it to another instance, the Data Store will not contain any data; it will, however, contain all of the fields and settings you applied to it in its original instance. This means that after importing to a new instance, you will need to reload your Data Stages with the relevant data.
What should be exported - You can export any individual Data Stage Definition you'd like. For simplicity, however, it is highly recommended that you export entire Pipelines. This is because to properly Import a Data Stage Definition, the destination instance needs to contain the parents of the Data Stage (its Pipeline and Path) and any dependencies the Data Stage may have.
For example, if you simply exported an Analysis Definition and then attempted to import it to another instance, the Import would fail for two reasons. The first reason would be that the Analysis' parent Pipeline and Path don't exist in the new instance. The second reason would be that the Data Stores the Analysis uses don't exist in the new instance either. To remedy this, you could simply bundle the Analysis and its Data Stores into a common Pipeline, and then export the entire Pipeline Definition.
Exporting a Data Stage definition - simply select it within the Pipeline context and use the Export Definitions option available in the More dropdown. Doing so will initiate the download of a zip file. This zip file is what you import to your new instance. Dirty State when Exporting Definitions When working with Pipelines, you may notice that some items have an asterisk to the right of their name. This marking signifies the item's 'dirty state', which is a flag that exists to help you track whether the item's definition has changed since the last time it was promoted or exported. After creation, all new Data Stages will have a dirty state of true, and will be marked with an asterisk next to their name. If the Data Stage Definition is exported to another environment, you will have the option to reset its dirty state. If you reset, dirty state will be set to false and the asterisk will disappear. If after this reset the Data Stage changes, dirty state will again be set to true and the asterisk will reappear.
Importing Data Stage Definitions - After you have exported a zip file containing the Data Stage Definitions you want to transfer, go to your target instance, enter the Pipelines context, and use the More dropdown to Import Definitions. Once you have imported the zip file obtained from exporting, your Data Stages will be created in your target instance.
Super Groups with same name Exists on Target Instance - If the target instance you are importing into already contains a Super Group with the same name as the Super Group associated to an imported Data Stage Definition, your work as an administrator is done. Users within that Super Group will have the same permissions to the imported Data Stage as they did in its source instance. Keep in mind, however, that the Super Group in the target instance may contain different users than it did in the source instance.