WebMethods.io B2B Environment Management & Promoting Assets Across Environment/Stages

Introduction

This article explains about how to promote B2B assets to higher environment and stages

Audience

It is assumed that readers of this article know how to set up B2B partners on the webMethods.io B2B platform.

Pre-Requisites

• Set up a B2B enterprise profile.
• Partner profiles, Business documents, channels, and processing rules are already created.
• The environment is provisioned to which the assets need to be published from the current environment(Source and Target environment)

Register environment:

• We need to register the environment to which assets need to be deployed from the current environment to a higher environment.
• Click on setting and select Environment
• Currently, we can see the default environment
• Click on Register environment

1040×329 35.2 KB

• Assign the name to a higher environment like UAT, PROD

1919×802 118 KB

• Select the environment on which we need to deploy the assets.
• In our case, we are deploying to PROD stage

1010×690 64.8 KB

•  Provide the username and click on the register

1010×690 64.8 KB

• Click on the Asset migration icon and select the export tab within it.

1911×702 120 KB

• We can see all partner profiles, business documents processing rules, and document attributes.
• Select partner profiles, business document, processing rules, and other dependent artifacts which needs to be deployed.
• After selecting all the artifacts click on add to export list.

1912×869 80.1 KB

1898×882 164 KB

1890×870 155 KB

Deployment:

              B2B assets can be moved to a higher environment in 2 ways

Export:

• Using export option all the components can be exported in zip format and then the same can be imported in another tenant.
• Channels and certificates won’t get exported.

1812×710 82.6 KB

Create a new Deployment:

• Select create a new deployment option.
• Provide the name for deployment.             
  Name: ABC_Prod_deployment

• Select the target environment
• Provide a user name and password.
• Click finish.
• Once we click finish assets are published to the target environment.  

1892×938 126 KB

Deployment Logs:

• We can see the deployment logs from the source system under the outbound tab.

1918×719 98 KB

• Deployment logs provide details such as event name, source environment, etc.

891×559 55.1 KB

• Connect to the environment (PROD, UAT) to which we have published the assets
• Click on Asset migration and select the Deployments tab.
• Click on Available deployments.

1913×615 63.7 KB

• Select available deployments and click Next.

1001×542 44.2 KB

• Click Proceed.

770×257 20.5 KB

Deployment logs from the target environment:

• We can see the deployment logs from the target system under the inbound tab.

1914×633 113 KB

1019×636 67.3 KB

Redeployment:

     Suppose if we want to deploy again the same assets to the higher environment.

• Go to Asset Migration --> Deployments
• Click on available deployments
• Select the desired deployments. 
  

  1910×716 83.3 KB

• Click on publish deployment.

1919×629 88.6 KB

• Provide the password and click publish.
• This will publish the deployable assets to the target environment.

766×435 31.9 KB

• Deployment logs for it can be viewed on source and target environments both.