Migration of Integration Solution


The customer was using a version of an integration platform that was soon going to lose supplier support. At the same time, there were new demands on functionality and performance in the integration platform. Amongst other things, the demands pertained to improving the architecture and increasing availability by duplicating components. The extremely large volume of integrations (300+) posed a challenge, as did several parallel projects in the old environment and a very large and complex installation.


A target architecture was defined. It addressed the requirements for the new environment, including requirements for failover components. The environment was installed, configured and tested. An automatic analysis of the entire code base was performed to identify services that would be affected by the upgrade as a result of dependencies on removed or modified services in the integration platform. These were updated or reprogrammed to function in the future as well. The test framework for the most common integration patterns was used. During the project, one test case was run every night so that changes or problems could be detected early. Deployment of solutions was done on several occasions to reduce risk and workload.


The project delivered new integration environments that were installed and configured on the basis of best practice. All of the integration solutions were migrated to a new platform. Automated and executable test cases were updated in accordance with the set of requirements. Updated distribution bundles and instructions were produced together with an updated integration directory. The old environments were shut down. Documentation was updated. The platform that was migrated to and from was webMethods from SoftwareAG.