Migrating webMethods Application to Cloud

Migrating the webMethods application to cloud

I'm writing this article to showcase the high-level steps and sequence involved for webMethods (wM) cloud migration projects. Hopefully this helps

Audience

• Architects
• webMethods Administrator
• webMethods Developers
• All cloud aspirants

Migration steps/sequences as below for wM application

The steps/sequences are pretty much same for most cloud provider (AWS, Azure, GCP, etc.,), so I'm writing this article generic.

1        Discovery/assessment for AS-IS Infra and application

1.1        Review and document all the on-prem infra services (like VMs, LBs, etc.,)

1.2        Review and document the database server, objects, usage, etc.,

1.3        Review and document the webMethods applications details (like IS, UM, MWS, etc.,)

1.4        Document all the external/internal application

2        Design Phase

2.1        Cloud Network architecture

2.2        Cloud Infra architecture for webMethods

2.3        webMethods architecture in Azure

2.3.1       Database Server

2.3.2       webMethods Application

3        Cloud Infra Readiness

3.1        Migrate all the Infra service from on-prem to cloud (AWS, Azure, GCP, etc.,)

3.2        Migrate the database server

3.3        Migrate the Meta and transactional data

3.4        Workspace

Note, preferably choose the PaaS offering from cloud vendor which gives high availability (like Azure SQL MI has 99.99% availability)

4        Database Readiness

4.1        Validate the DB server access

4.2        Validate the DB objects (like database, schemas, users, tables, views, etc.,)

4.3        Validate the Meta and Transactional data

5        wM Application Readiness

5.1        Validate the cloud (AWS/Azure) Infra access (like VMs, LBs, VM sizes, etc.,)

5.2        Re-configure the wM applications (like IS, UM, MWS, etc.,)

5.2.1       Database to be repointed to new cloud DB server in IS, MWS, etc.,

5.2.2       Private IP allocated to be VM in cloud may vary, updated accordingly

5.3        Bring the wM application online

5.4        Validate the wM Server logs

5.5        Monitor the application health

6        Interface Readiness

6.1        Validate the network connectivity

6.2        Validate the wM application access

6.3        Validate and update the application connectivity (like JDBS/SAP/MQ adapter connection, JMS connectivity, etc.,)

6.4        Conduct the Integration Testing

6.4.1       For all critical interfaces (like Finance)

6.4.2       High volume interface

6.4.3       Different integration pattern (Scheduler, File Polling, Web Service, etc.,)

7        Switchover

7.1        Prepare and review the cutover plan with application SME’s/Leads

7.2        Create Change Request (CR) and get the necessary approval from CAB approval

7.3        Switchover the wM interfaces as per plan

7.3.1       Disable the interface in on-prem wM Application

7.3.2       Enable the interface in Azure wM Application

7.4        Rollback the interfaces switched over if any major issues as described in plan

8        Hypercare

8.1        Monitor the wM Application health

8.2        Monitor the wM interfaces enabled in Azure

8.3        Apply fixes for any reported issues

8.4        Handover the wM applications in Azure to operations team

For wM application design in Cloud (Azure), refer this article.