You may need to integrate data store connectors or authentication plugins to maintain your Hybrid Data Pipeline cluster.

Update a DataDirect connector

A data store connector is the underlying connector Hybrid Data Pipeline uses to connect to a data store. The Hybrid Data Pipeline product package uses DataDirect JDBC drivers as the underlying connectors that make connectivity to data stores possible. For details, refer to Updating data store connectors.

Take the following steps to update a DataDirect driver in a cluster.

Note: You must first obtain the JDBC driver jar file for the data store connector you are updating from a Progress Software representative.
  1. Open your command-line interface.
  2. Copy the DataDirect driver to the dddrivers folder in the shared file location.

    kubectl cp drivers/ddpostgresql.jar hdp-hdpserver-0:hdpshare/dddrivers --namespace namespace-value

  3. Restart the cluster by running the kubectl delete command on each pod. After it is deleted, each pod is restarted based on the Helm chart configuration. For example:
    
# Restart the first pod
kubectl delete hdp-hdpserver-0

# Restart the second pod
kubectl delete hdp-hdpserver-1

# Restart the third pod
kubectl delete hdp-hdpserver-2

Add a third-party connector

Hybrid Data Pipeline supports the use of third-party JDBC drivers. This feature gives customers the ability to integrate data stores for which Hybrid Data Pipeline does not currently have a built-in integration. For details, refer to Using third-party JDBC drivers with Hybrid Data Pipeline.

Take the following steps to add or update a third-party driver.

Note: With the exception of the MySQL Connector/J driver to use with MySQL Community Edition, third-party drivers must be validated for use with Hybrid Data Pipeline.
  1. Open your command-line interface.
  2. Copy the third-party driver to the drivers folder in the shared file location.

    kubectl cp drivers/mysql-connector-j-8.0.33.jar hdp-hdpserver-0:hdpshare/drivers --namespace namespace-value

  3. Restart the cluster by running the kubectl delete command on each pod. After it is deleted, each pod is restarted based on the Helm chart configuration. For example:
    
# Restart the first pod
kubectl delete hdp-hdpserver-0

# Restart the second pod
kubectl delete hdp-hdpserver-1

# Restart the third pod
kubectl delete hdp-hdpserver-2

Add a Java authentication plugin

Hybrid Data Pipeline supports external authentication services through a Java authentication plugin. For details, refer to Integrating external authentication with a Java plugin.

Take the following steps to add a Java authentication plugin to the cluster.

  1. Open your command-line interface.
  2. Copy the plugin to the plugins folder in the shared file location.

    kubectl cp plugins/auth-plugin.jar hdp-hdpserver-0:hdpshare/plugins --namespace namespace-value

  3. Restart the cluster by running the kubectl delete command on each pod. After it is deleted, each pod is restarted based on the Helm chart configuration. For example:
    
# Restart the first pod
kubectl delete hdp-hdpserver-0

# Restart the second pod
kubectl delete hdp-hdpserver-1

# Restart the third pod
kubectl delete hdp-hdpserver-2