Message Store CORE SYSTEMS MANAGEMENT AND AVAILABILITY INTEGRATION – COPPERPOINT

What(s), where(s) and why(s) 1.Use Cases – What’s the general need 2.Technology selection and rationale – how will it benefit CopperPoint 3.Resource requirements and administrative needs

Use Cases – Room for improvement Core systems needs a way to communicate and consolidate arbitrary events across the various core systems Existing and newly-developed integrations will have the need to be more loosely coupled to allow flexibility in the system, in interest of growth We need an alternative to blocking operations between integration layers and applications; lack of flexibility can result in waste of resources and even outages We need support of an internal analytic system to allow us to proactively recognize and triage process issues, and can perform in a distributed environment

ActiveMQ - How will it benefit CopperPoint Allow us to scale out (broker network) and up (add queues), + for CoverAll and States expansion Persistence – allows us to guarantee transactions across systems, + for Finance Connectivity – supports many protocols - http/s, multicast, SSL, TCP, Stomp, etc. Security – property based, JAAS, custom, etc. Simplified administration – does not require an application server, has JMX interface, logging, etc. Flexibility in change – Enterprise Integration Patterns and Camel routing provide a lot of power to bring solutions to completion, faster

Resource reqs, administration, safety ActiveMQ/ServiceMix – Middlware Suite o ActiveMQ 5.x ~ 52mb base, small database (< 5 tables), o ServiceMix 5.x ~ 225mb base (if we opt for the full-stack integration framework) o Flexible security options, can adapt to ours (AD, LDAP, encryptions tools) o Queues can be monitored and administered by developers (similar to the existing Guidewire transport queues) o Professional services available if necessary o Widely adopted tool (Apache), open source (improved ownership) o Flexible deployment options for highest availability

Questions? Needs?