- AUTOMATIC DEPLOYMENTS
- CONTINUOUS DEPLOYMENT
- DEVOPS
- CONTINUOUS INTEGRATION
- WEBMETHODS
Promoting business adaptability by streamlining the delivery of new versions of applications to end users. An effective, efficient version deployment mechanism provides business users with faster access to the capabilities they need in their ICT applications.
In MAPFRE since 2012
30 to 100 deployments are made per month of versions of webMethods solutions
Deployments from source repository, in different organisational environments
Promoting the agility of business processes
MAPFRE adopted webMethods BPM as a corporate process management platform in 2011. Through this addition it gained agility in building and maintaining process-based applications. But for this agility to translate into actual delivery to business users and to improve time-to-market, a deployment automation system was required in this type of element. This is the only way to avoid the inefficiencies and problems that exist in manual models.
Integrating the various elements to generate greater profit
MAFPRE already had an automatic deployment mechanism (PDA). Integration of this mechanism into webMethods was required to incorporate the capability to deploy different components of webMethods solutions: processes, services, screens, and others.
This is a deployment production plant, based on closed versions of the source repository containing different components of different technologies. These versions are the absolute definition of the version used for deployment in all environments, which ensures configuration management: what is being deployed and what has been deployed in each environment is known.
Seeking points of connection, joining forces
In each deployment environment, the webMethods Asset Build Environment is used, once the files corresponding to the closed version being deployed have been downloaded from the source repository, to compile and package them to build the Deployment Repositories that are then deployed on the webMethods operating servers in the destination environment using webMethods Deployer Project Automator and webMethods Deployer.
Automation, factoring, agility
Thanks to the MAPFRE DevOps strategy and its integration into webMethods, the teams developing the different technological solutions can request their release from a self-service portal, which closes a version of the application in the source repository, and which the team takes to production to begin their deployment across the different environments.
This makes it possible to improve the times in making the necessary changes available to managers to remain competitive in a constantly changing and moving market.
