Abstract: A computer-based system can comprise a patch management system to a load patch to a software program; and an installer to install components of the software program. The installer can interpret metadata to instruct the patch management system to automatically load the patch to the software program.

Abstract: Mechanisms and methods for loading a first version of a class into a second version runtime environment running a second version of the class. The runtime environment may be comprised of a Java Virtual Machine (JYM). These mechanisms and methods make it possible for applications to retrieve and convert legacy data into current versions of the runtime environment. The conversion of data may be done automatically and/or transparently to a user or calling process.

Abstract: The present invention provides users and processes with various features to control the memory usage by a cache and pool dynamically at runtime. The cache and pool can be initialized on demand to remove idle objects of classes from them without the server being restarted. When the cache and pool reach their maximum sizes, idle objects in them may be removed to make room for newly active objects using various strategies in batches, where the schedule (periodicity), size and processing time of each batch can be dynamically adjusted. When a newly created object is being added to a full cache where each object is enrolled in a transaction, one or more active objects may be passivated from the cache based on various criteria to make room for the new instance to be added. Various features of the cache and pool can be defined in a configuration file. This description is not intended to be a complete description of, or limit the scope of, the invention.

Abstract: The deployment and management of differing versions of software components can be simplified. External interfaces of the component can remain constant in behavior while the internal logic, and possibly internal storage, can change between versions. Such a version management system can be transparent to the client programs, since interfaces can remain backwards compatible between component versions. This transparency can greatly reduce the risks of unpredictable behavior or system failure. A system can maintain each version of a software component, and can use a dispatch technique to determine and instantiate the currently active version whenever a client requests a service from the software component during a session. Old instances, possibly of other versions, can be maintained as long as required on the server. Such systems can apply to stateful and stateless components, using synchronous or asynchronous communications, and which may communicate over networks and may use web services type protocols.

Abstract: Methods and systems are disclosed for managing software licenses in a distributed computer network. The number of software licenses allocated to software users can be determined on a node-by-node basis in realtime with little or no additional processing overhead incurred by the network. Upon of the occurrence of a node failure, software licenses are efficiently reallocated to new users. In one implementation, users are periodically counted at each network node and transmitted to a master node with a sanity scan result message. A license allocation condition is periodically evaluated using the sum of the counts. If the condition is met, a license lockout can be performed upon the expiration of a grace period.

Abstract: Singleton services can be automatically migrated from one application server to another in a cluster using a lease table and a migration master in case of a failure of the first application server.

Abstract: A system for high level dynamic hot code generation. A class file container object is first created. Methods and code are then added to the class file container object. Byte code is then generated from the populated class file container object. From the byte code, instances of the new class object can by generated. The program code generator is configured to generate code at a programming language construct level, thereby working at a level of program language statements, expressions, variables, and other constructs.

Abstract: Incremental application deployment allows any files under development for an application to be modified directly in place, such as on a server disk. Application and module configuration information can be collected from a user as they build their application. Each time a developer modifies the configuration of the application, changes can be immediately deployed to the server in the background, including appropriate modifications to the deployment descriptors. Once modifications are completed, the application can have already been deployed to the server.

Abstract: A common handler framework can allow handlers for multiple different types of web services programming models to be used in a single handler chain.

Abstract: First and second RFID edge servers can interact with RFID tag readers. The first and second RFID edge servers can arbitrate which of the first and second RFID edge servers will be active upon start up or edge server failure.

Abstract: A system and method for adaptive or dynamic garbage collection and memory management in computer systems and virtual machine environments, including Java virtual machines. Adaptive techniques attempt to constrain the system to consistently move towards the desired goal. In accordance with an embodiment, the system successively calculates a value of error from the “perfect state”, and adjusts parameters so that this value will be reduced on the next round of calculations. In accordance with an embodiment, certain parameters, such as nursery size, can be defined; and the variation in that parameter used to calculate its effect on a particular goal, for example, the pause-time minimization. An error value is then evaluated as the difference between the desired or “goal” pause-time, and the current pause-time. By varying the nursery size in an adaptive manner, the pause-time can then be minimized.

Abstract: In embodiments, the present invention provides mechanisms and methods for making a set of configuration changes to a set of servers comprised of an administration server and one or more managed servers. These mechanisms and methods can enable a number of changes to be made to the configuration at once, e.g., in a batch. In such transaction based processing, embodiments process changes in batches, which enables embodiments to avoid failures in configuration changes that result in the machines being in a non-recoverable or unknown configuration state.

Abstract: A method and system are provided for storing multiple instances of a CMP bean enrolled in a transaction by utilizing CMP batch operations to update multiple entries in a database table in one SQL statement only, thus avoiding multiple database roundtrips. The batch operation of CMP beans can be enabled by specifying certain options in a DTD file. As part of the batch operation feature, another option may be added to the DTD file as well, enabling the container to delay all database operations in a transaction until the commit time, automatically sort the database dependency between the operations, and send these operations to the database in a way to avoid any potential database constraint violations.

Abstract: A debugging proxy can be used to manage communication between a client and a debugger or debugging component. A debugging protocol can be used by the debugging proxy to facilitate communication management. A debugging protocol can provide for asynchronous messaging, and can allow for the communication of large grain messages. A debugging protocol can also implement a priority scheme that can be used to process messages between a client and a debugger based upon a priority assigned to each message.

Abstract: High availability is obtained for the deployment and undeployment of application views by placing a redundant JMX server on each server in a cluster of servers for an application integration system. Each redundant JMX server can manage deployment work for the cluster, and is capable of sending a JMX notification to every other server in the cluster relating to the deployment work, such as a deploy, undeploy, or processing notification. While an administration server can manage the other servers in the cluster, the redundant JMX servers are capable of managing deployment work for the cluster in the event of a failure of the administration server. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Abstract: A system and method for implementing a deployment plan for an application server environment. In one embodiment, the deployment plan is an XML document that can be associated with any application that is deployed to an application server environment. The deployment plan may incorporate all server (vendor) specific deployment information as required by JSR-88 as well as the application configuration attributes that need to be resolved for each application server environment to which that application is deployed. Additionally, it can contain references to custom module descriptors.

Abstract: A portal includes an original configuration and extension. The original configuration can include resources and a portal file identifying the resources. The extension modifies the original portal to form an extended portal without changing the original configuration.

Abstract: A system and a method for scheduling disk writes for use with an application server, transactional system, or other server. The disk scheduler and method is independent of the underlying operating system and the disk hardware. This allows it to be used without porting to the various settings in which application server might be deployed. In some embodiments, a high-performance, transactional filestore is also provided to minimize the latency of small, synchronous writes to disk. The implementation uses a log-structured file system combined with disk scheduling. By relaxing the requirement that log records be physically contiguous, every modification to the disk can be scheduled.

Abstract: A plug-in framework can be used in an integration system to extend business process management functionality. A plug-in manager, which can be part of an integration process engine, is used to support configuration, design, and run-time management of the plug-ins. A plug-in API is used to provide support for configuration, design, and run-time interactions between the process engine and a deployed plug-in. The plug-in API can consist of components such as session beans, run-time management classes, and packages. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Abstract: An entity is abstracted through implementation of a proxy object of the present invention, including functions for a software application to programmatically interact with the entity at runtime, as well as optional compile and design time implementation classes to support the development and customization of declarative proxy object definitions. In one embodiment, builder and resource interfaces are provided to assist in the creation of the implementation classes. In one embodiment, an extension interface is also provided to facilitate extension of an implementation of the proxy object. Software applications including programmatic usage of proxy object functions are compiled into object codes with proxy objects and meta data files. The compiled object codes are executed using a runtime engine, which includes proxy context objects to facilitate interaction on an instance basis, and an asynchronous event router to route asynchronous events for the entity.