HA-MX Monitor v15 · 2018. 7. 24. · Introduction Overview Halcyon HA-MX Monitor v15.0 - 4 -...

Halcyon HA-MX Monitor

v15.0 Installation Guide

Copyright

Copyright HelpSystems, LLC. All rights reserved.

www.helpsystems.comUS: +1 952-933-0609Outside the U.S.: +44 (0) 870 120 3148

IBM, AS/400, OS/400, System i, System i5, i5/OS, Power Systems, and iSeries are trademarks or registered trade-marks of International Business Machines Corporation in the United States and/or other countries.

Windows and Windows Server are registered trademarks of Microsoft Corporation in the United States and/or other countries.

Java is a registered trademark of Oracle and/or its affiliates

All other product and company names are trademarks of their respective holders. For third-party conditions and disclaimers. see the Release Notes in the Product Directory.

Introduction 4Overview ..................................................................................... 4

Compatibility ........................................................................... 4External Messaging................................................................ 4

Monitored Events ........................................................................ 5

Installation and Configuration 6Downloading the software ........................................................... 6Copying HA-MX Monitor to IBM i ................................................ 6Installing HA-MX Monitor on IBM i ............................................ 11

Installation options ........................................................... 11Product Installation display .............................................. 16Halcyon Environments..................................................... 16

Installing HA-MX Monitor...................................................... 17Authorizing HA-MX Monitor ............................................. 19Setting the Default User Profile ....................................... 20Journaling ........................................................................ 20

Launching HA-MX Monitor ................................................... 22Importing Existing Rules from Legacy versions of HA-MX Monitor............................................................................. 22

Work with User Authority........................................................... 23Parameters on the Work with User Authority display ...... 24

Using the User Authority display .......................................... 24Exporting Halcyon User Authorities ................................. 26

Table of Contents

Introduction Overview

Introduction

OverviewHalcyon HA-MX Monitor monitors the status of v5 and v7 MIMIX processes, raising alerts in response toany problems as they occur and reporting when problems have been resolved. Multiple actions can beperformed in any pre-defined sequence when a particular alert is raised and escalating actions can bedefined for persistent or recurring problems.

The monitor is capable of performing up to 999 different actions per alert; so you can perform one actionwhen a problem occurs and other actions if the problem persists.

Alerts can be passed to a Halcyon Message Console on the local system, or a Halcyon Message Consoleor an Enterprise Console on another system.

Note: The Enterprise Console runs on a PC (Windows OS) and displays messages and alerts graphically. Messages can be received from an unlimited number of iSeries machines and displayed on a single screen. iSeries messages requiring a reply can be answered directly from the Enterprise Console. Halcyon Message Communicator is required to send alerts to the Enterprise Console.

The situation is monitored in real-time on the MIMIX Status display which is designed to be left active in avisible location. Colored background text indicates the current status of each monitored MIMIX process.The display also lists outstanding problems and is updated automatically whenever the monitor rechecksthe situation. (An alert; Functioning Normally; is raised as soon as there are no outstanding problems.)

CompatibilityHalcyon HA-MX Monitor is compatible with OS/400 version V7R1M0 upwards. Please check compatibilityof later versions of OS/400 on our website FAQ section.

External MessagingMessages can be sent out to mobile phones, pagers and email using Halcyon Message Communicator(the product must be purchased separately to run this facility).

Halcyon HA-MX Monitor v15.0- 4 -

Introduction Monitored Events

Monitored EventsHalcyon HA-MX Monitor allows the following events to be monitored. All events are compatible with MIMIXv5 unless indicated (* compatible with MIMIX v7 only):

Functioning normally IFS entries not journaled on target

Apply session status Journal inspection status*

Apply session backlog Journal manager status

Cluster services status Journal entry processing time*

Container send backlog Object apply backlog

Container send processes active Object apply processes active

Collector services status* Object configuration changed

Database apply processes active Objects failed distribution

Database reader status Object retrieve backlog

Database send backlog Object retrieve processes active

Database send status Object send backlog

Data group status Object send status

DLO configuration changed Object entries held not error

Data area poller status Object entries held error

Failed object entries exist Object entries not active

File entries being repaired Object entries not journaled on source

File entries held not error Object entries not journaled on target

File entries held error Parallel access path maintenancestatus*

File entries not active Remote journal backlog*

Files not journaled on source Remote journal link status

Files not journaled on target Status send status

IFS configuration changed System manager status

IFS entries held not error System manager system 1 job status

IFS entries held error System manager system 2 job status

IFS entries not active Communications status

IFS entries not journaled on source


Installation and Configuration Downloading the software

Installation and Configuration

Downloading the softwareThese instructions ensure that you have the downloaded the latest version of HA-MX Monitor from thewebsite.

https://community.helpsystems.com/products‐and‐downloads/downloads/

Note: You must have previously registered with the website and been accepted as a genuine user in order to download software.

Copying HA-MX Monitor to IBM i

1. Depending on your browser, you may be able to access the download direct from the toolbar.

Note: Please refer to your browser documentation for assistance with this feature.

If this is not possible, navigate to the directory path to where you downloaded Halcyon HA-MX Monitor software.

2. Double-click HalcyonSolution.exe to begin the installation.

Note: Ignore any publisher verification warnings and click Run to continue.

The following welcome dialog is displayed.:


Installation and Configuration Copying HA-MX Monitor to IBM i

3. Click Next to continue and display the End User License Agreement (EULA). In order to proceed withthe installation, the terms of the EULA must be accepted.

4. Once you have scrolled through and read the full licence agreement click Accept to open the IBM iComponents dialog. This display allows you to select the product that you want to install. Select HA-MXMonitor. Click Next to continue.



5. The Manuals dialog is displayed. Select the manuals that you want to install (if any) from those listed.(Click Select All to install all the manuals listed). Select the Destination Path to where you want to installthe manuals if you do not want to keep the default path.

6. Click Next to continue. The IBM i Partition Details dialog is displayed.



7. Enter the Host Name/IP Address for the IBM i onto which the product suite is to be installed.

8. Enter the User Profile under which the installation is to be actioned.

Note: The user profile must have *SECOFR class authority or greater. Additionally, the profile must also have *SECADM, *ALLOBJ and *AUDIT authority in order for the installation to complete successfully.

9. Enter the Password associated with the selected user profile.

10.Unless instructed otherwise, leave the FTP Port setting as 21.

11.Leave the Verify Connection To Host setting enabled to ensure that a valid connection is made to thehost machine prior to the installation.

12.If using FTPS (FTP-SSL) for the installation, click the Use FTP Secure option, confirming whether or notyou want to ignore any connection errors.

13.Click Next to continue. A summary of the choices made for installation is displayed, in order that theycan be reviewed prior to the installation being performed.

Note: Use Back (available on all dialogs except the Welcome dialog) to revisit any point where you want to amend the current settings.

When you are satisfied with the installation options that you have selected, click Install to begin theinstallation process, the progress of which is displayed on the Installation Progress dialog.



14.. Click Finish to complete this part of the installation process


Installation and Configuration Installing HA-MX Monitor on IBM i

Installing HA-MX Monitor on IBM i You are now ready to install the software onto the IBM i. Log on to the system onto which the software wascopied.

Important Installation Notes: Remember that the user profile used for installation must have *SECOFR class authority or greater. Additionally, the profile must also have *SECADM, *ALLOBJ and *AUDIT authority in order for the installation to complete successfully.

To avoid potential conflict when installing Halcyon HA-MX Monitor please search the library list for library DBU10. If found, please remove it from the library list prior to install.

If Halcyon Exit Point Manager is installed on the same system, the user profile running the install also requires *IOSYSCFG ‘Special Authority’.

You must be enrolled in the System Distribution Directory in order to install the software.

Please ensure that system value QALWOBJRST is set to *ALL prior to starting and for the duration of the installation otherwise the installation process fails. Once the installation is complete, QALWOBJRST can be reset to its previous value.

Installation optionsThese installation options are useful if you want to install Halcyon HA-MX Monitor from a remote devicesuch as a CD or DVD Drive or from installation files held on a file server.

Note: This documentation provides instructions on how to install from a remote device and not how to copy the files to a CD/DVD or file server. You need to have completed this prior to using the following.

1. From the Command line type:

HALINST/INSTALL

2. Press F4 to display an additional display allowing you to specify parameters specific to the type ofinstallation option chosen.



The following device options are available:

*DIR Specifies that the installation files are in a directory. Specify the directory path using the Save File Directory (DIR) parameter

*FTP Specifies that the installation files are in a library on a remote system. A valid user ID and password are required for this option

*LIB Specifies that the installation files are in a library. Specify the library name using the Save File Library (LIB) parameter

*OPT Specifies that the installation files are on a CD inserted in an optical drive on this system

*RMTOPT Specifies that the installation files are on a CD inserted on an optical drive on a remote IBM i. Specify the remote system using the Remote System (RMTSYS) parameter

Save File Directory (*DIR) parameterWhen Device(*DIR) is selected, this parameter specifies the path of the directory that contains theinstallation files.

1. Select Device as *DIR.

2. Enter the name of the directory that contains the installation files.

3. From within the Products parameter, use *SELECT to install with prompts, allowing you to control theinstallation. *UPGRADE can be used to upgrade an existing installation without further intervention.

4. If required, specify Product Setup options. *CTLEXTPNT causes the install to remove any registeredPrimary Exit Point handlers, as shown within ‘Work with Exit Point Handlers’ (WRKEXTHDL), before theinstall is performed. The Primary Exit Point handlers are then re-registered against the relevant ExitPoints after the install is complete. *MIGDSKBLD causes Halcyon Disk Space Manager setup (if inuse), to automatically migrate all available builds from the previous release during an upgrade.

5. Specify the product language to use. The default (*DFT) setting is English.

Note: If you select a language that is not supported by all products, English is used as the substitute language in the non-supported products. To determine which products support which languages, use PRODUCTS(*SELECT).



6. Determine whether to notify a user on the local system of any completion and error messages. IfPRODUCTS(*SELECT) is specified and F19=Submit to batch is used, messages are sent to the userwho is running this command. Otherwise, messages are not sent.

7. Press <Enter> to open the Product Installation display from where you can specify the Environment towhich the installation is actioned.

File Transfer Protocol (*FTP) parameterWhen Device(*FTP) is selected, this parameter specifies the path of the library that contains the installationfiles.

1. Select Device as *FTP.

2. Enter the name of the remote system which can either be a TCP/IP host name or a SNA LU 6.2 name.

3. If required, enter the name of the backup system which can either be a TCP/IP host name or a SNA LU6.2 name. The backup system is used if INSTALL is not able to access the save file library for anyreason, typically because the remote system cannot be reached.

Note: All other parameters apply to both systems, therefore the user id, password and save file library must be the same on each system.

4. Enter the User ID required to access the Remote System (use *CURRENT to keep the details of theuser ID that is being used for the current session).

5. Enter the Remote Password associated with the entered user ID. Note that the entry in this parameter ishidden.

6. Configure the Port setting to be used for the FTP connection.

*DFT The default setting uses port 21

*SECURE Port 990 is used. This port is reserved for secure FTP servers which use Transport Layer Security (TLS) or Secure Sockets Layer (SSL) protocols to encrypt data

1 - 65535 Specify a port number for the FTP connection

7. Specify the type of Secure connection used to protect the data (including User ID and password) duringthe file transfer.

*DFT Defaults to *NONE, unless *SECURE is specified in the Port parameter

*NONE No encryption is used when connecting to the FTP Server

*SSL The connection to the FTP Server is made and a SSL/TLS session is requested. If this type of session is not supported, the connection is closed

*IMPLICIT Both this and the target system must be running i5/OS v5R3 or higher. The connection is attempted using SSL/TLS. The session is closed if the server does not support this type of

connection

8. Specify the type of Data protection to be used during the file transfer.

*DFT Defaults to *PRIVATE if the Secure Connection parameter specifies a secure connection, otherwise it defaults to *CLEAR

*PRIVATE Data is encrypted during transmission. This option is only available if *SSL or *IMPLICIT is specified as the Secure Connection

*CLEAR Data is not encrypted during transmission regardless of the Secure Connection parameter setting. Both this and the target system must be running i5/OS v5R3 or higher

9. In the Save File Library parameter enter the name of the library that contains the installation files.



10.From within the Products parameter, use *SELECT to install with prompts, allowing you to control theinstallation or *UPGRADE to complete the installation without further intervention.

11.If required, specify Product Setup options. *CTLEXTPNT causes the install to remove any registeredPrimary Exit Point handlers, as shown within ‘Work with Exit Point Handlers’ (WRKEXTHDL), before theinstall is performed. The Primary Exit Point handlers are then re-registered against the relevant ExitPoints after the install is complete. *MIGDSKBLD causes Halcyon Disk Space Manager setup (if inuse), to automatically migrate all available builds from the previous release during an upgrade.

12.Specify the product language to use. The default (*DFT) setting is English.


Note: If you set the ‘Language option’ parameter to ‘JPN’ then system default HAL/SYSCCSID is automatically set to a value of 5026.

13.Determine whether to notify a user on the local system of any completion and error messages. IfPRODUCTS(*SELECT) is specified and F19=Submit to batch is used, messages are sent to the userwho is running this command. Otherwise, messages are not sent.

14.Press <Enter> to open the Product Installation display from where you can specify the Environment towhich the installation is actioned.

Note: An *FTP upgrade transfers the INSTALL file from the remote system library specified and uses it to compare PTF levels for the remote system library to the environment to be upgraded. Only FTP save files for Products that require upgrading are transferred. This does not work unless the HALINST library on the source and destination machines are at the same PTF Level.

Save File Library (*LIB) parameterWhen Device (*LIB) is selected, this parameter specifies the name of the library that contains theinstallation files.

1. Select Device as *LIB.

2. In the Save File Library parameter, enter the name of the library that contains the installation files.









Local System (*OPT) parameterWhen Device(*OPT) is selected, this parameter specifies the optical volume of the local system to use.

1. Select Device as *OPT.

2. Specify the volume as HALCYON unless instructed otherwise by Halcyon technical support staff.







Remote System (*RMTOPT) parameter When Device (*RMTOPT) is selected, this parameter specifies the remote system that has an optical driveloaded with an installation CD.

1. Select the Device as *RMTOPT.

2. Enter the name of the remote system which can either be a TCP/IP host name or an SNA LU 6.2 name.

3. Specify the volume as HALCYON unless instructed otherwise by Halcyon technical support staff.

Note: To access the remote system INSTALL uses QFileSvr.400 file system. If the QFileSvr.400 file system does not contain an entry that matches the value specified for the RMTSYS parameter, INSTALL creates an entry and removes it upon completion.









Product Installation displayThe main installation display is now shown, from where you can enter the details of the environment ontowhich you want to install the software.

If present, the installation uses the default environment on your IBM i, otherwise the environment ‘PROD’ isused, leaving you free to complete the environment description.

Installation DisplayThis display shows all products/suites that have been previously installed or are ready to be installed.

Note: The version and PTF level of the current products planned for installation are shown under the ‘Available’ heading. Note that it is possible to both upgrade and downgrade the version and PTF level of the current software.

Halcyon EnvironmentsPrior to installing the suite it is possible to specify the environment to which it is installed.

Note: An Environment is an installation of Halcyon products. Multiple copies of Halcyon products can be installed on a system or partition and then run independently of each other. The two main uses for this are:

• Allows you to install and evaluate a new version of a Halcyon product in a test environment while still running the existing version in the production environment.

• A high availability solution offering both production and backup system, allows you to have separate production and backup environments on both systems, with the appropriate environment active on each machine depending on its current mode and the other dormant.

If no previous installations of Halcyon products or suites have been undertaken on this IBM i, then theinstallation routine uses the default environment ‘PROD’.



If Halcyon products or suites have been previously installed on this IBM i then the environment displayed isthe last one to which an installation was undertaken, with both the ‘Environment Name’ and ‘Description’parameters completed.

In either of the above cases, you may change both the ‘Environment Name’ and ‘Description’ parametersto suit the requirements of your installation.

Note: Use the Change Environment Description (CHGENVDSC) to quickly change the description shown for the Halcyon Environment in which the command is run.

Installing HA-MX MonitorThe next step depends on the environment to which you are installing:

• If this installation is for the default ‘PROD’ environment, enter a Description for the environment andthen go to step 1

• If this installation is for the same environment used for the last install of Halcyon products, leave theEnvironment Name and Description parameters as they are and go to Step 1.

• If you want to create a new environment or use an environment that has previously been created butis not displayed, either overtype the current parameters with the new environment details or enter anexisting Environment Name and Description and go to step 1

1. Select option 1=Install against HAL Halcyon Common Library and HMX HA-MX Monitor.

Note: Only the individual products selected to install or upgrade are listed on this display.

2. Press <Enter> to confirm the installation.

Further displays are shown during the installation process which prompt the user for input prior to continuing.

Note: It is recommended that an interactive install is used for first time installations. If you want to update the PTF level of a product that has already been installed, use F19=Submit to Batch to automate the installation process.



The installation progress of each product is displayed on the next display using the following text colorlegend:

• Green Pending installation

• White Currently installing

• Blue Installation completed

Once the installation is complete, all the products are displayed in blue text and the message InstallationComplete is displayed at the bottom of this display.



Authorizing HA-MX MonitorYou are now prompted to enter a valid authorization code:

Note: This display is the same regardless of whether a temporary or permanent code is being applied.

.

Note: To obtain a license key for Halcyon HA-MX Monitor please email:

[email protected]

1. Type your Authorization Code. Leave the ‘System’ parameter set to *LOCAL and press <Enter>.

Once the authorization code has been entered, the Halcyon products secured by the code are displayedalong with the expiry date.



2. Press <Enter> to exit this display and open the Change System Default display. This display allows youto set the default system user profile.

Setting the Default User ProfileThe default value for the user profile is: QSYSOPR. If required, you may change this user for any otheruser profile on your system.

Note: For any user profile that is defined, even if you use the system default value of QSYSOPR, you must set user permissions for Halcyon Products using Configuration - Work with User Authority option from the Halcyon main menu.

When using GSM terminals for SMS alerting *IOSYSCFG will also be required.

In addition you must manually use the following command to grant all authority to the QAUDJRN journal object:

QSYS/GRTOBJAUT OBJ(QSYS/QAUDJRN) OBJTYPE(*JRN) USER(QSYSOPR)

AUT(*ALL)

*If you are not using QSYSOPR then please specify the correct user profile.

Once the User Profile has been selected, press <Enter> to open the Work with Journal display.

JournalingNote: Journaling provides an audit trail across Halcyon products allowing you to see what actions have been undertaken at what times and by which users. This can assist you in fault-finding should any issues arise during use of Halcyon HA-MX Monitor.



1. Press F20 to start journaling for this installation. If you do not want to start journaling at this point, press<Enter> to continue.

Note: Journaling can be activated later from within the Halcyon Utilities - Work with Journal menu option.

Assuming that you have started journaling at this point using F20, the following display is opened:

2. Press <Enter> to confirm the start of journaling.

Installation CompleteYou have now completed the installation of Halcyon HA-MX Monitor.



Launching HA-MX MonitorWhen the software has been installed, display the main menu by entering the following command in thecommand line:

GO HALPROD (where PROD = the name of the environment entered on installation).

You do not need to add any libraries to your library list if you are using the software via menu options. If youexecute any command directly via the command interface provided, you need to prefix the commands withthe HRPPROD library name, (however there is still no need to add the library to your library list).

Importing Existing Rules from Legacy versions of HA-MX MonitorCommand HMXIMPORT can be used to import rules from the legacy HA-MX Monitor. Any HMMAPI Actionsare replaced with an ACTSCH ACTSCH(MIMIX) Action. Please note that legacy rules with multiple selectcriteria are not imported as this functionality is not supported in this version. Messages are added to theHalcyon Message Log explaining which rules were and were not imported.

Note: See Halcyon HA-MX Monitor USer Guide - Display Message Log for more information,


Installation and Configuration Work with User Authority

Work with User AuthorityWork with User Authority governs user access and permission rights when using the HA-MX Monitor.

The effective authority that a user has to a product function is determined by system default (HAL/AUTHMODE). This can be set to either ‘1’ or ‘0’.

• Using the installed default setting of ‘1’, users with *ALLOBJ special authority automatically have *ALLauthority to all Halcyon products and functions, overriding any function authority that has been defined.

• If the system default setting is changed to ‘0’, users with *ALLOBJ special authority do not automaticallyhave *ALL authority to all Halcyon products and functions. Authority is derived from function authority inthe normal way.

Authority entries are checked in the following order:

1. Entry for the user.

2. Entry for the user’s group profile.

3. Entries for each of the user’s supplemental groups, in the order in which they are defined in the userprofile.

4. Entry for *PUBLIC authority.

The first authority found, that is not *UNDEF, is the effective authority for the user.

To view and edit User Authorities, type command WRKUSRAUT on the command line and press <Enter>.The Work with User Authority display is opened.

The body area of this screen shows all users and the authority that each has to the given product codes(listed vertically in columns) commonly used with the HA-MX Monitor.

Typically, within an installation of the HA-MX Monitor the following columns are shown:

* Halcyon Common Library

HMC Halcyon Message Communicator (required for sending messages)

HMX Halcyon HA-MX Monitor



Parameters on the Work with User Authority displayThe following parameters are available on the Work with User Authority display.

User profileDisplays the name of the authorized profile. The profile can be a user profile, a group profile or the specialvalue *PUBLIC.

Product codesDisplays the Halcyon product codes of installed products. The value shown at the intersection of user andproduct code summarizes the authority of the user to that product. One of the following summary values isshown:

Y User has at least *CHANGE authority to all functions of this product.

P User has some authority but does not have *CHANGE authority to all functions of this product.

X User has *EXCL authority to all functions of this product.

blank User has no defined authority to this product. Therefore the effective authority is derived from group membership or public authority.

Using the User Authority displayThe following options are available when working with user authority.

Note: Options on the Work with User Authority display work in a slightly different manner than they do on other screens in the HA-MX Monitor.

Note: The command RVKUSRAUT can be used to revoke ALL authority for a user to use Halcyon functions.

Options may be typed in the ‘Opt’ column as usual or in the intersecting parameters. Options typed into the‘Opt’ column effect ALL intersecting parameters for that user. An option typed in an intersecting parameterapplies only to that user and product.

ChangeUse option 2=Change to alter the current user authority settings via the Work with Function Authoritydisplay.



The user can be assigned the following function authorities where applicable:

*ALL User has all the authority that is possible for this function (not all functions support all types of authority).

*CHG User has change and use authority.

*USE User has use authority.

*UNDEF No authority is defined. Therefore, the effective authority is determined by a more generic entry such as a group entry or *PUBLIC.

*EXCL User has exclude authority. This means that the user is not authorized even if a more generic entry grants authority to this function.

Press <Enter> to confirm the changes. Press F12 to return to the Work with User Authority display.

DeleteUse option 4=Delete to open the Work with Function Authority display with all function authorities changedto *UNDEF (or *EXCL for *PUBLIC authority). Type any changes required and press <Enter> to update.

Note: If all function authorities in all products for a user are set to *UNDEF, that user is removed from the list of users.

DisplayUse option 5=Display to open the Work with Function Authority display in view mode only with the currentauthorities for the selected user and/or product.

Note: No changes can be made when displaying authorities.



The following functions are available when working with user authority:

F3=ExitUse F3=Exit to close the current display and return to the main menu.

F5=RefreshUse F5=Refresh to update the display with current information.

F12=CancelUse F12=Cancel to exit this display and return to the previous display.

Exporting Halcyon User AuthoritiesIt is possible to export Halcyon User Authorities to a remote Halcyon Environment via use of the command:EXPUSRAUT.

Note: This command supports the use of FTP SSL (FTPS).



To system Enter the Host Name or IP Address of the remote system to which the user authorities are to be exported.

Remote User ID Specify the User ID to be used by FTP when connecting to the remote system.

Remote password Specify the password associated with the Remote User ID to be used.

To environment Specify the Halcyon Environment code on the remote system to which the User Authorities are exported.

User IDSpecify the User ID of the user to be exported. *ALL indicates that all the user authorities on this systemare exported to the remote environment. *PUBLIC exports all *PUBLIC authorities.

Product Specify the Halcyon product code(s) of the authorities to be exported. Use *ALL to specify all products.

Note: *SECADM special authority is required by the user running the EXPUSRAUT command. This function does not support FTPS (Secure FTP).


AB/HMX/032216

HA-MX Monitor v15 · 2018. 7. 24. · Introduction Overview Halcyon HA-MX Monitor v15.0 - 4 -...

Documents

Transcript of HA-MX Monitor v15 · 2018. 7. 24. · Introduction Overview Halcyon HA-MX Monitor v15.0 - 4 -...