Drivers for using WebSphere Message Broker as an ESB

Typically, WebSphere Message Broker is used to integrate disparate systems. It is designed to transform any format of data between any type of application using any communications protocol or distribution method. It is used where there is a need for high-performance and complex integration patterns.

Consider the following reasons for using a WebSphere Message Broker as an ESB with WebSphere Process Server:

1: You are currently using WebSphere Message Broker and want to leverage existing skills.

2: You have extensive heterogeneous infrastructures, including both standard and non-standards-based applications, protocols, and data formats. For example, you are using industry formats such as SWIFT, EDI, or HL7.

3: You are implementing a wide range of messaging and integration patterns, for example, complex event processing and correlation, message splitting, and aggregation.

4: You need extensive pre-built mediation support.

5: Reliability and extensive transactional support are key requirements.

6: You want to achieve high-performance with horizontal and vertical scaling.

7: You want integration with other IBM WebSphere and Tivoli® products, as well as third-party JMS providers.

8: You want to natively transform non-XML formats without the use of adapters or user-written data transformations.

9: You want advanced publish and subscribe capabilities, including the use of a wide range of transports; high speed, low-latency messaging; and both topic and content-based routing.

10: You need complex event processing. Complex events are conditions that relate to multiple messages and are defined by applying a combination of logical, arithmetic, and temporal operators to messages or message attributes.

The IntelligentFilter and SituationManager SupportPac™ provides the ability to handle complex events that span multiple messages. Its complex event processing engine enables fast and reliable development of reactive applications, without requiring programming skills.

11: You want to integrate telemetry devices. WebSphere Message Broker can coordinate end-to-end telemetry integration. It can serve as a conduit for passing data from remote telemetry devices into enterprise applications.

Similarly, it can control data flow from command or control applications to remote control devices.

OSS - Operational Support Systems

Operations Support Systems (also called Operational Support Systems or OSS) are computer systems used by telecommunications service providers. The term OSS most frequently describes "network systems" dealing with the telecom network itself, supporting processes such as maintaining network inventory, provisioning services, configuring network components, and managing faults.

Operations Support System (OSS) performs management, inventory, engineering, planning, and repair functions for tele-communications service providers and their networks. For traditional telecom service providers, Operations Support Systems (OSSs) were mainframe-based systems designed to support telephone company staff members to automate their daily jobs such as order processing, line assignment, line testing and billing, etc.

Functions of an OSS solution may include the following components:

1: Order processing, accounting, billing and cost management
2: Network inventory, service provision, design and assign
3: Network discovery and reconciliation, trouble and fault management, capacity management
4: Network elements, asset and equipment management, field service management

A brief History of OSS Architecture:

A lot of the work on OSS has been centred on defining its architecture. Put simply, there are four key elements of OSS:
Processes : the sequence of events
Data : the information that is acted upon
Applications: the components that implement processes to manage data
Technology : how we implement the applications

During the 1990's, a 4-layer model of TMN was applicable within an OSS:

1: Business Management Level (BML)
2: Service Management Level (SML)
3: Network Management Level (NML)
4: Element Management Level (EML)

A fifth level is mentioned at times being the elements themselves, though the standards speak of only four levels.

To conclude, the OSS supports the traditional Resource and Resource Facing Service domains, whereas the BSS supports the more Customer Facing domains.

BSS - Business Support Systems

Business Support Systems (BSS) are the systems that a telephone operator or telco uses to run its business operations. The term BSS is no longer limited to telephone operators offering mobile to fixed and cable services but also can apply to service providers in all sectors such as utility providers.

Typical types of activities that count as part of BSS are taking a customer’s order, managing customer data, billing, rating, and offering B2B and B2C services. In summary, Business Support Systems (BSS) cover 4 main areas:

Product Management: Product management supports the sales and management of products, offers and bundles to businesses and mass-market customers. Product Management regularly includes offering cross-product discounts, appropriate pricing and customer loyalty programs.

Customer Management: Service Providers require a single view of the customer and regularly need to support complex hierarchies across customer-facing applications. Customer Management also covers requirements for partner management and 24x7 Web-based customer self-service.

Revenue Management: Revenue Management is a BSS focus on billing, charging and settlement that can handle any combination of OSS services, products and offers. BSS Revenue Management supports OSS order provisioning and often partner settlement.

Fulfillment Management: Fulfillment Management as part of assurance is normally associated with Operational Support Systems though Business Support Systems are often the business driver for Fulfillment Management and order provisioning.