Abstract: A distribution network communicates content to tenant groups in a secure manner. An engine of the distribution network receives content created utilizing an application having different customers and partners. The engine also receives: a first identifier indicating a customer of the application with which a tenant is associated, and a second identifier indicating a partner of the application with which the tenant is associated. The engine references a stored database table to correlate the first identifier and the second identifier. Based upon the first identifier and the second identifier, the engine evaluates whether the tenant is to be provided access to the content. The engine may provide the tenant with the content according to an access right determined from the first identifier and the second identifier. Certain embodiments may find particular use disseminating content to new tenants of a customer, based upon prior distribution to other tenants of that customer.

Abstract: Methods and apparatus are disclosed for serializing software objects for loading onto a cloud-hosted tenant, or for other serialized operations. Nodes and edges of a directed graph represent respective software objects and the dependencies among the software objects. A search for strongly connected components reveals cyclic dependencies. Each strongly connected component can be replaced by a contracted node to obtain a condensation of the original directed graph. A topological ordering can be determined for the condensation, and the software objects can be processed or loaded according to the topological ordering. Such ordering provides that software objects of a strongly connected component are processed consecutively while, for all other dependencies, a prerequisite object is processed (loaded) before its dependent object(s). Examples of SAP Analytics Cloud and Data Warehouse Cloud are provided. Exemplary, push and pull loading procedures, topological ordering, and validation are disclosed.

Abstract: Methods and apparatus are disclosed for serializing software objects for loading onto a cloud-hosted tenant, or for other serialized operations. Nodes and edges of a directed graph represent respective software objects and the dependencies among the software objects. A search for strongly connected components reveals cyclic dependencies. Each strongly connected component can be replaced by a contracted node to obtain a condensation of the original directed graph. A topological ordering can be determined for the condensation, and the software objects can be processed or loaded according to the topological ordering. Such ordering provides that software objects of a strongly connected component are processed consecutively while, for all other dependencies, a prerequisite object is processed (loaded) before its dependent object(s). Examples of SAP Analytics Cloud and Data Warehouse Cloud are provided. Exemplary, push and pull loading procedures, topological ordering, and validation are disclosed.

Abstract: A distribution network may efficiently communicate items/item details in a private manner, with different access rights tailored to various tenants residing within a same or different customer landscape. A first input comprising a flat file with items/item details, is received. A second input comprising permissions entries for per-user, per-item direct access rights (e.g., view, read, write, delete) is also received. The first and second inputs are recursively processed to find nearest ancestors having the direct access rights, with a hash maintained including the nearest ancestors. An effective permitted structure (e.g., tree comprising root and leaf nodes) is generated by recursively adding descendant items having inherited access rights, to the nearest ancestors. Ultimately, descendant item(s) are privately distributed to a user with an access right according to the effective permitted structure. Embodiments may be particularly suited to the private distribution of analytics content (e.g.

Abstract: A distribution network may efficiently communicate items/item details in a private manner, with different access rights tailored to various tenants residing within a same or different customer landscape. A first input comprising a flat file with items/item details, is received. A second input comprising permissions entries for per-user, per-item direct access rights (e.g., view, read, write, delete) is also received. The first and second inputs are recursively processed to find nearest ancestors having the direct access rights, with a hash maintained including the nearest ancestors. An effective permitted structure (e.g., tree comprising root and leaf nodes) is generated by recursively adding descendant items having inherited access rights, to the nearest ancestors. Ultimately, descendant item(s) are privately distributed to a user with an access right according to the effective permitted structure. Embodiments may be particularly suited to the private distribution of analytics content (e.g.

Abstract: A distribution network communicates content to tenant groups in a secure manner. An engine of the distribution network receives content created utilizing an application having different customers and partners. The engine also receives: a first identifier indicating a customer of the application with which a tenant is associated, and a second identifier indicating a partner of the application with which the tenant is associated. The engine references a stored database table to correlate the first identifier and the second identifier. Based upon the first identifier and the second identifier, the engine evaluates whether the tenant is to be provided access to the content. The engine may provide the tenant with the content according to an access right determined from the first identifier and the second identifier. Certain embodiments may find particular use disseminating content to new tenants of a customer, based upon prior distribution to other tenants of that customer.