The client is a leading retailer located in the Hudson Bay area, USA. They wanted to conduct a detailed feasibility case study on migrating their current IBM Sterling OMS version 9.4 along with the associated ecosystem to AWS Cloud.
The key objectives of this endeavour was to perform
- Migration of IBM Sterling OMS (version 9.4) instances from on-premises to AWS Cloud.
- Feasibility study of upgrade & migration of IBM Sterling OMS (version 9.4) instances from on-premises to latest version 10.0, on AWS cloud.
- Upgrading the IBM Sterling OMS Oracle Database instances from current 11g to 12c.
- Performing the upgrade of IBM MQ Server from current 7.5 version to latest supported version (as certified by IBM).
- Backup, Business Continuity and dilated recovery plan for IBM Sterling OMS.
- The migration of the current 9.4 version of IBM Sterling OMS to AWS cloud is a big challenge for the client involving various technical, business and financial impacts. They were pressed for completing this cloud migration before the start of the peak season which is end of July 2019.
- They needed to consider the overall feasibility and practicality of such a migration and its potential impact on applications, performance, security & compliance.
After conducting a comprehensive study of the client’s IBM Sterling OMS and its eco-system front, we proposed the following
- Migration Roadmap that included the migration tools, high level assumptions and risks.
- Migration Approach Document for On-premises IBM Sterling OMS from current version 9.4 to 9.4 on AWS cloud (like to like migration).
- Upgrade & Migration Approach Document for IBM Sterling OMS from current version 9.4 to version 9.5 in AWS Cloud.
- Upgrade & Migration Approach Document for IBM Sterling OMS from current version 9.4 to version 10.0 in AWS Cloud.
- Testing approach to ensure the migration is successful.
Kloud9 also provided a proof of concept that detailed the feasibility of this migration from a program management perspective:
- Provide high level team, size, roles and responsibilities.
- Provide high level schedule, effort, cost estimates and important milestones.
- Provide high level Project Plan.
- Provide project status reporting mechanism, scrum calls, status calls and leadership calls.
- Proposed Project Management tools.
The client had a clear picture on the possible impact of making the transition to AWS cloud for their IBM Sterling OMS migration. They had the detailed proof of concept study for any concerns regarding the below areas:
- Configuration management
- Monitoring & performance
- Compliance and governance
- Resource optimization
- Auto scaling & demand scaling
- DevOps implementation
- Backup, archival & restore strategy
- Disaster recovery strategies with AWS
- Security architecture
In addition, the client was able to leverage Kloud9’s value added services that helped them to realize cost savings.
AIDI constantly learns about the state of your cloud environment and can also be extended to other areas such as change management and enhancing security. It provides helpful recommendations and insights on usage and capacity via the AIDI dashboard.
It is a continuous delivery and microservices deployment platform framework that is focused on cloud operational excellence and time to market, without the hassle of setting up manual delivery pipelines.
They also had a guideline for the best practices followed for operational excellence. The guidelines dealt with the Security, Design Principles, Reliability, Performance Efficiency and Cost Optimization
Verify whether the entire OMS application works correctly (as previously). Verify if the migrated OMS still support all the components of the application (Configuration values are not changed, and no errors observed)
Verify and validate the query performance is same as the earlier on-premises performance.
Verify request response between application and the server (and compare with on-premises statistics). Verify if the environment is stable and the server hosted on it has no issues with the connectivity. i.e., there should be no environmental issues after migration.
Validate whether application instance is restored automatically in case of hardware failures. Also, if application data is restored automatically in case of crashes
Validate cloud providers ability to meet compliance requirements relating to data, validate data security during transit and storage
Validate backup plan and ensure application can be restored based on required SLA. Validate business continuity plan for business-critical functions.