Saturday, February 23, 2013

Service, Oriented, Arhictecture

Service:
         Encapsulation
         Interface
         Contract or service level agreements

Orientation:
         Granularity
         Collaboration

         Universality


Architecture:
         Consistency
         Reliability

         Extensible
         Scalable

Consistent architecture with standards(open and SOA) gives inter-operability.


Service orientation is an architectural concept that refers to the loose coupling of a service (an abstract resource with a defined job) and its provider (the physical asset(s) that perform the job tasks).

The two primary styles of SOA used in business solution development are
1. composite application development and flow.
2. a service may generate an event.

SOA principles:

Loose coupling
Inter-operability
Reusability

Standardization
Modularity
Composibility
Discoverability
Abstraction
Coarse-grained interfaces
Statelessness

SOA Implementation components:
Business Services
Application services: user access, business function, common services, user interaction, business process choreography, and information management.
Common Services: utilities
Information Management service: provide uniform way of representing, accessing, maintaining, managing, analyzing, and integrating data and content across heterogeneous information sources.
ESB: Service and metadata(e.g., endpoint) virtulization


What SOA gives to a business and technology?

It provides a common term of understanding for both business and technical org/ppl.
Interoperability: technology players agreed to be interoperate with SOA standards
Extensions and evolution: recognizes the ever changing world
Reuse:

Jargons:

Service component architecture
Component: a piece of business logic, process logic, BPEL process, mediator
Service
Reference
wire
composite.xml

OSB: service abstraction layer, simple orchestration

Oracle SOA: service composition

BPEL: complex orchestration

BPEL PM: system centric process engine

Business PM: human centric process engine

Business rule: business decision making, for decision point.

Secutiry is characteristic of service.

Centralize policy repository and distributed enforcement at boundaries

Enterprise Manager: is policy manager

B2B: EDIFACT, ANSIX12, Rossetanet, ebXML

CEP: time or series based analysis of data.

CEP(complex event processing) : requires to monitor several of them to spot and respond to trends
vs
MP(Message processing): requires some action on their own with little or minimal context.

EDN: need more citation

Application Server: WLS, CEP does not requires AS, OSB and SOA Suite components run in separate containers.

Database: to maintain runtime info and configuration info.
Oracle SOA designed to run on any sql DB. Oracle DB is best for production.


SOA Suite Layers:

Service Layer: BAM,B2B,BPEL, Mediator, Rules, CEP, HumanWorkflow
Infrastructure Layer: Transformation, Policy, SCA, Registry
Binding Layer: SOAP, JCA
Portability Layer: interface between SOA Suite and AS/J2EE platform

OSB VS Mediator:

1. Weblogic vs Multi platform(weblogic, jboss, websphere)
2. (M)validation, routing and transformation within composite
3. (M)low cost for service virtualisation comes with SOA
4. (O)

OSB:

Binding: provides abstract interface no info of physical end point and other configuration
Port: provides physical end points

Proxy service defines the message flow.

Service end point virtualisation: move the service to anywhere

"Test Console" service is not running. Contact administrator to start this service.

http://anuj-dwivedi.blogspot.no/2010/07/osb-11g-11113-test-console-not-working.html






Friday, February 22, 2013

Adaption path for SOA

Business architecture: as:is -> to be-> gap analysis-> process design-> governance requirements

SOA Application architecture: (as is)application communication protocol-> to be-> governance framework

Data Architecture: data models(source and target) and repository, database design

Service design

Governance reporting