Post-installation setup for Data Product Hub

To finish setting up the Data Product Hub service after installation, complete the mandatory post-installation tasks.

Mandatory tasks for setting up Data Product Hub

Required role
The Cloud Pak for Data cpadmin role is required to complete these tasks.

After installing Data Product Hub, the user with the admin or cpadmin role must log in to initialize Data Product Hub. When the cpadmin logs in for the first time, Data Product Hub is automatically initialized.

Initialization performs several automatic steps to configure Data Product Hub for use by your data community. A catalog is created with associated sample data products, delivery methods, workflows, and domains. The internal functional user is configured to make API calls.

Next steps

After the cpadmin logs in for the first time to initialize Data Product Hub, the next steps are:

  1. If you are not viewing Data Product Hub, then switch to the Data Product Hub experience. Click the Switch platform icon switch platform icon next to your avatar and select Data Product Hub.

  2. Add users to Cloud Pak for Data in Access control. Then add members to the Data Product Hub community and assign collaborator roles in Administration>Configurations and settings>Manage community.

Data Product Hub requires that all users have a collaborator role. Collaborator roles are assigned by the Data Product Hub Administrator from the Manage community page. Follow these steps to open Manage community:

  1. Switch to the Data Product Hub experience if you need to.
  2. From the main menu, select Administration>Configurations and settings.
  3. Select the Data Product Hub tile and then Manage community.

Configuring an external route to the Flight service

If you plan to use the Flight service as a delivery method for data products, you must configure an external Flight route on your cluster before installing Data Product Hub. For details, see Configuring an external route to the Flight service in the IBM Software Hub documentation.

After the external route is configured, you must bind the route to Data Product Hub. If you prefer to use the OpenShift console, see How to configure an external Flight URL route to deliver data products with Data Product Hub.

Steps for binding the external Flight service URL route to Data Product Hub from the command line:

  1. Open the terminal and log into the cluster where the Data Product Hub service is deployed. Execute: 
sudo su -
  1. Find the podname:
kubectl get pods -n <<operator-namespace>>| grep "data-product-operator"

Two pod names are returned: ibm-cpd-data-product-operator-xxxxx and ibm-cpd-data-product-operator-catalog-xxxxx. You will access the pod that does NOT contain "catalog".

  1. Access the operator pod:
kubectl exec -it <ibm-cpd-data-product-operator-xxxxx> -n <<operator-namespace>> /bin/bash

  1. Locate the update_fcrouteurl.yaml script in the /opt/ansible/installed-version/roles/data-product directory where installed-version is the Cloud Pak for Data version.

  2. Execute the update_fcrouteurl.yaml script:

ansible-playbook update_fcrouteurl.yaml -e "fcservicens=wkc fcservicename=wdp-connect-flight"

Ensure that fcservicens is the correct namespace for the wdp-connect-flight service.

  1. Restart the dataproduct-api service to bind the new external routeURL:
kubectl rollout restart deployment dataproduct-api -n wkc

Learn more