International Business Machines Corporation

Carroll Eugene Fulkerson, Jr

Jeffrey Alan Frey

Gary Stuart Puchkoff

Rodney Alan Little

Karunakar Bojjireddy

Amber Roy Chowdhury

Nataraj Nagaratnam

Roy Frank Brabson

Jim Alain Laredo

Anthony Joseph Nadalin

Lap Thiet Huynh

Constantinos Kassimis

Arthur James Stagg

Scott Andrew Fagen

Patrick S O'Donnell

Wesley McMillian Devine

John L Brady

Gregory J Rosensteel

Benjamin John North

Mark Albert Kowalski

A method for managing a configuration of heterogeneous software artifacts uses a common central configuration representation. An artifact of an unknown type, from an initial software solution, is submitted to a solution configuration tool. The solution configuration tool sends a request to a solution architect for locations of configuration files within the artifact. For each artifact whose configuration file locations have been requested from the solution architect, the solution configuration tool determines if each corresponding configuration file is a property file or an Extensible Markup Language (XML) file. If the corresponding configuration file is an XML file, then the solution architect provides a first and second xPath for locating the names and values of the configuration parameters in the XML configuration file. The configuration file and configuration parameter locator information is then stored in a configuration locator file. Information in the configuration locator file is used to introspect configuration parameters from the artifacts and store these generically in a central configuration file. Solution-level parameters are then defined and mapped to artifact-level parameters for use in configuring subsequent software solutions instantiated from the initial software solution.

Generically managing the configuration of heterogeneous software artifacts

A method for managing a configuration of heterogeneous software artifacts through a common central configuration representation includes adding a plurality of software artifacts from an initial software solution to a heterogeneous configuration tool. Using this heterogeneous configuration tool, artifact-level configuration parameters are extracted out of selected software artifacts by the heterogeneous configuration tool. The extracted artifact-level configuration parameters are then presented in a single representation. A subset of the presented extracted artifact-level configuration parameters is mapped to a set of solution-level parameters, which are then exposed in a subsequent software solution. Thereafter, parameters for one or more of the solution-level parameters, which are used by the subsequent software solution, are exposed. These parameters for the subsequent software solution are then mapped back to the artifact-level configuration parameters of the subsequent software solution.

Management of heterogeneous software artifacts through a common representation

A pluggable trust adapter architecture that accommodates a plurality of interceptors is provided. Each interceptor is adapted to perform security processing of communications having a specific protocol. Specifically, when a communication is received, it will be routed from a channel router to a specific interceptor based on the protocol of the communication. The interceptor will then 'security' process the communication (e.g., extract data, perform verification, etc.). Once the interceptor has processed the communication, the extracted data and the communication itself will be passed to an authorization system for authorization.

Pluggable trust adapter architecture, method and program product for processing communications

Methods, systems and computer program products are provided for providing transactional quality of service providing transaction service level information from an application requesting a data transmission transaction to a communication process executing on a data processing system. The transaction service level information is provided separate from the data for the data transmission transaction. A quality of service level associated with the data transmission transaction is determined based on the transaction service level information received from the application. Other embodiments also provide for establishing a quality of service level without reference to transaction data content while further embodiments provide for establishing a quality of service level for responses.

Methods, systems and computer program products for providing transactional quality of service

A set of management policies, selectable by the customer at object installation time, is used to manage one or more instances of an object. The set of policies includes at least one of an activation isolation policy, a passivation policy, a flush policy, and a refresh policy. The policies are managed by one or more containers of the computing environment.

Employing management policies to manage instances of objects

Management functions typically performed by containers of a server instance are delegated to resource managers coupled to the server instance. For example, responsibility for such management functions as locking, security control, multisystem caching and commitment control are removed from the containers and delegated to the resource managers. This enables ongoing improvements and functional extensions provided in the underlying resource managers to be immediately leveraged transparently in the server instance.

Delegating instance management functions to underlying resource managers

A composed business object of a server instance is provided. The server instance is coupled to a plurality of resource managers using a container of the server instance. A data object corresponding to the business object is populated with data retrieved using the plurality of resource managers. Thus, a business object is composed of data from multiple and/or diverse resource managers using a single container.

Providing composed containers and data objects to support multiple resources

A method and apparatus for serializing a request for access to a resource originating from a requester in a system of a multisystem complex. Each system of the complex maintains local contention data indicating contention between requesters on that system for access to the resource, as well as a local contention summary summarizing the local contention data. A global manager for managing contention between the systems uses the local contention summaries to determine the existence of global contention for the resource. In response to a request for access to the resource originating from a requester on a system, the system determines whether the request requires an update of the local contention summary for the system. If the request does not require an update of the local contention summary, the system processes the request in accordance with the local contention data for the system. If the request does require an update of the local contention summary, the system notifying the global manager of the update and processing the request in accordance with the response received from the global manager.

Growing community of inventors

Raleigh, NC, United States of America

Carroll Eugene Fulkerson, Jr