Building a Federated ESB with Multi-Site High-Availability. Presented By American Electric Power & ProSoft Technology Group Inc October 16 th 2012

Building a Federated ESB with Multi-Site High-Availability Presented By American Electric Power & ProSoft Technology Group Inc October 16 th 2012

Building a Federated ESB With Multi-Site High-Availability

Building a Federated ESB with MSHA Where we started Dennis P DeVendra, Manager: Enterprise Integration Development and Support, AEP, October 16 th 2012

AEP Facts (and Introduction) October 24, 2012 4 AEP ranks among the nation s largest generators of electricity and owns the nation s largest transmission system. 200,000 square miles of Service Territory 38,000 megawatts of generating capacity in the U.S. 39,000-miles of transmission lines 223,000-miles of distribution lines AEP is headquartered in Columbus, Ohio. President & CEO Nick Akins 5.3 million customers in Arkansas, Indiana, Kentucky, Louisiana, Michigan, Ohio, Oklahoma, Tennessee, Texas, Virginia, West Virginia Approximately 19,000 employees AEP Financial Statistics $1.504 billion of ongoing earnings in 2011 $3.12 ongoing earnings per share in 2011 $15.1 billion revenues in 2011 $52.2 billion in Assets http://www.aep.com/about/

AEP IT Role in Business Solutions Shared Services HR Payroll / Direct Deposit HR Talent Management Accounts Payable Accounts Receivable Treasury/Cash Management Supply Chain/Procurement (Procure-2-Pay) Wire Transfers October 24, 2012 5 IT is integrated throughout the enterprise supporting common shared services and utility specific functions. Line of Business Specific Smart Grid Ohio, Indiana, Texas, Oklahoma Customer Billing & Invoicing Customer Choice Transmission Support Distribution Power Outage and Restoration Commercial Operations Market Support - SPP, ERCOT, PJM Generation Technology Oracle Database, Microsoft for Collaboration, Java and.net for App Development, webmethods ESB EDI/B2B & EAI, PeopleSoft Fin & HR multiple packaged apps

AEP Enterprise Integration Business Process Management & Monitoring (BPM & BAM) Enterprise Integration Strategy Enterprise Webservice Governance (SOA) Integration Delivery Services Application Modernization Services External Business Partner Integration Services Integration Support Services Integration Architecture Consulting Services October 24, 2012 6 ESB Platform Role Central enterprise platform that provides integration for all of AEP s business units. Annual ACH and Wire payments total of $9.5 billion worth. No of transactions 1.098 million. About 41.6 million transactions per year for Commercial Operations 5.8 million invoices processed in 2011 totaling $1.6 billion. 9 million remittance transactions totaling $2.07 billion. 2012 is currently trending higher than 2011.

October 24, 2012 7 AEP ESB Current Model webmethods 8.2 Procure-2-Pay integration with Ariba webmethods 6.5 Environment 3 Node webmethods EI cluster for internal application integration (~ 200 integrations) 3 Node webmethods TN cluster for external partner integration (~ 100 integrations) webmethods 6.1 Environment 2 Node webmethods 6.1 environment processing outbound customer invoices webmethods 4.1 Environment Deal Trading Adapters Gentran 5.3 for UNIX 6 EDI Financial Integrations (AP, Payroll, Positive Pays)

AEP ESB Current Model October 24, 2012 8 IS 1.1 IS 1.2 IS 1.3 IS Stack IS 2.1 IS 2.2 IS 2.3 IS & TN Stack DBs Broker Server Broker s

October 24, 2012 9 AEP ESB Current Model Lessons Learned Used Models for integration visibility Processing overhead, upgrade complexity, additional time to develop, server administration issues. Upgrades multiple environments to support on various platforms led to increase in support costs. Business Logic within webmethods Legacy environments led to tight-coupling of applications and inability to scale upgrades to infrastructure were difficult to support. Responsibility gap between application and integration teams from a process perspective led to additional costs for training and coordination activities done by integration team on projects.

October 24, 2012 10 AEP ESB To Be Model Requirements To consolidate platform on supported software and hardware webmethods 8.x Being able to comply with industry standards for Security and messaging (SOAP 1.2, JMS) New Security & Architecture Using basic authentication for Broker Security Using TLS for web services Security Continue to maintain platform upgrades in order to be on supported platform Maintain SOX Compliance separation of duties for IT support and Business Unit To enable the platform and implement frameworks that support a lower cost for Future Upgrades

Building a Federated ESB with MSHA Where we are going Kevin Dunlap, Enterprise Integration Architect, AEP, October 16 th 2012

October 24, 2012 12 To Be EI/ESB Model (High level features) Empower the business via MWS For example, verifying document delivery Enterprise Scale Document Brokering/Messaging System Separation of Processing (Integration Servers) along business functions Enable Active/Active multi-site high availability which will provide the following benefits: Greatly reducing if not eliminate planned down time for maintenance work Eliminating the need for standby DR hardware Segregate User Interface (MWS) onto hosts not burdened by Integration Processing Security Model based on Enterprise Security Directory SAG components used include MWS, IS, Broker, CentraSite, Insight

To Be EI/ESB Model October 24, 2012 13 Data Center 1 Data Center 2 MWS 1 MWS 2 mywebmethods MWS 3 MWS 4 IS 1.1 IS 1.2 IS Stack 1 IS 1.3 IS 1.4 IS 2.1 IS 2.2 IS Stack 2 IS 2.3 IS 2.4 IS 3.1 IS 3.2 IS Stack 3 IS 3.3 IS 3.4 IS 4.1 IS 4.2 IS Stack 4 IS 4.3 IS 4.4 IS 5.1 IS 5.2 IS Stack 5 IS 5.3 IS 5.4 DBs Golden Gate Synchronization DBs Broker Server Broker Server Brokers Brokers

ESB Federation Criteria and Model October 24, 2012 14 Desire to provide an ESB using a Federated Model which provides the following: Interoperability and information sharing between lines of business Isolated processing between LOB s Varied maintenance windows for each LOB Leverage common ESB capabilities across each LOB Model 5 Stacks, hosting integrations grouped by business function: Corporate, Utilities, Commercial Operations, others. Use GSS network switches to spread load and allow servers to be taken off line for maintenance without impacting the business. Each stack uses its own Broker sharing documents as need using gateways

October 24, 2012 15 ESB - Multi Site High Availability Servers located in 2 data centers Columbus and Roanoke Each data center contains a complete webmethods environment MWS, IS, Broker, DB Oracle DB s synchronized using Oracle Golden Gate Each IS stack configured as a farm (not a cluster) Global Site Selection switches used to route incoming traffic across the farm Brokers in each data center function independently Special considerations were needed for serial/ordered delivery processes special GSS names route traffic to only one data center

October 24, 2012 16 Golden Gate Synchronization Data is synchronized bi-directionally as both data centers are active Integration design must definitely take Golden Gate into consideration Applications must allow for potential data discrepancies where you may not normally be expecting them For example, when processing document delivery acknowledgements, build retries to account for data synchronization latency Understand sequence number usage and account for it For example, EDI units of work requiring sequential numbers acquired from the DB should take place all in one data center

October 24, 2012 17 Unified Monitoring Across Federated ESB MWS Serves as a single point of reference for the Enterprise Challenge is to provide an environment which is common but appears to a line of business as if it is dedicated to them When navigating MWS, the BU selects their stack from the drop down in MWS Fine grained Role definitions within MWS allow for granting BU access to only what they should see Access can be controlled at both the service and data level All Roles are defined and managed in one place, the central MWS

October 24, 2012 18 Unified Proxy / Mediator Across Federated ESB CentraSite/Mediator serve as the single point of reference for inbound SOAP web service calls Using Mediator, we have much more flexibility routing inbound service calls to the appropriate service provider Performance metrics can be gathered for registered services using CentraSite The Proxy/Mediator is exposed to the internet via the Reverse HTTP Gateway All web services, not only webmethods provided web services are virtualized on Mediator

Unified and Enhanced TN Partner and Transactions Mgmt October 24, 2012 19 Enable the business to perform functions that were once only done by IT Trading partner management and transaction visibility is provided to business users Web based UI that enables customized views, data exports and queries based on document attributes. Developers and Administrators manage TN assets within MWS using the same unified console Single URL MWS Data Center A MWS Data Center B Real-time replication DB - A DB - B

October 24, 2012 20 SOA Governance Road Map Plans for this area Design Time leverage a tool and a Governance Process to increase opportunities for re-use and gain a better understanding of the service inventory Run Time leverage a tool to monitor performance metrics, perform alerts and identify rogue services What we have CentraSite, Insight and Mediator have been installed Governance Process has been defined What's next Implement the Governance Process in CentraSite Define and deploy enterprise services into the ESB Mature and refine the process

Source Code Control and Deployment Strategy October 24, 2012 21 SUBVERSION REPOSITORY SAND REPO Integrated Source Control Integrated Source Control PRIMARY REPO ACDL + Deployment Composite DEV-TEST DEPLOYER + ASSET BUILD ENV Runtime Deploy ACDL + Deployment Composite REPO-QA DEPLOYER Repository Deploy ACDL + Deployment Composite REPO- PROD DEPLOYER Repository Deploy SANDBOX DEV DEVELOPMEN T ENV IT TEST ENV QA UAT ENV PRODUCTION ENV

Building a Federated ESB with MSHA How we got there Ram Kanumuri, Director: Integration Services, ProSoft, October 16 th 2012

October 24, 2012 23 ProSoft Facts ProSoft Technology Group Inc (an Inc. 500 company established in 1995) is a leading-edge, global IT service provider Services include: Service Oriented Architecture, and Business Process Management, Business Activity Monitoring, Enterprise Resource Planning, Enterprise Portals and Composite Solutions ProSoft has been servicing the webmethods community since 1997 with Distinction and Excellence Over 250 successful webmethods implementations throughout USA and Canada 85+ webmethods SMEs and Consultants specializing in integration services Proven 3-Tier Global Delivery Model (GDM) with 24 x 7 support services Most experienced top-tier webmethods consultant base in the industry Experts in providing strategy for adoption of enterprise wide SOA

October 24, 2012 24 Delivery Model and Execution at AEP ProSoft has global presence and provides cost effective IT services with its Global Delivery Model ProSoft consultants were responsible in the areas of Technical Strategy, Architecture and Management Other responsibilities include: Environment Standup and Verification Upgrade Integration Rectification QA Testing and Code Propagation Cutover Planning and Go-Live Activities ProSoft Team on this initiative: 1 - Project Manager / Solutions Architect 1 - Senior Integration Architect 1 - On-Site Senior Lead Developer 2 Offshore Senior Developers 3 Offshore Developers

Q & A October 24, 2012 25

Thank You American Electric Power ProSoft Technology Group Inc Software AG