Sun Microsystems, Inc.

Software Ag, Inc.

Webmethods, Inc.

Rafael Bracho

Arthur A Van Hoff

Alan Michael Snyder

Mark W Hapner

David M Brownell

Maurice Balick

Steven Jankowski

Rod J McChesney

Tilman Sporkert

Steve M Jankowski

A scalable enterprise computer system having the capability to provide transaction security as well as providing subscription filtering is described. As a method of transacting an event in the enterprise computer system a connection with an information broker by the publishe established after which it is determined if the event registered with the information broker. Next, a subscription corresponding to the registered event by a subscriber is accepted by the information broker, after which a platform neutral event is created that is then populated with event content which is then published to and received by the information broker.

Enterprise computer system

A variety of methods and apparatus for managing deactivation and deletion of objects and server processes are taught. According to some embodiments of the present invention, a thread of execution termed the reaper thread systematically cycles through a computer process deactivating and/or deleting objects based upon a variety of criteria. One suitable criterion for object deactivation is based upon the amount of time lapsed since a client has requested services of the object. According to the timeout criterion, the reaper thread determines the period of time since the last client requested services from the object, compares this to a timeout value which may be defined by any suitable entity, and proceeds with deactivation and/or deletion accordingly. Object deletion may have a separate criterion or be specifically requested by a client. A deletion flag may be set to indicate that object deletion is requested. When an object has deactivated, the reaper thread further determines if the deletion flag for this object is set, and, if so, further proceeds to perform an object deletion operation. In some embodiments, the reaper thread is further responsible to shutdown the server process under which the reaper thread is executing. As is well known to those skilled in the art of object oriented programming, a thread of execution is essentially a sequential flow of the point of execution through a computer process. One suitable criterion for server process shutdown would be related to the server process activity.

Methods and apparatus for managing objects and processes in a distributed object operating environment

Methods and apparatus for managing objects and processes in a

A method and apparatus for publishing and receiving events to a network. A plurality of 'publisher' entities publish information and a plurality of 'subscriber' entities request and use the information. Publishers and subscribers are connected to each other through a network. The network is a 'store and forward' network whose routing is 'content-based.' The basic quanta of information is called an 'event.' Publishers publish events and subscribers subscribe to events that match criteria defined by the subscriber. Publication and subscription are performed asynchronously. Publishers and subscribers do not have direct knowledge of each other. The system receives a published event from a publisher and routes the event to all appropriate subscribers. Each subscriber is guaranteed to receive all events published on the system if, and only if, they match the subscription criteria specified by the subscriber. A legacy data base can be added to the network by way of a data base connector, which can be a publisher, a subscriber, or both.

Database network connectivity product

A method and apparatus for publishing and receiving events to and from a network. A plurality of 'publisher' entities publish information and a plurality of 'subscriber' entities request and use the information. Publishers and subscribers are connected to each other through a network. The network is a 'store and forward' network whose routing is 'content-based.' The basic quanta of information is called an 'event.' Publishers publish events and subscribers subscribe to events that match criteria defined by the subscriber. Publication and subscription are performed asynchronously. Publishers and subscribers do not have direct knowledge of each other. The system receives a published event from a publisher and routes the event to all appropriate subscribers. Each subscriber is guaranteed to receive all events published on the system if, and only if, they match the subscription criteria specified by the subscriber. A legacy data base can be added to the network by way of a data base connector, which can be a publisher, a subscriber, or both.

Middleware for enterprise information distribution

Growing community of inventors

Cupertino, CA, United States of America

Rafael Bracho