best practices for adopting soa
Download
Skip this Video
Download Presentation
Best Practices for Adopting SOA

Loading in 2 Seconds...

play fullscreen
1 / 37

Best Practices for Adopting SOA - PowerPoint PPT Presentation


  • 266 Views
  • Uploaded on

Best Practices for Adopting SOA. SOA Overview. What is SOA?. Service Oriented Architecture. Service. System capabilities that provide access to functions and data are appropriately exposed to other components (applications, devices, networks, etc.). Oriented.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Best Practices for Adopting SOA' - omer


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
what is soa
What is SOA?

Service Oriented Architecture

Service

System capabilities that provide access to functions and data are appropriately exposed to other components (applications, devices, networks, etc.)

Oriented

Uses “open” interoperability protocols

Architecture

In its purest form, it’s the connection of systems (simple or complex)

what has slowed true soa implementations

Application

Application

Application

Application

Application

Application

What Has Slowed True SOA Implementations?
  • Proprietary tools
  • Lack of universally accepted protocols
  • Enterprise governance less emphasized
  • Legacy roadblocks

Result is StovePipe Integration

what is different now
What is Different Now?
  • Numerous tools and open standards:Internet, XML, SOAP, UDDI, WSDL, JMS, .NET, etc…
  • General acceptance of standards
  • Architecturally integrated Web Services, MOM, and RMI architectures are now more achievable
  • Unprecedented urgency to share data
a practical step
A Practical Step

Enterprise Governance being the objective:

  • Leverage the legacy by decoupling point-to-point relationships and extending services to external requests
  • Monolithic legacy applications can be become “service providers”
  • Exposing services is more important than how
  • Service Orientation is infectious
integration of services

Application

Application

Application

Application

Application

Application

Application

Application

Application

Application

Application

Application

Business Rules

Publish

Inquire

Data Transformation Rules

Integration of Services
  • The integration of services becomes the Service Bus,or what we like to call the Interoperability Hub
walk then run

Business Function/Service Aggregation

Transformation/Routing Services

Orchestrated Transactionsand Event Driven Services

Walk Then Run
  • Start with simple document-oriented exchanges
  • Enhance through service aggregation
  • Prudently evolve toward document-oriented Publish/Subscribe and Orchestrated relationships
soa opens the architecture

Application

Application

Business Rules

Publish

Inquire

Application

Application

Data Transformation Rules

Application

Application

SOA Opens the Architecture
  • As external services development spreads and matures within an environment, the legacy application components become “open.”- and therefore -
  • New application development will begin to be based more on the integration of services, rather than linking of components and databases.
troy holmes
Troy Holmes

Implementing SOA

how services make applications open
How Services Make Applications Open
  • SOA is a service based architecture that utilizes open, standards-based Web Services
  • All applications can speak XML without requiring proprietary third party products
  • SOA breaks down the walls of conventional software design, by enabling reuse of existing applications.
  • SOA can be used to encapsulate legacy business logic and provide functionality to a larger user base.
how services make applications open12
How Services Make Applications Open
  • By wrapping services with SOA, agencies will be building the groundwork for information sharing throughout the government.
  • Building new solutions for agencies becomes faster and easier
    • Existing services can be quickly combined into new applications, that provide enhanced functionality
    • The applications are exposed in a standardized format
  • It becomes the “a la carte” of application processes
how services make applications open13

Database

Database

Consumer

Producer

API

API

Data Access

Tier

Business

Tier

Data Access

Tier

How Services Make Applications Open
  • In the past applications were integrated in a tightly coupled fashion which led to a frail implementation
  • By providing loose coupling to application processes, the consumer is not aware of the internal implementation, and therefore is protected from changes by the producer.
how services make applications open14
How Services Make Applications Open
  • In the past applications were integrated in a tightly coupled fashion which led to a frail implementation
  • By providing loose coupling to application processes, the consumer is not aware of the internal implementation, and therefore is protected from changes by the producer.

Database

Database

GenericService

Consumer

Producer

API

API

Data Access

Tier

Business

Tier

Data Access

Tier

how services make applications open15

Business Logic

Interface Facade

Customizable Presentation Tier

BusinessApplication

?

Service

XML

Producer

Consumer

Secure Business Applications

How Services Make Applications Open
  • An agency can quickly adapt to new methods of communication
  • New implementations can be added faster and more reliably in a SOA environment
  • New customers send messages based on an agreed contract between the producer and consumer
  • The implementation is independent of the producer which enables multiple views of information without impacting legacy applications

Message

Contract

how agencies are integrating stovepipe applications

Data

Data

Data

DataWarehouse

DataMarts

DataMarts

How Agencies are Integrating Stovepipe Applications

LegacyMainframes

Today’s Architecture

Workstation

ApplicationServers

ApplicationServers

Web Servers

ReportServer

technologies used for integration

Message Oriented MiddlewareMOM(Hub and Spoke)

Data Warehousing

Object

XML

Service

Legacy

Object

Marts

Marts

Warehouse

Marts

Marts

Web Services

Remote Method InvocationsRMI

Technologies Used for Integration
roadmap to soa

Application

XML

XML

XML

Service

Service

Service

BusinessProcess

BusinessProcess

BusinessProcess

Roadmap to SOA
  • Start by creating services around existing processes within applications
  • Define current business processes within existing applications
  • Create course grain services that satisfy particular business processes
  • Make these services available to the internal agency
  • Expose these services to external agencies via an Enterprise Interoperability Hub (Service Bus)
roadmap to soa19

Application

Application

Application

XML

XML

XML

XML

XML

XML

XML

XML

Service

Service

Service

Service

Service

Service

Service

Service

BusinessProcess

BusinessProcess

BusinessProcess

BusinessProcess

BusinessProcess

BusinessProcess

BusinessProcess

BusinessProcess

Roadmap to SOA

Moving from Stovepipes . . .

roadmap to soa20

Application

Application

Application

Transformation

Transformation

Transformation

Service

Service

Service

Service

Service

Service

Service

Service

BusinessProcess

BusinessProcess

BusinessProcess

BusinessProcess

BusinessProcess

BusinessProcess

BusinessProcess

BusinessProcess

Roadmap to SOA

Enterprise Interoperability Hub

XML

XML

XML

XML

XML

XML

XML

XML

XML

Moving from Stovepipes . . . To Shared Services

roadmap to soa21

SOAP Service

External AgencyService

Portal Service

Transformation/Routing Services

Request

Orchestrated Transactionsand Event Driven Services

Data Service

New ApplicationService

MOM Service

Roadmap to SOA
  • Enterprise Interoperability Hub
    • The next step is to provide a view of the agency to external customers via an Enterprise Interoperability Hub
    • The Hub will become the mechanism to represent services to external agencies.

Enterprise Interoperability Hub

roadmap to soa22

Data

Data

Data

DataWarehouse

DataMarts

DataMarts

Roadmap to SOA

LegacyMainframes

Today’s Architecture

Workstation

ApplicationServers

ApplicationServers

Web Servers

ReportServer

roadmap to soa23

Future Architecture

Exposed Service

Exposed Service

Exposed Service

Exposed Service

Exposed Service

Data

Data

Data

DataWarehouse

DataMarts

DataMarts

Roadmap to SOA

LegacyMainframes

EnterpriseInteroperabilityHub(Service Bus)

Workstation

ApplicationServers

ApplicationServers

Web Servers

ReportServer

roadmap to soa24

Future Architecture

Exposed Service

Exposed Service

Exposed Service

Exposed Service

Exposed Service

Data

Data

Data

DataWarehouse

DataMarts

DataMarts

Roadmap to SOA

LegacyMainframes

EnterpriseInteroperabilityHub(Service Bus)

Workstation

ApplicationServers

ApplicationServers

Web Servers

ReportServer

jeff simpson
Jeff Simpson

SOA Best Practices

what attendees will learn
What Attendees Will Learn
  • Best practices for the implementation of service-oriented architectures (SOA) and web services
  • How to design a roadmap to consolidate and rationalize diverse constituent portals, websites, and web services with a common architecture, security framework, and user interface
  • Practical suggestions for using resources from legacy systems with newer applications
implementation best practices
Implementation Best-Practices
  • What is the Use-Case?
  • Plan for reuse
  • Transactions
  • Tuning and Management
plan for reuse
Plan for Reuse
  • Scalability
  • Reliability
  • Deployment
  • Documentation
pick the right interface
Pick the Right Interface
  • Web Services and XML provide best interoperability but not the best performance
  • Web Services are not always the right answer
  • Maybe multiple interfaces? (WS, RMI, JMS, MQ, CORBA, etc.)
to uddi or to not uddi
To UDDI or to Not UDDI ?
  • When do you publish your WSDL?
    • The defacto standard – email
  • UDDI.org

Excellent source of information and resources regarding UDDI, the specification, and the future of WebServices discovery

webservice management
WebService Management
  • What does it provide?
    • Quality of Service (QoS)
    • Service Level Agreements (SLAs)
  • Registry Services
  • When to involve the technology?
rationalization roadmap
Rationalization Roadmap
  • Service Rationalization or Portal Rationalization?
  • Is there a difference?
    • A portal or portlet does not equal a WebService
  • Composite Application or Business Process Rationalization?
service rationalization

Service Fabric

Service Rationalization
  • Creating a new service contract or API that fronts multiple legacy implementations
  • Enables service consolidation
  • Terrific path to drastically reducing TCO

Rationalized

Service

router

adaptor

adaptor

adaptor

Legacy

Service A

Legacy

Service B

Legacy

Service C

portal rationalization
Portal Rationalization
  • Collapsing the web interfaces from multiple systems into a single portal by having each interface be its own portlet within the portal
composite applications
Composite Applications
  • Business Process Rationalization
    • A combination of Service and Portal Rationalization where, through a workflow engine, we create a new composite application and new interface that leverages existing IT assets in a new unified business process
integrating the integration

Process / Data Integration

App Server

SOA Fabric

Integrating the Integration

WebService Enabled

Broker

Broker (BEA, WebMethods or Tibco)

WebService Enabled

PeopleSoft

WebService Enabled

WebService Enabled

WebService Enabled

HR System 1

HR System 2

HR System 3

adapting legacy system for soa
Adapting Legacy System for SOA
  • Fronting with a WebService
    • Can be done with one of many technologies - Apache Axis, Systinet, J2EE Servlet containers (Tomcat, JBoss, WebSphere, WebLogic), etc
    • Look to using a WebService Management layer
  • Utilizing a Messaging system (ESB Flavor 1)
    • MQ Series, Tibco, one of many JMS providers
  • Utilizing Traditional EAI connectors (ESB Flavor 2)
    • Vitria, webMethods, SeeBeyond, etc.
ad