Broker 10.15 | webMethods Broker Documentation | Administering webMethods Broker | Exporting, Importing, and Deploying Assets | Exporting and Importing Broker Server and Broker Information
 
Exporting and Importing Broker Server and Broker Information
The export and import operations use ActiveWorks Definition Language (ADL) files for storage and retrieval of information. You can copy Broker Server and/or Broker information from a source Broker/Broker Server to a target Broker/Broker Server using the Export to File and Import from File options in My webMethods. In addition, you have the option of copying subsets of information. For example, you can copy only document types, or only client groups to an ADL file.
When you save the Broker Server and/or Broker information in an ADL file, you can store the ADL file in a source code control system, and move the file from a development environment to a production environment in a different network at a later date.
Use the Broker command line tools to process very large ADL files because the Export to File and Import from File functionality in My webMethods requires more memory. Using the Broker command line tools, you can import from the ADL file that was created using the Export to File option.
Important:webMethods Broker 9.0 and later export and import assets in ADL format, whereas webMethods Broker 8.2 SP2 or earlier versions exports assets in XML format. In webMethods Broker 9.0 and later, you cannot import the Broker assets that were exported in XML format from webMethods Broker 8.2 SP2 or earlier versions, but you can import the Broker assets that were exported in ADL format from webMethods Broker 8.2 SP3 or later versions.
For information about migrating the Broker assets stored in XML format to webMethods Broker, see the Upgrading Software AG Products guide.
The Export to File and Import from File options enable you to export and import the following:
*Broker Server configuration.
Broker Server configuration information available for export/import includes:
*Broker Server description
*Logging configuration
*SSL configuration
*Access Control List
When you export Broker Server configuration data, you save the metadata about the Broker Server in an ADL file. For security reasons, export Broker Server configuration data with caution.
When you import a saved ADL file containing Broker Server information, make sure that the new Broker Server already exists. You cannot create a new Broker Server from an import file.
*Broker configuration
Broker configuration information available for export/import includes:
*Broker description
*Document type definitions
*Client group definitions
*Territory information
*Gateway information, including shared document types
*Access Control Lists for client groups, territories, and territory gateways
You can reconfigure the Brokers, client groups, clients, and document types from an export file. You can rename Brokers imported onto a different Broker Server or into a different territory; however, you cannot rename client groups, clients, and document types.
*JNDI assets such as JMS queues and JMS topics created by webMethods JNDI providers.