You may deploy Hybrid Data Pipeline using the installation program on a host Linux machine, or you may deploy the service as a Docker container using the Docker image. If you are using the installation program, you will be prompted for configuration information. If you are deploying Hybrid Data Pipeline as a Docker container, you will provide configuration information as configuration properties in the hdpdeploy.properties files or as environment variables in the docker run command.

Before you proceed with deploying the service, you should familiarize yourself with available deployment configurations. The following table provides summary descriptions with links to detailed information.

Table 1. Deployment configurations
Configuration Description
Server hostname The hostname of any machine running the service.
Access ports Ports that must be available on server hosts.
System database The system database is used to store system and account information.
Note: Hybrid Data Pipeline supports failover when an Azure SQL Database is used as a system database.
Shared files and the key location The shared files and key location is used to store supporting files such as encryption keys. An internal key location option is available for single node deployments that do not use a load balancer.
Load balancer configuration A load balancer is required for cluster deployments. A load balancer may also be used in a single-node deployment. A load balancer offers availability and scalability that is not otherwise available. Network and cloud load balancer configurations are supported.
Load balancer hostname The hostname or IP address of the machine where the load balancer is running.
Default account credentials You must specify passwords for the default d2cadmin and d2cuser accounts.
SSL configuration Deployments that do not include a load balancer require SSL termination at the server. Deployments that use a load balancer allow client-side and server-side SSL configurations.
On-Premises Connector deployment configuration The On-Premises Connector is a component that enables on-premises connectivity.
Client application configuration JDBC, ODBC, and OData connectivity are supported. A driver must be installed for JDBC and ODBC connectivity. OData connectivity does not use a separate middleware component.
FIPS (Federal Information Processing Standard) Hybrid Data Pipeline can be configured to support FIPS (The Federal Information Processing Standard).
JRE support and integration Hybrid Data Pipeline can be configured to use an external JRE.
Importing data store SSL certificates Hybrid Data Pipeline can be configured to communicate with data stores that use less-well-known SSL certificates.
IP address whitelist deployment configurations Depending on your deployment scenario, you may be required to run a silent installation and configure additional settings to use IP address whitelists.
Branding the Web UI Hybrid Data Pipeline supports branding of the Web UI with branding information like logo, colors, icons, etc., using the CSS and properties files provided as samples.
Log management A central location for logs and the log levels for several services may be configured.