Export the Package
Launch IWS and call Export Solutions from its application menu.
Pick the solutions to be exported.
Click Next. You will see the files being downloaded and processed.
Eventually a file tree for the solutions will pop up. By default all files are selected for export.
Review the list and remove the tick next to the names of files you do not want to export. Click Next.
Select Export as MC Package, enter a name for you package and describe it, if necessary.
Click Finish.
Once you package is ready, commit it to the TFS if this step is required in your development process.
Import the Package
Go to the store folder you submitted ("FOR_EXPORT" folder in the screenshot) to find all files exported in MCE style there:
The folder contains .pkg files of packed streams and one common /tpe folder will all source files for each stream. These .pkg files can be imported via MCE one by one. But if you want to import them all at once, you should use the *main.pkg file. This is the main package with references to all other files.
The main package in our case is my_test_package_main.pkg. Launch Message Center Editor, go to Message Center Streams tab and launch import stream wizard:
Navigate to the *main.pkg package and select it.
Click Next. You will see the files you are going to import.
You should receive only one file missing warning (csv-0.rsf). If you are receiving more, please investigate and fix, if necessary.
NOTE: We are using the fake stream eagle_iws_service_data_empty to import files without the parent pkg file, for example all IWS source files like .ejmsln and .ejmwf. In addition, sometimes map files and wrf files have no references to packages.
Fake eagle_iws_service_data_empty stream needs a fake ruleset to simulate a stream – that is csv-0.rsf. This file does not exist, as a result you receive a warning.
Click Next.
Click Next and choose Create stream(s) option.
Click Next.
And click Finish. The process of import will start.
0 Comments