Migrating Trading Networks Assets to Cloud (webMethods.io B2B)

webMethods.io B2B supports migration of on-premises assets to cloud using webMethods Cloud Container.


In addition to the existing support for webMethods.io Integration, webMethods.io B2B also provides support for referencing documents and running services on webMethods Cloud Container.

Supported Trading Networks assets such as Partners, Business Documents, Processing Rules, TPA, and so on, can now be imported directly into webMethods.io B2B, and re-wired to existing documents or services on Cloud Container, or a new definition on webMethods.io Integration.

Any user-defined Integration Server assets such as FlowServices, Documents, Schema, and other supported assets need to be deployed on a solution in Cloud Container.

The following diagram shows the mapping of webMethods.io B2B assets with webMethods.io Integration and webMethods Cloud Container.

webMethods.io B2B webMethods.io Integration webMethods Cloud Container Description
Rules FlowServices
Custom Services webMethods.io B2B calls existing FlowServices through processing rules or invoke any third-party endpoints using an external call.
Business Documents Documents,
Schema (optional)
webMethods.io B2B refers to documents hosted on webMethods.io Integration through Business Documents.
Agreements (TPA) Documents,
Schema (optional)
Documents webMethods.io B2B refers to documents hosted on webMethods.io Integration or webMethods Cloud Container through TPA.
API Layer Applications Stubs Applications hosted on webMethods.io Integration, and Stubs hosted on webMethods Cloud Container communicates with the webMethods.io B2B's internal API Layer.

webMethods Cloud Container offers the ability to host custom packages and configurations that reside within on-premises Integration Server and provide an environment for running the services used for service orchestration. The same can be used in-conjunction with webMethods.io B2B. There is a two-way communication supported between webMethods.io B2B and webMethods Cloud Container:


Ensure that your environment meets the following preconditions in order to migrate the Trading Networks assets to cloud:

Required Versions

The following cross-components are the minimum supported versions for this activity:

webMethods On-premises Base Version webMethods Integration Server Software AG Designer webMethods Trading Networks
10.11 Use the IS_10.11_Core_Fix2. webMethods Service Development 10.11 fix # 1 TNS_10.11
  • Use the IS_10.7_Core_Fix6.
  • IS_10.7_SPM_Fix3
webMethods Service Development 10.7 fix # 1 TNS_10.7_Fix1

Important: You cannot deploy across versions. For example, you can deploy Trading Networks 10.7 assets only to Cloud Container 10.7 solution.

Supported Landscapes

Cloud Container supports all combinations of stateful and stateless servers. You can migrate services with any of the three types of solutions available on Cloud Container only with stateless Integration Server Clusters. Only the upgrade path from Integration Server clusters 10.7 version to 10.11 version is supported.

Roles and Permissions

You need the following roles and permissions for each product so that you can switch between them to perform this activity:

webMethods.io B2B requires Cloud-Tenant-Administrator Role. Contact your MyCloud administrator to obtain permissions.

See the respective sections in Trading Networks Administration Guide and Importing Assets for details.

For a comprehensive permission list in webMethods.io B2B, see User Roles and Permissions

Prerequisite Checklist

Migration Steps

The following image illustrates the activities involved in migration of assets:

  1. In My webMethods Server: Administration > Integration > B2B > Asset Management > Export.
    Export the mappings, transformations, and document references. For details see webMethods Trading Networks Administrator’s Guide.
    In webMethods.io B2B, go to Asset movement > Import and import the exported assets. For details see Importing Assets.

  2. In webMethods.io B2B, access the Cloud Container solution you created earlier. For details see Working with webMethods Cloud Container.
    You can follow any of the following approach to deploy packages and configuration assets to Cloud Container:
    a. By using Software AG Designer. For details see Deploying Packages and Configuration Assets to webMethods Cloud Container. If you are unable to deploy the services, reconfigure the global variables and deploy them from Software AG Designer to Cloud Container.
    b. By using Continuous Integration and Continuous Deployment CLI tool. For details see Continuous Integration and Continuous Deployment

  3. In Cloud Container, go to the Assets folder to access the deployed packages you want to run. If you would like to test a service before running it, then you can see the output directly under the Service Editor. For detailed steps, see Assets.

  4. In webMethods.io B2B, review and rewire the imported assets (for examples, the processing rule action and the TPA template) to point to the respective Cloud Container solutions. For detailed steps, see Working with webMethods Cloud Container.

Post Migration Steps

Points to Note

You should note the following points: