Abstract: Coordinating data sharing among applications in mobile devices, in one aspect, may include a shared data manager application on a mobile device that manages data trade requirements of a plurality of mobile applications, and permission grants or denials to reads and writes of data managed by the shared data manager and used by the plurality of mobile applications.

Abstract: Coordinating data sharing among applications in mobile devices, in one aspect, may include a shared data manager application on a mobile device that manages data trade requirements automatically of a plurality of mobile applications, and permission grants or denials to reads and writes of data managed by the shared data manager and used by the plurality of mobile applications.

Abstract: Managing data stewardship in multi-level MDM systems may include a steward data composer that creates data steward repository for a master data management system to define relationships between data stewards and data objects for which data stewards are responsible and steward data consolidator that creates an integrated data steward repository by combining multiple data steward repositories.

Abstract: Enforcing data sharing policy through shared data management, in one aspect, may include extracting data access rights from the one or more data policies based on a user role, data purpose, an object set and a constraint identification; extracting a data domain from the one or more data policies based on the data purpose and the object set; associating the data access rights and the data domain with data attributes of the shared data; automatically responding to application-based offers and requests for the shared data within a Software-as-a-Service platform based on the data access rights.

Abstract: Federating master data management systems may include a network-aware adapter configured with a host master data management node. The network-aware adapter may establish one or more links with other master data management systems to allow the system to work together and leverage each other's data.

Abstract: Providing an open data marketplace may include identifying one or more data attributes from a plurality of applications registered with a shared data management system; mapping said one or more data attributes to a data model to create a first set of mapped data; augmenting said first set of mapped data with additional data imported into the shared data management system from other data locations to create an augmented set of mapped data; receiving one or more of second set of mapped data from one or more shared data management system associated respectively with one or more shared data management networks; enabling of composing a data set by combining and cleansing one or more of said first set of mapped data, said second set of mapped data, and said augmented set of mapped data; and offering said composed data set in a digital marketplace with associated pricing characteristics.

Abstract: Dynamic application adaptation in software-as-a-service platform, in one aspect, may receive an access permission associated with a published shared data management data object in the software-as-a-service platform having shared data management and a plurality of applications deployed, look up one or more rules associated with one or more features of an application deployed on the software-as-a-service platform, based on the received access permission, and activate or deactivate said one or more features associated with said plurality of applications based on said one or more rules.

Abstract: Enforcing data sharing policy through shared data management, in one aspect, may include extracting data access rights from the one or more data policies based on a user role, data purpose, an object set and a constraint identification; extracting a data domain from the one or more data policies based on the data purpose and the object set; associating the data access rights and the data domain with data attributes of the shared data; automatically responding to application-based offers and requests for the shared data within a Software-as-a-Service platform based on the data access rights.

Abstract: Managing data stewardship in multi-level MDM systems may include a steward data composer that creates data steward repository for a master data management system to define relationships between data stewards and data objects for which data stewards are responsible and steward data consolidator that creates an integrated data steward repository by combining multiple data steward repositories.

Abstract: Federating multiple-level master data management systems may include a first set of master data management nodes having one or more common characteristics. A first group master data management node may be assigned to centrally manage the first set of master data management nodes, the first group master data management node maintaining master data management functionalities at a group level and providing a single logical view of master data to the first set of master data management nodes. Each master data management node in the first set has data access link with the first group master data management node based on implementation style of said each master data management node.

Abstract: Federating master data management systems may include a network-aware adapter configured with a host master data management node. The network-aware adapter may establish one or more links with other master data management systems to allow the system to work together and leverage each other's data.

Abstract: Shared data management in software-as-a-service platform may provide a common object data schema for one or more data objects and one or more data attributes associated with said one or more data objects stored in a master database. A plurality of applications may be enabled to be deployed dynamically on a platform and interoperate by sharing said data values stored in the master database. Data trading is enabled in which applications request permissions to read from or write to, or both, the master database, and in which the requests are mediated by granting or denying permissions.

Abstract: Methods and arrangements for collecting tracing data from a plurality of threads of a program. A storage buffer is provided, a first number of units of tracing data for a first thread of the program is determined, and a second number of units of tracing data for a second thread of the program is determined. In the storage buffer, a first block of storage space is reserved for storing the first number of units of tracing data and a second block of storage space is reserved for storing the second number of units of tracing data. Tracing data are then written concurrently into the first and blocks.

Abstract: A method for automating the deployment and lifecycle management of an integration solution by using a deployment solution template to gather deployment information, where the integration solution combines components developed separately or on different platforms. The deployment information gathered includes the computing environment topology into which the integration solution is being deployed, as well as the resource requirements and non-functional requirements of the integration solution and its components. The method provides computer implemented models for analyzing the gathered deployment information, and identifying and optimizing deployment options. Choices for selection among identified and optimized options based on non-functional requirements of the integration solution may be displayed to a user of the deployment method.

Abstract: Methods and arrangements for collecting tracing data from a plurality of threads of a program. A storage buffer is provided, a first number of units of tracing data for a first thread of the program is determined, and a second number of units of tracing data for a second thread of the program is determined. In the storage buffer, a first block of storage space is reserved for storing the first number of units of tracing data and a second block of storage space is reserved for storing the second number of units of tracing data. Tracing data are thence written concurrently into the first and blocks.

Abstract: Methods and arrangements for collecting tracing data from a plurality of threads of a program. A storage buffer is provided, a first number of units of tracing data for a first thread of the program is determined, and a second number of units of tracing data for a second thread of the program is determined. In the storage buffer, a first block of storage space is reserved for storing the first number of units of tracing data and a second block of storage space is reserved for storing the second number of units of tracing data. Tracing data are thence written concurrently into the first and blocks.

Abstract: A method for automating the deployment and lifecycle management of an integration solution by using a deployment solution template to gather deployment information, where the integration solution combines components developed separately or on different platforms. The deployment information gathered includes the computing environment topology into which the integration solution is being deployed, as well as the resource requirements and non-functional requirements of the integration solution and its components. The method provides computer implemented models for analyzing the gathered deployment information, and identifying and optimizing deployment options. Choices for selection among identified and optimized options based on non-functional requirements of the integration solution may be displayed to a user of the deployment method.

Abstract: Methods and arrangements for collecting tracing data from a plurality of threads of a program. A storage buffer is provided, a first number of units of tracing data for a first thread of the program is determined, and a second number of units of tracing data for a second thread of the program is determined. In the storage buffer, a first block of storage space is reserved for storing the first number of units of tracing data and a second block of storage space is reserved for storing the second number of units of tracing data. Tracing data are thence written concurrently into the first and blocks.