Abstract: A system and process for enhancing procedural software using object oriented classes. Implementation classes are constructed that provide a defined object oriented interface to applications and are able to invoke the procedural software using defined procedural application program interfaces (APIs). New function is added to the software by adding classes that interface to the implementation classes or directly to the procedural API. The new function builds upon the procedural software without accessing the procedural software source code or modifying that source code.

Abstract: A method of discovering native or non-native authentication server domains in a computer network. The various domains are "discovered" by issuing requests from the client to one or more of the servers in the network. Each response is then characterized as being from a native or non-native server, and a list of each such server type is then compiled at the client. If desired, the administrator may then apply a discovery "policy" to tailor the way in which a user may access and interact with the discovered information.

Abstract: A system, method and article of manufacture for automatically inserting transactional recoverability object service in binary classes in an information handling system employing object oriented technology, includes the steps of recognizing a constraint indicating that an object is not recoverable and generating a recoverable version of the object. One alternative for generating a recoverable version of the object includes the step of saving a first state of the object in a stream before execution of any method which might change the state of the object. Another alternative for the generating step includes the steps of creating a persistence synchronous class object, registering the persistence synchronous class object, and executing the persistence synchronous class object.

Abstract: A system and method for effectively synchronizing data in an object oriented distributed transaction processing system employing a multilevel data store. Each object that maintains first-level volatile data registers as a synchronization object if unsynchronized changes to that data exist. A register object at each node tracks synchronized objects registered for that node. Each registered synchronization object, in turn, registers with its superior node when registered synchronization objects are present. A hierarchy of registered synchronization objects and synchronization objects is thereby created. The transaction termination process transmits a pre-prepare message to the registered synchronization hierarchy providing each synchronization object an opportunity to flush its data to the second-level persistent data store. The hierarchical structure of registered objects ensures that the minimum number of messages are transmitted over the network.

Abstract: A system, method and article of manufacture for automatically inserting concurrency object services into binary classes in an information handling system employing object oriented technology, includes the steps of recognizing a constraint indicating that an object does not support concurrency and generating a concurrent version of the object. One alternative for generating a version of an object supporting concurrency is automatic transactional locking. The approach includes the steps of inheriting from the Lockable class which adds state to a class to allow object-level locking, inheriting from the Serialised metaclass which adds before and after methods to all methods of the non-concurrent version, and the object must be a RecoverableObject. Another alternative for generating a version of an object supporting concurrency is automatic per method locking.