IBM Support

Convert MGTC Monitors to IBM Navigator for i Monitors

News


Abstract

Convert Management Central Monitors to IBM Navigator for i Monitors

Content

You are in: IBM i Technology Updates  > IBM Navigator for i > Enhancements list > System Monitors > Convert MGTC Monitors to IBM Navigator for i Monitors


A tool to help you convert your Management Central iNav Monitors to IBM Navigator for i Monitors.

The tool is located in the zip file mcexport.zip at the Navigator FTP site:  ftp://public.dhe.ibm.com/as400/products/navigator/

Download and follow the steps to deploy and run.

Migration Steps


Deploy:

  • 1.  Copy mcexport.zip to /qibm/proddata/os400/mgtc/ 
  • 2.  Extract the contents of the zip file using the following command:
  • > QSH CMD('cd /qibm/proddata/os400/mgtc/; jar xvf /qibm/proddata/os400/mgtc/mcexport.zip')
  • When the following message appears, press Enter:
  • Press Enter to end the terminal session.
  • The following directory now exists:  /qibm/proddata/os400/mgtc/mcexport
  • 3.  Check the path /qibm/proddata/os400/mgtc/mcexport and all the jar files
image-20200117150428-1

Run:

  1. Open the green screen and connect to your IBM i system
  2. Save the monitors of MC to a xml file using the following commands:
  • QSH
  • > cd /qibm/proddata/os400/mgtc
  • If you want to store the monitors information to the file test.xml, please ensure there is no file named test.xml under /qibm/userdata/os400/mgtc.

> McExport.qsh -m -f test.xml  

image-20200117150437-2
test.xml is the file name. You don’t need to specify the path, only the file name.
3.  Export the monitors saved in the xml file to the IBM Navigator for i, using the following qshell commands:
  • > cd mcexport
  • If you want to copy both message monitors and system monitors from test.xml, run the following qshell command:

> java -jar MonitorsCopy.jar a test.xml

image-20200117150444-3

If you want to copy only message monitors from test.xml, run the following qshell command:

> java -jar MonitorsCopy.jar m test.xml 

If you want to copy only system monitors from test.xml, run the following qshell command:

java -jar MonitorsCopy.jar s test.xml

Verify:
1.  Check that the system monitors have been copied to the IBM Navigator for i:
  • Open MC and click the Monitors->System
  • Open the IBM Navigator for i and click Monitors->System Monitors
  • Check whether the MC monitors are shown in the IBM Navigator for i
2.  Check that the message monitors have been copied to the IBM Navigator for i:
  • Open the MC and click the Monitors->Message
  • Open the IBM Navigator for i and click Monitors->Message Monitors
  • Check whether the MC monitors are shown in the IBM Navigator for i.
 3.  Verify that the IBM Navigator for i exist and work as expected
image-20200117150453-4

Other documentation

Migrating all monitors

Migrating "all" monitors (all that do not have Sharing Property set to NONE):
  • Use a MC script to export monitor definitions to an xml file
    • Only monitors that the current user has access to can be exported in this step
      • Monitors that were created by this user or
      • Monitors created by others with the sharing property set to Read Only or Controlled on MC GUI
      • If Sharing property is set to NONE, then other users cannot see it, so it cannot be exported.  To export these monitors, the user who owns them will first need to change the sharing properties to the MC GUI.
  • Use mcexport tool to import these monitor definitions to Navigator for i as documented above.

Limitations to migration

The tool cannot migrate the monitors owned by others if the sharing option on them is set to None.  In MC, only the owner can see a monitor with the sharing property set to None.  

Loss of attributes

Not all attributes will be migrated to the IBM Navigator for i monitors because these monitors do not have the same attributes available. Attributes will be lost if the properties do not match.

System Monitors

1.  Some metrics are not supported in IBM Navigator for i, so these metrics will not be migrated.  For example:
  • CPU Utilization (Interactive Feature)
  • CPU Utilization (Database Capability)
  • CPU Utilization (Secondary Workloads)
  • Disk IOP Utilization (Maximum)
  • Communication IOP Utilizaiton (Max, Avg)
  • Machine Pool Faults
  • User Pool faults (Max)

When migrating to Navigator for i, a reminder message will be shown in the green screen when the monitor has any unsupported metrics.  For example:

Disk IOP Utilization (Maximum) of System Monitor [SysMonName] is not supported in IBM Navigator for i and won't be shown.
2.  The two attributes under the General tab for MC monitors are not supported in IBM Navigator for i so will not be migrated:
  • Maximum graphing value
  • Display time
 3.  The Actions are not supported in IBM Navigator for i and will not be migrated:  Log event, Open event log, Open monitor, Sound alarm
Log event is always done for IBM Navigator for i monitors, and Trigger and Reset actions will be taken when defined.
4.  Systems and Groups are not supported in IBM Navigator for i monitors so will not be migrated
5.  The Sharing setting is not supported in IBM Navigator for i so will not be migrated:  Sharing: None, Read-Only, Controlled

Message Monitors

  • 1.  Collection Interval is not supported in IBM Navigator for i Message Monitors so will not be migrated
2.  The Actions are not supported in IBM Navigator for i and will not be migrated:  Log event, Open event log, Open monitor, Sound alarm
  • Log event is always done for IBM Navigator for i monitors, and Trigger and Reset actions will be taken when defined.
3.  Systems and Groups are not supported in IBM Navigator for i monitors so will not be migrated
4.  The Sharing setting is not supported in IBM Navigator for i so will not be migrated:  Sharing: None, Read-Only, Controlled

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Component":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]

Document Information

Modified date:
21 January 2020

UID

ibm11167442