The export and import features of the Data Server allow request definitions to be transported between systems. For example, if you have created a reporting system based upon certain MAINVIEW views, you can transfer the Data Server setup for it to another environment by exporting the set of requests that it uses, moving the resulting file, and importing it in the new system.
The set of requests to be exported as a unit should all have the same schedule. A schedule calling for 24 hours a day, seven days a week is acceptable, the schedule is simply used to flag the requests to be exported.
The first step is to choose one or more schedules to be exported:
Choose a schedule designating the set of requests to export. "<all>" will export all currently defined requests and schedules. "<unlabeled>" will export the requests with no associated schedule. Click "next" to go to the next panel, to choose where to create the export file:
Navigate to the correct directory, and enter the desired file name using a ".xml" extension. When you click "next" the file is created. and the results panel is displayed:
The requests in a file created by the Export function may be installed in the Data Server by selecting Import. The first step is to select the file to be imported:
When a file has been selected, the "Next" button will be enabled. Clicking on "Next" will cause the import file to be read and analyzed, The next two panels will appear if needed.
If the import file has a schedule that has the same name as an existing schedule, but is defined differently, the schedule rename panel will be displayed:
For each schedule shown, enter a replacement name. To skip importing the requests using the schedule, clear the input area.
If there is more than one instance of a product called for by the requests being imported, the server selection panel will be displayed:
The requests can be applied to any, all, or none of the available product instances by checking those that are to be used.
When the import operation is complete. the results will be displayed: