-
UBUNTU上安装ZD&T手顺
1.设置权限并解压
root@localhost:~# cd /data/zdtee/ root@localhost:/data/zdtee# chmod 755 ZDT_Install_EE_V13.0.0.0.tgz root@localhost:/data/zdtee# tar -xzvf ZDT_Install_EE_V13.0.0.0.tgz README ZDT_Install_EE_V13.0.0.0.x86_64
2.安装
root@localhost:/data/zdtee# ./ZDT_Install_EE_V13.0.0.0.x86_64 The following products can be installed, updated, or uninstalled. Select one action: 1) ZD&T Enterprise Edition A simple role-based Web utility to ease the process of creating and managing your IBM ZD&T instances. It includes features to create assets, monitor and automatically configure, install and deploy to target systems. This offering can be installed on the same system as the ZD&T Hardware-Based License Server and as the ZD&T Software-Based License Server. 2) ZD&T Software-Based License Server A server for centralized management of software-based license keys for one or more instances of ZD&T. This offering cannot be installed on the same system as ZD&T Hardware-Based License Server but can be on the same system as the ZD&T Enterprise Edition. 3) ZD&T Hardware-Based License Server A server for centralized management of hardware (USB)-based license keys for one or more instances of ZD&T. This offering cannot be installed on the same system as ZD&T Software-Based License Server but can be on the same system as the ZD&T Enterprise Edition. 4) ZD&T Emulator A platform for mainframe application demonstration, development, testing and education. It enables IBM z/OS® middleware and other z/OS software to run on Intel-compatible platforms without IBM Z® mainframe hardware. It emulates IBM Z architecture with virtual I/O and devices. It cannot be installed on the same system as the ZD&T Software-Based License Server, ZD&T Hardware-Based License Server and ZD&T Enterprise Edition.
3.选择1 <ZD&T Enterprise Edition>,1<install>
==>1 What do you want to do with ZD&T Enterprise Edition? 1) Install 2) Update 3) Uninstall ==>1 Press ENTER and read the following license agreements carefully. LICENSE INFORMATION 省略 The following replaces Items 8.2b and 8.2c: b. special, incidental, exemplary, or indirect damages or consequential damages; or c. wasted management time or lost profits, business, revenue, goodwill, or anticipated savings. Z125-5544-05 (07/2011)
4.输入y接受并同意
Do you accept the terms in the license agreements? (y/n): Do you accept the terms in the license agreements? (y/n): Do you accept the terms in the license agreements? (y/n): Do you accept the terms in the license agreements? (y/n): Do you accept the terms in the license agreements? (y/n): Do you accept the terms in the license agreements? (y/n): Do you accept the terms in the license agreements? (y/n): y
5.如果需要有需要更改的选项则输入n,否则y,因为没有license server,所以我在修改默认密码处选择n,随后删除。
Do you want a user called 'zdt' to be created automatically for running the Enterprise Edition server? (Y/n): Y Do you want to install to the /opt/ibm/ directory? (Y/n): Y Do you want to use the default port to access Enterprise Edition Server (9443)? (Y/n): Y A new installation of ZD&T Enterprise Edition will setup the web server to use HTTPS and has a default user registry containing the user 'zdtadmin' which can be used to login via basic access authentication. Refer to the Starting and accessing the Enterprise Edition web server section of the ZD&T Knowledge Center (https://www.ibm.com/support/knowledgecenter/SSTQBD) for more information on this setup and changing to use other user registry types. The default password for the 'zdtadmin' account is 'password'. Do you want to change this password? (Y/n):n
6.开始安装,看到ZD&T Enterprise Edition install was successful.代表成功
Installing ibm-java-x86-64-jre +++++ Selecting previously unselected package ibm-java-x86-64-jre. (Reading database ... 71338 files and directories currently installed.) Preparing to unpack .../ibm-java-x86_64-jre-8.0-6.11.x86_64.deb ... Unpacking ibm-java-x86-64-jre (8.0-6.11) ... Setting up ibm-java-x86-64-jre (8.0-6.11) ... Installing zdtliberty +++++ Selecting previously unselected package zdtliberty. (Reading database ... 71946 files and directories currently installed.) Preparing to unpack .../zdtliberty-5-20.0.0.6.x86_64.deb ... Unpacking zdtliberty (5-20.0.0.6) ... Setting up zdtliberty (5-20.0.0.6) ... User id zdt added to '0' group. Server zDTServer created. Installing zdtpostgresql +++++ Selecting previously unselected package zdtpostgresql. (Reading database ... 75283 files and directories currently installed.) Preparing to unpack .../zdtpostgresql-1-10.10.x86_64.deb ... Unpacking zdtpostgresql (1-10.10) ... Setting up zdtpostgresql (1-10.10) ... Installing zdtapp file +++++ Selecting previously unselected package zdtapp. (Reading database ... 88973 files and directories currently installed.) Preparing to unpack .../zdtapp-1-13.0.0.0.20201102130739.x86_64.deb ... Unpacking zdtapp (1-13.0.0.0.20201102130739) ... Setting up zdtapp (1-13.0.0.0.20201102130739) ... Installing zsystem file +++++ Selecting previously unselected package zsystem. (Reading database ... 88976 files and directories currently installed.) Preparing to unpack .../zsystem-1-13.0.0.0.20201102130739.x86_64.deb ... Unpacking zsystem (1-13.0.0.0.20201102130739) ... Setting up zsystem (1-13.0.0.0.20201102130739) ... Installing zdtserverenv files +++++ Selecting previously unselected package zdtserverenv. (Reading database ... 89014 files and directories currently installed.) Preparing to unpack .../zdtserverenv-1-13.0.0.0.20201102130739.x86_64.deb ... Unpacking zdtserverenv (1-13.0.0.0.20201102130739) ... Setting up zdtserverenv (1-13.0.0.0.20201102130739) ... Installing zdttoolsdb file +++++ Selecting previously unselected package zdttoolsdb. (Reading database ... 89041 files and directories currently installed.) Preparing to unpack .../zdttoolsdb-1-13.0.0.0.20201102130739.x86_64.deb ... Unpacking zdttoolsdb (1-13.0.0.0.20201102130739) ... Setting up zdttoolsdb (1-13.0.0.0.20201102130739) ... using curve name prime256v1 instead of secp256r1 Run the following command to start the IBM Z Development and Test Environment Enterprise Edition server: /opt/ibm/zDT/bin/startServer.sh ZD&T Enterprise Edition install was successful.
7.输入/opt/ibm/zDT/bin/startServer.sh启动web
root@localhost:/data/zdtee# /opt/ibm/zDT/bin/startServer.sh Creating zdtee postgresql database... /opt/ibm/zDT/bin/zdtee_db_handler.sh: line 44: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory Database creation success Starting the IBM Z Development and Test Environment Enterprise Edition server: sudo -H -u zdt /opt/ibm/zDT/bin/zdtee_cmd.sh start Starting server zDTServer. Server zDTServer started with process ID 2659. IBM Z Development and Test Environment Enterprise Edition can be accessed using the following URL: https://localhost:9443/ZDTMC/index.html
8.登录网页https://你的IP地址:9443/ZDTMC/index.html
注:装入ADCD前需要新建存储器
存储器注意点:- 完成以下所有步骤,以使此产品能够发现 ADCD 软件包:
- 提供存储器的必需设置。了解更多信息
- 在存储器设置页面上指定的基本目录中,创建一个标注为 adcd 的目录(如果该目录不存在)。
- 在步骤 2 中创建的 adcd 目录中,使用任何标签为您要在工具中提供的每个 ADCD 创建一个目录;例如 adcd/may2020。
- 将 ADCDTOOLS.XML 文件传输到步骤 3 中指定的目录。此文件用于描述 ADCD 到该产品的元数据。
- 在步骤 3 中指定的目录中创建一个 volumes 目录;例如 adcd/may2020/volumes。
- 将 ADCD 附带的所有卷文件传输到步骤 5 中指定的目录。
- 这些工具将自动从 ADCD 页面中的“映像”上找到随 IBM Z Development and Test Environment V11.0.0 或更高版本一起提供的任何 ADCD。
装入存储器方法
9.创建目标环境
10.创建映像
11.仿真器许可证
注:前一条帖子里说明了这里只是试验安装,所以并没有真的运行许可证服务器。这里仅是示例。
12.部署
理论上来说,再有许可证服务器的基础上,应该可行了。但是!!!
还是我最初设想的样子。一台服务器是行不通的,不能省钱!!!
加了台高配服务器,可以继续进行了。
期待许可服务器好了的样子。
-
RE: ZD&T安装基于软件的许可证服务器
在Azure上安装License Server手顺
1.修改权限并解压
Last login: Fri Apr 23 11:20:02 2021 from 119.109.97.131 [azureuser@onezos ~]$ cd /data/zdtee [azureuser@onezos zdtee]$ ls ee.md5 ZDT_Install_EE_V13.0.0.0.tgz [azureuser@onezos zdtee]$ sudo chmod 755 ZDT_Install_EE_V13.0.0.0.tgz [azureuser@onezos zdtee]$ sudo tar -xzvf ZDT_Install_EE_V13.0.0.0.tgz README ZDT_Install_EE_V13.0.0.0.x86_64 [azureuser@onezos zdtee]$ ls ee.md5 README ZDT_Install_EE_V13.0.0.0.tgz ZDT_Install_EE_V13.0.0.0.x86_64
2.使用sudo ./ZDT_Install_EE_V13.0.0.0.x86_64安装
[azureuser@onezos zdtee]$ sudo ./ZDT_Install_EE_V13.0.0.0.x86_64 The following products can be installed, updated, or uninstalled. Select one action: 1) ZD&T Enterprise Edition A simple role-based Web utility to ease the process of creating and managing your IBM ZD&T instances. It includes features to create assets, monitor and automatically configure, install and deploy to target systems. This offering can be installed on the same system as the ZD&T Hardware-Based License Server and as the ZD&T Software-Based License Server. 2) ZD&T Software-Based License Server A server for centralized management of software-based license keys for one or more instances of ZD&T. This offering cannot be installed on the same system as ZD&T Hardware-Based License Server but can be on the same system as the ZD&T Enterprise Edition. 3) ZD&T Hardware-Based License Server A server for centralized management of hardware (USB)-based license keys for one or more instances of ZD&T. This offering cannot be installed on the same system as ZD&T Software-Based License Server but can be on the same system as the ZD&T Enterprise Edition. 4) ZD&T Emulator A platform for mainframe application demonstration, development, testing and education. It enables IBM z/OS® middleware and other z/OS software to run on Intel-compatible platforms without IBM Z® mainframe hardware. It emulates IBM Z architecture with virtual I/O and devices. It cannot be installed on the same system as the ZD&T Software-Based License Server, ZD&T Hardware-Based License Server and ZD&T Enterprise Edition.
3.选择2<ZD&T Software-Based License Server>,选择1<Install>
==>2 What do you want to do with ZD&T Software-Based License Server? 1) Install 2) Update 3) Uninstall ==>1 Press ENTER and read the following license agreements carefully. LICENSE INFORMATION The Programs listed below are licensed under the following License Information terms and conditions in addition to the Program license terms previously agreed to by Client and IBM. If Client does not have previously agreed to license terms in effect for the Program, the International License Agreement for Early Release of Programs (Z125-5544-05) applies. Program Name (Program Number): IBM Z Development and Test Enterprise Edition 13.0 (Early Release) The following standard terms apply to Licensee's use of the Program. .......... c. wasted management time or lost profits, business, revenue, goodwill, or anticipated savings. Z125-5544-05 (07/2011)
4.接受并同意y
Do you accept the terms in the license agreements? (y/n): Do you accept the terms in the license agreements? (y/n): Do you accept the terms in the license agreements? (y/n): y *******************************Warning******************************* Software-based License Server needs to be a static resource in any infrastructure configuration. In a virtualized or cloud infrastructure, it does not tolerate physical moving. If the Software-based License Server is manually or automatically moved return the license before moving, acquire the license after movement, and configure the Software-based License Server again. Do you accept the above terms? (y/N): y *******************************Warning******************************* You are attempting to install the IBM ZD&T Software-based license server on virtual hardware. The licensing for IBM ZD&T is based on a hardware signature and if the underlying hardware changes then the licenses on this license server will become invalid, preventing any IBM ZD&T emulators from functioning. This scenario can happen very easily if the license server is installed on a virtual machine and it will require IBMs assistance to help resolve the problem and is a very time-consuming effort, sometimes taking up to a week to resolve. For this reason it is strongly recommended that you only install the IBM ZD&T Software-based license server on physical hardware; However, if you wish to proceed with installing on this virtual machine then press Y indicating that you have read this warning and acknowledge the consequences if the virtual machine stops working as a result of the hardware changing.
5.全部都选y
I acknowledge the above statement and agree to install on virtual hardware y/N: y Do you want the necessary Linux dependencies for the product to be installed? (y/N): y Installing dependencies ... Installation of dependencies was successful Installing +++++ Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:zpdtldk-1-10.55.05.01 ################################# [100%] Installing aksusbd pkg +++++ Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:aksusbd-8.13-1 ################################# [100%] Created symlink /etc/systemd/system/multi-user.target.wants/aksusbd.service → /etc/systemd/system/aksusbd.service. Created symlink /etc/systemd/system/multi-user.target.wants/hasplmd.service → /etc/systemd/system/hasplmd.service. Copy in hasp shared object +++++ Installing UIM +++++ Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:zpdtuim-1-10.55.05.01 ################################# [100%] To start the uimserver , using a non-root id, execute : /usr/z1090/bin/uimserverstart To generate a License request, issue command : /opt/IBM/LDK/request_license and then send the resulting file to your IBM representative. Using port 9451 IPv4 2021-04-23_22:18:19: uimserver started successfully. The installer has created the non-root user id "ibmsys1" with a generated password. Do not forget to change the password of this account
6.确认安装是否成功
[azureuser@onezos zdtee]$ rpm -qa | grep zpdtldk zpdtldk-1-10.55.05.01.x86_64 [azureuser@onezos zdtee]$ rpm -qa | grep zpdtuim zpdtuim-1-10.55.05.01.x86_64
7.更改ibmsys1密码
[azureuser@onezos zdtee]$ sudo passwd ibmsys1 Changing password for user ibmsys1. New password: BAD PASSWORD: The password fails the dictionary check - it does not contain enough DIFFERENT characters Retype new password: Sorry, passwords do not match. New password: Retype new password: passwd: all authentication tokens updated successfully.
8.生成请求的zip文件
[azureuser@onezos IBM]$ sudo /opt/IBM/LDK/request_license zPDT/LDK license request started. fingerprint status 0 The request file created is: ~/onezos_1619217288.zip Success
9.更改root密码
[azureuser@onezos /]$ sudo passwd root Changing password for user root. New password: Retype new password: passwd: all authentication tokens updated successfully. [azureuser@onezos /]$ su - Password:
10.找到生成的zip位置
[root@onezos home]# cd /root [root@onezos ~]# ls onezos_1619217288.zip [root@onezos ~]# cd /opt/IBM/LDK [root@onezos LDK]# ls chisel display_gen2_acclog LDK_runtime license query_license request_license rules.ini serverconfig serverconfig_cli update_license
11.请求服务器确认
[root@onezos LDK]# ./update_license onezos_1619217288.zip
-
Azure linux如何挂载数据磁盘
Azure linux报错:SSH2_MSG_CHANNEL_FAILURE for nonexistent channel0
原因:Azure linux报错:SSH2_MSG_CHANNEL_FAILURE for nonexistent channel0
参考:
Azure参考手册
CSDN参考1.查看新挂载的卷名,可根据容量判断Disk /dev/sdb 512G
[azureuser@onezos /]$ sudo fdisk -l Disk /dev/sda: 20 GiB, 21474836480 bytes, 41943040 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xa48a0604 Device Boot Start End Sectors Size Id Type /dev/sda1 2048 41940991 41938944 20G 7 HPFS/NTFS/exFAT Disk /dev/sdc: 64 GiB, 68719476736 bytes, 134217728 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: B8265C8F-141E-4E0B-B7DE-9DE6F75CCF40 Device Start End Sectors Size Type /dev/sdc1 1026048 2050047 1024000 500M Linux filesystem /dev/sdc2 2050048 134215679 132165632 63G Linux LVM /dev/sdc14 2048 10239 8192 4M BIOS boot /dev/sdc15 10240 1024000 1013761 495M EFI System Partition table entries are not in disk order. Disk /dev/mapper/rootvg-tmplv: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/rootvg-usrlv: 10 GiB, 10737418240 bytes, 20971520 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/rootvg-homelv: 1 GiB, 1073741824 bytes, 2097152 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/rootvg-varlv: 8 GiB, 8589934592 bytes, 16777216 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/rootvg-rootlv: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdb: 512 GiB, 549755813888 bytes, 1073741824 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes
2.分区
[azureuser@onezos /]$ sudo fdisk /dev/sdb Welcome to fdisk (util-linux 2.32.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Device does not contain a recognized partition table. Created a new DOS disklabel with disk identifier 0x15fe7954. Command (m for help): n Partition type p primary (0 primary, 0 extended, 4 free) e extended (container for logical partitions) Select (default p): p Partition number (1-4, default 1): First sector (2048-1073741823, default 2048): Last sector, +sectors or +size{K,M,G,T,P} (2048-1073741823, default 1073741823): Created a new partition 1 of type 'Linux' and of size 512 GiB. Command (m for help): p Disk /dev/sdb: 512 GiB, 549755813888 bytes, 1073741824 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x15fe7954 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 1073741823 1073739776 512G 83 Linux Command (m for help): wq The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks.
3.格式化
[azureuser@onezos /]$ sudo mkfs.xfs /dev/sdb1 meta-data=/dev/sdb1 isize=512 agcount=4, agsize=33554368 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=0 = reflink=1 data = bsize=4096 blocks=134217472, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=65535, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 [azureuser@onezos /]$ sudo blkid /dev/sda1: UUID="c357eccc-5bd5-4af3-84cb-fd068f37b6d6" TYPE="ext4" PARTUUID="a48a0604-01" /dev/sdc1: UUID="58e5db49-8935-4325-80c1-6628c0d61820" TYPE="xfs" PARTUUID="dbc4d454-142c-4c6b-b847-7c3a45697ce2" /dev/sdc2: UUID="nqwdS4-Gvs3-eccT-l4w6-e0fd-yFan-73oea9" TYPE="LVM2_member" PARTUUID="88262e85-6ced-4c85-a844-181f2963c3d6" /dev/sdc15: SEC_TYPE="msdos" UUID="F3D4-BA52" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="9a17795a-c9fe-43d3-948d-b8478d7f1bea" /dev/mapper/rootvg-tmplv: UUID="8d4f8350-fec9-465b-9c15-945032f09d8e" TYPE="xfs" /dev/mapper/rootvg-usrlv: UUID="6f701637-4bfc-4067-a1b8-ff322b287bd2" TYPE="xfs" /dev/mapper/rootvg-homelv: UUID="b8f675fe-6736-484e-b34a-edba5f85080a" TYPE="xfs" /dev/mapper/rootvg-varlv: UUID="83266738-232f-4daa-b442-a3e0bdbc1979" TYPE="xfs" /dev/mapper/rootvg-rootlv: UUID="233e5dcb-51f0-48b1-a941-e948ed6ec8ec" TYPE="xfs" /dev/sdc14: PARTUUID="15f2ea65-e018-497e-b63b-8f2feacbadfe" /dev/sdb1: UUID="4a61f98e-5d32-4f0a-9c17-1455f32558df" TYPE="xfs" PARTUUID="15fe7954-01" [azureuser@onezos /]$ cd / [azureuser@onezos /]$ ls bin boot deployTemp dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var [azureuser@onezos /]$ sudo mkdir /data [azureuser@onezos /]$ ls bin boot data deployTemp dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var
4.MOUNT新挂载的卷
[azureuser@onezos /]$ sudo mount /dev/sdb1 /data [azureuser@onezos /]$ sudo chmod 755 /data [azureuser@onezos /]$ cd /data [azureuser@onezos data]$ mkdir zdtee mkdir: cannot create directory ‘zdtee’: Permission denied [azureuser@onezos data]$ sudo chmod -R 777 /data [azureuser@onezos data]$ mkdir zdtee
-
RE: 配置目标环境
配置Linux目标环境
了解有关配置或删除Linux目标环境的步骤。
要配置Linux目标环境,请完成以下步骤:1.单击主页上的“Target environments”,或单击右上角的“设置”按钮导航到“Target environments”。
2.单击Target environments。
3.单击Target environments type的下拉菜单,然后选择“ Linux”。
4.输入可用于标识Linux环境的唯一名称。
5.选择要由ZD&T managed或Client managed的模拟器类型。 如果选择“ZD&T managed”,则ZD&T企业版将在部署过程中自动配置高级设置。 如果选择“Client managed”,则在创建部署之前,必须确保满足以下先决条件。- ZD&T模拟器已安装并配置为可与许可证服务器一起使用。
- 执行操作并运行ZD&T模拟器的用户需要具有适当的权限和特权。
Linux网络已配置为正确路由到目标仿真的z /OS。 需要Linux端口2022路由到内部IP地址上的端口22,该地址是在目标环境设置中设置的值。 首先确保您有权访问软件存储库以在RHEL机器上运行YUM命令,或在Ubuntu机器上运行apt-get命令。 ZD&T安装程序将安装所有必需的软件包。 但是,如果您不希望ZD&T安装程序安装下面列出的必需软件包,则需要先安装这些软件包,然后再启动ZD&T安装程序。
RHEL: yum -y install iptables yum -y install ftp yum -y install libstdc++.i686 yum -y install perl yum -y install zip yum -y install unzip yum -y install gzip yum -y install bc UBUNTU: apt-get -y install iptables dpkg --add-architecture i386 apt-get -y update apt-get -y install libc6:i386 libncurses5:i386 libstdc++6:i386 lib32z1 lib32stdc++6 apt-get -y install ftp apt-get -y install perl apt-get -y install zip apt-get -y install unzip apt-get -y install gzip apt-get -y install bc apt-get -y install libasound2 apt-get -f install 注意:默认情况下,在RHEL 7.4和7.5上'nc'命令不可用。 由于在开始部署到目标环境之前需要使用“ nc”命令来通过验证,因此丢失的“ nc”命令可能会导致连接失败。 要安装该命令,请运行以下命令。 yum -y install nc
- 执行操作并运行ZD&T模拟器的用户需要具有适当的权限和特权。
#新建zpdt用户组 addgroup zpdt #新建用户添加到apdt组里,新建/bin/bash ibmsys1,更改密码 sudo useradd -m -g zpdt -s /bin/bash ibmsys1 sudo passwd ibmsys1 给ibmsys1权限 ibmsys1 ALL = (root) NOPASSWD: ALL
- Linux网络已配置为正确路由到目标模拟器的z /OS。 需要Linux端口2022路由到内部IP地址上的端口22,该地址是在目标环境设置中设置的值。
注:为了使其他系统与您的模拟z / OS通信,您需要配置模拟环境以确保可以访问该模拟环境。 唯一的要求是将端口号路由到模拟的z / OS上的端口22。 要路由的端口号是在ZD&T Web服务器上配置源系统时将指定的端口号。
iptables --table nat --append POSTROUTING --out-interface eth1 -j MASQUERADE iptables --table filter --append FORWARD --in-interface tap0 -j ACCEPT iptables --table filter -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -A PREROUTING --table nat -i eth1 -p tcp --dport 2022 -j DNAT --to 10.1.1.2:22 iptables -A FORWARD -p tcp -d 10.1.1.2 --dport 2022 -j ACCEPT 注: eth1是网络接口名称的示例。 要查找可用的网络接口,请运行命令 ifconfig,ip -o address show等。 2022是将路由到端口22的端口号。 10.1.1.2是网络接口tap0的IP地址,可以通过运行命令find_io找到它。
6.输入合格的主机名和Linux环境的SSH端口号。
通过以下方式之一添加Linux目标环境:- 清除Adjust advanced settings选项,然后单击Add a target environment以将目标环境保存到Enterprise Edition资源库。
- 启用Adjust advanced settings选项。 然后,完成以下可选步骤:
- 修改要同时提取和传输的卷数。
- 选择您是否具有对Linux目标环境的root访问权限。(ibmsys1已经设置好root权限)
- 选择是否要在部署期间安装所需的Linux软件包。 (已经配置好就选择clear)
- 选择是否要在部署期间配置Linux用户设置。(已经配置好选择clear)
- 指定模拟的z / OS IP地址。
- 选择是否要通过更改默认的TCP和UDP端口转发和重定向规则来将Linux操作系统路由规则修改为模拟的z / OS。 (注1:对于从Linux重定向到z / OS的端口,请输入路由到z / OS的其他端口的端口。 例如2022> 22。 另外,TCP端口规则需要规则2022> 22。 )(注2:如果选择clear,确保手动配置好)
- 单击Add a target environment,将目标环境保存到Enterprise Edition资源库。
-
RE: 配置目标环境
配置Docker目标环境
了解添加可运行Docker的目标环境的步骤,以部署运行ZD&T模拟器的容器。
在添加Docker目标环境之前,请确保已完成以下先决任务。
- 使用TLS加密协议将Docker守护程序配置为进行HTTPS通信。
- CA证书,服务器证书和客户端证书的文件已保存,并且运行ZD&T Enterprise Edition的浏览器可以访问证书。
- 所有Docker容器的端口映射均已就绪。
Docker目标环境要求
在正常的Docker设置中,容器映像被推送到可远程访问的Docker注册表。然后,可以通过需要使用Docker命令行实用程序(例如docker pull或docker run)运行该映像的实例来提取容器映像。
ZD&T Enterprise Edition 13.0提供了一个名为wazi-sandbox的容器映像,以在容器中运行模拟的z/OS环境。要使用容器映像,请完成以下步骤。- 使用受TLS加密协议保护的HTTPS与Docker守护程序进行通信。
- 将映像直接加载到运行容器的系统的本地Docker映像注册表中。
- 使用少量端口绑定在特权模式下从映像创建容器。包含所有持久性数据(例如卷)的Docker卷将在模拟器上运行。
启动wazi-sandbox容器后,ZD&T Enterprise Edition可以使用容器提供的功能ZD&T实例控制器来配置仿真器,获取ZD&T映像,启动仿真器并最终执行z / OS的IPL。
为了完成任务,在创建部署之前,需要完成以下初始设置。
-
配置Docker守护程序进行HTTPS通信
要将Docker守护程序配置为进行HTTPS通信,请参阅保护Docker守护程序套接字中的说明。
使用TLS加密协议将Docker守护程序配置为进行HTTPS通信后,请保存CA证书(ca.pem),服务器证书(cert.pem)和客户端证书(key.pem)的文件。 参考docker官方文档 -
规划Docker容器的端口映射
每个Docker环境最多支持五个容器。 在Docker环境中,每个容器都运行自己的模拟z / OS实例,并将为客户端分配100个端口,以供客户端访问每个模拟z / OS实例上的服务。 所有容器的整个端口集(最多五个)必须是连续的,并以100为间隔指定。 建议使用临时端口范围。
对于每个容器,以下端口映射就位:
xxy00映射到容器中的端口3270
xxy21映射到容器中的端口21(FTP)
xxy22映射到容器中的端口22(SSH)
xxy23映射到容器中的端口23(Telnet)
xxy99映射到容器中的端口8443(ZD&T实例控制器)
其中xx是千位数字,y是百位数字。
例如,如果您计划使用40000作为起始端口并配置两个Docker容器,则配置的第一个容器将使用端口40000-40099,而配置的第二个容器将使用端口40100-40199。
容器的第一个配置具有来自主机系统的端口40000-40099,该端口已分配给该容器,并具有以下端口映射:
40000 → 3270
40021 → 21
40022 → 22
40023 → 23
40099 → 8443
第二个容器将具有以下端口映射:
40100 → 3270
40121 → 21
40122 → 22
40123 → 23
40199 → 8443
添加Docker目标环境
要添加Docker目标环境,请完成以下步骤:
1.单击主页上的“Target environments”,或单击右上角的“设置”按钮导航到“Target environments”。
2.单击Add target environment。
3.单击Target environment type的下拉菜单,然后选择“ Docker”。
4.输入可用于标识Docker环境的唯一名称。
5.在“Service port section”中,指定运行Docker守护程序的系统的主机名,以及在“规划Docker容器的端口映射”中设置的Docker守护程序HTTPS端口。 使用TLS为HTTPS配置的Docker守护程序的默认端口为2376。
6.在“Port ranges”中,指定Enterprise Edition允许供应的最大容器数以及所有容器都可以使用的连续端口范围的较低端口值。 可以在配置过程中定义自定义端口映射。
7.单击Add certificates,然后上载生成的证书文件,包括CA证书,客户端证书和服务器证书的文件。 然后,单击“下一步”。
8.单击“Add a target environment”,将目标环境保存到Enterprise Edition资源库。 -
配置目标环境
目标环境页面可用于具有不同角色的所有用户。 您可以提供要将映像部署到的Docker,Linux或OpenStack云目标环境的列表。
- 配置Docker目标环境
了解添加可运行Docker的目标环境的步骤,以部署运行ZD&T模拟器的容器。 - 配置Linux目标环境
了解有关配置或删除Linux目标环境的步骤。 - 配置OpenStack云目标环境
了解配置OpenStack云目标环境的步骤。
- 配置Docker目标环境
-
配置存储服务器
存储是企业版的关键功能。 您可以使用SFTP(SSH文件传输协议)和FTP(文件传输协议)将提取的工件传输并存储在存储服务器上。
在配置存储服务器之前,需要首先安装FTP或SFTP服务器。
安装FTP服务器
要安装FTP服务器,请完成以下步骤:1.运行以下命令以安装FTP服务器。
yum install vsftpd ftp
2.启用FTP服务。
Systemctl enable vstpd.service
3.编辑/etc/vsftpd/vsftpd.conf文件
确认添加local_enable = YES write_enable = YES anonymous_enable = YES
4.创建一个FTP用户ID和密码。
useradd userid passwd userid
5.输入新密码,然后再次确认新密码。
6.启动FTP服务器。systemctl start vsftpd.service
7.检查端口21是否开启。 如果不是,请运行以下命令以启用端口21。
iptables -I INPUT -p tcp --dport 21 -j ACCEPT
安装SFTP服务器
要安装SFTP服务器,请完成以下步骤:
1.执行以下命令,查看是否安装了SSH。
rpm -qa|grep ssh
2.如果未安装SSH,请运行以下命令。
yum install openssh-server
3.打开端口22。
iptables -I INPUT -p tcp --dport 22 -j ACCEPT
- 创建目录并更改权限。
mkdir -p /data/sftp chmod 701 /data
5.添加一个组和一个SFTP用户。 然后,提供您的新密码。
groupadd sftpusers useradd -g sftpusers -d /upload -s /sbin/nologin sftpuser passwd sftpuser
6.创建用于文件传输的目录。 然后,进行所需的更改。
mkdir -p /data/sftpuser/upload chown -R root:sftpusers /data/sftpuser chown -R sftpuser:sftpusers /data/sftpuser/upload
7.在/etc/ssh/sshd_config中添加以下行。
Match Group sftpuser ForceCommand internal-sftp
8.重新启动SFTP服务。
service sshd restart
连接FTP或SFTP服务器
安装FTP或SFTP服务器之后,可以转到Enterprise Edition Web用户界面,并完成以下步骤:
1.单击主页上的“Storag”,或单击右上角的“设置”按钮导航到“Storag”。
2.选择您需要使用的SFTP或FTP。
3.输入存储服务器的合格主机名以及端口和目录。
4.输入存储服务器的凭据。
5.单击Save按钮。