Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Jolt   |   Topic List   |   Previous   |   Next   |   Contents   |   Index

   Using BEA Jolt

Jolt Event Subscription receives event notifications from either BEA Tuxedo services or other BEA Tuxedo clients:

Unsolicited Event Notifications. A Jolt client receives these notifications as a result of a BEA Tuxedo client or service subscribing to unsolicited events, and a BEA Tuxedo client issuing a broadcast (using either a tpbroadcast() or a directly targeted message via a tpnotify() ATMI call). Unsolicited event notifications do not need the TMUSREVT server.

Brokered Event Notifications. A Jolt client receives these notifications through the BEA Tuxedo Event Broker. The notifications are only received when both Jolt clients subscribe to an event and any BEA Tuxedo client or server posts an event using tppost(). Brokered event notifications require the TMUSREVT server.

Configure the BEA Tuxedo TMUSREVT server and modify the application UBBCONFIG file. The following listing shows the relevant sections of TMUSREVT parameters in the UBBCONFIG file. See Programming a BEA Tuxedo Application Using C for information about the syntax of the entries for the file.

TMUSREVT        SRVGRP=EVBGRP1  SRVID=40        GRACE=3600
                ENVFILE="/usr/tuxedo/bankapp/TMUSREVT.ENV"
                CLOPT="-e tmusrevt.out -o tmusrevt.out -A --
                -f /usr/tuxedo/bankapp/tmusrevt.dat"
                SEQUENCE=11

In the SERVERS section of the UBBCONFIG file, modify the SRVGRP and SRVID parameters as needed.

Filtering is a process that allows you to customize a subscription. If you require additional information about the BEA Tuxedo Event Broker, subscribing to events, or filtering, refer to Programming a BEA Tuxedo Application Using C.

In order to filter BEA Tuxedo FML or VIEW buffers, the field definition file must be available to BEA Tuxedo at run time.

Note: There are no special requirements for filtering STRING buffers.

BEA Tuxedo Buffer Types

Buffer Type	Description
FML	Attribute, value pair. Explicit.
VIEW	C structure. Very precise offsetting. Implicit.
STRING	Length and offset are different values. All readable.
CARRAY	Character array. BLOB of binary data. Only client and server know - JSL doesn't.
X_C_TYPE	Equivalent to VIEW.
X_COMMON	Equivalent to VIEW, but used for both COBOL and C.
X_OCTET	Equivalent to CARRAY.

FML Buffer Example

The listing FIELDTBLS Variable in the TMUSREVT.ENV File shows an example that uses the FML buffer. The FML field definition table is made available to BEA Tuxedo by setting the FIELDTBLS and FLDTBLDIR variables.

To filter a field found in the my.flds file:

1. Copy the my.flds file to /usr/me/bankapp directory.

2. Add my.flds to the FIELDTBLS variable in the TMUSREVT.ENV file as shown in the following listing:

   FIELDTBLS Variable in the TMUSREVT.ENV File

   ---

   FIELDTBLS=Usysflds,bank.flds,credit.flds,event.flds,my.flds
   FLDTBLDIR=/usr/tuxedo/me/T6.2/udataobj:/usr/me/bankapp

   ---

If ENVFILE="/usr/me/bankapp/TMUSREVT.ENV" is included in the definition of the UBBCONFIG file (shown in the listing UBBCONFIG File), the FIELDTBLS and FLDTBLDIR definitions are taken from the TMUSREVT.ENV file and not from your environment variable settings.

If you remove the ENVFILE="/usr/me/bankapp/TMUSREVT.ENV" definition, the FIELDTBLS and FLDTBLDIR definitions are taken from your environment variable settings. The FIELDTBLS and FLDTBLDIR definitions must be set to the appropriate value prior to booting the BEA Tuxedo system.

For additional information on event subscriptions and the BEA Jolt Class Library, refer to Using the Jolt Class Library.