Global Distribution Platform Program

Review of Future State Architecture

1/22/2015

FOR INTERNAL USE ONLY. 1

 Integration
DR
A
Understanding:
•Major simultaneous business and technology initiatives are posing application integration and data distribution challenges

FT
•New applications need to be connected with existing applications and infrastructure while existing applications need to be retired or re-
wired
•Integration with cloud based /external applications (like Salesforce) provide additional integration challenges
•Firm has chosen to use an MDM tool for mastering of data
•There is a need to minimize point-to-point integrations between applications
•A Data access layer consisting of various data access tools has been proposed
•Several integration tools exist in-house, including MQ, and Mule

Feedback:
•Having concrete guidelines on application integration and data distribution/access is key to support major business initiatives
•Point-to-point connections should be minimized
•Boiler-plate integration code should be avoided
•There have been several options to consider in the enterprise integration space:
• Traditional Hub-Spoke vs ESBs
• Decentralized (application centric) vs Centrally deployed
• Light-weight integration vs Highly-Available, Fault-Tolerant
• Performant vs Highly-reliable
• In-house vs Integration in the cloud
Point-To-Point Hub n’ Spoke ESB

FOR INTERNAL USE ONLY. 2

 Integration (contd.)
DR
Feedback
•Some Factors to consider when choosing an ESB:
• Functional features supported such as Connectivity, Protocols, Orchestration, BPM etc.
• Deployment options such as embedded within application, clustering, IPAAS
• Costing/Charge-back policy to application teams
A FT
• Licensing and Operational cost
• Flexibility and Ease of implementation eg. having a UI/Management console etc.
•When to use an ESB?
• Need to integrate a number of applications
• Need to exchange between several different protocols
• Transformations and Filtering
• Scalability for performance
• Fault-tolerance

•It is not an Either-or choice rather it is establishing a set of tools with guidelines on their appropriate usage
•Need to evaluate current vendor capabilities
• Some popular open source options are Apache Camel, Spring Integration and MuleESB
• Traditional offerings are IBM Websphere ESB, Tibco ESB,
•There is a need to deep dive on the DAO layer to understand the guidelines, patterns of access and tools
•It is necessary to take an inventory on the in-house integration tools that current exist and document their adoption and usage patterns
•It should be determined which flows need to be centrally managed vs not based on the aforementioned criteria

FOR INTERNAL USE ONLY. 3

 Security
DR
A
Understanding
•MFS has a strong security team on premise

FT
•On-premise security devices like gateways and firewalls exist

Feedback
•Unclear on how exactly existing infrastructure will handle encryption/decryption of Salesforce data
•Encryption gateways are typically employed for handling encryption of data in Salesforce
•XML Firewalls/Gateways should be considered for XML traffic flowing in/out of the organization
•A robust central key-management strategy needs to be in place

FOR INTERNAL USE ONLY. 4

 Operational and APM Tools
DR
A
Understanding
•There are limited or no central operational intelligence tools

Feedback
•With more and more systems added to the enterprise, the complexity of monitoring and/or troubleshooting increases
FT
•With the use of cloud based systems such as Salesforce, there may be a need both from a business and technology perspective to gain
insight on modes of access, usage patterns, reports, response times, issues etc.
•There is also need to monitor end-to-end performance of complex systems both in development and in production
•Traditional tools for monitoring are very specific to each product/vendor and may be too expensive
•There are several tools like Splunk, Loggly, Dynatrace etc.in the market to help centrally monitor and analyze enterprise systems
•Some benefits of using such operational tools:
• End-to-End application monitoring and troubleshooting
• End-to-End performance management of applications
• End-to-End visibility of all IT infrastructure and activities
• Gain security Intelligence
• Visibility into both in-house and cloud applications

FOR INTERNAL USE ONLY. 5