The administration of Hybrid Data Pipeline involves the management of three basic resources common to any Hybrid Data Pipeline environment: tenants, user accounts, and data sources.

A Hybrid Data Pipeline system administrator can develop either a single-tenant or multitenant architecture. In a single-tenant architecture, the system administrator creates user accounts in the default system tenant. In a multitenant architecture, the system administrator first creates one or more child tenants in the system tenant. Then, the system administrator may create user accounts in either the system tenant or any one of the child tenants. The user accounts that reside in one tenant are isolated from those in other tenants.

Once a tenant architecture has been established, a system administrator can provision user accounts in two general ways. First, an administrator can provision an account such that the user has direct access to the Hybrid Data Pipeline service. In this case, the administrator can provision the user to create, manage, and query data sources. The administrator can also promote or restrict access to Hybrid Data Pipeline features, such as the Web UI, the SQL Editor, and the Management API.

Alternatively, an administrator can provision an account such that user access is limited to queries against a data source. For example, an administrator may want to provision user access such that a user can run an OData application against a backend data store. In this scenario, the administrator creates the data source and supplies the end user with connection information for the data source. The end user can query the data store with the connection information supplied, but he or she does not have access to the connection information stored in the data source definition or to Hybrid Data Pipeline itself.

Beginning with information on initial log in, the topics in this section provide information on administering Hybrid Data Pipeline and configuring Hybrid Data Pipeline features.