This page provides a summary of enhancements and bug fixes for version 7.1.0.
On the Environment configuration page you can configuredeployment triggers on an environment. The deployment trigger causes the specified App Proc Request to run whenever a specified component imports a new version. This results in deploying the newly imported version automatically to all environments that have configured triggers.
This feature replaces the run process after version import functionality on a component.
External approval process
The external approval process is a pre-deployment process that allows or prevent the deployment from running based on the status of the external approval process. The process runs on an agent and has access to all plug-in steps. This feature can be used for or reaching out to change management systems. Access to the feature is on the Environment Configuration page under Require approvals.
Server cluster management improvements
Server to server communication now uses the new websocket communication technology. Front end servers are now displayed on the Networks tab. Additionally, connectivity status for all servers in a cluster can be viewed on the Networks tab.
Resource tree performance improvements
The performance when loading many resources has been improved.
Merge ZOS Version
Incremental ZOS versions can be consolidated into a single versions. The most recent files will be kept and older files of the same name / extension will be replaced by the most recent. Can only merge versions that follow the new ZOS package format. Where to enable: Snapshots page.
Deployment Dialog replaced by a separate page that breaks the fields up by relevance to each other. Now includes a final “review” page that lets you verify all inputs before starting your deployment. RFE = no
Enhancements to containers
The following enhancements added to HCL™ Launch containers.
- Kubernetes Operator Models for Agent, Relay, and Server
- Helm V3 support
- You can now configure the file system group ID used when accessing persistent storage required for deployment of the HCL™ Launch server, agent and agent relays. This support is important for multi-cloud environments where the persistent storage support may differ in implementation and require the use of a specific file system group ID.
- The Openshift plug-in now supports OpenShift Container Platform 4.x. In addition, new plug-in steps have been added to provide a complete integration scenario.