Phase 2: Adding IBM Z Systems to the Ironstream Configuration Tool - ironstream_for_micro_focus_universal_discovery

Phase 2: Adding IBM Z Systems to the Ironstream Configuration Tool - ironstream_for_micro_focus_universal_discovery - 7.4

Ironstream for Micro Focus® Universal Discovery for IBM Z® Administration

Product type

Software

Portfolio

Integrate

Product family

Ironstream

Product

Ironstream > Ironstream for Micro Focus® Universal Discovery

Version

7.4

Language

English

Product name

Ironstream for Micro Focus Universal Discovery for IBM Z

Title

Ironstream for Micro Focus® Universal Discovery for IBM Z® Administration

2022

First publish date

2007

Last updated

2023-08-23

Published on

2023-08-23T16:22:42.216000

Start the Ironstream for Micro Focus Universal Discovery for IBM Z Configuration Tool web interface by entering the following from a web browser on the Ironstream UCMDB Probe server:

http://localhost:9853

Enter a fully qualified domain name for the mainframe LPAR in the New node name box to register the new node. The new node will be added to the list of Ironstream processes.

Check the box on the left of the Node Name and Click the Edit button to modify the parameters for the processes which will run for this new node. The port numbers will allow an Ironstream connection to all necessary processes, but you may change these values if there is a conflict with other software running on your system. If you want to use TLS, you will need to configure how Ironstream is to access certificate information. You can follow the steps below to do this.

If you do not need to use a secure connection to your z/OS system then uncheck the 'TLS' box and leave the Windows Certificate Store and the PKCS#12 fields empty.

Parameter	Description
Hostname	The network name of the managed IBM Z LPAR node. The name may need to be fully qualified, depending on your DNS setup. Create a separate node for each LPAR.
Host command port	A port reserved for Ironstream inter-process communications on the UCMDB Probe server. The default port is 6101, and must be unique on the UCMDB Probe server. It will increase automatically to avoid port conflicts as other IBM Z nodes are added. Valid Value: Any unused port number on the UCMDB Probe server Note: The port must be open for and outbound traffic.
Message port	The TCP/IP port on the IBM Z LPAR that the UD Probe server connects to, to receive messages. The default port number is 6106. Valid Value: Available mainframe TCP/IP port (greater than 1024). Note: The port must be in a Listening status on the IBM Z LPAR. Note: This port number MUST match the first number on the TCP parameter card for the started task on the mainframe agent. (See the TCP card definition in the Installation Guide.)
Command port	The TCP/IP port on the IBM Z LPAR that the Ironstream UD Probe server connects to, to send commands. The default port number is 6107. Valid Value: Available mainframe TCP/IP port (greater than 1024). Note: The port must be in a Listening status on the IBM Z LPAR. Note: This port number MUST match the second number on the TCP parameter card for the started task on the mainframe agent. (See the TCP card definition in the Installation Guide.)
Command timeout	The amount of time (in seconds) to wait for a response from a IBM Z command. The default is 30 seconds.
Windows Certificate Store common name	This is the common name (CN) of a leaf certificate that has been imported into the Windows Certificate Store. See the Installation Guide for details of how to import a certificate and find the Common Name required for this field. If you set a common name in this field then any information in the PKCS#12 fields is ignored.

Operator ID	Defines the name of the NetView/390 autotask ID under which commands may be issued. If NetView/390 is in use on the mainframe, this name must match the name of the autotask defined in the NetView/390 DSIPARM(DSIOPF) member. The default is EVOAUTO1.
License key	The license key for this mainframe node. Each mainframe managed node requires a unique key to connect to the Ironstream management server, although the same key may be used for multiple LPARs of the same physical IBM Z system. See the Installation Guide for information on acquiring a license key.
Max log size (kilobytes)	Maximum size (in Kilobytes) of any file which is created on the Discovery probe server by Ironstream for logging or debug purposes. The default is 3000 (3MB).
Log level	Granularity of log tracing. Valid values are: info debug warning error The default is info.
TLS	If selected, enables TLS encryption between the server and the mainframe agent. See the Installation Guide for instructions on setting up a TLS encrypted connection.
PKCS 12 file	The full path and filename of the PKCS #12 file that was exported from the mainframe when using TLS encryption. See the Installation Guide for instructions on setting up a TLS encrypted connection.
PKCS 12 password	The password of the PKCS #12 file that was exported from the mainframe when using TLS encryption. See the Installation Guide for instructions on setting up a TLS encrypted connection.

Click Save to close the Node Editor window, then select the added node and click the Start button to start the Ironstream processes for the node.