Web services and their associated connections and queries can be moved from one server to another by exporting them on one server and importing them on another.
To export a web service, first select it on the Web Services tab and then click on the export icon (=>) which is the last icon in the list. Clicking on the export icon will cause the export UI to be shown:
This screen list all currently defined web services. The web services which will be exported are indicated by a tick in the Export? column. The Select All tick box will select or unselect all web services for export.
Clicking on the Browse button will open the standard Windows dialog for choosing a name and location for the export file.
The OK button will export the selected web services and write them to the chosen file.
To import a web service click on the import icon (<=) which is the second-last icon in the list. Clicking on the import icon will cause the import UI to be shown:
The Browse button opens the standard Windows choose file dialog to choose the file to import from.
The triangular icons allow web services and queries to be expanded or contracted to show or hide queries and connections respectively. The above screen shot shows a web service and its queries fully expanded.
The tick boxes associated with each item control whether that item will be imported and the Select All tick box will select or unselect all items for import.
Red text indicates that the item already exists in the database and that importing the item will overwrite the existing one.
The OK button will import the selected items, overwriting any matching items.
After a web service has been moved from one machine to another, it may be necessary to make changes prior to publishing it. For example, a web service moved from development into production may need its connections updated to point to a production database. Once these changes have been made it will be necessary to preview the data in each query before publishing the web service.
Once a web service has been imported, it may be more convenient if future updates only import the parts of the web service that have changed. For example, once a web service has been moved to production it may be easier to only import new or changed queries rather than to import the entire web service and have to repeatedly edit the connections to point to the production databases.