JBoss.orgCommunity Documentation

Chapter 6. Advanced custom configuration and extension

6.1. Channel
6.1.1. Pipe
6.1.2. Valve
6.1.3. Components
6.2. Factories
6.3. Virtual Endpoint Composition
6.4. Connection Composition

A common theme for JBoss Communications Media Server is the breaking out of internal fixed subsystems into stand-alone components.JBoss Communications Media Server strategy for making available the various voice/video services as independent components, so that they can be wired-together on demand

JBoss Communications Media server architecture promotes the usage of Service Objects to represent the media flow path. The component architecture divides the process of constructing media services into two major parts:

The role of channel is to construct media flow path by joining components using pipes. Channel can be connected to any source/sink or to other channel. The following diagram explains channel structure.

Respective channel declaration:


Configurable aspects of the channel are:

components

The list of components used by the channel

pipes

The list of pipes wich defines the actual media flow path

For creating any component Media Server uses suitable Factory. Each component has its unique identifier and name defined by its factory. Component identifier is unique within the entire server implementation. The name of component in opposite way is shared across component produced by same factory.

If the endpoint is implemented by software components only (virtual endpoint) then in this case endpoint can be constucted dynamic


Configurable aspects of the virtual endpoint are:

connectionFactory

Specifies factory used to construct connection.

groupFactory

Specified resource group.

mediaSource

Specifies media source component

mediaSink

Specifies media sink component

Connection consits from collection of channels specific for direction and media type: