摘要:
Systems and method for routing search query results in a networked computing environment. An initial search query is reformulated into at least one sub-query in accordance with one or more configurable rules. The sub-query is sent to at least one information system or source, and any potential hits associated with the same are optionally combined and then rendered for viewing.
摘要:
Systems and method for routing search query results in a networked computing environment. An initial search query is reformulated into at least one sub-query in accordance with one or more configurable rules. The sub-query is sent to at least one information system or source, and any potential hits associated with the same are optionally combined and then rendered for viewing.
摘要:
A query pipeline for an enterprise search system is configurable by a user of the system. A user may create rules for custom query transformation and parallel query generation, federation of queries, mixing of results and application of display layouts to the received search results. A user interface (UI) assists a user in configuring the search pipeline. For example, a user may enter condition action rules for queries that affect how a query is transformed, how parallel queries are generated, how queries are federated, how search results are ranked and displayed, how rules are ordered and the like.
摘要:
A query pipeline for an enterprise search system is configurable by a user of the system. A user may create rules for custom query transformation and parallel query generation, federation of queries, mixing of results and application of display layouts to the received search results. A user interface (UI) assists a user in configuring the search pipeline. For example, a user may enter condition action rules for queries that affect how a query is transformed, how parallel queries are generated, how queries are federated, how search results are ranked and displayed, how rules are ordered and the like.
摘要:
Rules, such as condition-action rules, are configured at different levels of a hierarchy. For example, a top level site administrator may configure rules, lower level administrators may configure rules and end users may configure rules. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined. The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved. While the ordering of any rules remains constant when inherited at the lower levels, the lower level may toggle on/off the execution of each rule within the ordering.
摘要:
Rules, such as condition-action rules, are configured at different levels of a hierarchy. For example, a top level site administrator may configure rules, lower level administrators may configure rules and end users may configure rules. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved. While the ordering of any rules remains constant when inherited at the lower levels, the lower level may toggle on/off the execution of each rule within the ordering.
摘要:
Non-administrators selectively move content from a source network to a destination network. The source network includes a deployment server that can deploy an item and its dependencies (if any) listed in a quick deploy list without having to get specific administrator authorization for the deployment. The deployment server can be configured to check the quick deploy list relatively frequently so that any items listed in the quick deploy list are quickly deployed. The listing of items in the quick deploy list is organized into “jobs” and identifies a path that indicates the source and destination for each job. A job is associated with one path and specifies one or more items of the source to be deployed and a schedule to deploy the specified item(s). The deployment server is configured by the administrator with permissions for specific authors to list items in the quick deploy list.
摘要:
A secondary location is configured as a recovery service for a primary location of the service. The secondary location is maintained in a warm state that is configured to replace the primary location in a case of a failover. During normal operation, the secondary location is automatically updated to reflect a current state of the primary location that is actively servicing user load. Content changes to the primary location are automatically reflected to the secondary location. System changes applied to the primary location are automatically applied to the secondary location. For example, removing/adding machines, updating machine/role assignments, removing adding/database are automatically applied to the secondary location such that the secondary location substantially mirrors the primary location. After a failover to the secondary location, the secondary location becomes the primary location and begins to actively service the user load.
摘要:
A secondary location is configured as a recovery service for a primary location of the service. The secondary location is maintained in a warm state that is configured to replace the primary location in a case of a failover. During normal operation, the secondary location is automatically updated to reflect a current state of the primary location that is actively servicing user load. Content changes to the primary location are automatically reflected to the secondary location. System changes applied to the primary location are automatically applied to the secondary location. For example, removing/adding machines, updating machine/role assignments, removing adding/database are automatically applied to the secondary location such that the secondary location substantially mirrors the primary location. After a failover to the secondary location, the secondary location becomes the primary location and begins to actively service the user load.
摘要:
A history of locations of tenant data is maintained. The tenant data comprises data that is currently being used by the tenant and the corresponding backup data. When a tenant's data is changed from one location to another, a location and a time is stored within the history that may be accessed to determine a location of the tenant's data at a specified time. Different operations trigger a storing of a location/time within the history. Generally, an operation that changes a location of the tenant's data triggers the storing of the location within the history (e.g. upgrade of farm, move of tenant, adding a tenant, load balancing of the data, and the like). When tenant data is needed for an operation (e.g. restore), the history may be accessed to determine the location of the data.