This document gives an overview of the major value-added services provided by EntireX Broker. These services relieve the administrator or application builder of the task of providing the desired functionality.
This document covers the following topics:
Application bindings allow applications developed in different programming languages and executing on various different platforms to be enabled by using EntireX Broker, see Architecture of Broker Stub. Specifically, Java, Natural and other programs are easily enabled using EntireX Broker. These bindings are available on all major mainframe, Linux and Windows platforms.
The application binding is the glue between the application and the EntireX Broker kernel (see Architecture of Broker Kernel, allowing your application to leverage all the functionality of EntireX regardless of
programming language
operating system
hardware platform
transport mechanism and
choice of programming interfaces.
This binding capability enables various different application components to be integrated in a loosely coupled manner. See EntireX Java ACI and EntireX Broker ACI for Assembler | C | COBOL | Natural | PL/I | RPG.
Applications on z/OS, Linux, Windows etc. communicating with each other using stubs:
Character conversion within the EntireX Broker means the incoming data is converted to the encoding of the target platform, using the codepages of the caller and receiver. See Internationalization with EntireX.
EntireX Broker includes a set of monitoring and control functions that enable you to monitor system resource utilization and view the current activities of the clients and servers on the system. These services are available through a Web-based interface, in addition to a command-line tool. An interface exists to allow program access to these facilities.
EntireX Broker provides accounting information based upon the flow of message sequences (or conversations). On z/OS, this information is written to standard accounting (SMF) records; on other platforms it is written to a file. The information can be used for:
application chargeback: apportioning EntireX resource consumption on the conversation and/or the application level
performance measurement: analyzing application throughput (bytes, messages, etc.) to determine overall performance
trend analysis: using data to determine periods of heavy and/or light resource and/or application usage
EntireX allows compression of messages passed between application components so as to consume less network bandwidth. This is done independently of transport mechanism by compressing the message in the application binding before it is transmitted to the Broker Kernel. The Broker kernel decompresses the message to enable security and data conversion to be applied.
The following graphic illustrates the sequencing of data compression within the stub and Broker kernel:
The persistent store stores units of work for client and server applications.
Persistent message delivery ensures that messages sent between client and server (or server and client) application components can reach their target even in the event of application or system failures. The user application programs units of work to achieve persistent messaging. EntireX Broker provides persistent message delivery by grouping messages into units of work (UOWs) that are committed in one atomic operation by the sender. See also Units of Work.
Persistence is implemented centrally within the Broker Kernel. Therefore, the consistency of all the stored messages is guaranteed independently of the different application components and platforms from which the messages are derived.
A persistent store driver is an executable, or a load module, which implements access to the physical persistent store. EntireX Broker allows the choice of three persistent store repositories: Adabas (DBMS), Data In Virtual (DIV) for z/OS, and native file system. The following table gives an overview of the persistent store options:
| Persistent Store Type | Description | Operating System | Notes |
|---|---|---|---|
| Adabas | Uses Adabas database. | z/OS, Linux, Windows, BS2000 | Adabas, Software AG's ADAptable dataBASe, is a high-performance, multithreaded, database management system. |
| DIV | Uses IBM Data In Virtual facility on z/OS. | z/OS | This persistent store option is implemented as a VSAM linear data set. |
| CTREE | c-tree© is an embedded local database that can be used as your persistent store. | Linux and Windows | c-tree© is the fast and reliable embedded database of FairCom Corporation®. |
Units of work inform the sender of messages about their past and current status. Specifically, UOWs are used to:
commit the sending of messages
acknowledge the receipt of messages
track the progress of sent messages at any point in time
Units of work are also the vehicle for achieving persistent messaging, although UOWs can be used without persistence.
See also Using Units of Work under Using Persistence and Units of Work in the platform-independent Administration documentation.
EntireX Security enables distributed application components running with Broker to be executed securely. EntireX Security is located centrally in the kernel of EntireX Broker giving it an overview of all messages sent between application components and therefore providing complete control over the authentication and authorization of each component.
Security checks are performed using a choice of security repositories, including:
RACF
CA ACF2
CA Top Secret
Linux and Windows security systems
The security repository chosen depends on the location of the Broker kernel. Because EntireX was designed to operate together with a security system, there is no additional application programming necessary.
This diagram depicts the location of the security components of the kernel and stubs of EntireX Broker:
See also EntireX Security.