Abstract: Under the present invention a definition file and an object file are provided. The definition file includes a defined syntax for managed object descriptions, while the object file contains a description of a particular desired object. When a process is started (or re-started), the files are automatically read and the description in the object file is automatically validated based on the defined syntax in the definition file. Once validated, the description is used to automatically create a managed resource from which a managed object can be created.

Abstract: Problem diagnostics may be obtained from components that log messages using a unique component identifier which is provided within each message so as to enable routing of callbacks to the component that originated the message. Similarly, problem diagnostics may be obtained from components that generate alerts, where the alerts contain the unique identifier of the component that generated the alert. Each component supports a diagnostic provider interface comprising operations which may be dynamically invoked, for example to solicit information from the component such as its configuration data, its state information, to execute self-diagnostic tests, and so forth. In addition or instead, operations may be provided that can be invoked to cause the component to alter its configuration data (such as notifying the component to change its level of message logging) or its behavior.

Abstract: Problem diagnostics may be obtained from components that log messages using a unique component identifier which is provided within each message so as to enable routing of callbacks to the component that originated the message. Similarly, problem diagnostics may be obtained from components that generate alerts, where the alerts contain the unique identifier of the component that generated the alert. Each component supports a diagnostic provider interface comprising operations which may be dynamically invoked, for example to solicit information from the component such as its configuration data, its state information, to execute self-diagnostic tests, and so forth. In addition or instead, operations may be provided that can be invoked to cause the component to alter its configuration data (such as notifying the component to change its level of message logging) or its behavior.

Abstract: Provided is a method for programming module load balancing and failover in a distributed computing environment. The Java Management extensions (JMX) specification is enhanced to support load balancing and provide a high-availability of JMX management beans (Mbeans). Also provided are enhancements to the programming model and infrastructure to support the enhanced programming model. Two exemplary approaches for load balancing and failover are provided, one based both upon clustered Mbeans and one based upon unclustered Mbeans. In the unclustered approach, client affinity is supported in that a request from a particular client can be routed to a particular Mbean. In the clustered approach, a specific Mbean can be invoked by providing a special parameter in the Mbean invocation or by adding a special property to the specific Mbean's ObjectName to indicate that during runtime automatic routing should not be employed.

Abstract: Provided is a method for programming module load balancing and failover in a distributed computing environment. The Java Management extensions (JMX) specification is enhanced to support load balancing and provide a high-availability of JMX management beans (Mbeans). Also provided are enhancements to the programming model and infrastructure to support the enhanced programming model. Two exemplary approaches for load balancing and failover are provided, one based both upon clustered Mbeans and one based upon unclustered Mbeans. In the unclustered approach, client affinity is supported in that a request from a particular client can be routed to a particular Mbean. In the clustered approach, a specific Mbean can be invoked by providing a special parameter in the Mbean invocation or by adding a special property to the specific Mbean's ObjectName to indicate that during runtime automatic routing should not be employed.

Abstract: Problem diagnostics may be obtained from components that log messages using a unique component identifier which is provided within each message so as to enable routing of callbacks to the component that originated the message. Similarly, problem diagnostics may be obtained from components that generate alerts, where the alerts contain the unique identifier of the component that generated the alert. Each component supports a diagnostic provider interface comprising operations which may be dynamically invoked, for example to solicit information from the component such as its configuration data, its state information, to execute self-diagnostic tests, and so forth In addition or instead, operations may be provided that can be invoked to cause the component to alter its configuration data (such as notifying the component to change its level of message logging) or its behavior.

Abstract: The present invention routes object requests in a distributed system using address information identified in object headers that accompany the request. Specifically, when an object is created under the present invention, address information is inserted into a corresponding object header. When a request related to the object is later issued, the object header accompanies the request. The address information is used to ensure that the request is efficiently and accurately routed to a target process within a target node of a target cell.

Abstract: A system, computer program product and method of collecting metadata of application programs installed on a computer system are provided. A check is generally performed to determine whether metadata of an application program is to be collected. If so, the metadata is automatically collected and stored. The collected metadata may be provided to a system managing the computer system upon request. The check may be performed periodically. If the check is performed periodically, however, it is always performed before providing metadata to the managing system.

Abstract: A method of deploying enterprise applications or updates to data processing systems in a complex data processing environment. The enterprise applications or updates are phase deployed to the target data processing systems. Phased deployment includes the steps of preparing one affected node, quiescing all affected servers in the node, stopping all affected servers in the node, synchronizing the node, delivering the applications or updates, starting all affected servers, reactivating all affected servers, restoring the affected node, and repeating these steps for each affected node one at a time until all targeted data processing systems have been affected.

Abstract: A method of automating the deployment of a number of enterprise applications on one or more computer data processing systems. Each enterprise application or update is stored in a dynamic distribution directory and is provided with identifying indicia, such as stage information, target information, and settings information. When automated enterprise deployment is invoked, computer instructions in a computer readable medium provide for initializing deployment, performing deployment, and finalizing deployment of the enterprise applications or updates.

Abstract: A method, system and apparatus for dynamically linking a content server to one or more application servers can include updating a routing configuration for the content server by automatically cataloging host application servers for an application serviced by the content server. Specifically, the updating step can include determining each host application server for portions of the application; and, adding each determined host application server to a list of application servers fronted by the content server. Moreover, the determining step can include determining each host application server for each target of each module of the application. Finally, the method further can include automatically cataloging host application server clusters for the application serviced by the content server.

Abstract: Methods, systems, and media to automatically deploy an, e.g., a JS2EE file between environments are disclosed. Embodiments include hardware and/or software for selecting one or more applications in an original system for export. The applications along with their corresponding application data, configuration data, and descriptor files, are compressed into one or more archive files such as Enterprise Archives (EARs). Variable configuration data associated with the target environment is identified so the values of the variable configuration data can be adapted for the target environment. Then, the target environment is adapted for installation of the application and the application is installed in the target environment. Advantageously, this deployment of the application may reduce the chance of user error, require less J2EE knowledge and script maintenance, and complete faster than deployments effected manually.

Abstract: Methods and arrangements to propagate application software to a virtual deployment target are contemplated. More specifically, a user may create multiple virtual deployment targets in a software system such as WebSphere™ and deploy applications to multiple the virtual deployment targets without having to manually fit policy-driven applications into each virtual deployment target. Embodiments are particularly advantageous when the application software is a business solution that needs to be deployed multiple times such as during the development and testing of the business solution. For example, application software of a business solution typically includes a group of applications designed to cooperatively function as a single entity. An application bundle such as an Enterprise Application Solution (EAS) file describes the application software and includes pertinent information about the application software, application configuration data, and runtime configuration data to implement the business solution.

Abstract: A method, apparatus and computer instructions are disclosed for maintaining the compatibility of a multiple nodes in a distributed systems management environment with multiple configuration settings, by transforming the configuration data stored in the master repository (one possible realization is where XML documents contain the configuration data) from one version of the product to a previous version of the product. For multiple versions of the systems management environment, a transformation pipeline process (one possible realization of such a process may utilize XSLT) can be used by a “master” node to transform the configuration data multiple times for each version of the environment, until the configuration data has the format of the intended recipient “slave” node.

Abstract: Methods, systems, and media are disclosed for managing a resource managed by a mbean server having an mbean. One embodiment includes receiving a request by the application, wherein the request constitutes an action a user seeks to perform on the resource, and adding a number of instance identifier fields to an mbean descriptor file associated with the mbean. Further, the embodiment includes populating the number of instance identifier fields with an equivalent number of properties from an objectname of the resource, thereby producing a populated mbean descriptor file that identifies the resource among resources. Further still, the embodiment includes reading the mbean descriptor file after the populating, and determining, based on the reading, whether the user has an authority to perform the request. If authority exists, then an mbean method performs the action on the resource, and filters the obtained results to coincide with the user's authority.

Abstract: Methods, systems, and media are disclosed for determining access rights to a resource managed by an application. One embodiment includes receiving a request by the application, wherein the request comprises an action a user seeks to perform on the resource, and locating, based on the request, the resource in both a containment relationship graph and in a structure having groupings of resources, wherein the groupings comprise a grouping having the resource. Further, the embodiment includes traversing a vertex of the containment relationship graph, wherein the vertex comprises a generational resource of the resource, and reading an authorization table associated with a grouping having the generational resource in the groupings. Further still, the embodiment includes determining whether to grant the access rights for performing the action on the resource.

Abstract: Methods, systems, and media are disclosed for determining access rights to a resource managed by an application. One embodiment includes receiving a request by the application, wherein the request comprises an action a user seeks to perform on the resource. Further, the embodiment includes locating, based on the request, the resource in a structure having groupings of resources, wherein the groupings include a grouping having the resource. Typically the groupings comprise files having mappings of resources to assigned groups, and each group has an associated authorization table mapping roles or policies to users. Further still, the embodiment includes reading an authorization table associated with the grouping having the resource, and determining whether to grant the access rights for performing the action on the resource.

Abstract: A method is presented for managing applications using application-based names. A naming service registers an alias name; the alias name represents a first compound name that includes an application name that is associated with an application and a deployment name that is associated with a deployment attribute that characterizes a deployment of an instance of the application. The naming service is also able to generate an application-based name associated with an application; the application-based name represents a context within a naming system, and the application-based name is a second compound name that includes the alias name. Applications are managed within a data processing system using application-based names. The first compound name can be associated with a first topology-based name that represents a first context for organizing files that are related to the instance of the application.

Abstract: A system, method and software product for providing an implementation for “management beans” or MBeans in a multiple Java Virtual Machine (JVM) server is disclosed. By providing a single MBean interface so that a client or an element external to the server executes a single request and/or receives a single notification, no matter how many servant JVMs exist, to the external element, the multiple JVM system appears to act like a single JVM system. These new techniques for providing management across several JVM servers depend upon one server being designated as a control JVM and the remaining JVM servers being designated as servant JVMs, under the control of the control JVM. The control JVM distributes work requests across the servant JVMs in an implementation specific way.

Abstract: Under the present invention a definition file and an object file are provided. The definition file includes a defined syntax for managed object descriptions, while the object file contains a description of a particular desired object. When a process is started (or re-started), the files are automatically read and the description in the object file is automatically validated based on the defined syntax in the definition file. Once validated, the description is used to automatically create a managed resource from which a managed object can be created.