Abstract: A system and method for modeling cross system content between a hub and one or more backend systems is disclosed. Model content of one or more data models is stored in a model stack defined in a storage. The model content of each data model includes model metadata representing a model of a backend system. Cross model content is stored in a cross model stack. The cross model content includes reference metadata representing one or more references associated with a data model of one backend system and that reference a data model of another backend system. Central cross model content is stored in a central cross model stack. The central cross model content includes one or more cross elements that do not belong to the model content of any of the data models, and that establish a connection between two data models of different backend systems.

Abstract: A system and method for handling of cross-system metadata in a system landscape with a hub and backend systems is presented. Reference metadata that is associated with a first backend system and that refers to metadata of a second backend system is stored in a storage associated with the first backend system, the storage further separately storing backend system metadata that is associated only with the first backend system. Connecting metadata, which establishes a connection between backend system metadata associated with the first backend system and backend system metadata of any other backend system, is stored separately. At 206, the first backend system is linked to the hub by the connecting metadata from storage associated with the first backend system to a hub storage associated with the hub. The connecting metadata is activated in the hub to link the first backend system with the second backend system.

Abstract: Example systems and methods of integrating text analysis and search functionality are presented. In one example, a plurality of documents, as well as search information comprising search terms for a search category, are accessed. Each of the documents that include at least one of the search terms is identified. The identified documents are analyzed to determine those of the identified documents that are logically associated with the search category. Each of the documents determined to be logically associated with the search category are tagged with the search category.

Abstract: Example systems and methods of integrating data tags with their associated object data are presented. In one implementation, a data object employed in a first computer application is accessed. Examples of the data object include, but are not limited to, structured data and unstructured data. Tagging data that is descriptive of the first data object is also accessed. The tagging data is stored in at least one of the first data object and a separate data object linked with the first data object. The tagging data and the first data object are processed using a second computer application.

Abstract: A system and method for establishing cross-relationships between objects is presented. A primary search is executed on a first object. A set of tagger identifiers is then determined based on the primary search. Each tagger identifier includes an internal instance key and one or more attributes of a match with the first object related to the primary search, and each tagger identifier of the set of tagger identifiers provides data for a secondary search. The secondary search is then executed on each of a secondary object that is tagged by the first object scanned by the primary search, the secondary search using the internal instance key and one or more attributes of the match with the first object.

Abstract: A system and method for establishing cross-relationships between objects is presented. A primary search is executed on a first object. A set of tagger identifiers is then determined based on the primary search. Each tagger identifier includes an internal instance key and one or more attributes of a match with the first object related to the primary search, and each tagger identifier of the set of tagger identifiers provides data for a secondary search. The secondary search is then executed on each of a secondary object that is tagged by the first object scanned by the primary search, the secondary search using the internal instance key and one or more attributes of the match with the first object.

Abstract: A system and method for modeling cross system content between a hub and one or more backend systems is disclosed. Model content of one or more data models is stored in a model stack defined in a storage. The model content of each of the one or more data models includes model metadata representing a model of a corresponding backend system. Cross model content is stored in a cross model stack defined in the storage. The cross model content includes reference metadata representing one or more references associated with a data model of one backend system and that reference a data model of another backend system. Central cross model content is stored in a central cross model stack in the storage. The central cross model content includes one or more cross elements that do not belong to the model content of any of the one or more data models, and that establish a connection between two data models of different backend systems.

Abstract: A system and method for handling of cross-system metadata in a system landscape with a hub and backend systems is presented. Reference metadata that is associated with a first backend system and that refers to metadata of a second backend system is stored in a storage associated with the first backend system, the storage further separately storing backend system metadata that is associated only with the first backend system. Connecting metadata, which establishes a connection between backend system metadata associated with the first backend system and backend system metadata of any other backend system, is stored separately. At 206, the first backend system is linked to the hub by the connecting metadata from storage associated with the first backend system to a hub storage associated with the hub. The connecting metadata is activated in the hub to link the first backend system with the second backend system.

Abstract: Disclosed is a method and system for receiving a first message and creating a before image of the first message by comparing the first message with a second message stored in a message database. An actual message to be updated in a target device is identified by combining a transaction data and the before image of the first message.

Abstract: Embodiments of the invention are generally directed to systems and methods for setting status flags for mobile data distribution based on the subscription rules. A mobile middleware manages several objects between the mobile device and the backend system. The mobile data distribution happen based on subscription rules set up on the object. A status flag is assigned to each such subscription rule and any change in the subscription rule triggers updating of that corresponding status flag. The mobile middleware distributes data to the backend system and to the mobile devices based on the subscription rule evaluation. For updating the subscription rule, it is sufficient to evaluate only the status flags that have changed.

Abstract: Middleware for mobile data management may include an association table and a message store. The middleware may operate to receive a business object instance from a backend system, determine one or more mobile devices associated with the business object instance, associate the business object instance with the one or more mobile devices and with an insert state in an association table, and associate, in the association table, the business object instance and the one or more mobile devices with a full-state message in the message store.

Abstract: Embodiments of the invention are generally directed to systems and methods for setting status flags for mobile data distribution based on the subscription rules. A mobile middleware manages several objects between the mobile device and the backend system. The mobile data distribution happen based on subscription rules set up on the object. A status flag is assigned to each such subscription rule and any change in the subscription rule triggers updating of that corresponding status flag. The mobile middleware distributes data to the backend system and to the mobile devices based on the subscription rule evaluation. For updating the subscription rule, it is sufficient to evaluate only the status flags that have changed.

Abstract: The method by which an information distribution system distributes information to subscribers is controlled by user profiles. A user profile is automatically generated by a profile generator based on information known about the user and a plurality of policies detailing what kind of users is eligible to receive what kind of information. User information and policy definitions are found on a user record store and a policy store connected to the profile generator, and the generated user profile is stored on a user profile store.

Abstract: Disclosed is a method and system for receiving a first message and creating a before image of the first message by comparing the first message with a second message stored in a message database. An actual message to be updated in a target device is identified by combining a transaction data and the before image of the first message.

Abstract: Middleware for mobile data management may include an association table and a message store. The middleware may operate to receive a business object instance from a backend system, determine one or more mobile devices associated with the business object instance, associate the business object instance with the one or more mobile devices and with an insert state in an association table, and associate, in the association table, the business object instance and the one or more mobile devices with a full-state message in the message store.