What's new in ZD&T V12.0.0.1?
The following new features and changes were added for ZD&T Enterprise Edition in Version 12.0.0.1.
A new installation option for Enterprise Edition
A new installer prompt verifies whether you want the 'zdt' user ID to be automatically created to run the server process. If you select n on the prompt, specify the existing user ID that you want to use to run the web server process. An upgrade from a previous version automatically sets the user ID to 'zdt'. For more information, see Installing Enterprise Edition.
Updated startServer and stopServer scripts
The startServer and stopServer scripts are renamed to startServer.sh and stopServer.sh. The scripts do not require root credentials. However, if you want to run the scripts, you must have the authority to switch to the user ID that runs the server process.
Both the startServer.sh and stopServer.sh scripts source a new script zdtee_env.sh. The new script defines the following two variables that are used by the startServer.sh and stopServer.sh scripts. The zdtee_env.sh is never modified by the installation or upgrade process.
- ZDTEE_USER
- The user ID that runs the ZD&T Enterprise Edition server process. The initial value is set based on the user ID that the installer specifies. If you want to change the value, you also need to change the file ownership of all the files in the directory /opt/ibm/zDT/Liberty/usr/servers/zDTServer/ to the user ID.
- PRIVILEGED_ZDTEE_CMD
- The command from your privileged management system. You can use the command to switch the user ID that runs the startServer.sh or stopServer.sh to the user ID that is defined in the ZDTEE_USER variable to start the server process. By default, the sudo command is used.
For more information, see Starting and accessing the Enterprise Edition web server.
Enhancements for the Enterprise Edition web interface
- Support for extracting and transferring multiple volumes simultaneously is added. When you create application images from IBM Z® components or deploy application images to a target environment, you can set the maximum volumes that you want to extract or transfer simultaneously. For more information, see Creating an application image from IBM Z components and Deploying application images.
- Support for stopping and resuming application image creation is added. When you create an application image from IBM Z components, you can stop the application image that is being created, and resume a stopped or failed application image. For more information, see Monitoring application images.
- Support for retrieving the diagnostic log files is added on the Monitor page. The log files belong to an application image that failed to be constructed as a part of extracting z/OS® volumes.
- System administration actions that occur during the deployment process can be customized on the
target environment.
- Support for changing the privileged management command is added. The privileged management command is used to elevate a non-root user ID that deploys an application image. By default, the sudo command is used. However, the command can be changed to use another system that is installed on your Linux system. The variable ${script} can be used to represent the product scripts that run during the deployment.
- Support for disabling the following automatic system administrative actions during the
deployment is added.
- Installing the required ZD&T dependencies
- Applying the ZD&T network configuration
- Configuring user settings
Note: The actions are still required for the ZD&T emulator to work properly. If you disable the administrative actions for the deployment process, ensure that the equivalent functions are enabled before you deploy an application image from the ZD&T Enterprise Edition interface.
For more information, see Configuring Target environments.