|
|
unadvertise command is issued or a MIB request removes the service.
| Note: | In this context, the term business program is defined as a set of one or more programs that work together. Similarly, in conversation the term application is often used loosely: it may refer to a standalone program or to a set of programs that work together to accomplish a particular business objective. |
BRIDGE allows the use of nonfailing network paths by listening and transferring data using multiple network address endpoints.
ball might include the attribute color. The idltojava compiler would generate a C++ or Java programming language method to get the color, and, unless the attribute is read-only, would generate a method to set the color. CORBA attributes correspond closely to JavaBeans properties.
CORBA object and object.
Object.
See also IDL interface, instance, Java, metadata interface, and object.
new keyword.
See also class, instance, Java, metadata interface, and object.
UBBCONFIG (ASCII version) or TUXCONFIG (binary version) configuration.
See also TUXCONFIG file and UBBCONFIG file.
tpsetctxt() is not called. The default context may differ from thread to thread. This term is often used interchangeably with application context.
See also application context.
DMCONFIG) File
try, catch, and throw keywords. There are two categories of exceptions: system and user-defined.
In C++, system exceptions inherit from CORBA::System_Exception and user-defined exceptions inherit from CORBA::User_Exception.
COSLifeCycle.FactoryFinder interface, as well as the BEA Tobj.FactoryFinder interface.
See also factory, local factory, object, client application, and server application.
TMFFNAME service when it is started as a Master NameManager. The file contains information used by NameManagers to control the import and the export of object references for factory objects with other domains.
See also domain, factory, and object reference.
BRIDGE process always tries to use the highest-priority circuit defined for the node; when traffic is flowing on a lower-priority circuit, whether due to circuit failure or just non-availability, the BRIDGE periodically checks higher-priority circuits to find one that is usable. When a higher priority circuit becomes available again, the data flow is returned to it. This mechanism is called failback.
.java files.
See also OMG IDL.
NamingContext object returned by a call to the method orb.resolve_initial_references("NameService"). It is an object reference to the CosNaming Service registered with the ORB. The initial naming context can be used to create other NamingContext objects.
See also naming context.
CORBA::ORB::object_to_string, results in the CORBA::MARSHAL system exception being raised.
BRIDGE processes impossible. For example, when a high-priority network fails, its load can be switched to an alternate network with a lower priority. When the higher-priority network returns to service, the network load returns to it.
buildobjclient command. The BEA Tuxedo software does not support Java native joint client/server applications.
joint client/server application.
Tobj::TransactionCurrent is an example of an object interface provided by the BEA Tuxedo software.
CORBA object, OMG IDL, and operation.
buildobjserver command for servers using the TP Framework. Note that joint client/server applications must provide their own main procedure and must use the -P switch on the buildobjclient command.
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.
buildobjclient command or with the Java client application commands.
CORBA ORB, client application, and WebLogic Express.
main() in building a server process. The BEA Tuxedo system’s main() provides server initialization and termination, and receives incoming requests and dispatches them to service routines. All of this processing is transparent to applications.
.jar) file.
JAR files (.jar).
_tie is appended to the end of the class name.
CosTransactions module. In addition, the TransactionCurrent object supports APIs to open and close the resource manager.
TransactionCurrent defines the methods that allow a client of the CORBAservices Object Transaction Service (OTS) to explicitly manage the association between threads and transactions. This object also defines methods that simplify the use of the OTS for most applications.
See also application programming interface (API), CORBAservices Object Transaction Service (OTS), Credentials object, and resource manager (RM).
TUXCONFIG file, is generated from the UBBCONFIG file.
See also application, client, server, and TUXCONFIG file.
(No terms starting with the letter "Y")
(No terms starting with the letter "Z")
|