Table of contents

Install Watson Studio Local by command line and configuration file

As an alternative to the web browser UI installation, you can automate the Watson Studio Local installation by creating a configuration file named wdp.conf that will complete all of the parameters. The file must be in the same directory as the installation package before you run the installation, and the installation package must be in the installer files partition.

Requirement: Before you install Watson Studio Local, ensure that your servers meet all of the system requirements.

To install Watson Studio Local by configuration file, complete the following steps:

  1. Download the Watson Studio Local installation package to the first master node of your dedicated Watson Studio Local cluster.
  2. Move the installation package to the installer files partition you created (you cannot install from any path that is mounted as /), and make the installation package executable by entering chmod +x <installpkg>.
  3. If you already have a wdp.conf file, put it in the same directory as the installation package. To generate a new wdp.conf template, run the installation with parameter --get-conf-user (for a sudo user) or --get-conf-key (for an SSH key).
    • For a six or more node installation, no further parameters are required.
    • For a three, four, or five node wdp.conf template, add the --three-nodes parameter.
    Tip: Use the --help parameter for assistance.
  4. After wdp.conf is generated, you can customize the parameters. Ensure that every field is completed. To use your own load balancer for the HA cluster instead of a proxy IP, comment out the virtual_ip_address= line in the wdp.conf file and insert the new line: load_balancer_ip_address= or alternatively, the load balancer's fully qualified domain name in the new line load_balancer_fqdn=.
    Requirement: The load balancer must be configured before installing Watson Studio Local to forward traffic for port 6443 and 443 to all three control nodes (or master nodes) with persistent IP round robin for the cluster to function properly.
  5. Optional: To automatically install add-ons such as SPSS Modeler or H2O Flow, create a new addon-packages sub-directory in the same directory as the installer files. Download the installation package TAR files into the addon-packages sub-directory. Later, the installer will prompt for confirmation to install those add-ons. Restriction: This method does not work for the Watson Explorer oneWEX add-on.
  6. In /etc/selinux/config, ensure SELINUX=enforcing or SELINUX=permissive for Watson Studio Local to install. POWER requirement: Ensure that all of the nodes use container-selinux version 2.21 or later before you install Watson Studio Local.
  7. Run the installation package with the --extract-pre-install-scripts parameter to extract the pre-installation scripts for Watson Studio Local. RHEL cluster only: You can automatically install an RHEL docker on each node (requires a minimum of 200 GB raw disk) by completing the following steps on each node in the cluster:
    1. Enable a Red Hat repo for package installation on each node.
    2. Enable the extras repo on each node so docker can be installed, for example, --subscription-manager repos --enable rhel-7-server-extras-rpms.
    3. Ensure that there is a raw disk available (200G or more) on each node that has no partitions and no file systems. You can use wipefs --all --force /dev/xxx to prepare it.
    4. Run the script you extracted on all nodes in the cluster to install docker using the RHEL repo.
  8. If you chose not to use the script and selected SELINUX=enforcing, then after installing docker complete the following steps:
    1. In the /etc/sysconfig/docker file, remove --selinux-enabled from the OPTIONS line.
    2. Enter the following command: setsebool -P docker_transition_unconfined 1
    3. Restart docker.
  9. Run the extracted pre-installation check script on each node in the cluster:
    • For a cluster with five nodes or less, run --type=3nodes on all of the nodes.
    • For a cluster that exceeds five nodes, run --type=9nodes_master on all master nodes, --type=9nodes_compute on all compute nodes, and --type=9nodes_deploy on all deployment nodes.
    The script prompts for information about your installation such as path to the installation files, location of data (for master nodes), and the subnet being used by weave (the default is You will get a pass or a fail for mandatory requirements, or a warning for issues such as cron jobs asking to make sure there are no scripts being run that might change the network configuration.
  10. Run the installation package, and ensure it detects the wdp.conf file. You will be prompted to use this file for the configuration.
  11. Accept the terms and conditions, and type in the password (if you're using the user name). If an installation step fails, you can view the log and contact IBM support. To avoid unexpected issues, make sure to resolve the issue in the log before click before you retry or skip the step.
    Tip: If you see an error during deployment of Watson Studio Local or dashboard helm charts, then do not retry or skip; instead, watch the logs by running the following command: kubectl get po --all-namespaces | grep ibmdp-assistant-deployment | awk '{system("kubectl logs -n "$1" "$2)}'.
  12. When the installation completes successfully, save the URL address for the Watson Studio Local client. Sign in as the primary Watson Studio Local administrator (default user is admin) and change the default password of password. You can toggle to both the Watson Studio Local client and administration dashboard client from the same web address.

    Context switcher for client to the admin dashboard

See set up to configure your Watson Studio Local system.