The Hybrid Data Pipeline installer supports installation of the server in GUI or console mode.
You can deploy Hybrid Data Pipeline on a standalone node, or on one or more nodes behind a load balancer.
Important: There is currently no migration path from a standalone deployment to a load balancer deployment. Therefore, a standalone deployment is not recommended for environments where scaling up the service may be desired. A standalone node deployment is also not recommended for security and system recovery purposes. If you want to move from a test environment to a production environment, you should begin by deploying Hybrid Data Pipeline on a single node behind a load balancer. When deploying the service on a single node behind a load balancer, you can increase availability and scalability as demanded, and address security and recovery concerns as required.
If you are deploying Hybrid Data Pipeline on more than one node behind a load balancer, you must install Hybrid Data Pipeline on each node in the cluster. During the initial installation of the server, the Hybrid Data Pipeline installer writes properties files, encryption keys, and system information to the key location. When performing subsequent installations on additional nodes, you will need to specify this key location. The installer uses the files written to the key location during the initial installation to install the server on additional nodes. Hence, for installations on additional nodes, the installer bypasses prompts for load balancing, SSL, external database, and On-Premises Connector configurations.
If you are using the silent installation process to deploy Hybrid Data Pipeline on more than one node behind a load balancer, the response file generated during the initial installation must be modified to install the server on any additional nodes. For a GUI generated response file, you will need to designate the name of an additional node with the D2C_HOSTNAME option. For a console generated response file, you will need to designate the name of an additional node with the D2C_HOSTNAME_CONSOLE option. See Silent installation process for details.
You can also install Hybrid Data Pipeline on a standalone node for a 30 day evaluation period using a Docker image. An installation with a Docker image is for evaluation purposes. It cannot be upgraded to licensed installation, and it cannot be migrated to a load balancer environment. If you want to move from a test environment to a production environment, you should begin by deploying Hybrid Data Pipeline on a single node behind a load balancer with the Hybrid Data Pipeline installation program.
Note: Before proceeding with an installation of the Hybrid Data Pipeline server, you must copy the product file to a temporary directory, for example, /tmp.
If you want to install Hybrid Data Pipeline using a Docker image, see Install using a Docker image. (30 day evaluation standalone node deployment only)
If you prefer to use a Graphical User Interface (GUI), see GUI mode installation.
