Abstract: A computer system has a runtime environment (e.g. Java) and a deployment system (e.g. a Spring framework layer) arranged to deploy an application into the runtime environment. The application comprises bundles (e.g. OSGi bundles or JSR modules) each with manifest metadata defining dependencies for the respective bundle. A deployment management unit refers to one or more personality specific deployers to determine which of the bundles have a specific personality from a predetermined set of personality types. The personality specific deployers transform the respective personality-specific bundles by inserting one or more additional dependencies into the metadata of the bundle according to their personality type. The deployment management unit applies one or more operations to all of the plurality of bundles, including installing each of the bundles ready for deployment and deploys those bundles not having a specific personality type.

Abstract: A computer system and a method are disclosed for use in automatically deploying an application program to execute with one or more library resources. The computer system includes a deployment unit which deploys the application program into a runtime execution environment. When a predetermined trigger condition is detected, the deployment unit clones a first library resource to create a clone, transforms the application to depend upon the clone and resolves the dependencies of the application using the clone. In one embodiment, the trigger condition relates to a pinning situation, whereby a library upon which the application program depends cannot be wired to the application program to resolve the dependency. Here, the clone now satisfies that dependency. In another embodiment, the trigger condition is a mandatory cloning property that requires the library to be cloned. The mandatory cloning property may also be user-specified through a user interface.

Abstract: A computer system and a method are disclosed for use in automatically deploying an application program to execute with one or more library resources. The computer system includes a deployment unit which deploys the application program into a runtime execution environment. When a predetermined trigger condition is detected, the deployment unit clones a first library resource to create a clone, transforms the application to depend upon the clone and resolves the dependencies of the application using the clone. In one embodiment, the trigger condition relates to a pinning situation, whereby a library upon which the application program depends cannot be wired to the application program to resolve the dependency. Here, the clone now satisfies that dependency. In another embodiment, the trigger condition is a mandatory cloning property that requires the library to be cloned. The mandatory cloning property may also be user-specified through a user interface.

Abstract: Provided is a method for providing Java modularity class loader protection by controlling the visibility of WebSphere, service provider, library and utility code interfaces. Interface access authorization is checked once, during module and class loading to effectively protect vulnerable programming interfaces, eliminating permission checking during execution. Code in a WebSphere Application server (WAS) computing environment is categorized into a finite number of sets in which one permission type is assigned to each set and the code in each set runs at the same privilege zone. Each set exposes programming interfaces to provide functional service and code in a particular set can only access code in the same or a lower security zone set. Also provided is a technique for explicitly providing to specific modules in lower security zones access to modules or designated interfaces of modules in higher security zones.

Abstract: A method and system for controlling an operation of a Java Virtual Machine (JVM) component on a per-classloader basis. A manifest of a bundle in an Open Services Gateway Initiative (OSGi®) compliant framework is parsed and metadata in the manifest is identified. The metadata is stored in a Java® classloader uniquely associated with the bundle. An upcoming performance of an operation which can be affected by a value of the stored metadata is identified by the JVM component. A value of the stored metadata is read from the classloader. The operation of the JVM component is controlled based on the value of the stored metadata.

Abstract: A computer system has a runtime environment (e.g. Java) and a deployment unit (e.g. in a Spring framework layer) arranged to deploy the application into the runtime environment. The application comprises bundles (e.g. OSGi bundles) with manifest metadata having export statements defining exported packages. The deployment unit comprises a receiver unit to receive the bundles, an extractor unit to examine the metadata and extract the export statements, a converter unit to convert each of the export statements into a corresponding import statement, and a creator unit to add a synthetic bundle having the import statements inserted in its metadata. The deployment unit sets a thread context class loader to delegate class loading to a class loader of the synthetic bundle. Thus, at runtime, classes of the application are only loaded when they are explicitly exported packages as defined by the synthetic bundle.

Abstract: A system and associated method for utilizing file names for diagnostic data files generated by a runtime environment. The method employs a file counter base that defines a predefined maximum number of files permitted in a file system, a generation number that indicates an instance of the runtime environment, and a file counter that comprises a file name. The file counter circulates by a cycle equal to the file counter base such that the file system uses only a limited disk space. The method determines the generation number per instance of the runtime environment by examining file counters of existing files in the file system. The generation number initializes the file counter for creating file names in the instance of the runtime environment. The method guarantees a longest life span of a diagnostic data file in a file system that has a limited number of files.

Abstract: A method and system for controlling an operation of a JVM® component on a per-classloader basis. A manifest of a bundle in an OSGi® compliant framework is parsed and metadata in the manifest is identified. The metadata is stored in a Java® classloader uniquely associated with the bundle. An upcoming performance of an operation which can be affected by a value of the stored metadata is identified by the JVM® component. A value of the stored metadata is read from the classloader. The operation of the JVM® component is controlled based on the value of the stored metadata.

Abstract: A computer system and a method are disclosed for use in automatically deploying an application program to execute with one or more library resources. The computer system includes a deployment unit which deploys the application program into a runtime execution environment. When a predetermined trigger condition is detected, the deployment unit clones a first library resource to create a clone, transforms the application to depend upon the clone and resolves the dependencies of the application using the clone. In one embodiment, the trigger condition relates to a pinning situation, whereby a library upon which the application program depends cannot be wired to the application program to resolve the dependency. Here, the clone now satisfies that dependency. In another embodiment, the trigger condition is a mandatory cloning property that requires the library to be cloned. The mandatory cloning property may also be user-specified through a user interface.

Abstract: A computer system has a runtime environment (e.g. Java) and a deployment unit (e.g. in a Spring framework layer) arranged to deploy the application into the runtime environment. The application comprises bundles (e.g. OSGi bundles) with manifest metadata having export statements defining exported packages. The deployment unit comprises a receiver unit to receive the bundles, an extractor unit to examine the metadata and extract the export statements, a converter unit to convert each of the export statements into a corresponding import statement, and a creator unit to add a synthetic bundle having the import statements inserted in its metadata. The deployment unit sets a thread context class loader to delegate class loading to a class loader of the synthetic bundle. Thus, at runtime, classes of the application are only loaded when they are explicitly exported packages as defined by the synthetic bundle.

Abstract: A computer system has a runtime environment (e.g. Java) and a deployment system (e.g. a Spring framework layer) arranged to deploy an application into the runtime environment. The application comprises bundles (e.g. OSGi bundles or JSR modules) each with manifest metadata defining dependencies for the respective bundle. A deployment management unit refers to one or more personality specific deployers to determine which of the bundles have a specific personality from a predetermined set of personality types. The personality specific deployers transform the respective personality-specific bundles by inserting one or more additional dependencies into the metadata of the bundle according to their personality type. The deployment management unit applies one or more operations to all of the plurality of bundles, including installing each of the bundles ready for deployment and deploys those bundles not having a specific personality type.

Abstract: A system and associated method for utilizing file names for diagnostic data files generated by a runtime environment. The method employs a file counter base that defines a predefined maximum number of files permitted in a file system, a generation number that indicates an instance of the runtime environment, and a file counter that comprises a file name. The file counter circulates by a cycle equal to the file counter base such that the file system uses only a limited disk space. The method determines the generation number per instance of the runtime environment by examining file counters of existing files in the file system. The generation number initializes the file counter for creating file names in the instance of the runtime environment. The method guarantees a longest life span of a diagnostic data file in a file system that has a limited number of files.

Abstract: A method loads a resource in a software application. The software application comprises an ordered search path identifying at least one of a plurality of resource containers. Each of the resource containers includes a timestamp and an index in the ordered search path.

Abstract: In a workload managed system comprising a plurality of server processes each capable of supporting a given program entity, such as an Enterprise JavaBeans™ specified stateful session bean, a stateful session bean instance is passivated, by writing it to a bean store, on completion of a unit of work. On next use the session bean is reactivated, by reading it from the bean store, in any one of the plurality of servers thereby allowing workload management for stateful session beans. A routing table is maintained, in non-volatile mass storage, that contains location information for units of work and stateful session bean instances, used to maintain unit of work-server affinity for the lifetime of the unit of work Stateful session beans instances are associated with ID keys that include a flag that is used to indicate whether or not the routing table contains location information for the bean instance.

Abstract: Provided is a method for providing Java modularity class loader protection by controlling the visibility of WebSphere, service provider, library and utility code interfaces. Interface access authorization is checked once, during module and class loading to effectively protect vulnerable programming interfaces, eliminating permission checking during execution. Code in a WebSphere Application server (WAS) computing environment is categorized into a finite number of sets in which one permission type is assigned to each set and the code in each set runs at the same privilege zone. Each set exposes programming interfaces to provide functional service and code in a particular set can only access code in the same or a lower security zone set. Also provided is a technique for explicitly providing to specific modules in lower security zones access to modules or designated interfaces of modules in higher security zones.

Abstract: A method loads a resource in a software application. The software application comprises an ordered search path identifying at least one of a plurality of resource containers. Each of the resource containers includes a timestamp and an index in the ordered search path.

Abstract: In a workload managed system comprising a plurality of server processes each capable of supporting a given program entity, such as an Enterprise JavaBeans™ specified stateful session bean, a stateful session bean instance is passivated, by writing it to a bean store, on completion of a unit of work. On next use the session bean is reactivated, by reading it from the bean store, in any one of the plurality of servers thereby allowing workload management for stateful session beans. A routing table is maintained, in non-volatile mass storage, that contains location information for units of work and stateful session bean instances, used to maintain unit of work-server affinity for the lifetime of the unit of work Stateful session beans instances are associated with ID keys that include a flag that is used to indicate whether or not the routing table contains location information for the bean instance.

Abstract: Disclosed is a method for providing synchronization of a transaction in a data processing system where the transaction involves a plurality of agents participating in the transaction and one coordinator for coordinating the transaction. The agents include at least a middleman which coordinates a set of at least one of the agents. A vote is sent indicating the availability or non-availability to commit from each of the agents to the coordinator. The coordinator determines a commit or backout decision when all the votes are received. A Not Known decision message is sent from the middleman to each of the agents in the set available to commit if the decision is not available at the middleman because of a failure. The Not Known decision message stops resynchronization of each of the available agents. If the middleman has responsibility for resynchronization then, on availability of the decision at the middleman, a resynchronization message is sent to each of the available agents.

Abstract: In a data processing environment where a client requests a server to perform part of its processing, a method of updating the client's version of server-related data without requiring the client to be a server, includes steps of: receiving, at a control point server, a first request from the client requesting that server-related data be transferred from the control point server to the client; and in response to the first request, sending the server-related data from the control point server to the client, along with a unique bind token identifying a version number of the server-related data such that each time the server-related data changes a new unique bind token is associated with the data, where the client uses the server-related data to form a second request for the server to perform part of the client's processing, and where the client sends said bind token to the server as part of the second request.

Abstract: A method of performing workload management within an object-oriented client/server computing environment wherein one of a plurality of servers is chosen to satisfy a client request based on at least one workload management policy, said method, which takes place within the client, includes steps of: deciding whether a client application program has issued a request for a server to do some work; forming an extended object reference based on said request, said extended object reference having, in addition to a server address field and an object key field, at least one additional field; accessing workload management policy data based on said extended object reference; and selecting one of said plurality of servers based on said accessed workload management policy data.