Folder structure

Folders can be created at runtime. Each folder servers a purpose so you should not delete them unless you know what you are doing.

Mugnsoft Webserver component

File structure

The structure looks as follows: 


/webserver
├── webserver.exe / webserver
├── license_MNS.dat
└── /config
    └── /sec
        ├── webserver.key.priv (auto-generated on installation)
        ├── webserver.key.pub (auto-generated on installation)
    └── /ssl
        ├── webserver.crt
        ├── webserver.key
└── /dbs (created at runtime)
    ├── webserver.db
    ├── webserver.lock
    └── /backup (created at runtime)
        ├── webserver_<xxx>.db
└── /log (created at runtime)
    ├── webserver.log
    ├── webserver_<xxx>.log.gz
└── /data (created at runtime)
    └── /<monitor> (created at runtime)
        ├── <tmpFiles>.zip
        └── /logs (created at runtime)
            ├── MNSCli.log
            ├── MNSCli.log<xxx>
        └── /screenshotsReport (created at runtime)
            ├── <xxx>.png
        └── /hars (created at runtime)
            ├── <monitor>.har
            ├── <monitor>_<xxx>.har
        └── /screenshotsOnError (created at runtime)
            ├── screenshotOnError.png
            ├── screenshotOnError_<xxx>.png
        └── /videos (created at runtime)
            ├── <monitor>_videoOnError_<xxx>.gif
            ├── <monitor>_videoOnOK_<xxx>.gif

  • the /sec folder contains the private and public key to encrypt password
  • the /ssl folder contains the certificat and its private key
  • the /dbs folder contains the KV store
  • the /dbs/backup folder contains the KV store backups
  • the /log folder contains the webserver log file
  • the /data folder contains files and folders of monitors downloaded from the probe

Mugnsoft integrator component (optional component)

File structure

The structure looks as follows: 


/integrator
├── integrator.exe / integrator
├── license_MNS_integrator.dat
└── /config
    └── /sec
        ├── integrator.key.priv (auto-generated on installation)
        ├── integrator.key.pub (auto-generated on installation)
    └── /ssl
        ├── integrator.crt
        ├── integrator.key 
└── /dbs (created at runtime)
    ├── integrator.db
    ├── integrator.lock
    └── /backup (created at runtime)
        ├── integrator_<xxx>.db
└── /log (created at runtime)
    ├── integrator.log
    ├── integrator_<xxx>.log.gz

  • the /sec folder contains the private and public key to encrypt password
  • the /ssl folder contains the certificat and its private key
  • the /dbs folder contains the KV store
  • the /dbs/backup folder contains the KV store backups
  • the /log folder contains the integrator log file

Mugnsoft Monitor component

File structure

The structure looks as follows: 


/monitor
├── monitor.exe / monitor
└── /config
    └── /sec
        ├── monitor.key.priv (auto-generated on installation)
        ├── monitor.key.pub (auto-generated on installation)
    └── /ssl
        ├── monitor.crt
        ├── monitor.key      
└── /actions (binaries inside are not mandatory)
    ├── <action>.exe
    ├── <actionXXX>.exe
└── /drivers
    ├── chromedriver.exe / chromedriver
    ├── geckodriver.exe / geckodriver 
    ├── msedgedriver.exe
└── /exec
    ├── log4j2.xml
    ├── MNSCli.jar
└── /scripts (scripts inside are not mandatory)
    ├── <script>.bat /<script>.sh
    ├── <scriptXXX>.bat /<scriptXXX>.sh
└── /dbs (created at runtime)
    ├── monitor.db
    ├── monitor.lock
    └── /backup (created at runtime)
        ├── monitor<xxx>.db
└── /log (created at runtime)
    ├── monitor.log
    ├── monitor<xxx>.log.gz
└── /data (created at runtime)
    └── /<monitor> (created at runtime)
        ├── config_<monitor>.cfg
        ├── <tmpFiles>.zip
        └── /logs (created at runtime)
            ├── MNSCli.log
            ├── MNSCli_last.log (temporary file)
        └── /report (created at runtime)
            ├── <xxx>.png
        └── /hars (created at runtime)
            ├── <monitor>.har
            ├── <monitor>_<xxx>.har
        └── /screenshotsOnError (created at runtime)
            ├── screenshotOnError.png
            ├── screenshotOnError_<xxx>.png
        └── /videos (created at runtime)
            ├── <monitor>_videoOnError_<xxx>.gif
            ├── <monitor>_videoOnOK_<xxx>.gif

  • the /sec folder contains the private and public key to encrypt password
  • the /ssl folder contains the certificat and its private key
  • the /actions folder contains some binaries that could be used in your selenium code (not mandatory but could be use in your script if the case arise)
  • the /drivers folder contains the KV store
  • the /exec folder contains the log level of the MNSCli.jar execution. MNSCli.jar is the actual jar executable for the monitor
  • the /scripts folder contains the scripts to be executed upon success, failure or status change of a monitor execution (not mandatory)
  • the /dbs folder contains the KV store
  • the /dbs/backup folder contains the KV store backups
  • the /log folder contains the monitor log file
  • the /data folder contains the scenario file and folders related to the monitor execution
Install on Mac OS Usage