BCM-FERA-Presentation [EDocFind.com]

8/7/2019 BCM-FERA-Presentation [EDocFind.com]

1/12

April, 2005

ebSOA Based on FERA

Reference Model

Vasco DrecunVasco Drecun

Collaborative Product Development Associates, LLCCollaborative Product Development Associates, LLC

Goran ZugicGoran Zugic

ebXMLsoft Inc.ebXMLsoft Inc.


2/12

April, 2005

FERA reconciles BPM with SOA

-Activities-Inputs/outputs

-Flows-Deliverables

-Dependencies-Transactions

-Decisions

-Contracts-Documents

-Interfaces-Security

-Messages-Registries

-Repositories-Content maps

-Services

-Events-Agents

Patterns or usecases of

information

exchange

FERABPMReference models SOA standards


3/12

April, 2005

Recognizing FERA configuration

Four process characteristics determine what FERA configuration is required

Human interaction determines the need for portal and collaborative services capabilities Sign-on, authentication, plug-in services (meetings, calendars, chat, visualization, reporting, etc.)

Process administration determines the need for federation server and gateways Security, protocols, content exchange formats, meta-data mapping, B2B process standards

(RosettaNet, CPFR, )

Process flow determines the need for event management Alerts, Escalation, Messaging, Queries, Flow controller

Business logic reconciliation determines the need for agent framework Synchronous vs. asynchronous reconciliation


4/12

April, 2005

Mapping to FERA components

Reference model steps Step1: Define content and context elements (static view Federation Information Model

(FIM) and Collaborative Process Information Model (CPIM)) Step 2: Define choreography (dynamic view) Collaborative Process Flow Information

Model (CPFIM) and Agent Interface Information Model (AIIM)

Step 3: Determine FERA configuration. Four configurations are formally specified and theysupport all possible collaboration cases (patterns) examined so far. Step 4: Document FERA capabilities and specific features required to support the

choreography (requirements) Step 5: Select applicable standards for the specified capabilities and features Step 6: Produce a final document with all architectural requirements and components to

support the pattern Step 7: Deploy to ebSOA


5/12

April, 2005

Portal

FERA Functional Architecture

FederationServer

CP

Flo

w

Agent

Framework

Collaborative

Services

Gatew

ay

Plug-inServices

Gat

ew

ay

Plug-inServices

Federated

Syste

m

Federated

Syste

m

Federated User Federated User

SOA Federation


6/12

April, 2005

ebSOA Information Model

Federation Information Model (FIM) Content and Context FIM is an informational bridge between the public and private world. Definition of federate profiles, business process specifications, collaboration protocols and

agreements, security policies, etc. Information that supports public processes anddocuments of any type for both public and private processes.

Agent Interface Information Model defines types of agents, invocation rules and statuscontrol.

Collaborative Process Information Model (CPIM) Supports complete CP context including all possible flows, participants and shared context

elements like metrics, rules and joint events The main CPIM entities are: CP Flows, Roles, Rules, Metrics and Clusters of Events

Collaborative Process Flow Information Model (CPFIM) Supports definition of the possible flows of activities, decisions and events within the CP The main CPFIM entities are: Activities, I/O-s, Events, Triggers, Decisions, Sequences,

References, etc.


7/12

April, 2005

ebSOA Collaboration Semantics

ebSOA collaboration semantics in connection with ebSOA information modelprovides full dynamic collaboration support.

ebSOA collaboration semantics formally defines all necessary interfaces with

methods/functions required for the collaboration data (ebSOA information model)manipulations and interactions between SOA Federation architectural components.

SOA Federation is a central block of the ebSOA architecture with the following

components which interfaces and methods/functions are already defined as a part of

the ebSOA architectural specification: Gateway Portal

Plug-in Services Security SOA Federation (Federation Server, Agent Framework, CP Flow Controller and

Collaborative Services)


8/12

April, 2005

Federation

Registry

ebSOA Collaboration Data and Semantics(Business Process Management)

CPA

Process Flow

RegistryCPID

ebSOA CollaborationSemantics

ebSOA Collaboration

Semantics

SOA Federation

BPSS

CPP


9/12

April, 2005

ebSOA Specifications

ebSOA Specifications include both static (SOA Federation Information Model) anddynamic view of the ebSOA architecture. The dynamic view support includesformalized ebSOA collaboration semantics of the SOA Federation internalcollaboration and its interface for the external collaborations (federated systems) viaFederation Server and Gateway.

The key components of the ebSOA Specifications include: ebSOA Information Model that fully supports informational aspects of both external and

internal collaborations Collaboration semantics and interfaces for

Gateway

Portal Plug-in Services Security SOA Federation (Federation Server, Agent Framework, CP Flow Controller and

Collaborative Services)


10/12

April, 2005

BusinessProcess

Documentation

creation

and validation

Gateway

Registry

Collaboration

Protocol

G

ATEWAY

INTE

RFACE

Modeling

F

E

DE

R

A

T

I

O

N

G

A

T

E

W

A

Y

P O R T A L

Federation Server

Security ProviderFederation Registry

CP Flow Controller

DataCollection Analysis Reporting Other Built-InServices

Service

Consumer

Service

Provider

Agent Framework

F

E

D

E

RA

T

E

D

S

Y

S

T

E

M

F

E

D

E

RA

T

E

D

S

Y

S

TE

M

Federation Manager

P

L

U

GI

N

S

E

R

V

I

C

E

S

Collaborative Services

Agent Interface

Manager

SOA Federation

ebSOA


11/12

April, 2005

ebSOA Standard-Based Components Mapping

Gateway

- Public processesebXML BPSS for public process collaborations

ebXML CPP/CPA

- Business documents creation and validation

OASIS CAM

- Communication

ebXML Messaging, SOAP with WS-Security, SMTP, JMS,

etc.

- Interface

ebSOA Gateway Interface specification.

- Registry

Gateway Registry based on standard (ebXML Registry, UDDI) or

proprietary implementation. Portal

Web server portal based on ebSOA Portal Interface specifications

Plug-in ServicesWeb services based on ebSOA Plug-in Services Interface specification

Agent FrameworkBased on ebSOA Agent Framework Specification


12/12

April, 2005

ebSOA Standard-Based Components Mapping (cont.)

Federation Server

- Federation ManagerebSOA Federation Manager Specification

- Agent Interface Manager

ebSOA Agent Interface Manager Specification

- Federation Registry

ebXML Registry Specifications (RIM and RS)

- Security Provider

ebSOA Security Provider Specification, XACML, SAML, etc. Process Flow Registry

Based on ebSOA Process Flow Registry Specification Flow Controller, Event Manager, Activity Manager and Decision Manager

Based on ebSOA Flow Controller, Event Manager, Activity Manager and

Decision Manager Specifications. Collaborative Services

Third-party tools for data analysis, reporting, collaboration pattern analysis, data quality, etc.