Abstract: A storage system query mechanism and corresponding techniques for implementing queries are provided. In one exemplary method, queries are processed by providing a server-side meta-model for creating queries on the server; and providing a client-side meta-model for creating queries on the client, wherein the client and the server are based on different programming languages and wherein the queries created on the client are translated from a language of the client into a language of the server for processing by the server. The query results are optionally converted to data transfer objects for presentation on the client. In an exemplary query service method, at least one base meta-model is provided having a plurality of base classes and a domain-specific injection point; and at least one domain-specific meta-model is received and injected into the base meta-model at the domain-specific injection point.

Abstract: A storage system query mechanism and corresponding techniques for implementing queries are provided. In an exemplary method, control path data in a storage array is processed by obtaining an object model (OM) data object comprising retrieved control path data upon an initial user request; storing the OM data object in a cache using one or more façade data classes; employing a refresh service to listen to refresh events that impact a validity of the OM data object, wherein the OM data object is evicted from the cache when the validity of the OM data object is impacted by one of the refresh events; and delivering the OM data object from the cache upon a subsequent user request if the OM data object remains in the cache at a time of the subsequent user request.

Abstract: A storage system query mechanism and corresponding techniques for implementing queries are provided. In an exemplary method, control path data in a storage array is processed by obtaining an object model (OM) data object comprising retrieved control path data upon an initial user request; storing the OM data object in a cache using one or more façade data classes; employing a refresh service to listen to refresh events that impact a validity of the OM data object, wherein the OM data object is evicted from the cache when the validity of the OM data object is impacted by one of the refresh events; and delivering the OM data object from the cache upon a subsequent user request if the OM data object remains in the cache at a time of the subsequent user request.

Abstract: A storage system query mechanism and corresponding techniques for implementing queries are provided. In one exemplary method, queries are processed by providing a server-side meta-model for creating queries on the server; and providing a client-side meta-model for creating queries on the client, wherein the client and the server are based on different programming languages and wherein the queries created on the client are translated from a language of the client into a language of the server for processing by the server. The query results are optionally converted to data transfer objects for presentation on the client. In an exemplary query service method, at least one base meta-model is provided having a plurality of base classes and a domain-specific injection point; and at least one domain specific meta-model is received and injected into the base meta-model at the domain-specific injection point.

Abstract: A storage system query mechanism and corresponding techniques for implementing queries are provided. Queries can be created on a client and server, where the client and the server are based on different programming languages, by providing a server-side meta-model and client-side meta-model. A base meta-model is provided having a plurality of base classes and a domain-specific injection point to allow domain specific meta-models to be injected into the base meta-model. Domain-specific query executors can be employed to process a query. Techniques are also provided for caching control path data in a storage array using one or more façade data classes and a refresh service to listen to refresh events that impact a validity of the cached data objects. Applications can optionally register domain specific query executors, object model providers and/or class loaders. Query results can be presented on a client device by providing a declarative data grid component as part of a graphical user interface.

Abstract: A device establishes access to a first set of storage devices associated with a first storage characteristic and a second set of storage devices associated with a second storage characteristic. The first storage characteristic and the second storage characteristic include at least one of a consistency characteristic or a latency characteristic. The device receives a first request to store content, and determines a storage rule associated with the content, based on the first storage characteristic and the second storage characteristic. The storage rule specifies a manner in which the content is to be stored. The device transmits first information, associated with the content, to a first storage device of the first set of storage devices, based on the storage rule. The device transmits second information, including the content, to a second storage device of the second set of storage devices, based on the storage rule.

Abstract: A system determines status of agent execution of a command in a network. The system identifies a command to be performed by an agent and issues the command to the agent for execution. The agent operates a status manager that tracks execution status of commands in the agent. The system sends status requests to the agent to determine a status of execution of the command by the agent and the agent responds and sends a status response indicating the status of the execution of the command by the agent. Applications are thus provided with current status of execution of long running commands in an agent.

Abstract: In a storage area network (SAN), different tasks may expect different types of commands for commencing execution, such as interactive or offline, and may have different formats for reporting status and completion, such as log files or message based. A framework for defining the business logic enveloped in a particular task, and providing a common manner of deploying, or enabling invocation, of the task provides consistent operator control for scheduling, monitoring, ensuring completion, and tracking errors and other events. Business logic modules are identified as commands corresponding to a task. Transactions including a set of the commands define an ordered sequence for completing the task. The operator requests a particular set of tasks, using a selection tree, and the task manager builds a corresponding execution tree to identify and map the transactions and commands of the task to the execution tree to optimize execution and mitigate redundancies.

Abstract: A client application interface, or toolkit, provides a specified, exposed set of software components, or objects, for external user access. Development of a common interface for external user applications allows a remote access object model to define the interface corresponding to a base object model. The remote access object model, therefore, defines a generic toolkit upon which a user builds a custom application to suit individual remote access needs. Development of a single remote access object model limits regressive testing and provides a known baseline of tested functionality for the remote interface without compromising the existing base object model. Limited exposure of the objects in the client application interface avoids security, integrity, and inconsistency breaches.

Abstract: A debugger mechanism that provides for debugging source code of a target by correlating messages in a log file associated with source code with corresponding lines of the source code.

Abstract: A system can analyze an application programming interface definition to automatically produce software string generator and parser software components allowing remote access to functions within the application programming interface definition by processes that are not natively compatible with the computing system environment in which the application programming interface operates. A first string generator processes can produce an encapsulated function call from a first process, such as a Java-based process, that calls a first function in a first computing environment. A second parser process operates in a second computing environment to receive the encapsulated function call and to invoke a second function call in a second process, such as a C-based process. Results from the second function call are returned to a second string generator which produces an encapsulated response that is returned to a first parser process.