Previous Next

ZD&T Enterprise Edition - Web utility installation & emulator deployment

We will continue to explore IBM Z Development & Test Environment Enterprise Edition. This time, we will focus on installing the web utility and deploying a z/OS system from an image. This tool is used to manage our emulated systems in a simple way. In addition, it also provides access by REST APIs to be able to create our own processes and automate the administration.

 

We will follow this part of the installation manual:

Also, the link to the user's manual:

 

The web tool can be installed on the same system as the license server, but in this case I will do it separately. The reason, simply, I prefer not to touch the license server, because this version is a trial and "if I break it", I will have to bother third parties to generate a new license for me.

For this reason, I have created a new virtual machine in VMware ESXi with Ubuntu Desktop 18.04.4.

 

The installation steps are the same as when we install the license server.

We copy the installation package to this machine. In my case, it is called ZDT_Install_EE_V12.0.5.0.tgz. We open a terminal and go to the path where we copied it.

We changed the permits to 775:

chmod 755 ZDT_Install_EE_V12.0.5.0.tgz

Decompress the file with the command:

tar -xzvf ZDT_Install_EE_V12.0.5.0.tgz

Run the program to do the installation:

./ZDT_Install_EE_V12.0.5.0.x86_64

 001 watermark

 

This time, we chose to install option 1.

002 watermark

 

Option 1 to install.

003 watermark

 

If we agree, we accept.

In addition, you will tell us that the proccess is going to create a user named "zdt" to run the web tool.

It will also ask us the path where to install it and if we want to use the default port, 9443. In my case, I leave everything by default.

005 watermark

 

Now, it will indicate if we want to change the user's password to access the web tool. By default, the user is "zdtadmin" and the password "password", without quotes.

In my case, I will change the password.

006 watermark

 

Once the installation is complete, we will have to start the server. We'll use the command:

/opt/ibm/zDT/bin/startServer.sh

007 watermark

 

Once started, it will indicate the link.

008 watermark

 

In my case, I use the system IP to access the server:

https://192.168.1.32:9443/ZDTMC/login.html

We'll see the login screen. We will use the user "zdtadmin" and the password that we put before.

009 watermark

 

A message will appear giving instructions in case we have to migrate our previous installation to this one. In my case, it is a new installation.

010 watermark

 

We will see the different options available. I will not explain what they all do, as they are explained in the user's manual.

If we are going to do the whole "walkthrough" to make the ADCD image display on a new system

011 watermark

 

I'm going to start with the "Image storage" option. This option is used to connect to the image "repository" (disks of the systems we want) through FTP (port 21, by default) or SSH (port 22, by default).

I don't know if the image storage can be in the same server as the web tool. In my case, I will install FileZilla Server (FTP server) in another PC for the image store (the reason is that in that PC I have more space available).

Once FileZilla Server is installed in Windows (I don't put screenshots, it's a very simple installation), I will create a user for ZD&T. I will call it "ibmsys1".

012 watermark

 

Now I will create a series of directories and store the ADCD version I have (ADCD z/OS 2.4 November 2019).

In my case the path will be "E:zdt_ftpadcdovember2019\volumes". The folder "zdt_ftp" will be the root path to be accessed by FTP. The name of the rest of the directories I have put them following the manual.

Inside the folder that contains the ADCD version ("november2019", in my case), we must save the file ADCDTOOLS.XML that we downloaded with the product. The web utility uses this file to obtain information about the volumes.

013 watermark

In the "volumes" folder I will have the system disks.

014 watermark

 

Now I will assign the folder "zdt_ftp" to the FTP user "ibmsys1".
014a watermark

 

In addition, I had to allow the incoming connection of the "FileZilla Server" application in the Windows Firewall. If I allowed the connection only to port 21, when trying to get the image data, it failed, because when entering "Passive Mode" it uses random ports (although you can define custom ports).

015 watermark

 

Windows Firewall screenshot.

016 watermark

 

Now in the ZD&T web tool, let's go to the "Image storage" option.

017 watermark

 

Check the option "File Transfer Protocol" (FTP) and fill in the data.

Save and test the connection. The message "Connection is successful!" should appear.

018 watermark

 

We return to the main screen and enter the "ADCD" option on the right. Also, we could go directly to the option on the left, but the option on the right explains how to distribute the volumes so that it works properly (which we did above with the Windows folders: E:\zdt_ftp\adcdovember2019).

019 watermark

 

We check that we have done the steps correctly and click on "ADCD IMAGE".

020 watermark

 

Here we will choose the ADCD version from which we will create the image. I was surprised that it allows us to select components that we want to include or not.

As I want this system to take little space (due to space issues), I will choose only the z/OS and z/OSMF system. Then, we will press the "Create image" button.

021 watermark

 

022 watermark

 

A message will appear confirming the creation.

023 watermark

 

Go to "Emulator Licenses" to define the license server.

024 watermark

 

We put the IP of the license server (if we have it installed in the same system as the web utility, we can put 127.0.0.1).

025 watermark

 

The next step is to define the target system, that is, the system where the emulator and the created image will be installed, but first we must install an SSH server in the target machine.

In my case, I have created a new system using the same Ubuntu 18.04, but...

VERY IMPORTANT! The language of the target system must be ENGLISH.

If the system is not in English, when deploying the images on the target system, we will have errors of the type:

[10/08/20 23:36:36:239 CEST] 0009bae0 W Unexpected exception.

[10/08/20 23:48:52:225 CEST] 0009bd63 E  is not a supported CPU architecture.

[10/08/20 23:48:52:537 CEST] 0009bd63 com.ibm.zdt.rest.v1.services.BaseJPAService                  E [ZDT-LOG-SEVERE] deployLinuxValidation exception: For input string: ""

 

This happens because the application launches commands and waits for the message in English.

026 watermark

 

Then I installed the SSH server using the command:

apt-get install openssh-server

027 watermark

 

Once installed, we can check that we access it using the "PUTTY" utility.

028 watermark

 

In my case, I will use a root user on the target machine to distribute the volume on the target system. It is necessary to create the "ibmsys1" user on the target machine. In addition, you must create the group "zpdt" and assign the user "ibmsys1" to this group.

Create the group "zpdt".

addgroup zpdt

 

Create user "ibmsys1". In addition, we assign you to the group "zpdt". This command automatically creates the directory "/home/ibmsys1".

useradd -m -g zpdt -s /bin/bash ibmsys1

passwd ibmsys1

029 watermark

 

As I will use the ibmsys1 user to do the deployment, we must give him "sudo" permissions without password.

There are two options:

  • The fast, but less secure one:

ibmsys1 ALL = (root) NOPASSWD: ALL

 

  • The correct one is to give permissions to the scripts you will use:

ibmsys1 ALL=(root) NOPASSWD: /bin/chown root /home/ibmsys1/zdt/zdtInstall/zdt_modify_files_byRoot.sh, /home/ibmsys1/zdt/zdtInstall/zdt_modify_files_byRoot.sh, /home/ibmsys1/zdt/zdtInstall/zdt_install_dependencies_byRoot.sh, /home/ibmsys1/zdt/zdtInstall/zdt_config_user_byRoot.sh, /home/ibmsys1/zdt/zdtInstall/zdt_install_product_byRoot.sh, /home/ibmsys1/zdt/zdtInstall/zdt_config_network_byRoot.sh, /home/ibmsys1/zdt/zdtInstall/zdt_cleanup_byRoot.sh, /bin/chown ibmsys1 /home/ibmsys1/zdt/zdtInstall/zdt_env.sh,/home/ibmsys1/zdt/zdtInstall/zdt_env.sh, /bin/chown ibmsys1 /home/ibmsys1/zdt/zdtInstall/zdt_start.sh, /home/ibmsys1/zdt/zdtInstall/zdt_start.sh, /bin/chown ibmsys1 /home/ibmsys1/zdt/zdtInstall/zdt_ipl.sh,/home/ibmsys1/zdt/zdtInstall/zdt_ipl.sh

 

NOTE: There must be no line breaks. Replace "/home/ibmsys1" with your deployment directory.

IMPORTANT: The last six commands are mandatory in order to stop and start the system automatically.

We should include this in "/etc/sudoers".

Command:

visudo

030 watermark

 

We must put the whole sentence on the same line. Save (Control+O) and exit (Control+X).

031 watermark

 

Go back to the main page of the web utility and click on "Target environments".

032 watermark

 

Click on "Add target environment".

033 watermark

 

The type of environment will be Linux.

034 watermark

 

We label the server, the IP and the SSH port (default 22). Select "Set advanced values".

035 watermark

 

In "Privilege Management Mandate Syntax" we chose "sudo". The rest of the options are left by default.
036 watermark

 

On the last screen, it will ask for the IP of the emulated z/OS. Set one that matches your configuration.

In my case, I will leave the default one and change it later because if we put a wrong IP we can have problems with the display of the image.

ATTENTION: During the deployment, the IP configuration of the system will be changed, if we put a wrong configuration, we will not connect with the license server and the z/OS system will not start.

The deployment will be stopped with no possibility to do anything, we will have to restart the web utility server and, possibly, the instance (in my case, reinstalling the instance).

037 watermark

 

It will be added correctly.

038 watermark

 

Return to the initial screen and enter "Monitor and Manage".

039 watermark

 

In the part of the images we can see that the image we create has the two components we chose and occupies about 151 GB.

In target environments it is important to look at the instance we have added. It must appear with the "green check". If a red check appears, it means that it is not possible to connect to the destination server (maybe because the SSH or port 22 is blocked) and the image cannot be deployed.

040 watermark

 

If during a deployment we find errors, we can download the log (messages and console) from the option in the image.

041 watermark

 

042 watermark

 

We go back to the main page and enter "Deploy".

043 watermark

 

Choose the image and target server we want (if we have several). Click on "Deploy image".

044 watermark

 

You will be asked for a login form. We can choose between credentials and certificate. In my case, credentials. As a deployment directory I will put “/home/ibmsys1”.

045 watermark

 

The password for the IBMUSER user I will use is "sys1".

046 watermark

 

I will use the following configuration. Use the parameters that suit your environment.

047 watermark

 

048 watermark

049 watermark

 

A message will appear indicating that the process has been initiated. We can check it by clicking on "Monitor".050 watermark

 

If we click on the percentage, we'll see the detail.

051 watermark

 

052 watermark

 

We can also download the log.

053 watermark

 

In my case, the first time it ended in error because I put the volumes "A4RES1" and "SARES1" decrypted and the rest of the volumes were uncompressed. It is mandatory to put the ZPD volumes ("A4RES1.ZPD" and "SARES1.ZPD") and the rest of them compressed (".gz")..

Once corrected, click on "Resume display".

 

After deploying the volumes I had another problem. The system was losing the connection to the license server. This was because I configured a wrong IP (different from the one in the previous screenshot) when I defined the target system.

054 watermark

 

NOTE: This log can be found in the target system. Path: /home/ibmsys1/zdt/log

In "zdt_start.sh.log" we'll see the console and emulator messages.

055 watermark

 

I reinstalled the system and redeployed the image. This time, it all ended correctly. The system will start up automatically.

056 watermark

 

Now we can log on to the system. The IP will be that of the target system and port 3270.

The first terminal we connect will be the console (LU 700). With the second one (LU 701) we can already connect to TSO.

057 watermark

 

We can stop the system automatically with the option shown in the image.

058 watermark

 

In my case, I couldn't run it.

059 watermark

 

Looking in the log, the error is because you cannot execute the commands

060 watermark

 

Some commands have yet to be added in "/etc/sudoers" on the target system:

/bin/chown ibmsys1 /home/ibmsys1/zdt/zdtInstall/zdt_env.sh,/home/ibmsys1/zdt/zdtInstall/zdt_env.sh

061 watermark

 

Now it will stop properly. Whenever we want, we can start the system again.062 watermark

 

To start the system automatically, we must add the following commands in "/etc/sudoers":

/bin/chown ibmsys1 /home/ibmsys1/zdt/zdtInstall/zdt_start.sh,/home/ibmsys1/zdt/zdtInstall/zdt_start.sh, /bin/chown ibmsys1 /home/ibmsys1/zdt/zdtInstall/zdt_ipl.sh,/home/ibmsys1/zdt/zdtInstall/zdt_ipl.sh

063 watermark

 

The system will now boot up properly. What I "miss" is some indication that the system is booting (some spinner or something that indicates it's in process).

I hope you found interesting this web utility to deploy the mainframe emulator and the z/OS image on new systems. 

 

 

 

 

 

View Javier Fernández García's profile on LinkedIn

LINKEDIN

 

View Javier Fernández García's profile on Acclaim

ACCLAIM

 

dinoland site logo

DINOLAND

Search

© 2015-2020 EMUFRAME