HP NonStop CORBA 2.6 Glossary HP NonStop CORBA 2.6 Glossary Part number: 525939001. Published November 2003. Legal Notice Abstract This glossary defines terms used in NonStop CORBA documentation. Product Version: HP NonStop" CORBA® 2.
Copyright 2003 Hewlett-Packard Development Company L.P. Hewlett-Packard, HP, the HP invent logo, Compaq, the Compaq logo, Alpha, Atalla, CLX, Deskpro, Enform, Expand, Guardian, Himalaya, Inspect, Integrity, NonStop, OpenVMS, PayMaster, ProLiant, ServerNet, SignMaster, SNAX, Tandem, VAX, VMS, and WebSafe are trademarks of Hewlett-Packard Development Company L.P. in the U.S. and/or other countries.
subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause in DFARS 252.227-7013. Hewlett-Packard Development Company L.P. 10600 Ridgeview Court Cupertino, CA 95014 USA Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR 52.227-19(c)(1,2). Export of the information contained in this publication may require authorization from the U.S. Department of Commerce. HEWLETT-PACKARD DEVELOPMENT COMPANY L.P.
New and Changed Information New and Changed Information New terms have been added to the glossary as needed to provide definitions of terms used with new product features at NonStop CORBA 2.6. HP NonStop CORBA 2.
About This Glossary About This Glossary Manuals in the NonStop CORBA Set Terms defined in theNonStop CORBA 2.6 Glossary are taken from the entire NonStop CORBA documentation set. The individual manuals do not contain a glossary. Most of the terms defined in theNonStop CORBA 2.6 Glossary are specific to NonStop CORBA. However, some are generic CORBA or SSL terms. Manuals in the NonStop CORBA Set The NonStop CORBA 2.
Glossary Glossary ABCDEFGHIJKLMNOPQRSTUVWXYZ adapter activator A server-side object used by the ORB when a request is made for a child POA that does not exist. In such a case, the adapter activator creates the child POA. admin DB The database that stores the operational data used by the NSDAdminServer and NSDEnvironServer processes. The location of the database is given by the environment variable NSDOM_ADMIN_DB. AdminServer See NSDAdminServer.
(1) In IDL, the relationship between an IDL construct and the corresponding construct in a programming language. (2) In the Naming Service, the relationship between a name and an object. (3) In networking, binding is the establishment of a logical connection between communicating entities. Bootstrap Daemon (BSD) A protocol that provides operations for resolving an initial object reference and for listing the supported initial reference ids.
In object technology, an application component that makes requests of an object. More generally, an application component that makes requests of a server. client event handler An object defined by the NonStop CORBA event framework to support asynchronous communication between a NonStop CORBA client and a server that uses other technology. NonStop CORBA provides various types of client event-handler objects to support transport functions such as I/O completions and error handling.
concurrency Simultaneous operation. This term can apply to processes running in parallel, simultaneous transactions, or multiple clients using the same object (or other resource) at the same time. concurrency service An application service that manages simultaneous access to objects by multiple clients, primarily by supporting read-locking and write-locking requests.
control over application transactions. For example, the Current interface defines methods to mark the beginning of a transaction, to commit a transaction, to suspend a transaction, and to undo (roll back) a transaction. data access objects (DAOs) Objects that isolate process-blocking database access operations, which cannot take advantage of multithreading, from functions that can be implemented using multithreading.
A request style in which the client constructs a request at runtime, not needing to know the object interface (the calling sequences for requesting specific operations) at compile time. dynamic link library (DLL) A way of packaging application functions that lets the functions be loaded into a process at runtime rather than at compile time. Such functions can be unloaded when they are no longer required in the application while the rest of the application continues to run.
A development tool for debugging a NonStop CORBA application. While the esadmin tool can also be used to perform Event Service administrative and management tasks, the Console is the preferred tool for management in production environments. event (1) The link between the behavior that a component wants to react to and the code that tells the application how to respond. Java differentiates between the source of an event (the provider) and the handler for an event (what to do).
stream; the receiver performs transformations required to process the data in its local environment. factory object An object that creates other objects. An application might place factory objects into the Naming Service. You must implement a factory as a static method. fleshed-out script The results of editing skeletons, for example, nsdstart or default.db. Once configured, the fleshed-out script can be used to start, stop, or uninstall an existing NonStop CORBA installation.
See Interface Definition Language (IDL). IDL specification An OMG IDL specification consists of one or more type definitions, constant definitions, exception definitions, or module definitions. See also Interface Definition Language (IDL). IIOP Internet Inter-ORB Protocol. An object-oriented protocol that allows distributed programs written in different programming languages to communicate over the Internet. IIOP is a critical part of CORBA.
An object of a particular class. For example, an object that represents a particular person's bank account is an instance of the object class that generically defines a bank account. In Java programs, an instance of a class is created by using the new operator followed by the class name. interface (1) In IDL, an interface is a description of a set of possible operations that a client may request of an object.
Interoperable Object Reference. IP address The type of network address associated with the TCP/IP protocol. IPC Interprocess communication. NonStop systems use a message-based style of IPC. IR See Interface Repository (IR). jacket routine A procedure or function call that hides a protocol, translating it into another protocol that can more readily be handled by a calling program.
The series of steps through which an object is created and deleted, activated and deactivated. lifecycle service A standard application service for creating and deleting objects. See also Common Object Services (COS). link A logical connection between processes. In NonStop TS/MP, the logical connection between a requesting process and a server in a server pool. LINKMON process The NonStop TS/MP process that obtains links for all requesters in a CPU.
A NonStop CORBA process that assigns a client to a Comm Server and looks up the addresses of direct TCP servers having persistent policy. See also Comm Server. makefile A file that describes the dependencies among application modules that together constitute an executable program. The make utility (present in NonStop OSS and other implementations of UNIX or POSIX) interprets a makefile and initiates recompiling of changed and dependent modules.
A Java function. An operation defined for an object, implemented as a procedure or function in a programming language. The calling sequence for a method is called a method signature. A call to a method is called a method invocation. multi-tiered architecture See tiered application architecture. name binding Also known as name-object binding. An object consisting of a name and a binding. name component A structure containing a name-id string and a name-kind string.
DOM was replaced as a separate product by the NonStop CORBA product. NonStop JORB/MP (NonStop JORB) A component of NonStop CORBA that implements a Java programming environment. NonStop JORB was replaced as a separate product by the NonStop CORBA product. NonStop TCP/IP An HP product that implements the TCP/IP protocol. NonStop CORBA uses NonStop TCP/IP for communication with remote clients and servers.
The principal building block of object-oriented programs. An object is an instance of an implementation and an interface. Each object is a programming unit consisting of data and methods or functions. See also CORBA object. object adapter A CORBA component, residing in a server, which provides an interface between the Object Request Broker and the objects running in a server. CORBA defines a Portable Object Adapter (POA).
environment. The ORB provides services such as locating the target object and performing any transformations required for transmission of a request or receipt of a response across the network. See also marshaling. object services See Common Object Services. Object Transaction Service (OTS) (1) Former name for the OMG Transaction Service. See transaction service (2) A special client stub, provided as part of NonStop CORBA, that implements the OMG Transaction Service API. OBV See Object by Value.
overloading In C++, the redefinition of a language element to provide for different behavior depending on context. For example, the addition operator (+) could be overloaded to support concatenation of text strings. In Java, using one identifier to refer to multiple items in the same scope. You can overload methods but not variables or operators. overriding Providing a different implementation of a method in a subclass of the class that originally defined the method.
of PATHMON is called a PATHMON environment. Pathsend facility The set of procedures a requester uses to exchange requests and replies with a NonStop TS/MP server pool. (The actual procedure call to send a messages can have a different name, such as SERVERCLASS_SEND.) NonStop CORBA uses the Pathsend facility internally to support invocations of objects running in NonStop TS/MP server pools.
ORB services to transfer context information between clients and servers. IOR interceptors are used to establish tagged components in the profiles within an IOR. Portable Object Adapter (POA) The CORBA-specified object adapter that connects an object residing on a server with an ORB. The adapter provides a namespace within which the client and the server can connect and exchange information. porting Rewriting or modifying an existing component to run on a different system, language, or platform.
public key In a public-key (asymmetric) cryptosystem, the component of a key pair that is revealed. QIO An HP product that uses shared memory segments to optimize the performance of its client process. QIO stands for Queued Input/Output. reentrant code See thread-safe code.
kinds of security policies, including access control policy, audit policy, message protection policy, non-repudiation policy, etc. security service An application service that verifies user identity as a means of restricting certain operations to users who have proper identification (authentication). sequence An IDL data type that is essentially a one-dimensional array of specified maximum size and length. IDL sequences can be bounded or unbounded. They are mapped to a Java class that has a current length.
server selection The process of choosing a server process to handle a request. In NonStop CORBA stateless processing, each request can be handled by any server that can host the object interface. In stateful processing, a specific server is chosen to handle all of a series of requests. service A set of related functions available to applications on a system or network. See also Common Object Services. setting In general, the value of a parameter or variable.
default behavior for objects as specified by the root POA. stateless processing A style of application logic in which operations directed to the same object can result in requests to different servants, which in turn can reside in different processes in a server pool. A stateless object cannot maintain state information in memory between operations, because the state information would be available to only one process. A client reference can address any of a set of instances.
thread is suspended or destroyed. Threads differ from server pools in that threads require the same process to handle multiple requests, whereas server pools allow requests to be handled by different processes running in parallel. thread-blocking operation Operations that block only the calling thread, rather than the entire process, while they are in progress. Examples are nowait file I/O operations and operations directed to distributed objects.
Transaction Management Facility (TMF) The facility that manages transactions on NonStop systems. TMF collaborates with the transactional components of NonStop CORBA. transaction protection A feature that ensures consistency of databases and other stored data. Transaction Service A standard application service (one of the OMG Common Object Services) for ensuring the consistency of a database or other stored information when a request involves multiple updates to databases or state repositories.
