event-driven service-oriented architecture (edsoa)

8/9/2019 Event-Driven Service-oriented Architecture (EDSOA)

1/19

Event-Driven Service-oriented Architecture (EDSOA)


2/19

Presentation Outline2Background

IntroductionChallenges

e a e orProposed ArchitectureModel, Composition, and Deployment

ContributionConclusion & Future Work

2/16/2010 Event-Driven Service Oriented Architecture


3/19

Web Services3Definition by World Wide Web consortium (W3C)

a software application identified by a URI, whose interfacesand bindings are capable of being defined, described anddiscovered as XML artifacts. A web service supports direct

-

messages exchanged via Internet-based protocols


Registry

Producer Consumer


4/19

Web Service Interaction Pattern4



5/19

WS* Stack5



6/19

Web Services Composition6Business applications exposing their functionalities through web services

Developing and exposing Web Services is not sufficient. We need tocombine the functionality of several web services.The process of developing a composite service is called service composition.Service composition can be either performed by composing elementary or

composite services.



7/19

Introduction7A business process consists of a set of activities to provide aspecified servers..Business processes require composition of services to fulfill itsgoal, e.g. loan approval, Orderbook, generate result.Business rocesses are driven b events and d namic in nature.

Service-oriented Architecture (SOA) is an extension todistributed computing paradigms to publish, discover, invokesoftware component as services and for loosely coupledinteroperable integration of distributed heterogeneous system.



8/19

Challenges8Dynamically changing business requires

Service description and discoveryEvent-driven modeling and CompositionAdaptive to the changes (State, Event and Execution)

Heterogeneous partner infrastructure requires

Interoperability, common vocabularyVanilla Web Services are lacking these requirements.

Standards and specifications are syntax orientedNo semantic support to make it machine processableLimited usability



9/19


10/19

Event-driven SOA Lifecycle10



11/19

Event-driven SOA Architecture11



12/19

Event Driven Composition12Event-Condition-Action rule: when an event occurs, the

condition will be evaluated and action will be taken ifthe condition is true.

RULE[(,)]WHEN

IF THEN

IF THEN

ENDRULE



13/19

Backward Chain Rule13Backward Chain Rule: Contains preconditions for the tasksBackward Chaining Algorithm Deals with the backward chain rulesand identifies the tasks that need to be executed.Input: Backward Chain RuleOutput: A={A1,A2,A3,....An} where A1,A2...An are the activities thatneed to be performed

beginTask Pool TP = //empty initiallyfor each rule r in BCR{

if (r.pre-condition TP)

add r.pre-condition to TP}

A= TPend



14/19

Forward Chain Rule14Forward Chain Rule: ECA rules are define as a Forward Chain RuleForward Chaining Algorithm deals with the forward chain rules and

identifies the order in which tasks need to be executed.Input : ForwardChain Rules FCR, A set of activities that need to beperformed, initial task IOutput : P[n] where Pi A and P is the process schema

begin

Task Pool P = //empty initiallyAdd I to Ptemp=I

Label:index_of_task = Search(A,temp)

//Search will return -1 if temp is not present in Awhile (index_of_task ! = - 1){

forward_index = Search(FCR,P[index_of_task].taskname)

add FCR[forward_index].action to Ptemp = FCR[forward_index].action

goto Label

}end



15/19

Deployment: Grid Business Process15

Grid Business Process: to capture the requirements of dynamic

business processes.Grid computing utilize SOA to capture the requirements of abusiness process.

onvergence o e erv ces an r compu ng rep aceOGSI functionality with web services based set ofspecifications:

WS Resource Framework (WS-RF)WS Notification (WSN)



16/19

Six-Step Process161. Model the business process.2. Develop WS-RF service using factory pattern.3. Modification of wsdl files.

4. nser on o ea er var a es5. Orchestration of a process6. Execution of process in grid environments



17/19

Convergence of SW, WS and GS17

Discovery

u s

i n e s s

S e r v

i c e s

Semantic Web

Standards are syntax based

Automation of business process

Domain Ontology and Rules

Business Ontology and Business Rules


Composition

Deployment

S e m a n t i c

G r i

d B u s i n e s s

P r o c e s s Web Services

Grid Services

state, transaction, event and notification

Scalability, Execution and Monitoring

Middleware support

Business Process Modeling

Event-driven Composition

Business Services

Grid Services


18/19

Conclusion18We have identified issues related to composition of a businessprocess and discussed the requirements for event-driven composition

and event-driven service-oriented architecture.We have implemented event-driven lifecycle (model, compose,deploy, and execution) and proposed Event-driven Service-orientedArchitecture.

We have demonstrated realization of event-driven Service-orientedArchitecture with the use of policy, service level agreement, andservice grouping for effective coordination of resourcesCreation of Virtual Organization (VO) based on the policy to allowaccess and sharing of resources

Use of semantic and policy to provide better search, query, andmanagementContext, content and contract based dynamic services selection



19/19

Thank You!Contact Us -For more information:

Attune Infocom Pvt Ltdwww.attuneinfocom.com

[email protected] : +91-79-40047259Cell : +91-9737339652

event-driven service-oriented architecture (edsoa)

Documents