Providing a Pathway from Stovepipe Systems to a Secure SOA Enterprise

Neil CusterSenior Enterprise Systems Engineer/Developer

Eagle Technology Group, LLC

Pathway from Stovepipe to SOA Enterprise

• Eagle Technology Group, LLC

• Properties of Stovepipe Enterprise/Systems

• Our method to migrate to a SOA enterprise

• Crucial Role of WSO2 Products

Eagle Technology Group, LLC

• Information technology engineering and integration• Enterprise architecture, virtualization, data center solutions• System and application design, development, deployment and

maintenance; agile/scrum practice• BPM, architecture frameworks, .NET, Java, and Javascript• WSO2 Preferred Partner• Microsoft Gold Partner• Average of 18+ years of technology experience per employee• Eagle TG is owned by the Native American Modoc Tribe of Miami,

Oklahoma -- SBA Certified 8(a) entity

Stovepipe System:

“…a pejorative term for a system that has the potential to share data or functionality with other systems but which does not.”

- Wikipedia

potential

Properties of Stovepipe Enterprise/Systems

• Primarily ‘Ad-hoc’ architectures• Under constant maintenance, little upgrade• Designed independently at almost every level• Little to no interoperability – existing/known interfaces only• Incompatible terminology, development approaches and

implementation technology• Business centers focused on own specific business functions

instead of delivering enterprise value• Some data model integration had started to evolve

Our Method to Migrate to a SOA Enterprise

• Change the software development/deployment methodology

• Proof of concept w/modern web UI dev kit (custom Bootstrap)

• Introduce web services components (SOAP & REST) for business logic -- link to legacy with middleware

• WSO2 middleware platform to provide all of the enterprise capabilities you want every app to have

Crucial Role of WSO2 Products

• Provides complete platform for ‘Trying Out’ distributed web apps

• Many products available to provide enterprise capabilities

• Agile, flexible, open to suggestions

• Keep the tech current/forward thinking—not afraid to switch out a component technology

• Identified six initial products crucial to success for our customer:– ESB, IS, API-M, MB, G-Reg, AS/DSS

Crucial Role of WSO2 Products (cont’d)

• Message translation to allow mixed technologies

• Mediation to add security information for backend services

• Centralized proxy service for common security, authorization, and logging

• Move backend services without changing front end

• Redeploy artifacts to any environment: dev, testing, training, staging, production, ...

Crucial Role of WSO2 Products (cont’d)

• Capture user info for future/modernized Federated Systems/SSO

• Built a custom callback authenticator to use customer's existing SSO capability

Crucial Role of WSO2 Products (cont’d)

• OAuth 2.0-secured service calls

• Easy role-based authorization management

• Usage throttling & monitoring

Crucial Role of WSO2 Products (cont’d)

• Use in any large distributed, message-based system for guaranteed message delivery

• Used to replicate update requests/messages to multiple systems

• May replace RabbitMQ's virtual host capability (multi-tenancy built into the WSO2 Carbon framework)

Crucial Role of WSO2 Products (cont’d)

• Primarily registry

• Dynamic endpoints

• Centralized security policies

• Additional artifacts to come

Crucial Role of WSO2 Products (cont’d)

• Hosting for Services

• Reused Existing Datasources

• Rapid prototyping of data-driven services (DSS)

• Integration at Service Host

Crucial Role of WSO2 Products (cont’d)

• In development– BPS (Business Process Server)

– DAS (Data Analytics Server)

Crucial Role of WSO2 Products (cont’d)

• Other things we like about WSO2– Open source using standard web/Internet technologies

– Same binary you run on the server, workstation, container, or cloud; on Windows, Linux, etc.

– Connect Anything to Anything

Thank You!