Abstract: Embodiments of the invention store log event records in a secure database log by encrypting information in a query, or in query results, that would otherwise be subject to unwanted disclosure (either from within or without a given organization). For example, an organization (e.g., a research institution) may allow a database administrator to review log event records to diagnose and correct system performance issues, without being forced to trust the administrator with sensitive medical data (e.g., medical records related to participants in a research study). Thus, the security of sensitive information may be maintained, while at the same time, the database administrator may still access the information needed to maintain a working system.

Abstract: Embodiments of the invention store log event records in a secure database log by encrypting information in a query, or in query results, that would otherwise be subject to unwanted disclosure (either from within or without a given organization). For example, an organization (e.g., a research institution) may allow a database administrator to review log event records to diagnose and correct system performance issues, without being forced to trust the administrator with sensitive medical data (e.g., medical records related to participants in a research study). Thus, the security of sensitive information may be maintained, while at the same time, the database administrator may still access the information needed to maintain a working system.

Abstract: A method, system and program product for providing domain level business object keys in Enterprise JavaBeans (EJB) applications. An instance of an EntityBean object is provided with both a primary key and a domain key class. The primary key class is associated with a home selected for the EntityBean object, and the domain key class is associated with a particular business application within which the EntityBean object is being utilized. The EntityBean and associated home is utilized across different business applications, while ensuring uniqueness across the different applications.

Abstract: The present invention utilizes a hardware Window Storage Protection Controller (WSPC) and an Object Encapsulation Enforcement Manager (OEEM) to limit access to object data to only those methods which are encapsulated by the object All of the objects of the computer system which require protection are stored in protected storage by a base storage protection mechanism so that only the mechanisms of the present invention can deny or permit access to the data encapsulated by the objects.

Abstract: Disclosed is a method, system and program product for providing domain level business object keys in Enterprise JavaBeans (EJB) applications. An instance of an EntityBean object is provided with both a primary key and a domain key class. The primary key class is associated with a home selected for the EntityBean object, and the domain key class is associated with a particular business application within which the EntityBean object is being utilized. The EntityBean and associated home is thus able to be utilized across different business applications while ensuring uniqueness across said different applications.

Abstract: A method and computer program product are provided for implementing pushdown queries in a distributed object management system. A pushdown query to a system datastore is performed for a query type returning a single object. Responsive to the system datastore finding the match, checking whether the match refers to an object changed in the current transaction is performed. Responsive to the match not referring to a changed object, the object is returned. Responsive to the match referring to the changed object and the changed object matching the pushdown query, the changed object is returned. Responsive to the system datastore not finding the match, a list of changed objects in a current transaction is obtained. Each of the changed objects are in a current transactional state. An object query is performed on the changed objects in the list of changed objects. A multiple object pushdown query to the system datastore is performed for a query type returning multiple objects.

Abstract: The method maintenance mechanism of the present invention is comprised of two submechanisms, a method update mechanism and a method call manager. The method update mechanism is used to make changes to existing methods. The method call manger manages calls to methods in a way that allows active programs to continue to use old versions of methods while at the same time providing access to new method versions when programs are reactivated or activated for the first time.

Abstract: In an object-oriented or object-based computer system, object methods are routed to users (e.g., client programs) after automatically performing supervisory functions. Examples of suitable supervisory functions include authorization checking and locking. One suitable way to automatically perform the supervisory functions is to provide a call method instruction in the operating system that automatically performs these supervisory functions when a user invokes the object method using the instruction. In this manner, the operating system can assure that the user calling the object method has sufficient authority and lock to access the object method. In addition, the method routing mechanism has the ability to forego authorization checking and locking for objects that are unprotected, and may perform abbreviated authorization checking and locking if the operating system determines from local knowledge that a user is currently authorized to and locked on the called object.

Abstract: This invention relates in general to object-oriented encapsulated enforcement mechanisms. In particular, a hardware independent object encapsulation enforcement mechanism is disclosed herein. The object encapsulation enforcement mechanism of the present invention uses encryption technology to ensure that data controlled by an object is accessed solely through use of the object's method programs. When an object is instantiated, the virtual address used to refer to the object is encrypted before it is returned to the instantiating application program. When access to a previously instantiated object is requested, the object encapsulation enforcement mechanism decrypts the presented object address and passes the address to the identified method program, thereby ensuring that only object method programs have access to data controlled by the object.

Abstract: The present invention utilizes a hardware Window Storage Protection Controller (WSPC) and an Object Encapsulation Enforcement Manager (OEEM) to limit access to object data to only those methods which are encapsulated by the object. All of the objects of the computer system which require protection are stored in protected storage by a base storage protection mechanism so that only the mechanisms of the present invention can deny or permit access to the data encapsulated by the objects.