...
For more information and help with opFlow see it's community homepage
opMaps Configuration
Configuration of opMaps is a short process.
First we need to get the locations of each group you have configured in NMIS into the file that opMaps will use to function. When you start off this file will exist, in order to make sure you can migrate your groups without problems we will first delete the existing file.
| Code Block |
|---|
rm /usr/local/opmantek/conf/GroupLocations.nmis |
Now we will convert your groups to a GroupLocations.nmis file
| Code Block |
|---|
cd /usr/local/opmantek/bin/
./configmaps.pl /usr/local/nmis8/conf/Nodes.nmis /usr/local/opmantek/conf/GroupLocations.nmis |
This file can be edited using vi or your favourite editor to adjust the fields to your liking.
The next step is to get a google maps api key. If you don’t already have one, please follow these steps from Google to acquire one. Next we will put this key into the opMaps configuration file:
| Code Block |
|---|
vi /usr/local/opmantek/conf/Maps.nmis |
| Code Block |
|---|
#Find the following line under 'mapview' =>
'googleApiKey' => ''
#Replace the defaultAPI with your own Google API KEY
eg: 'googleApiKey' => 'AIzaSyBfa5791NQUs3N7x--ueD3DwQPmscElk-8' |
There are several other parameters that can be configured in the Maps.conf file to adjust the view to suit your needs. For more information on setting up and configuring opMaps see it's community homepage.
One troubleshooting note:
If you are trying to view the map in NMIS and getting a licensing error even though you have entered the license (something like the following):
It is most likely that you have not accepted the EULA. Open opMaps from the NMIS Modules drop down:
This should pop-up opMaps in a new page (make sure you have pop-ups disabled for this host) and accept the EULA. If you now go back to the NMIS page and refresh the map should appear properly.
Once again, for more information on setting up and configuring opMaps see it's community homepage.