
	Version 9.5 SP1	SEARCH CONTENTS \| PDF BOOKS \| HOME UP PREV NEXT

— Broker —

Broker Quick Reference

This document covers the following topics:

Functionality: Communication Models
ACI Syntax of Messaging Model
Location of Broker Kernel and Stubs
Transport: Broker Stubs and APIs

Functionality: Communication Models

The table below shows which functionality of EntireX Broker is supported by each of the two communication models: Client and Server and Publish and Subscribe.

Functionality	Client and Server	Publish and Subscribe
Application bindings (stubs)	x	x
Command and Information Services	x	x
Accounting	x
Data compression	x	x
Codepage conversion	x	x
Persistent store	x	x
Security	x	x
Units of work	x

ACI Syntax of Messaging Model

This table provides the ACI syntax used in both of EntireX Broker's communication models Client and Server and Publish and Subscribe

Messaging Term		Client and Server		Publish and Subscribe
Messaging Term		Client	Server	Publish	Subscribe
	Synchronous	`SEND` ⁽¹⁾ `WAIT=YES` ⁽¹⁾	`RECEIVE` `WAIT=YES`	not applicable	not applicable
	Asynchronous ⁽³⁾	`SEND` `WAIT=NO` `WAIT=YES`	`RECEIVE` `WAIT=NO`	`SEND_PUBLICATION` `WAIT=NO`	`RECEIVE_PUBLICATION` `WAIT=NO` `WAIT=YES` ⁽²⁾
	Conversational ⁽³⁾	`SEND` `CONV-ID=NEW`	`RECEIVE`	not applicable	not applicable
	Non-conversational ⁽³⁾	`SEND` `CONV-ID=NONE`	`RECEIVE`	`SEND_PUBLICATION`

Notes:

The synchronous SEND, WAIT=YES command contains an implied RECEIVE command.
The subscriber has the option of specifying WAIT=YES.
Example: The subscriber uses a repeat loop that issues a RECEIVE_PUBLICATION. The advantage is that the program runs continuously, processing publications arising as random events, which simplifies programming effort.
Persistence available. See Concepts of Persistent Messaging.

Location of Broker Kernel and Stubs

This graphic shows the locations where the broker kernel and broker stubs can be installed. See Architecture of Broker Kernel and Architecture of Broker Stub.

graphics/bro_inst.png

Transport: Broker Stubs and APIs

This table gives an overview of the transport methods supported by EntireX Broker stubs.

Operating System	Environment	Module	Transport to Broker
Operating System	Environment	Module	TCP	SSL	NET ⁽¹⁾	HTTP(S) ⁽⁶⁾
z/OS ⁽²⁾	Batch, TSO, IMS (BMP)	BROKER	x	x	x
	Com-plete	COMETB	x	⁽³⁾	x
	CICS	CICSETB	x	⁽³⁾	x
	IMS (MPP)	MPPETB	x	x	x
	IDMS/DC ⁽⁴⁾	IDMSETB	x	⁽³⁾
	Natural	NATETB23	x	x	x
	UNIX System Services	Java ACI	x	x		x
UNIX		broker.so	x	x
UNIX		Java ACI	x	x		x
Windows		broker.dll ⁽⁵⁾	x	x
Windows		Java ACI	x	x		x
BS2000/OSD	Batch, Dialog (formerly TIAM)	BROKER	x	x	x
z/VM		BKIMBCMS	x		x
IBM i		EXA	x
OpenVMS		BROKER	x	x

Notes:

NET is available for transport to a broker running under mainframe platforms only; not to a broker running under UNIX or Windows.
Under z/OS you can use IBM's Application Transparent Transport Layer Security (AT-TLS) as an alternative to direct SSL support inside the broker stub. Refer to the IBM documentation for more information.
Use AT-TLS. See Note 2.
Tracing and transport timeout are not supported in this environment.
Stub broker32.dll is supported for reasons of backward compatibility. The functionality is identical to broker.dll.
Via Broker HTTP(S) Agent; see Settting up and Administering the Broker HTTP(S) Agent under UNIX | Windows.