benjamin groeschen , manager, it development october 14, 2014

Innovation World 2014 October 13 – 15 New Orleans

Benjamin Groeschen,Manager, IT DevelopmentOctober 14, 2014

Improving the DevOps Process at CokeCCE using CrossVista


CCE Company History

Existing CCE SDLC

wM Upgrade and CV Installation

CrossVista Features

Key Learnings


A little Coca-Cola Enterprises history…

20101986 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 buys the Coca-Cola bottling operations in Belgium and France.

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.


Country HQManufacturing Site

BrusselsAntwerpChaudfontaineGhent

Paris

ClamartDunkirkGrignyToulouseMarseille

Uxbridge

ColwallEast KilbrideEdmontonMilton KeynesMorpethSidcupWakefield

Rotterdam

Dongen

Oslo Oslo

Stockholm

Stockholm

Who We Are & What We Do

Norway

SwedenGreat Britain

France Belgium

The Netherlands

17 manufacturing facilities

11,750 employees


PRODUCE DIRECT & INDIRECT DELIVERY

Who We Are & What We Do

SELL, SERVICE & MERCHANDISE


‣ Data Center in New York USA‣ Help Desk in South Africa‣ Support in Mumbai, Bangalore,

Noida, Hyderabad, and Chennai India

Locally based across our European

territories: Norway, Sweden, Great Britain,

Netherlands, France, and Belgium

Atlanta, Georgia (USA)Louisville, Kentucky (USA)Uxbridge, Great BritainSofia, Bulgaria

Headquartered in Atlanta and locally based across our European territories

Global CCE IT Organization

IT Leadership & Governance

IT Deployment

IT Development IT Operations


Existing CCE SDLC


Integration@CCE has become complex

IaaS/PaaS SaaS

IBM and SercoHosted Datacenter

CCE Computer Rooms (BE, SE, NO)

Trading PartnersBanks Customers

Warehouses

Distributors

Amazon

Wholesalers

Taleo

SuccessFactors

TribePad

MEI

Planorama

SalesForce

SAP Systems

BASISReadsoft

EnterpriseOMS

American Express

SPEOSBrand PartnersXEROX

SalesForce

Margin Minder

DIVAFactory Planner

PIN Codes

FileNetData

Warehouse

ProMark

SAP Cloud for Travel

Rosslyn AnalyticsADP Benify

Ariba

Transporeon


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

Involved in 45 of 50 CCE 2014 Projects

Integration is integral to CCE’s strategy


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


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


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


wM Upgrade and CV Installation


webMethods 7.1/8.2 webMethods 9.5

INTERFACE MIGRATION

Parallel UpgradeAdvantages:Lowest Risk

Removal of decommissioned codeIntroduction of new architecture

Disadvantages:Testing Required for all interfaces

Environment complexity while two systems are operational

SoftwareAG Recommends:

Alternative option is an over install. • Much higher risk.• No failback option.• Much more complex.

webMethods Upgrade Approach – 7.1/8.2 to 9.5


CCE webMethods 9.5 Landscape

Gateway

Mapping

SAP

API

Command Central

IS cluster

IS cluster

IS cluster

IS cluster

IS cluster

IS cluster

IS cluster

IS cluster

MWS cluster

Optimize

DB2 9.7 active-passive

Broker

CrossVistaTEAM Server


SAG Designer w/

CrossVista TeamVCS

plugin

CCE CAB Meeting


CrossVista Ticketing and

Flows

New Software Development Life Cycle



Components and Integrations

Audit DB

Internal File Repositories

Internal CM Systems

CVCM Package

WmTomcat on IS host

TEAM VCS Plugin for Development

Change Management System

(Jira, ClearQuest, HP Quality Center, MSFT TFS, etc.)

Version Control System

(SubVersion, CVS, VSS,Microsoft TFS, ClearCase, Borland

Starteam, GitHub, etc)


Setting up CrossVista

Note: Three repositories is different than

what you’re used to…


CrossVista Features


Terminology


Repositories and Live EnvironmentsDevelopment Activities


Easily track changes through Designer

Changed

Not Change

d

What is Changed


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


Release Management through CrossVista TEAM browser

Portlets

Patch12Integration Server

Services

Process Models

TN Processing Rules

Service A - Rev 4.3Service B - Rev 1.2Service C – Rev 7.8

Model A – Rev 3.2Model B – Rev 4.1Model C – Rev 8.3

Rule A – Rev 1.5

Rule B – Rev 5.6

Portlet A – Rev 8.3Portlet B – Rev 3.2

Note: This is a “Release”… not a

Deployer Deployment Set


CrossVista Sites


Audit Log


Changed

Changed

Compare/Diff to ensure accuracy


• 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.

Integrated ticketing & embedded workflow


Key Learnings


• CrossVista is not wM Deployer, 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.

Basic Setup Tips & Lesson’s Learned

benjamin groeschen , manager, it development october 14, 2014

Documents