Import/Export of DM-ETL+ solutions
The Export option allows you to export a selection of solutions at once. Details
Select > File menu> Export See Figure 1.
Select the desired solutions that you would like to export and Click "Export" See Figure2.
A folder select box will popup. Select a folder
and click on OK
. The selected solution are now successfully exported to the selected folder.
The Import menu option allows you to import an DM-ETL+ solution from disk and store it in the DM-ETL+ database. Details
Select > File menu> Import See Figure 3.
The Import option is used to
- Restore a backup of a Solution that is previously created on this or another DM-ETL+ system using the Export Solution menu item.
- Promote solutions on solution by solution base from test/development to Acceptance to Production that have been exported previously on other DM-ETL+ systems using the Export Solution menu item
When Solutions of other DM-ETL+ systems are imported they will refer to particular datasources. These data sources need to exist within the DM-ETL+ environment you try to import the DM-ETL+ solution in. Also the data sources need to be accessible from this DM-ETL+ system. When data sources are missing, the DM-ETL+ Import wizard will present a message about the particular data sources that are missing and will abort the import. As soon as the data sources are created in the DM-ETL+ environment that you want to import a solution in, the import wizard allows you to finalize the import. See Figure 4.
See Figure 5.
- Browse to the appropriate directory and select the required Scope4mation formatted Solution (ending in .s4m) and press the Open button
- Enter the Name the solution should have in this DM-ETL+ system
- Select > Ok Button to finalize the import process
The DM-ETL+ import solution wizard will now check if the data sources used in the solution also exist in the current DM-ETL+ environment. If this is not the case you will receive an error message. You now might add an additional Data source so that the solution can be imported. If the connections to the databases exist already, but are not consistent you might reconfigure the select datasources used in the Diagram tasks of the solution later on. It is also an option to - either permanently or temporarily - rename the data source name in the existing source or the target DM-ETL+ environment to make it consistent with the import (as long as the data source refers to a database with a similar database structure, table names and table views. This resolution will not cause DM-ETL+ solutions already existing in the source or target environment to fail, since the name is just a logical name and will remain referring to the appropriate data source. Once the data source issue has been resolved a new import can be performed as explained above. See Figure 6.
Once the solution successfully has been imported you can select to either open the imported solution or not. Select > the Yes button
to open the solution Important; Before opening the imported solution take care to save the current solution, since opening the imported solution will close any current open solution
Select > the No button
to remain working with the current open solution