Abstract: Embodiments relate to file-based sharing of content through a content distribution network. A request is received from a source to disseminate content to a target consumer. The request does not include target consumer URL information. Based upon the request, content metadata stored in a database with content data, is referenced to generate a file including metadata comprising a portion of the content metadata. The file does not include the content data. The file is exported to the source. The source delivers the file to the target consumer through a communication channel (e.g., shared folder, email) located outside of the distribution network. The file is imported from the target consumer. The metadata of the file is processed to examine its integrity. The metadata may comprise a key for reference during this process. Upon confirming integrity of the file, the content data and the content metadata are distributed to the target consumer.

Abstract: Indexing natural language processing, a request is received from a user to access a document at a server, the server routes the request to an indexing server. A validation service checks if the CUID of the document is available in the indexing server repository or a file system associated with the indexing server. If the CUID of dataset exists, determine if a timestamp of the new document matches the timestamp of the previously indexed document. Upon determining that the above conditions are fulfilled, the previously indexed data is returned to the server. If it is determined that the above conditions do not match, then a transformation service is invoked at the indexing server. The transformation service compares a hash value of a dataset. If the transformation service determines that the hash value of a dataset in the document is not available, an indexing service is invoked to index the document.

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, systems, and computer-readable storage media for receiving, by an analytics content network (ACN), a configuration request through a tenant configuration application programming interface (TC-API) of a plurality of APIs, the configuration request including an identifier that uniquely identifies an analytics system tenant that is embedded in an application tenant within a customer landscape, the ACN distributing analytics content to multiple customer landscapes, determining, by the ACN, one or more analytics content that is to be distributed to the analytics system tenant at least partially based on the identifier, providing, by the ACN, a content package that includes the one or more analytics content within an API payload for response to the request, and transmitting, by the ACN, a response to the request through the TC-API, the response comprising the API payload.

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.

Abstract: Embodiments relate to file-based sharing of content through a content distribution network. A request is received from a source to disseminate content to a target consumer. The request does not include target consumer URL information. Based upon the request, content metadata stored in a database with content data, is referenced to generate a file including metadata comprising a portion of the content metadata. The file does not include the content data. The file is exported to the source. The source delivers the file to the target consumer through a communication channel (e.g., shared folder, email) located outside of the distribution network. The file is imported from the target consumer. The metadata of the file is processed to examine its integrity. The metadata may comprise a key for reference during this process. Upon confirming integrity of the file, the content data and the content metadata are distributed to the target consumer.

Abstract: Methods, systems, and computer-readable storage media for receiving, by an analytics content network (ACN), a configuration request through a tenant configuration application programming interface (TC-API) of a plurality of APIs, the configuration request including an identifier that uniquely identifies an analytics system tenant that is embedded in an application tenant within a customer landscape, the ACN distributing analytics content to multiple customer landscapes, determining, by the ACN, one or more analytics content that is to be distributed to the analytics system tenant at least partially based on the identifier, providing, by the ACN, a content package that includes the one or more analytics content within an API payload for response to the request, and transmitting, by the ACN, a response to the request through the TC-API, the response comprising the API payload.

Abstract: Indexing natural language processing, a request is received from a user to access a document at a server, the server routes the request to an indexing server. A validation service checks if the CUID of the document is available in the indexing server repository or a file system associated with the indexing server. If the CUID of dataset exists, determine if a timestamp of the new document matches the timestamp of the previously indexed document. Upon determining that the above conditions are fulfilled, the previously indexed data is returned to the server. If it is determined that the above conditions do not match, then a transformation service is invoked at the indexing server. The transformation service compares a hash value of a dataset. If the transformation service determines that the hash value of a dataset in the document is not available, an indexing service is invoked to index the document.

Abstract: Indexing natural language processing, a request is received from a user to access a document at a server, the server routes the request to an indexing server. A validation service checks if the CUID of the document is available in the indexing server repository or a file system associated with the indexing server. If the CUID of dataset exists, determine if a timestamp of the new document matches the timestamp of the previously indexed document. Upon determining that the above conditions are fulfilled, the previously indexed data is returned to the server. If it is determined that the above conditions do not match, then a transformation service is invoked at the indexing server. The transformation service compares a hash value of a dataset. If the transformation service determines that the hash value of a dataset in the document is not available, an indexing service is invoked to index the document.

Abstract: Indexing natural language processing, a request is received from a user to access a document at a server, the server routes the request to an indexing server. A validation service checks if the CUID of the document is available in the indexing server repository or a file system associated with the indexing server. If the CUID of dataset exists, determine if a timestamp of the new document matches the timestamp of the previously indexed document. Upon determining that the above conditions are fulfilled, the previously indexed data is returned to the server. If it is determined that the above conditions do not match, then a transformation service is invoked at the indexing server. The transformation service compares a hash value of a dataset. If the transformation service determines that the hash value of a dataset in the document is not available, an indexing service is invoked to index the document.