All notable changes to the Zowe Installer will be documented in this file.
- Updated ZWEWRF03 workflow to be up to date with the installed software
- app-server's uninstall-app.sh script is now available in the instance bin folder.
- zss's zis-plugin-install.sh script is now available in the instance bin/utils folder.
- A new dataset is created during instance creation. The dataset is to be used for holding ZIS plugins, as an alternative to putting the plugins inside of the ZIS loadlib which is still the default.
- New instance parameters describing ZIS are available and automatically recorded in instance.env if a new install is done via a convenience build. These parameters can be used in future automation of detecting ZIS and installing ZIS plugins
- New instance creation parameters -d or -l, -p, and -z are now available in the instance creation script for manually specifying the new ZIS parameters.
- server-bundle docker image has been optimized to greatly reduce the size without impacting the content and usability
- server-bundle docker image now runs zowe under the user "zowe", and the default mount locations of instance, keystore, and plugins directories is now within /home/zowe as a result
- You can now start ZSS independent from the Zowe Application Framework server by specifying the
LAUNCH_COMPONENT_GROUP "ZSS"
. IfDESKTOP
is specified instead ofZSS
, ZSS will still be included as a prerequisite to the Application Framework server. #1632 - Zowe instance configuration script (
zowe-configure-instance.sh
) can now skip checking for Node.js by passing in the-s
flag since Node.js may not be needed if the components to be launched don't require it. #1677 - The
run-zowe.sh
script can also skip the checking for Node.js by setting the environment variableSKIP_NODE=1
for the cases where the components to be launched don't require Node.js. - Exported the
EXTERNAL_CERTIFICATE_AUTHORITIES
variable to thezowe-certificates.env
file such that it may be used by the Application Framework server. #1742
- Moved explorer-ui-server out of explorers into new
shared
folder under Zowe Runtime Directory. It involved following PRs (zowe/zowe-install-packaging#1545), (zowe/explorer-jes#207), (zowe/explorer-ui-server#37). Thanks @stevenhorsman, @nakulmanchanda, @jackjia-ibm - Created
zowe-setup-keyring-certificates.env
and removed the overloaded properties fromzowe-setup-certificates.env
to try and clarify the user experience when setting up certificates in the keyring and USS keystore modes. #1603
- Allow the user to verify the authenticity of a Zowe driver. The script
zowe-verify-authenticity.sh
will check that a ZoweROOT_DIR
for an installed release matches the contents for when that release was created, which assists with support and troubleshooting. To verify pre-1.14 releases, the script and its associated code are available separately (see #1552). For more information, see the new topic Verify Zowe Runtime Directory that describes the operation of the script. - Allow multiple domains (names/IP Addresses) when generating certificates. This also includes SMP/E
HOLDDATA
for the affected functionZowe Configuration
. #1511 - Included z/OSMF workflows for Zowe z/OS configuration. #1527
- Added warning if
ZWESVSTC
runs under user IDIZUSVR
. #1534 - [Docs] Changed the documentation to say that SZWEAUTH PDSE load library members should not be copied elsewhere, but instead that the original installation target SZWEAUTH PDSE should be APF-authorized and used as the runtime load library. This also includes SMP/E
HOLDDATA
for the affected functionSTC JCL
as well as changes to topics Installing and configuring the Zowe cross memory server (ZWESISTC) and Installing and starting the Zowe started task (ZWESVSTC). - [Docs] Added a new topic Installing and configuring Zowe z/OS components using scripts.
- Updated zowe-configure-instance upgrade to update ROOT_DIR #1414
- Update port validation logic to reduce false negatives #1399
- Update install and configure to tolerate ZERT Network Analyzer better #1124
- Edit default plugin references to point to $ROOT_DIR env var
2020-05-08 Timothy Gerstel [email protected]
-
Set up SSO in a standard install of Zowe via new environment variables set in zowe-setup-certificates.env
-
Automate conversion of APIML public key and storage within PKCS#11 token
-
When the hostname cannot be resolved use the IP address instead. This covers the scenario when the USS
hostname
command returned a system name that wasn't externally addressable, such asS0W1.DAL-EBIS.IHOST.COM
which occurs on an image created from the z/OS Application Developers Controlled Distribution (ADCD). -
Separate zss component from app-server component