Start the Ironstream for ServiceNow Discovery for IBM Z Configuration Tool web interface by entering this from a web browser on the Ironstream proxy server:
http://localhost:9853
- At the bottom of the screen is a "Node Configuration" section, which contains a text box with the default text “New node name”. If necessary, enter a fully qualified domain name for the mainframe LPAR (for example, bluebox1.mycompany.com) in the “New node name” box to register the new node. The new node will be added to the list of Ironstream processes.
-
From the list of Ironstream
processes, check the box to the left of the Node Name that corresponds to your
mainframe LPAR, then click the Edit button to modify the parameters for
the processes which will run for this new node. A dialog box will appear. The
parameters will initially be populated with default values. The default values 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.
Parameter Description Hostname The network name of the managed z/OS 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. The default port is 6101, but it will increase automatically to avoid port conflicts as other z/OS nodes are added. Change the recommended number, if necessary, to prevent a conflict with other applications' known port usage on the Discovery probe server. Command timeout The amount of time (in seconds) to wait for a response from a z/OS command. The default is 30 seconds.
Note: We recommend increasing this value, especially for busy production systems. In our experience 600 seconds is a reasonable timeout value. See the section Customizing Script Timeout Values below for finer control over this option.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. Message port The TCP/IP port that the Master Message Server connects to on the z/OS managed node to receive messages. The default port number is 6106. This port number MUST match the first number on the TCP parameter for the started task on the mainframe agent. For more details, see the TCP parameter definition in the Installation Guide. 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). Command port The TCP/IP port that the Command Server connects to on the IBM Z managed node to send commands. The default port number is 6107. This port number MUST match the second number on the TCP parameter for the started task on the mainframe agent. For more details, see the TCP parameter definition in the Installation Guide. 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. Log level Granularity of log tracing.Valid value Description error Only error messages are written. warning Error and warning messages are written. info All messages except debug/trace messages are written. debug All messages are written. Changes to the log level value only take effect after the node has been restarted (click stop and then start in the configuration tool).
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. LPAR Owner Username This value should only be populated when a domain-separated ServiceNow instance is being used. If the ServiceNow instance is domain-separated and Ironstream records are to be domain-separated, then this field should contain the ServiceNow username of the MID server user running Discovery for this LPAR. CPC Owner Username This value should only be populated when a domain-separated ServiceNow instance is being used. If the ServiceNow instance is domain-separated and Ironstream records are to be domain-separated, then this field should contain the ServiceNow username of the MID server user running Discovery for this LPAR. - Click Save to close the Node Editor window.
- Select the new node by checking the box to the left of the its Node Name, or clicking the row corresponding to that node, then click the Start button to start the Ironstream processes for that node.
Use the Ironstream Configuration Tool to start and stop the processes for each defined z/OS node. To stop the Ironstream processes, click the row of each node that you wish to stop then click the Stop button.