[Top] [Prev]



Glossary

Applicable BEA TUXEDO Conversational Calls
The BEA TUXEDO calls tprecv, tpsend, TPRECV, and TPSEND that may return the TPEV_SVCERR error event due to a service time-out. (In the future, other BEA TUXEDO calls may be applicable, but these are specific to the service time-out.)
Applicable BEA TUXEDO Request/Response Calls
The BEA TUXEDO calls tpcall, tpforward, tpgetrply, TPCALL, TPFORWAR, and TPGETRPLY that may return the TPESVCERR error code due to a service time-out. (In the future, other BEA TUXEDO calls may be applicable, but these are specific to the service time-out.)
BRIDGE
The process that connects BEA TUXEDO networks. One BRIDGE process serves a domain, one message queue per BRIDGE. In Titan 6.3 and earlier releases, one network address exists per BRIDGE (see NADDR). Only one virtual circuit is permitted to a particular pre v6.4 BRIDGE.
Circuit
See Virtual Circuit.
Conversations and Conversational Messages
BEA TUXEDO conversational messages are to be delivered in the order they are sent. When parallel data circuits are transmitting these messages, care must be taken that the messages are delivered to the remote queue in order.
When a lower priority circuit gracefully terminates in favor of a reestablished higher priority circuit, there are conversational race conditions between these circuits. (See Failover/Failback). The conversation aborts rather than sends data out of order.
DEFAULTNET
When 6.4 NADDR BRIDGE network addresses are specified, they are associated with a NETGROUP. By default there is still the virtual network, DEFAULTNET. All pre-6.4 NADDRS have an implicit NETGROUP value of DEFAULTNET.
DLL
Dynamic Link Library
Parallel Data Circuits
BEA TUXEDO v6.4 systems may be configured with multiple addresses to be used simultaneously. When you configure parallel data circuits, network traffic is scheduled over the circuit with the largest network group number (NETGRPNO). When this circuit is busy, the traffic is scheduled automatically over the circuit with the next lower network group number. When all circuits are busy, data is queued until a circuit is available. Alternate scheduling algorithms may be introduced in future releases.
Failover and Failback
Network failover occurs when a redundant unit seamlessly takes over the network load for the primary unit. Some OS and hardware bundles transparently detect a problem on one network card and have a spare automatically replace it. When done quickly enough, application level TCP virtual circuits have no indication a fault happened - this is failover.
Data flows over the highest available priority circuit. If network groups have the same priority, data travels over all networks simultaneously. If all circuits at the current priority fail, then data is sent over the next lower priority circuit. This is called failover.When a higher priority circuit becomes available, data flows over this higher priority circuit. This is called failback. All unavailable higher priority circuits are retried periodically. After connections to all network addresses have been tried and failed, connections are retried again the next time data needs to be sent between machines.
Generic BEA TUXEDO Errors
TPESYSTEM, TPEOS, TPESVCERR
GPNET
GPNET is the new networking library that will eventually replace libnet.
IDE
Integrated Development Environment
MFC
Microsoft Foundation Class library
msdev
The application name for Microsoft Visual C++.
NADDR
NADDR is the BRIDGE address in the Bulletin Board. 6.3 (Titan) and previous releases that permit only singular addresses. Release 6.4 and beyond have multiple network (NADDR) addresses.
NETGROUP
See Chapter 2, "Improved BRIDGE Processing" and the following sections: "Updates to the UBBCONFIG(5) Manual Page" and "Updates to the TM_MIB(5) Manual Page."
Parallel Data Addresses and Parallel Data Circuits
Version 6.4 systems may be configured with multiple NETGROUP addresses. Those at the same highest (NETPRIO) priority (in the highest priority band) flow data simultaneously. These are Parallel Data Circuits.
Priority Network Characteristics
Assigning priorities appropriately for each netgroup enables you to maximize the capability of network BRIDGES. When determining your netgroup priorities, keep in mind that data flows over the highest available priority circuit. If network groups have the same priority, data travels over all networks simultaneously.
If all circuits at the current priority fail, then data is sent over the next lower priority circuit. This is called failover. When a higher priority circuit becomes available, data flows over this higher priority circuit. This is called failback. All unavailable higher priority circuits are retried periodically.
After connections to all network addresses have been tried and failed, connections are retried again the next time data needs to be sent between machines.
Service Time-Out
A configurable period of time when a single invocation of a service is permitted to run before BEA TUXEDO terminates the server process in which the service is executing.
SVCTIMEOUT
The configurable parameter in the BEA TUXEDO UBBCONFIG file for setting the service time-out.
TA_SVCTIMEOUT
The dynamically configurable attribute of the T_SERVER and T_SERVICE classes in the MIB for setting the service time-out. In this guide, SVCTIMEOUT represents both the UBBCONFIG parameter as well as this MIB attribute.
TPEDSVCTIMEOUT
The symbolic name for the error detail related to a service time-out.
TPESVCERR
The error code currently returned by the applicable BEA TUXEDO request/response calls when a service time-out occurs, or when a server processing a request exits abnormally. It is also returned when tpreturn, tpforward, TPRETURN, or TPFORWARD detect improper parameters, outstanding replies, open subordinate connections, or the caller's transaction is marked abort-only.
TPEV_SVCERR
The conversational event currently returned by the applicable BEA TUXEDO conversational calls when a service time-out occurs or when a server processing a request exits abnormally. It is also returned when tpreturn, tpforward, TPRETURN, or TPFORWARD detect improper parameters, outstanding replies, open subordinate connections, or the caller's transaction is marked abort-only.
Virtual Circuits
Virtual circuits are established network connections between two machines. The term usually focuses on multiple established network paths connecting one pair of BEA TUXEDO BRIDGES. Titan v6.3 BRIDGES use one and only one circuit for BEA TUXEDO messages between machines in the same domain. BEA TUXEDO v6.4 may establish only one circuit to a pre v6.4 system.
WAN
Wide Area Network. A WAN address may be the least common denominator connecting all networks in the organization. It may also be the slowest link between machines. Because only one address could be specified in v6.3, it had to be the WAN because any node may have to call any other. It could not always be the highest speed LAN (local area network) because it may be inaccessible from the whole organization.



[Top] [Prev]