Abstract: A distributed object application builder apparatus filters an object definition to determine the information needed (plugs) and provided (sockets) by an object. Each part (a run-time instance of an object) in the builder has plugs and sockets that are interconnected to other parts to define a distributed object application. At run time, actual instances of objects are substituted for the parts. A method of determining the plugs of an identified part begins by retrieving the interface (object definition) that corresponds to the part. Once retrieved, the plugs of the part are identified by determining the object-valued attributes of the retrieved interface, determining the operations from the retrieved interface that require one object-valued argument, and retrieving the factory argument list from the factory method for the object. These attributes and arguments constitute the plugs of the part. Sockets of a part are determined similarly.

Abstract: A distributed object application builder apparatus filters an object definition to determine both information needed (plugs) and provided (sockets) by an object. Each part (a run-time instance of an object) in the builder has plugs and sockets interconnected to other parts to define a distributed object application program. At run time, actual instances of objects are substituted for the parts. A method of determining the plugs of an identified part retrieves the interface (object definition) corresponding to the part. Once retrieved, the plugs of the part are identified by determining the object-valued attributes of the retrieved interface, by determining the operations from the retrieved interface that require one object-valued argument, and by retrieving the factory argument list from the factory method for the object. These attributes and arguments constitute the plugs of the part. Sockets of a part are determined similarly.

Abstract: A technique for automating the assembly of networked, language independent objects into a network application for use in a distributed object computing system uses program templates and a symbol table. A schematic representation of the network application is formed within a visual application builder. The schematic representation defines connections among representations of previously defined distributed objects. These connections are formed among parts, plugs and sockets that are associated with representations of distributed objects termed components. The schematic representation of the network application is loaded into a symbol table and portions of the schematic representation are stored as a number of entries in the symbol table. These entries include identifier-value pairs; that is, identifiers are mapped to values. The program source files to be generated are determined and the program templates for use in generating the program source file are also determined.

Abstract: A computer system in a distributed object programming environment includes a number of host computers providing services to clients on a network through internally stored servers. Various types of configuration information for each server are available to clients through persistent server administrators, which are objects containing such information about individual servers. A server administrator can store such information as startup execution definitions, saved program definition, object interfaces and implementations, reaping, tracing, and logging configuration data. Being persistent and external to the server, the server administrator can manipulate and determine its information about a server in response to client requests without starting up the server, thereby facilitating system administration.