ESB Project Team Members: Bill Brickman (Data Warehouse) Anita Cutting (FinProc) Leo Dai (Grants) Sreeni Gunnala (FinProc) Lisa Justiniano John Marks (Grants) Shanti Muppirala (Peoplesoft) Joe Rickert (FinProc) John Shen (Peoplesoft) Brian Sullivan (Data Warehouse) Curt Springer (Student Financials) Karen Stelle Mike Thomas Goals: Get experience with ESBs in general and with 2 or 3 specific ESB products Determine if an ESB would benefit ATS Evaluate ESBs to identify one that best fits our needs Get our feet wet with Amazon Web Services Timeline: POC: April June 2014 Pilot: July present Budget: $200 per month Slide 1

ESB Project We built a HA stack at Amazon: 2 x AZ 2 x ServiceMix ESB 2 x ActiveMQ Message Broker 1 x VPC 4 x network subnets 3 x security groups 1 x direct connect 2 x (or 4x) ELB Slide 2

ESB Project We built four integrations: COA Validator: Anita, Joe and Sreeni Existing validator PL/SQL  Web Service Eureka to PeopleSoft Feed: Shanti and John Shen Standalone ServiceMix  Queue  PeopleSoft Web Service FRAP Data Load: Leo and John Marks FRAP control laptop  Queue  GMAS DB Staff Terminations: Curt, Bill and Brian DB  Queue, using another Queue to maintain batch state Slide 3

ESB Project What Challenges Did We Encounter? HUIT's OpenStack infrastructure was cancelled. Fabric8 went to Docker, so... Needed to build our own deployment mechanism to sync two stacks Amazon Direct Connect, asymmetric routing, and Elastic Load Balancers Enabling ActiveMQ authentication turned out to be all or nothing The following features were missing in our free product stack: Discovery of Services Rate Limiting (so we could guarantee SLAs) Analytics Web-based admin of users, groups, roles, notifications Debug support Drag and drop development Slide 4

ESB Project 9 of 9 developers reported getting experience with ServiceMix Camel9/9 CXF3/9 JDBC4/9 8 of 9 reported getting experience with ActiveMQ 7 of 9 reported getting experience with AWS and in many cases it was their first experience. Every developer who hadn't already taken the one day AWS course took it. What did the developers learn? Slide 5

ESB Project What did the Developers Learn? Learning about the different services in ServiceMix and their functionality was a very positive experience. I feel it could come in handy when prototyping integration projects in the future. I learned a good amount about ESB and how to jump out to custom code, and what a message broker is all about, good hands-on experience. I learned about redundancy and failover in the cloud. Hosting/consuming web services in Servicemix, using OSGi blueprint with Camel for routing data and XSL... ActiveMQ for data transportation, AWS. I learned to create Camel routes using blueprint to work with ActiveMQ... I created a Java bundle... performed the transformation using XSL. I was assigned to work on installing SSL keys for the load balancers... this is a great introduction to AWS for me. I had no prior experience with AWS. Very easy to learn and start developing bundles, fewer lines of code to create an integration, more configuration rather than coding, loosely coupled systems For me it was an intro to the new products/tools, infrastructure and terminology. This technology is in its infancy. Slide 6

ESB Project Almost universally developers felt ServiceMix is suitable when embedded alongside an application for the exclusive use of that application, but what they want is an ESB deployed as a centralized service for ATS or HUIT as a whole. They felt ServiceMix was not appropriate in that centralized service role because: security is not flexible enough to truly isolate integrations from one and other naming collisions and version collisions were possible across code bundles no GUI for administrative functions like adding users and groups, deploying code, examining logs, etc. debugging is too difficult it doesn't offer any "discovery" features to help others find services What did the developers think about the products? Slide 7

ESB Project YesNoAbstain Is the ServiceMix ESB production ready?9 Is the ActiveMQ Message Broker production ready?531 ESBMessage Broker If you could have only one product, which would it be? 36 What did the developers think about the products? Slide 8

ESB Project What is Next? Winding down our infrastructure We can continue to use the products: We can use standalone ServiceMix to ease integrations, e.g. FRAP We can embed Camel directly in Java applications to get the nice terse integration language without the overhead of a service Interoperation Project led by Jon Saperia ATS Participants: Bill Brickman, Sreeni Gunnala, Curt Springer Much larger scope: data governance, etc. This will be a capital project; vendor research has begun Slide 9