Benjamin Groeschen , Manager, IT Development October 14, 2014

2. Improving the DevOps Process at CokeCCE using CrossVista Benjamin Groeschen,Manager, IT Development October 14, 2014

3. CCE Company History Key Learnings Existing CCE SDLC wM Upgrade and CV Installation CrossVista Features

4. A little Coca-Cola Enterprises history… CCE buys the Coca-Cola bottling operations in Belgium and France. 2010 1986 1996 2006 The Coca-Cola Company merges some of its bottling operations with the John T. Lupton franchises and BCI Holding Corp’s bottling holdings – forming Coca-Cola Enterprises Inc., a publicly traded company on the New York Stock Exchange. CCE celebrates its 20th birthday and John Brock joins the company as President and CEO. CCE sells its operations in North America to The Coca-Cola Company and acquires the Coca-Cola bottling businesses in Norway and Sweden.

5. Who We Are & What We Do 17 manufacturing facilities 11,750 employees Norway Sweden Great Britain The Netherlands France Belgium

6. Who We Are & What We Do DIRECT & INDIRECT DELIVERY SELL, SERVICE & MERCHANDISE Produce PRODUCE

7. Global CCE IT Organization IT Development IT Leadership & Governance IT Deployment IT Operations Headquartered in Atlanta and locally based across our European territories Locally based across our European territories: Norway, Sweden, Great Britain, Netherlands, France, and Belgium Atlanta, Georgia (USA) Louisville, Kentucky (USA) Uxbridge, Great Britain Sofia, Bulgaria • Data Center in New York USA • Help Desk in South Africa • Support in Mumbai, Bangalore, Noida, Hyderabad, and Chennai India

8. Existing CCE SDLC

9. Integration@CCE has become complex SaaS IaaS/PaaS Ariba SalesForce SalesForce SAP Cloud for Travel Amazon Taleo MEI American Express Trading Partners TribePad XEROX Brand Partners SuccessFactors SPEOS Warehouses Planorama Rosslyn Analytics Banks Customers ADP Benify Transporeon Wholesalers Distributors IBM and Serco Hosted Datacenter CCE Computer Rooms (BE, SE, NO) PIN Codes Margin Minder SAP Systems Readsoft Data Warehouse FileNet Enterprise BASIS DIVA Factory Planner OMS ProMark

10. Integration is integral to CCE’s strategy Involved in 45 of 50 CCE 2014 Projects 7,500,000 Monthly Transactions 400+ Integrated Apps/Partners 75% Annual Revenue from Electronic Orders 500 Service Technicians enabled Integration traffic increasing ~40% per year

11. Existing Development Process • Developer and Designer IDE • Small team required every developer be an admin • Tickets from multiple products • IBM Maximo incidents and change requests • HP Quality Center defects • Email requests • What source control? • Local file locks • Failed to set up VCS on AIX • IS 7.x could not communicate to remote server without a local client installed • No known local file system VCS

12. Existing release management process • Change incident opened in IBM Maximo OR HP Quality Center • Tracked by the business • References business tests • Deployment item entered in SharePoint • Tracked by integration team • Assumes unit testing • Developer manually lists dependent code and config • Developer manually emails release manager • Release manager compares with Deployer, documentation before deployment MANUAL STEPS

13. Existing deployment process • Used SAG Deployer 7.1 for IS and some TN • Generally stable • Included with SAG IS • Manually construct deployment sets for each deployment • Deployment of individual code or IS package • Manually deployed some TN configuration • TPAs with document lists • Environment-specific configuration • Manually deployed some IS elements • Triggers, custom flat files, WSDs • Troubles with automated deployment of these elements • Manually recompiled Java code after deployments MORE MANUAL STEPS

14. wM Upgrade and CV Installation

15. webMethods Upgrade Approach – 7.1/8.2 to 9.5 SoftwareAG Recommends: Parallel Upgrade Advantages: Lowest Risk Removal of decommissioned code Introduction of new architecture Disadvantages: Testing Required for all interfaces Environment complexity while two systems are operational • Alternative option is an over install. • Much higher risk. • No failback option. • Much more complex. INTERFACE MIGRATION webMethods 7.1/8.2 webMethods 9.5

16. CCE webMethods 9.5 Landscape IS cluster IS cluster CommandCentral Gateway IS cluster IS cluster CrossVista TEAM Server Mapping IS cluster IS cluster SAP IS cluster IS cluster API Broker MWS cluster DB2 9.7 active-passive Optimize

17. New Software Development Life Cycle CCE CAB Meeting SAG Designer w/ CrossVistaTeamVCSplugin CrossVista TEAM Server CrossVista Ticketing and Flows CrossVista TEAM Server

18. Components and Integrations TEAM VCS Plugin for Development Internal File Repositories Internal CM Systems CVCM Package WmTomcat on IS host Audit DB Version Control System (SubVersion, CVS, VSS,Microsoft TFS, ClearCase, Borland Starteam, GitHub, etc) Change Management System (Jira, ClearQuest, HP Quality Center, MSFT TFS, etc.)

19. Setting up CrossVista Note: Three repositories is different than what you’re used to…

20. CrossVista Features

21. Terminology

22. Repositories and Live EnvironmentsDevelopment Activities

23. Repositories and Live EnvironmentsDevelopment Activities

24. Easily track changes through Designer Not Changed Changed What is Changed

25. Repositories and Live EnvironmentsCompose (i.e. “Build”), Promote, and Deploy

26. Release Management through CrossVista TEAM browser Patch12 Integration Server Services Note: This is a “Release”… not a Deployer Deployment Set Service A - Rev 4.3 Service B - Rev 1.2 Service C – Rev 7.8 Process Models Model A – Rev 3.2 Model B – Rev 4.1 Model C – Rev 8.3 TN ProcessingRules Rule A – Rev 1.5 Rule B – Rev 5.6 Portlets Portlet A – Rev 8.3 Portlet B – Rev 3.2

27. CrossVista Sites

28. Audit Log

29. Compare/Diff to ensure accuracy Changed Changed

30. Integrated ticketing & embedded workflow • Integrated Ticketing • Out of box support for MTFS, Jira, HP Quality Center, Clear Quest, local file system • Tickets can represent a Feature or a Fix. • Link multiple projects, packages, components to a single ticket • Link actions performed on TEAM to particular tickets. • CrossVista Flow (i.e. “CVFlow”) • CVFlows are not the same as webMethods IS “Flow” • Use CVFlows with ticketing to automate replication process • Very little manual intervention • Faster, cleaner promotion and deployment of projects • Multiple editable CVFlow templates available.

31. Integrated ticketing & embedded workflow

32. Integrated ticketing & embedded workflow

33. Key Learnings

34. Basic Setup Tips & Lesson’s Learned • CrossVista is not wMDeployer, ABE, or WmVCS. It is very different. • Plan some architecture beforehand. • Naming standards • Number of repos • Project package groupings • If starting a completely new webMethods project, then define baseline in Dev. If starting with CrossVista to manage an existing webMethods project, then define baseline using Prod code and promote it “backwards” to QA and Dev. • CrossVista support has been very responsive. Reference the user guides but, if you have a question, then ask. • CrossVista has some powerful functionality and regularly makes available new features.