Let's have a look what new functions E2E Automation provides with the new release of IBM Z System Automation V4.2 which became GA on December 2019.
Short flashback: E2E Automation has already been introduced with IBM System Automation V4.1. E2E Automation is able to automate resources between multiple sysplexes using the E2E Adapter and cross Linux platforms and other distributed systems clusters using the Universal Automation Adapter. The E2E Adapter and the Universal Automation Adapter connects z/OS and non-z/OS resources to IBM Service Management Unite (SMU). SMU is a customizable service management user interface that provides dashboards to monitor and operate Z system environments. For more details about E2E Automation in general follow this link
IBM Z System Automation version 4.2 provides enhancements for E2E Automation. These enhancements are also provided for IBM System Automation version 4.1 via APAR OA58444.New functions for SMU 1.1.7
The E2E Adapter supports new functions for SMU 1.1.7, for example
- Display group details and group members of a MOVE or SERVER group model 2
- Modify availability or satisfactory target of a SERVER group
- Show detailed resource information in the additional property list of any resource.
This information is a collection of attributes taken from INGINFO and DISPINFO command
- Show whether an application resource (APL) is a dynamic or a static resource
- Support special RACF usage for the functional user id internally used by SMU
For more details about SMU 1.1.7 follow this link
.z/OS Security Server (RACF) Key Ring
E2E Automation supports to use RACF as certificate repository for SSL communication. A key ring is a collection of certificates that identify a networking trust relationship. For E2E Automation you may define a key ring for the E2E Agent and for the E2E Adapter. The key ring for the E2E Adapter may also contain the certificate of the SMU sever. You specify the name of the RACF safkeyring in the configuration file ing.adapter.ssl.properties and inge2eagt.ssl.properties using the already existing SSL parameters. For example
eez-ssl-truststore = safkeyring:///E2EAdapterKeyring
eez-ssl-keystore = safkeyring:///E2EAdapterKeyring
For more details about how to set up RACF keyrings for SSL communication between the E2E Adapter and E2E agent and SMU follow this link
to the System Automation Knowledge Center (KC).Multiple TCP/IP Stacks
E2E Automation supports multiple TCP/IP stacks. This allows E2E Automation network isolation so that the E2E Adapter, E2E Agent and the NetView EAS adapter use a TCP/IP stack of its own. You specify the TCP/IP stack name for use by E2E Automation in a specific parameter within configuration file ingadapter.properties or inge2eagt.properties.
For more details follow this link
to the System Automation KC.Exploit MVS System Symbols
You may use MVS system symbols for certain E2E Automation parameters. For example the TCP/IP stack name or the hostname of the SMU server or the XCF group ID of the SAplex that the E2E Adapter represents:
eif-send-to-hostname = &SMUHOST.
For more details how the E2E Adapter and E2E Agent supports system symbols follow this link
to the System Automation KC.Use the MVS STOP Command
For stopping the E2E Adapter and the E2E agent it is strongly recommended to use the MVS STOP command
rather then using the shell script with the deprecated option stop. Using the MVS STOP command reduces the time to stop the E2E Adapter. The E2E automation sample policy provided by Z System Automation uses already this STOP command.