
CORBAClnt
Page 49
Working with CORBA Server Objects
PeriRDB version 1.2 supports integration with CORBA (Common Object Request
Broker Architecture). The CORBA Block in PeriProducer accesses information in a
CORBA server through CORBAClnt. The CORBAClnt daemon connects to a
specified VMST, after which it connects and binds to an Object Request Broker
(ORB). After these initial operations, CORBAClnt waits until it receives a CORBA
request from an application CORBA block.
Installing PeriRDB installs SQLClnt.
For more information, see the Installing MPS Software on a Solaris Platform or
Installing MPS Software on an NT Platform book.
CORBAClnt is currently not supported on Windows NT.
CORBAClnt
The information that an application developer enters in the CORBA block is used to
build and send a request from the application to corbaclnt.
The corbaclnt uses the CORBA Dynamic Invocation Interface (DII) to invoke any
method on any CORBA object using knowledge obtained at run-time from either a
CORBA Interface Repository (IR) server or a CORBA "stringified" Internet Object
Reference (IOR). The CORBA block in conjunction with corbaclnt is a dynamic, run-
time invocation of CORBA services, not a static, precompiled invocation. The DII
approach allows PeriPro applications to invoke operations on any CORBA registered
object without having to link the client-side stubs that may have been generated for a
particular object by an Object Request Broker (ORB) vendor's Interface Definition
Language (IDL) compiler.
The Interface Repository mode functionality has not been implemented for this
release.
Application requests are handled by corbaclnt on a first-in, first-out basis, and all
application requests are managed in a queue. If increased parallelism is necessary,
multiple corbaclnt processes can be started. The number of corbaclnt
processes necessary is determined by the number of applications executing and the
rate at which CORBA requests are made.
Comentarios a estos manuales