enterprise backbone overlay std3.2

7/28/2019 Enterprise Backbone Overlay Std3.2

1/23

Please contribute {8>D)V3.2

Codex Confidential

Please contribute {8>D) Codex Confidential

The

Enterprise Backbone

Overlay

(EBbO)

Distributionof

Services, Events and Data

AnInformation Delivery

Engineering Viewpoint

2013Q3 Copyright 2005-13, New Global Enterprises 1
mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]


2/23


Codex Confidential

Contents Overview

Base Concepts

EBbO Protocols Common Functionality

Reliable Broadcast Protocol

Publish Subscribe Protocol

Request Reply Protocol

Data Stream Protocol

EBbO Protocol Design Patterns

mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]


3/23


Codex Confidential

Please contribute {8>D) Codex Confidential

Overview

Motivation

Intended Use

The

Information Delivery

Engineering Viewpoint



4/23


Codex Confidential

MotivationFor an Integration and Software Designed Network

Strategy, answer three questions from an EngineeringViewpoint

What is the effective set of service, event, and data

distribution protocols necessary to provide a fullyfunctional Enterprise Backbone?

What components are needed to implement an Enterprise

Backbone Overlay?

What are some design patterns to assist in the

implementation, deployment and use of the proposed

EBbO protocols?


Please contribute {8>D)


5/23


Codex Confidential

Intended Use Enterprise Architecture Statement

Target Architecture of Record

Evaluation Framework

Tools

Methods

Technology

Guide for Application Development

Implement Integration COE Strategy

Implement Data Transformation Strategy


Please contribute {8>D)


6/23


Codex Confidential

The Information DeliveryEngineering Viewpoint


App l icat ion Components

Enterprise Backbone Overlay

Environmental Compo nents

Sys

tem

Process

Mon

itor

Bus

iness

Process

Mon

itor

State

Manager

Dep

loyment

Manager

Da

ta

Cac

he

Manager

Po

licy

Manager

Even

t

Manager

Serv

ice

Leve

l

Manager

Bus

iness

Func

tion

/In

forma

tion

Serv

ice

Orc

hes

tra

tor

Integra

tor

User

Scenario

Work

Flow

Channe

l

Con

tro

ller

User

Interface

Con

tro

ller

Environm ental Bus

Appl ica tion Bu sUser

Interface

Transac

tionManagem

entSystems

,

Analyt

icsManagem

entSystems

Configura

tionManagem

entSystems

&

DataManagemen

tSystems


7/23Please contribute {8>D)V3.2

Codex ConfidentialPlease contribute {8>D) Codex Confidential

Base Concepts

Event

TopicView

Bus/Conduit

YellowBoard




Codex Confidential

Base ConceptsPrimitive Logical System Resources

Event

A significant occurrence at the BusinessProcess, Application Execution or SystemOperation level that is identified in aRegistry

Topic

A categorical key word or key phrase(possible sequence of either) that is

defined within a taxonomic or semanticstructure

View

Specification of a data context needed tosupport the realization of an ApplicationScenario or execution of a Service

Can be articulated by an SQLstatement)

Bus

A collection of conduits through whichflow service requests, events and/ordata:

Application

Supports collaborations amongstcomponents to realize a specific UserExperience

Environmental

Supports collaborations amongstcomponents used to control operationsof systems

YellowBoard

A global system structure that allowsposting and reading of availableresources and states of services in flight

2013Q3 Copyright 2005-13, New Global Enterprises 8Please contribute {8>D)

Event

A significant occurrence at theBusiness Process, Application

Execution or System Operation level

that is identified in a Registry

Topic

A categorical key word or key phrase(possible sequence of either) that is

defined within a taxonomic or

semantic structure

View

Specification of a data context needed

to support the realization of an

Application Scenario or execution of a

Service

Can be articulated by an SQL

statement)

Bus

A collection of conduits through whichflow service requests, events and/or

data:

Application

Supports collaborations amongst

components to realize a specific User

Experience Environmental

Supports collaborations amongst

components used to control

operations of systems

YellowBoard

A global system structure that allowsposting and reading of available

resources and states of services in

flight



Codex Confidential

Supporting Componentsfor Base Concepts


Enterprise Backbone Overlay

Event

Registry

Topic

Registry

YellowBoard

Resource & ServiceStatus Postings

View

Registry

Appl ica tion B usconduits

Environm ental Busconduits




EBbO Protocols

Common FunctionalityReliable Broadcast

Publish Subscribe

Request Reply

Data Stream




Codex Confidential

Universal Object

Functional

Context

EBbO Contextual Questions

Where is my Root of Trust?

Who certifies me?

Where am I?

What is my geographic location?

When am I?

What time is it where I am?

Why am I?

What am I and What is my purpose?

Who controls me

Who controls my life cycle? (Whos my Daddy?)




Codex Confidential

Universal Object

Functional

Content

Common EBbO Protocol FunctionalityService Points advertiseService( { ( aServiceDescription, aVoI, aServiceLevelOffer ) }, aYellowBoard, aProvider )

returns ( aPostingRecord )

Advertise on a YellowBoard, a set of service and level offerings { (S, VoI, SLO)i } by a provider

locateService( aServiceDescription, aServiceLevelRequirement, aYellowBoard )

returns ( anSLARecord )

Locate on a YellowBoard, a provider of a service described

Usage All returns are described as XML documents

Can be compiled or rendered into more efficient forms for execution

All System Components have three (wait! four) common instrumentation methodsCommunicated via a designated conduiton the System Management Environmental Bus

reportNameVersion()

Whats your name?

reportRequirements()

What resources do you need to work?

reportProtocolList()

What do you speak?

reportUseStatistics()

What have you done?

Notes





Reliable Broadcast Protocol

Service where receiver can know if

message/event missed and request

resend


R li bl B d P l



Codex Confidential

Reliable Broadcast ProtocolService Points

subscribeRBEoI( { ( { ( { anEoIk }, aToI )m }, aVoI )n }, aBroadcastProvider )

returns ( aBroadcastRegistration )

Register sets of ( sets of ( list of Events of Interest undera Topic of Interest ) within View a of Interest ) to a Broadcast Provider

receiveAsynchRB( aBroadcastRegistration )returns ( aMessage )

Receive Messages asynchronously on the Conduit of a Broadcast Registration

resendRB( aBroadcastRegistration, lastGoodMessage )

returns ( aStatus )

Resend messages after the last good message received through the Conduit of a Broadcast Registration for Messages

suspendRB( aBroadcastRegistration )

returns ( aStatus )

Suspend receipt through the Conduit of a Broadcast Registration for Messages

resumeRB( aBroadcastRegistration )

returns ( aStatus )

Resume receipt through the Conduit of a Broadcast Registration for Messages

disengageRB( aBroadcastRegistration )

returns ( aStatus )

Disengage from the Conduit of a Broadcast Registration for Messages





Publish Subscribe Protocol

Service based on taxonomy of

topics/event types of interest

where consumer and provider areunknown to each other


P bli h S b ib P t l



Codex Confidential

Publish Subscribe ProtocolService Points

subscribePSEoI( { ( { ( { anEoIk }, aToI )m }, aVoI )n }, anInformationProvider )returns ( anInformationSubscription ) Register sets of ( sets of ( list of Events of Interest undera Topic of Interest ) within View a of Interest ) from an information provider

registerPSEoI( { ( { ( { anEoIk }, aToI )m }, aVoI )n }, anInformationProvider )

returns ( anInformationPublication ) Register sets of ( sets of ( list of Events of Interest undera Topic of Interest ) within View a of Interest ) as an information provider

receiveAsynchPS( anInformationSubscription )returns ( aMessage ) Receive Messages asynchronously on the Conduit of a Information Subscription

publishPSEoI( aMessage, anEoI, aToI, aVoI, anInformationPublication )returns ( aStatus ) Publish message and its context (EoI, ToI, VoI) on the Conduit of a Information Registration

suspendPSSubscription( anInformationSubscription )returns ( aStatus )

Suspend receipt through the Conduit of a Subscription for Messages resumePSSubscription( anInformationSubscription )

returns ( aStatus ) Resume receipt through the Conduit of a Subscription for Messages

disengagePSSubscription( anInformationSubscription )returns ( aStatus ) Disengage from the Conduit of a Subscription for Messages

suspendPSPublication( anInformationPublication )

returns ( aStatus )

Suspend receipt on the Conduit of a Publication of Messages

resumePSPublication( anInformationPublication )

returns ( aStatus )

Resume receipt on the Conduit of a Publicatiof Messages

disengagePSPublication( anInformationPublication )

returns ( aStatus )

Disengage from the Conduit of a Publication of Messages



17/23Please contribute {8>D)

V3.2


Request Reply Protocol

Service invocation which is

potentially dynamically locatable

where result is returned


R t R l P t l



V3.2

Codex Confidential

Request Reply ProtocolService Points

requestAsynchRR( anSLARecord )returns ( aConduit ) Request asynchronously a Service through a Conduit per an SLA Record

receiveAsynchRR( aConduit )

returns ( aMessage )

Receive Messages asynchronously through the Conduit of a Service request

requestRR( anSLARecord )returns ( aMessage ) Request synchronously a Service through a Conduit per an SLA Record

disengageRR( anSLARecord )

returns ( aStatus )

Disengage from an asynchronous Service request through a Conduit per an SLA Record




V3.2


Data Stream Protocol

Service that delivers large units of

data of differing types, textual or

bit-based


D t St P t l



V3.2

Codex Confidential

Data Stream ProtocolService Points

receiveDS( aConduit, aVoI, aStoreType, aProvider )

returns ( aStoreRecord )

Connect and Receive into a store, a data stream of a VoI from a providerthrough a conduit

suspendDS( aConduit, aVoI, aStoreLocation, aProvider )returns ( aStopRecord )

Suspend receiving a data stream of a VoI from a service providerthrough a conduit

resumeeDS( aConduit, aVoI, aStoreLocation, aProvider )

returns ( aStopRecord )

Restart receiving a data stream of a VoI from a service providerthrough a conduit

disengageDS( aConduit, aVoI, aStoreLocation, aProvider )

returns ( aStopRecord )

Stop receiving a data stream of a VoI from a service providerthrough a conduit




V3.2


EBbO Protocol Design Patterns

Application Scenarios

Data Transparency

Migration Transparency

mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]



V3.2

Codex Confidential

Data Transparency


T B D

JudiciousReplicationof

Data


23/23

V3 2

Migration Transparency

2013Q3 Copyright 2005-13 New Global Enterprises 23

T B D

Fungibilityof

WorkLoads
mailto:[email protected]

enterprise backbone overlay std3.2

Documents