IBM Support

Connect the DataStage Designer legacy client to IBM Cloud Pak for Data

How To


Use these procedures to configure and connect the legacy DataStage Designer client to IBM Cloud Pak for Data. You can then use the Designer client to edit jobs in Cloud Pak for Data.


Configure and connect the legacy DataStage Designer client to Cloud Pak for Data. You can then use the DataStage Designer client to edit jobs in Cloud Pak for Data.


1. Configure IBM Cloud Pak for Data for use with the legacy DataStage Designer client
  1. Ensure that the Red Hat OpenShift (RHOS) client, oc, is installed on your computer (Windows or Mac). You use the oc client to access the Red Hat OpenShift cluster where Cloud Pak for Data is deployed.  You can also log in directly to the Linux Infrastructure node and use the oc client already installed there for this procedure.
  2. If you need the oc client, download the oc command line tool by following the instructions at Get Started with the CLI.
  3. Install the RHOS client tool and put the directory in which you installed the tool into your path in the OS environment.
  4. Ensure that you have an account created for you in RHOS so that you can log in and get access to the cluster. Contact the administrator of the RHOS system that is running your instance, if necessary.
  5. If required, add the IP address and host name for your RHOS system to your hosts file. On Windows, the hosts file is located in:
    For example: ibm-master master
  6. From a terminal or command window, log in to the RHOS cluster: oc login https://<openshift cluster>:port. For example:
      oc login
    Log in to Cloud Pak for Data with your RHOS credentials. If you get a message about certificates, enter Y. 
  7. Follow the instructions to configure the services in Red Hat OpenShift  3.x for use with the legacy DataStage Designer client.
2. Expose and configure legacy client access to the NodePort service on OpenShift

Red Hat OpenShift 3.x:
  1. Get the list of services by running the command:
      oc get service | grep is
    Look for is-en-conductor and is-servicesdocker in the list. The designation 'ClusterIP' should appear in the rows for those two services. 'ClusterIP' means that the service is visible only inside of the cluster. 
  2. Edit the file by running the command:
      oc edit service is-en-conductor-0
    This command will launch a vi editor to edit the service object.
    Type /ClusterIP to search for the string "ClusterIP". Change "ClusterIP" to "NodePort".  Save the file (:w) and quit editing (:q).
  3. Repeat Step 2 for the is-servicesdocker service.
  4. Retrieve the list of services again to ensure that the instances of "ClusterIP" are now changed to "NodePort". The ports are now mapped externally.
Red Hat OpenShift 4.x
  1. Enable IPv4 forwarding in infra node by adding
      net.ipv4.ip_forward = 1

    line to /etc/sysctl.conf and running "sysctl -p" command. OR by running

      sysctl -w net.ipv4.ip_forward=1

  2. Expose an external IP address to allow access to the Services tier and Engine tier using kubectl command, not oc
      kubectl expose deployment iis-services --type=LoadBalancer --name=iis-services-external -n ds
    kubectl expose service is-en-conductor-0 --type=LoadBalancer --name=iis-engine-external -n ds

    where ds means the OpenShift project name with Cloud Pak fo Data. You can find your actual project name using "oc describe pod is-en-conductor-0 | grep -i ^namespace:" command.

  3. Note the node port for Engine tier port 31538 and Services tier port 9446, you need to configure Linux packet filter rules for those ports. For instance, in the following example you need to take care of port 32160 for Engine tier connection and 30653 for Services tier connection from the DataStage thick clients.

      [root@dsopenshift-inf ~]# oc get svc | grep external
    iis-engine-external      LoadBalancer   <pending>     31538:32160/TCP,31531:31063/TCP   22h
    iis-services-external    LoadBalancer    <none>        9446:30653/TCP                    24h  
  4. Determine the worker node private IP for the Information Server Engine and Services tier pods.
    - Worker nodes: Get the INTERNAL-IP of your worker nodes by running the following command.
      oc get nodes -o wide | grep -E 'NAME|worker'
    - Determine the worker node on which is-en-conductor-0 pod and iis-services-* pod are running by running the following command. 
      oc get pods -o wide | grep -E 'NAME|is-(en-conduct|service)'
  5. Configure infra node's Linux firewall to forward the ports identified in step 3 to INTERNAL-IP of the worker nodes. In the following example, port 32160 for Engine tier connection is redirected to port 32160 on the worker node running is-en-conductor-0 pod, port 30653 for Services tier connection to 30653 on the worker node running iis-services-xxx-xxx pod. 
      iptables -t nat -A PREROUTING -p tcp --dport 32160 -j DNAT --to-destination <worker private IP>:32160
    iptables -t nat -A PREROUTING -p tcp --dport 30653 -j DNAT --to-destination <worker private IP>:30653  
    Use the masquerade command to mask the IP address of the connecting system and use the gateway IP address instead. This configuration is necessary for it to communicate back to the gateway, then to your client. 
      iptables -t nat -A POSTROUTING -j MASQUERADE
    Next, verify your iptables settings by running the following command: 
      iptables -t nat -L -v -n
3. Connect your Windows Designer client to the services and engine tier that are running on your OpenShift cluster
  1. Edit the C:\Windows\System32\drivers\etc\hosts file on your DataStage Designer client computer to add following line:
    • <infra node public IP address> is-servicesdocker is-en-conductor-0.en-cond
  2. Start the Designer client and enter the following information into the fields of the login screen:
    • Host name of the services tier: is-servicesdocker:<nodeport-for-Services-tier-port-9446>
    • User name: The user name that you use for Cloud Pak for Data
    • Password : The password that you use for Cloud Pak for Data
    • Project: Select the project that you want to work in and then change the project name path from
      IS-EN- CONDUCTOR-0.EN-COND:<nodeport-for-Engine-tier-port-31538>.

      For example, if your project is dstage1, change the project name to:
    • desginer-login-window
  3. Click Login to log in to DataStage on the Cloud Pak for Data Cluster.

Document Location


[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSHGYS","label":"IBM Cloud Pak for Data"},"Component":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
10 November 2020