Abstract: The system and method to control hybrid deployment of an application is disclosed. The method comprises receiving an application developed utilizing an application archetype and further deploying the application in a hybrid deployment. The hybrid deployment comprises of cloud datacenter deployment and local datacenter deployment. The method further comprises obtaining a configuration data dynamically at runtime associated with primary and secondary configuration data. The primary configuration is associated with the cloud datacenter and the secondary configuration is associated with the local datacenter deployment. The method further more comprises storing the configuration data as a metadata in the application archetype. Further, based on metadata, the access to the functionalities of the application are allowed or denied, thereby controlling the hybrid deployment of an application.

Abstract: Disclosed is a method and system for automatically testing an API. The system may determine a type of the API, inputs handled and outputs generated by the API. The system may identify a web application template for invoking the API. Further, the system may generate a Hyper Text Markup Language (HTML) page for accepting input parameters. The system may then create input data elements using the input parameters. The system may invoke the API using the input data elements in order to generate output. The system may generate another HTML page for providing the output. The system may generate a set of test scripts for accepting inputs from a data file and then receive the inputs in the first HTML form. The system may submit the first HTML form to generate final outputs by the API. Further, the system may verify the final outputs in order to test the API.

Abstract: A method and system for entity customization in a hierarchical service provider, multi-tenant system is disclosed. The method disclosed uniquely identifies plurality of participants in the hierarchical system as a root service provider, sub-provider or a tenant. Further, the method enables identification of entities as customizable or non-customizable and authorizes the participants to customize the respective entity. The method enables to define scope of the entity that indicates whether the entity is applicable to a tenant or a provider or a sub-provider or a combination of these. The method enables identification of non-customizable or mandatory attributes within an entity. Further, the method aggregates customizations through the hierarchy and applies them for a specific tenant or a provider.

Abstract: Methods, systems, and apparatus, including computer programs encoded on computer storage media, for generating query plans for queries that include common table expressions. One of the methods includes receiving a query that includes a common table expression (CTE), wherein the CTE signifies that a system can compute a result for the query using a query plan that includes a CTE producer operator and a corresponding CTE consumer operator. A first query plan that includes a CTE producer operator and a corresponding CTE consumer operator and a second query plan that inlines an instance of the CTE consumer operator are generated. Respective costs are computed for the first query plan and the second query plan, and a result for the query is computed using the second query plan if the second query plan has a lower cost.

Abstract: System and method for accelerating automated testing is disclosed. First, a test script of a screen is recorded to identify user interface elements comprising data fields present on the screen. An input is received in the data fields. Based on the input, one or more test case templates are selected. Further, data sets and verification types required corresponding to the input are obtained. The data sets are obtained based on the one or more test case templates. The verification types are obtained from a user. Subsequently, the one or more test case templates, the data sets, and the verification types are integrated to generate an executable test case file. Based on the executable test case file, the test script is modified and further executed. Upon executing, a report is generated.

Abstract: Methods, systems, and apparatus, including computer programs encoded on computer storage media, for generating query plans for queries that include common expressions. One of the methods includes receiving an initial query plan generated for a query that includes multiple common expressions; identifying two or more matching subtrees of the initial query plan; generating an alternative query plan that includes a CTE producer operator and having an instance of one of the matching subtrees as one or more descendant operators of the CTE producer operator, including replacing at least one instance of a matching subtree in the initial query plan with a CTE consumer operator corresponding to the CTE producer operator; computing respective costs for the initial query plan and the alternative query plan; selecting the alternative query plan based on the cost for the alternative query plan; and computing a result for the query using the alternative query plan instead of the initial query plan.

Abstract: A request for a metadata object is received where the request includes an identifier. It is determined whether the metadata object is stored in a metadata cache, including by: selecting a sub-cache in the metadata cache based at least in part on the identifier and determining whether the metadata object is stored in that sub-cache. If it is determined the metadata object is not in the metadata cache, a request (in a format associated with the source) to obtain the metadata object is sent to a source with which the metadata object is associated. If the metadata object provided by the source is in a native format which is not the same as the common format, the metadata object is transformed from the native format into the common format. Access to the metadata object in the common format is provided.

Abstract: Disclosed is a method and system for automatically testing an API. The system may determine a type of the API, inputs handled and outputs generated by the API. The system may identify a web application template for invoking the API. Further, the system may generate a Hyper Text Markup Language (HTML) page for accepting input parameters. The system may then create input data elements using the input parameters. The system may invoke the API using the input data elements in order to generate output. The system may generate another HTML page for providing the output. The system may generate a set of test scripts for accepting inputs from a data file and then receive the inputs in the first HTML form. The system may submit the first HTML form to generate final outputs by the API. Further, the system may verify the final outputs in order to test the API.

Abstract: The embodiments herein relate to product/application customization and, more particularly, to develop multi instance single code base product/application with centralized management. The central repository present in the system fetches and holds all differentiation information for various instances of the application. Then the synchronization framework allows the differentiation data to be available to the individual instances. Further, the application archetype provides all the services needed to adhere to the principles of externalizing require facets of each instance and ensures the right configurations are fetched from the central repository. Finally, the application is executed with required configuration data.

Abstract: Data movement driven placement of data in a distributed database is disclosed. A set of one or more queries anticipated to be performed with respect to a data set is received. A set of statistics associated with the data set is received. The set of queries and the statistics are used to explore algorithmically a search space of distribution policy alternatives, to determine an optimal distribution policy to distribute data comprising the data set across a plurality of database servers.

Abstract: The embodiments herein relate to product/application customization and, more particularly, to develop multi instance single code base product/application with centralized management. The central repository present in the system fetches and holds all differentiation information for various instances of the application. Then the synchronization framework allows the differentiation data to be available to the individual instances. Further, the application archetype provides all the services needed to adhere to the principles of externalizing require facets of each instance and ensures the right configurations are fetched from the central repository. Finally, the application is executed with required configuration data.

Abstract: A request for a metadata object is received where the request includes an identifier. It is determined whether the metadata object is stored in a metadata cache, including by: selecting a sub-cache in the metadata cache based at least in part on the identifier and determining whether the metadata object is stored in that sub-cache. If it is determined the metadata object is not in the metadata cache, a request (in a format associated with the source) to obtain the metadata object is sent to a source with which the metadata object is associated. If the metadata object provided by the source is in a native format which is not the same as the common format, the metadata object is transformed from the native format into the common format. Access to the metadata object in the common format is provided.

Abstract: A method and system for entity customization in a hierarchical service provider, multi-tenant system is disclosed. The method disclosed uniquely identifies plurality of participants in the hierarchical system as a root service provider, sub-provider or a tenant. Further, the method enables identification of entities as customizable or non-customizable and authorizes the participants to customize the respective entity. The method enables to define scope of the entity that indicates whether the entity is applicable to a tenant or a provider or a sub-provider or a combination of these. The method enables identification of non-customizable or mandatory attributes within an entity. Further, the method aggregates customizations through the hierarchy and applies them for a specific tenant or a provider.

Abstract: A request for a metadata object is received. It is determined whether the metadata object is stored in a metadata cache. In the event the metadata object is not stored in the metadata cache, a request to obtain the metadata object is sent to a source with which the metadata object is associated in a format associated with the source. The metadata object is transformed from a native format of the source into a common format if the metadata object as provided by the source is in a native format that is not the same as the common format. Access to the metadata object in the common format is provided.