Exporting assets and creating deployments

Edit online

Export assets that are in active or inactive status from one webMethods B2B Integration environment as a compressed file or as a deployment, and then import them into another environment. The status of assets on the source instance is maintained on the target instance after the movement.For example, you can export assets from a test environment and import them to a production environment. A deployment is a collection of webMethods B2B Integration assets that you can export from one environment and import into another. Unlike compressed files, deployments reside in the database of the source or target environment. You cannot export the secondary certificate.

Procedure

  1. In webMethods B2B Integration, from the side navigation menu, click Asset movements and choose one of the following option:
    • Export assets
    • Deployments. Click Add new deployment.
  2. Select the assets to export from the asset type tabs.
  3. Verify the final export set, and click Next.
  4. Select one of the following options on the selected assets, and click Finish.
    Export as a compressed file
    Specify a name for the export file. webMethods B2B Integration downloads the exported assets as a compressed file.
    Note: An 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.
    Create a new deployment
    Specify a name, and optionally provide a description. The deployment that you create appears on the Deployments page.

    To publish the deployment to another environment follow the following steps:

    1. Select Publish deployment to another environment checkbox.
    2. Select the target environment, and provide your credentials.
    The Remove deleted assets option appears only if the selected deployment contains assets that no longer exist. You cannot publish the deployment until you remove the deleted assets from the deployment.

    You can track deployment errors on the Deployment logs page. For more information, see Deployment logs.

What to do next

After you export the assets, perform the following tasks:
Retain the original copies of the documents
After exporting documents from a webMethods B2B Integration instance, keep the same copies unchanged until you import them into the new instance.

The document changes that you make on a webMethods B2B Integration instance also reside in the IBM webMethods Integration instance. If you export a set of documents from webMethods B2B Integration and edit the same documents in the IBM webMethods Integration by using the EDI application, moving those documents to a new instance results in an error. This error occurs due to discrepancies between the two sets of documents.

Export XML documents
Export XML documents as the part of their corresponding project from the IBM webMethods Integration instance.
Export referenced documents for orchestrations
For orchestrations to work seamlessly in the new instance, export the documents that are referenced in those orchestrations from the IBM webMethods Integration instance.