Bea Systems, Inc.

Salesforce Com, Inc.

Oracle International Corporation

Rob Woollen

Seth John White

Dean Bernard Jacobs

Vinod Mehra

Peter Wung Lee

Adam Messinger

Mark Griffith

Matthew Shinn

Peter Laird

Michael Jasnowski

Ruslan Bilorusets

Systems, apparatus, and methods for implementing enterprise level social and business information networking are provided. Users can receive relevant information about a database system and its users at an appropriate time. Users can then use this relevant information to reduce errors and limit redundant efforts. For example, an update of a record in the database can be identified, and a story created automatically about the update and sent to the users that are following the record. Which updates have stories created and which stories are to be sent to which users can be configured. Other events besides updating of records can also be tracked. For example, actions of a user that result in an event can be tracked, where such tracking can also be configurable. Subscriptions to follow an object can be automatic, and access checks can be used to ensure that unauthorized users do not see certain data.

Customizing enterprise level business information networking

Security in enterprise level business information networking

Implementing enterprise level business information networking

Enterprise level business information networking for changes in a database

A system for determining when an EJB compiler needs to be executed, comprising: a server, including an EJB or plurality of EJBs and an EJB compiler operating thereon that determines a first snapshot of the EJB at a particular moment in time or for a particular server version, and a second snapshot of said EJB at a later moment in time or a subsequent server version, and compares the first and second snapshots to determine whether the EJB should be recompiled.

System and method for determining when an EJB compiler needs to be executed

In accordance with one embodiment of the present invention applications are configured with custom modules. A deployment descriptor of an application includes a definition for a new container type and modules of the new container type. A deployment system reads the deployment descriptor and implements the modules of the new container type. The new containers are then available to assist in the deployment of the application.

System and method for creating and deploying applications with new container types

A customer portal application can reference a module. The files of the module can be combined with the files of the customer portal application wherein the files of the customer portal application take precedence.

Portal federated applications and portal federated web applications

Resources provided by web applications can be extended through the implementation of library modules and extensions. Library modules stored outside a web application can provide resources in a web application environment as if they were part of the web application itself. Additionally, web applications can be configured with application extensions that are web applications stored as archives within containing web applications.

System and method for web application extensibility

Federated applications are configured to use both modules created for the applications as well as library modules which perform commonly used functions. The library modules are stored separately for deployment when utilized by applications. A deployment descriptor is configured with descriptions of internal modules and references to library modules. A deployment tool reads the deployment descriptor, extracts the library modules according to the information stored in the deployment descriptor, and loads the modules specific to the application.

System and method for deploying applications with library modules

Scoped applications are configured as self-contained units that do not require external configuration of messaging or database access settings. The applications can be deployed to multiple and disparate environments and utilized without the need for additional server configuration by an administrator. The applications include metadata indicating information specific to a particular server that can be provided at deployment.

Scoped applications

There are provided mechanisms and methods for enabling the deployment of applications into new execution environments by adding extensions to base deployment capability for each of the new containers. These mechanisms and methods can enable embodiments to instantiate modules that augment deployment and/or execution environments for applications being deployed. The ability of embodiments to provide augmented deployment and/or execution environments can enable server embodiments to become more flexible environments from the point of view of developers seeking to implement applications on the server.

System and method for application container architecture

A development-oriented directory structure that can be used with an application server, and which solves a number of the problems associated with traditional Enterprise Archive (EAR) files. The directory structure comprises a source folder that stores source files for use with or as part of a software application; and an output folder that stores compiled files for use with or as part of the software application. The source folder and the output folder output folder form a split directory which is then used in deploying the software application.

System and method for using a split-directory structure for software development

Concurrency can be maintained in cluster caching when processing an update request on network server that is storing a local copy of a data item. The request can be processed using the local copy of the data item. A predicated update request can be sent to a network database storing the data item, wherein the database can commit the update if the local copy is current with the data item. If the local copy is not current, the network server can request a new copy, process the request using the current copy, and try another predicated request. The process can continue until the update is committed to the database or aborted. Once committed, any other servers in the cluster can be notified that the data item has been updated. Those other servers can drop any local copy of the data item and can request an updated copy of the data item.

Cluster caching with concurrency checking

System and method for custom module creation and deployment

Transactions are granted concurrent access to a data item through the use of an optimistic concurrency algorithm. Each transaction gets its own instance of the data item, such as in a cache or in an entity bean, such that it is not necessary to lock the data. The instances can come from the data or from other instances. When a transaction updates the data item, the optimistic concurrency algorithm ensures that the other instances are notified that the data item has been changed and that it is necessary to read a new instance, from the database or from an update instance.

Growing community of inventors

San Francisco, CA, United States of America

Rob Woollen