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|
||Custom Services||webMethods.io B2B calls existing FlowServices through processing rules or invoke any third-party endpoints using an external call.|
|webMethods.io B2B refers to documents hosted on webMethods.io Integration through Business Documents.|
|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:
webMethods.io B2B referencing assets on Cloud Container
Within the Processing Rules, you can now navigate and call any user-defined services (under custom packages) on Cloud Container. Note that the Cloud Container user configured on webMethods.io B2B, should have permission to execute these services.
Within the Trading Partner Agreement template definition, you can now refer to an existing document type on Cloud Container.
For more information, see Working with webMethods Cloud Container.
webMethods Cloud Container support for TN and EDI/EDIINT services
Any new solution using any of the supported Integration Server product versions (see Supported Landscapes) can now optionally add B2B support from the Manage Additional Packages dialog box. for more information.
If you are using any of the supported Trading Networks or EDI/EDIINT services on-premises and want to move them to a Cloud Container solution, communicate with webMethods.io B2B without changing any logic or mapping in your existing implementation, see Migration Steps.
The support is currently limited to only runtime services, and there is no support to modify any design-time asset modification services on webMethods.io B2B. For example, one cannot create or update a partner, or business document type or a processing rule by using a FlowService.
For a complete list of supported services on Cloud Container, see section Working with Trading Networks Built-In Services on webMethods Cloud Container and section Working with EDI and EDIINT Built-In Services on webMethods Cloud Container in Deployable Assets and Configurations.
Ensure that your environment meets the following preconditions in order to migrate the Trading Networks assets to cloud:
The following cross-components are the minimum supported versions for this activity:
|Product 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|
||webMethods Service Development 10.7 fix # 1||TNS_10.7_Fix1|
|10.5||Use the IS_10.5_Core_Fix14.||webMethods Service Development 10.5 fix # 10||TNS_10.5_Fix_6|
Important: You cannot deploy across versions. For example, you can deploy Trading Networks 10.7 assets only to Cloud Container 10.7 solution.
Although Cloud Container supports all the 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 as only these combinations are certified to work.
The following table shows the certified combination:
|Solution Types||Without Cluster||Cluster - Stateless||Cluster - Stateful||Integration Server 10.7||Integration Server10.5||Universal Messaging||Upgrade with cluster - 10.5 > 10.7|
[1C + 2GB]
[2C + 4GB]
[4C + 12GB]
[1C + 2GB]
[1C + 2GB]
[2C + 4GB]
[3C + 6GB]
[5C + 14GB]
[2C + 4GB]
[2C + 4GB]
[3C + 6GB]
[5C + 10GB]
[9C + 26GB]
[3C + 6GB]
[3C + 6GB]
Roles and Permissions
You need the following roles and permissions for each product so that you can switch between them to perform this activity:
- Integration Server administrator
- Developer access for Software AG Designer
- In the MyCloud account you must have the following roles:
webMethods.io B2B requires Cloud-Tenant-Administrator Role. Contact your MyCloud administrator to obtain permissions.
For a comprehensive permission list in webMethods.io B2B, see User Roles and Permissions
- You must be conversant with writing and editing flow services on Software AG Designer, and must have an understanding of how webMethods Cloud Container works, along with a working knowledge of Trading Networks, webMethods.io B2B, webMethods.io Integration, and MyCloud.
- You must have a subscription to Cloud Container that is configured within your Software AG MyCloud account.
- You must configure webMethods.io B2B to connect with Cloud Container by adding the Cloud Container account in the Extensions menu of webMethods.io B2B. For detailed steps, see Working with webMethods Cloud Container.
- You must create a solution in Cloud Container that includes the WmTNStub, WmEDI, WmEDIforTNStub, and WmEDIINTStub packages. For more detailed steps, see Creating Solutions.
- You must log in and log out of webMethods.io B2B and Cloud Container at least once.
- You must remove package dependencies on the WmTN, WmEDIINT, and WmEDIforTN packages from all custom Trading Networks packages that you are going to deploy to Cloud Container.
- You must go to the Software AG Designer and deploy the global variables -
mycloud.passwordto Cloud Container using Software AG Designer, either in stand-alone mode or along with the relevant packages.
The global variables are required to be configured one-time, per solution. This refers to the Software AG Cloud user, which is used to call services on webMethods.io B2B. If there is any change to the user or password, or both, the changed configuration need to be re-deployed to Cloud Container again.
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.
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
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.
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
Any changes you make to the Trading Networks assets in your on-premise set up does not automatically synchronize with webMethods.io B2B assets. Therefore, you must redeploy the on-premise assets to webMethods Cloud Container.
Use webMethods.io Integration to design and run any new flow services.
Points to Note
You should note the following points:
Cloud Container only supports a limited set of services (that is, Trading Networks Stubs, EDIINT Module Stubs, and webMethods Module for EDI), and any custom implementation making use of unsupported services does not work when executed on Cloud Container. For a complete list of Trading Networks, EDI, and EDIINT Built-In Services supported on Cloud Container, see section Working with Trading Networks Built-In Services on webMethods Cloud Container and section Working with EDI and EDIINT Built-In Services on webMethods Cloud Container in Deployable Assets and Configurations. You cannot invoke services in system packages.
Large document handling is not certified on Cloud Container.
To host the Trading Networks assets, the Trading Networks Stubs on Cloud Container require a subscription to webMethods.io B2B.
Some assets and configurations might require re-implementation to adapt to cloud. For complex use-cases, Software AG recommends you engage with Software AG Professional Services.