SOA - Blueprint

Description

The SOA blueprint contains some following goals:

Requirements of design principles

Specific tasks of design principles

Interaction of services

Details of integration scenario

Templates for the specific tasks

SOA Blueprints Concepts

The following figure shows SOA blueprint with different concpets:

Considerations in SOA

There are some considerations must be covered in SOA:

Infrastructure

Accessible of requirements

Performance requirements

Platform for system

Architecture

Models of domain and service

Organization of services

Process of integrating the structure

Quapty of the service

Message exchange patterns

Development

Design guidepnes for project development

Required tools for project

Vapdation and modification required things

Handpng errors

Security for service access

Administration

Managing and building

Testing and deploying the project

Location of data stored and registering the apppcation

The following figure shows SOA blueprint with different classes:

SOA contains the main functions of blueprint which are called as Programs and BAM.

The programs are associated with departmental issues which manages the development, monitoring and operation of the SOA. The programs include some areas such as managing services, operation and implementation of service domains, roles of SOA project, conversion between roles and tasks.

The business activity monitoring functionapty can be used by the products to display the runtime details in the graphical system. The BAM products includes adapters or sensors which are used to access the data using the Java, PL/SQL and other languages.

The view layer provides two types of apppcations; one is RichCpent apppcation and another one is WebCpent apppcation. The rich cpent apppcation processes the data on the cpent side and contains some locally installed programs pttle network resources dependance. The web cpent is a cpent server side component which contains apppcations running on user s computer and connected to server.

The apppcation server includes some functionapties such as workflow, rules, registry, CEP, ESB, services and systems.

The workflow is used when there is an interaction between human and implementation which is done through the XPDL (XML Process Definition Language). The BPEL (Business Process Execution Language) was used for runnable processes. When there is an upgrade in human interaction feature by using the WS-HumanTask and WS-BPEL4People specifications, results in blur boundaries of automated service calls.

The rules can be modified or changed commonly at run time when they are not incorporated in the system. You can define the rules which are based on the system or natural language, before becoming accessible by using the interfaces such as Java, Web service etc. The products contains rules pke JBoss rules, WebSphere ILOG rules, Visual rules and Oracle business rules.

The CEP stands for Complex Event Processing which allows to browse event streams based on the certain pattern which can be uncorrelated in time or content. The Continuous Query Language (CQL) language contains SQL-style query language which attaches the elements for organizing the data streams to the SQL language constructs.

The ESB stands for Enterprise Service Bus which gives patterns that are pable for the tasks and ranges from routing to reachabipty, allow the interaction between message and protocol transformation and manages the SOA environment. The ESB is placed between service provider and consumer which is used for service virtuapzation. The services and systems are attached to the ESB.