Evolving Broadcast Operations With ESB

Chris Contakes, Vice President IT, PBS

Sylvain Nazef, Sr. Enterprise Architect, PBS

Bryan Boggio, Sr. Director, Media Systems, PBS

Joy Wang, Director Software Development, PBS

Murali Rajendran, Sr. Software Developer, PBS

Agenda • What is ESB? • Why implement ESB in your

infrastructure? • High level overview of BPM • ESB Pilot at PBS • Open discussion

What is ESB? • ESB = Enterprise Service Bus

• Software architecture model used for designing

and implementing communication between mutually interacting software applications in a service-oriented-architecture (SOA).

• Enables integration of different applications and systems via messaging in a “bus like” architecture.

What is ESB? • Promotes agility and flexibility by decoupling

systems and allowing them to communicate without direct dependency or knowledge of other systems on the bus.

• The ESB is implemented in software that operates between the business applications. This software is the “bus”.

Why ESB ? • Removes “point-to-point” connections. • Decoupling of services. • System integration via standard APIs. • Event monitoring. • Capture technical metrics about processes. • Capture and surface business metrics (KPIs).

Basic ESB Architecture

ESB Features • Message Routing

Routes messages according to Policies and/or Business Rules.

• Message Transformation Can convert messages from/to various formats, such as XML and JSON.

• Message Enhancement Provides ability to augment the content of a message with data from other sources (database, webservice API, etc…).

• Message Processing Provides state management for requests, sync/async messaging, publish/subscribe, etc…

• Protocol Transformation Ability to communicate between multiple system using different protocols (HTTP, TCP Socket, etc…).

• Service Orchestration Provides the ability to create higher-level services by combining and orchestrating other services.

• Transaction Management Provides transaction support for processes that span across multiple services.

• Security Provides fine grained authentication and authorization at the service level but also at the message level.

What about the end user? • ESB focuses on lower level system

integration and orchestration

• BPM implemented for higher level user interactions (business processes) Example: An error condition is detected by ESB requiring a user decision or action before proceeding to the next step of a workflow.

What is BPM? • BPM = Business Process Management

• BPM complements ESB

It provides a user interface allowing human interactions with the ESB system. The ESB also has the ability to initiate human processes when needed.

• Process Modeling Non-technical people can graphically design/maintain processes, using BPMN language.

• Process State Management State of a process is maintained by BPM, along with audit data used for statistical reporting.

• SLA and Escalations BPM provides ability to monitor processes and send alerts, re-assign or terminate tasks, based on business rules.

ESB Pilot at PBS • PBS has embarked on an ESB implementation to:

– Simplify complicated architecture. – Provide layer of abstraction around broadcasts

systems. – Provide an architecture that will scale and evolve with

the business. – Have a better understanding of throughput and

capacity of systems.

ESB Pilot at PBS • Team chose a well understood and well defined

existing workflow – AS03-File Transfer

• Pilot workflow utilizes many of the building blocks for other systems (Real Time, DDMS, etc.): – QC Solution – Program Schedule – Media Storage Solution – Accelerated File Transfer Solution

ESB Pilot at PBS

ESB Pilot

at PBS

*FIMS = Framework for Interoperable Media Services

Thank You!

Discussion / Questions

crcontakes@pbs.org