Exporting assets

Edit online

Export assets from one webMethods B2B Integration environment, and import them in another webMethods B2B Integration environment. For example, export assets from a test environment to a production environment.

About this task

Search for an asset across asset types, such as partner profiles, business documents, processing rules, document attributes, trading partner agreements, and field groups.
Note: The size of each export file cannot exceed 4 MB. If the export file exceeds the 4 MB limit, then create another export file to export the remaining assets.

Procedure

  1. In webMethods B2B Integration, from the side navigation menu, click Asset movements > Export.
  2. On the Export assets page, select the assets to export from the asset type tabs and click Next.

    Each asset specifies the number of dependent assets that it contains. To view all the dependent assets, click the count in the Dependencies column.

    The Include dependencies checkbox is selected by default. Clear the Include dependencies checkbox to exclude the dependent assets in the export file.

    Note: The Include dependencies checkbox is not enabled for field groups. You can view the selected assets on the export page.
  3. Verify the final export set, and click Next.
  4. Select Export as a compressed file and specify a name for the export file and click Finish.
    The exported assets are in the form of a compressed file. The location of the downloaded file depends on your browser configuration.

What to do next

After you export the assets, perform these actions:

  • The document changes that you make on a webMethods B2B Integration instance also reside on the IBM webMethods Integration instance.

    If you export a set of documents from a webMethods B2B Integration instance and edit the same set of documents in the IBM webMethods Integration by using the EDI application, any movement of those documents to a new instance results in an error. This error occurs due to discrepancies between the two sets of documents.

    To avoid such a situation, you must retain the same copies of the documents until you import them in a new instance.
  • For XML documents, make sure that they are exported as part of the corresponding project from the IBM webMethods Integration instance.
  • For the orchestrations on IBM webMethods Integration instance to work seamlessly in a new instance after the asset movement, you must export the documents that are referenced in the orchestrations.