Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.