Exporting Broker Server and Broker Configuration to a File

Using the Export to File functionality in My webMethods, you can export:

If you have configured SSL and ACLs on the Broker from which you want to export the configuration, make sure you have proper identity before you export.

1. In My webMethods: Administration > Messaging > Broker Server s > Servers.

2. In the Broker Servers List, click the name of the Broker Server from which you want to export. If the Broker Server is not in the list, use the search functionality to locate it.

3. Click the Broker s tab.

4. In the Brokers List, click the Broker from which you want to export the assets. If the Broker does not appear in the list, use the search functionality to locate it.

5. On the Broker Details page, click the Export to File tab.

You see the name of the Broker Server and the Broker you selected for export.

6. Select the Export Server Configuration option if you want to export the metadata of the specified Broker Server. If you are using export and import only to replicate information about Brokers, client groups, clients, and document types, you do not need to save server configuration information. Use this option with caution for security reasons.

7. Select the Export Broker Configuration option if you want to export the configuration of the specified Broker.

8. Select the Format for saving the Broker Server and Broker configuration file.

If you select Platform Independent, the export file includes unicode escape characters. You can use the configuration file to export Broker Server and Broker configuration to hosts that use different languages (and sometimes different types of host machine that use the same language). This is the default option.

Reading or editing configuration file might be difficult if the escape characters are present in the file. If your language uses an expanded character set, and you want to read or edit the Broker Server and Broker configuration file, you should save the configuration in native format.

If you select Native, the export file does not include unicode escape characters. You can use the configuration file only on hosts of the same type and which use the same language and encoding.

In English, or other languages that do not use an extended character set, always use the platform-independent file format to save an export file.

9. Click Proceed to Step 2.

Note that volatile clients and system defined document types are not exported, but if you have selected the Include Dependencies option, the dependent system defined document types are exported.

10. To select a subset of the document types, client groups, or clients for export, perform the following steps.

a. Click the link mentioning the number of corresponding assets selected for export.

b. If you have selected assets in multiple pages, click the Selected column title to sort by selected assets/not selected assets.

c. Select or unselect the checkboxes corresponding to the assets for export.

e. Use the search functionality to search assets. Specify the asset name that you are looking for and click Search.

11. Use the Include Dependencies option to specify whether you want to add the dependencies of the assets selected for export to the export file.

12. Click Export to File. The assets selected for export and the corresponding dependencies (if you have specified Include Dependencies) will be stored in an ADL file.

The configuration is saved as an ADL file and compressed in a .zip file for downloading.

13. Download the configuration file by clicking Click here to download ADL Zip-File.

If you want to build the assets in the .zip source file and then use webMethods Deployer to deploy the Broker assets, see Building Assets for Deployment.