Abstract: A directory includes information about various systems (e.g., applications, processes, tasks, objects, services) and data, and may include data ownership information. The directory may define existing systems, corresponding locations by address, and corresponding semantic names. The directory may also specify the role of each system, e.g., a consumer or provider role. The directory may also define a scope of data a provider system can provide. As such, the directory may also include information about whether and how such data is being replicated. When a user requests data, a service may, based on the directory, determine and select an appropriate provider system for the data. The service may further create a subscription process to provide the user a local cache of the requested data. With such directory information, a service can provide data access services that integrate subscription processes.

Abstract: A request is received to initiate an operation (e.g., a query, etc.) on a view on a business object type. Such a request contains data characterizing the view which in turn characterizes a plurality of hierarchically arranged elements. Such elements characterized are associated with elements characterized by one or more business objects types. Thereafter, the operation is performed on the elements of the two or more business objects types. Responsive results of the operation responsive are mapped to the elements of the virtual business object type. After such mapping occurs, a message is generated that contains the results of the request in a structure compatible with the view.

Abstract: A first device transmits messages to a second device. The first device keeps track of messages that have already been transmitted from the first device to the second device, experiences an interruption in transmission of messages at the first device, and resumes the transmission from the first device following the interruption. Resuming the transmission includes transmitting only messages that have not already been completely transmitted from the first device to the second device.

Abstract: Methods and apparatus, including computer program products, are provided for processing messages including structured data, such as objects and business objects. The method may include a receiver inhibiting processing of a first message including a first object referencing a second object, when the receiver of the first message does not include key mapping information for the second object. The receiver may then receive key mapping information determined for the second object, when a second message, received at the receiver, includes the second object without references to another dependent object. The mapping information may be representative of a location of the second object. The receiver may then automatically resume processing of the first message, when the key mapping information is received. Related apparatus, systems, methods, and articles are also described.

Abstract: Methods and apparatus, including computer program products, are provided for processing messages including structured data, such as objects and business objects. The method may include a receiver inhibiting processing of a first message including a first object referencing a second object, when the receiver of the first message does not include key mapping information for the second object. The receiver may then receive key mapping information determined for the second object, when a second message, received at the receiver, includes the second object without references to another dependent object. The mapping information may be representative of a location of the second object. The receiver may then automatically resume processing of the first message, when the key mapping information is received. Related apparatus, systems, methods, and articles are also described.

Abstract: A directory includes information about various systems (e.g., applications, processes, tasks, objects, services) and data, and may include data ownership information. The directory may define existing systems, corresponding locations by address, and corresponding semantic names. The directory may also specify the role of each system, e.g., a consumer or provider role. The directory may also define a scope of data a provider system can provide. As such, the directory may also include information about whether and how such data is being replicated. When a user requests data, a service may, based on the directory, determine and select an appropriate provider system for the data. The service may further create a subscription process to provide the user a local cache of the requested data. With such directory information, a service can provide data access services that integrate subscription processes.

Abstract: A directory includes information about various systems (e.g., applications, processes, tasks, objects, services) and data, and may include data ownership information (e.g., data scope, read-write access, master-copy, etc.) and system role information (e.g., consumer or provider role). The directory may define existing systems, corresponding locations by address, and corresponding semantic names. With such information, a service may create routing rules that may provide the requested data via a semantic-based request. The routing rule may be selected to optimize communications and/or response time.

Abstract: A first device transmits messages to a second device. The first device keeps track of messages that have already been transmitted from the first device to the second device, experiences an interruption in transmission of messages at the first device, and resumes the transmission from the first device following the interruption. Resuming the transmission includes transmitting only messages that have not already been completely transmitted from the first device to the second device.