Folder structure

Some folders will be created at runtime. Each folder serves 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
├── webserver.json
├── license_MNS.dat
└── /config
    └── /sec
        ├── webserver.key.priv (auto-generated on installation)
        └── webserver.key.pub (auto-generated on installation)
    └── /ssl
        └── /certficates
            └── webserver.pem (auto-generated on startup for self-signed one)
        └── /private
            └── webserver.key (auto-generated on startup for self-signed one)
└── /dbs (created at runtime)
    ├── metrics.db
    ├── webserver.db
    └── /backup (created at runtime)
        ├── metrics`<xxx>`.db
        └── 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/certificates folder contains the certificate
the /ssl/private folder contains the certficate 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
├── integrator.json
├── license_MNS_integrator.dat
└── /config
    └── /sec
        ├── integrator.key.priv (auto-generated on installation)
        └── integrator.key.pub (auto-generated on installation)
    └── /ssl
        └── /certficates
            └── integrator.pem (auto-generated on startup for self-signed one)
        └── /private
            └── integrator.key (auto-generated on startup for self-signed one)
└── /data (created at runtime)
    ├── *.csv (created at runtime if log events to CSV file is enabled)
    └── *.json (created at runtime if log events to JSON file is enabled)
└── /dbs (created at runtime)
    ├── integrator.db
    ├── metrics.db
    └── /backup (created at runtime)
        ├── integrator_`<xxx>`.db
        └── metrics`<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/certificates folder contains the certificate
the /ssl/private folder contains the certficate 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
├── monitor.json
└── /config
    └── /sec
        ├── monitor.key.priv (auto-generated on installation)
        └── monitor.key.pub (auto-generated on installation)
    └── /ssl
        └── /certficates
            └── monitor.pem (auto-generated on startup for self-signed one)
        └── /private
            └── monitor.key (auto-generated on startup for self-signed one)
└── /actions (binaries inside are not mandatory)
    ├── `<action>`.exe
    └── `<actionXXX>`.exe
└── /drivers
    ├── chromedriver.exe / chromedriver
    ├── geckodriver.exe / geckodriver
    └── msedgedriver.exe / msedgedriver
└── /exec
    ├── jdk
    ├── ffmpeg.exe / ffmpeg
    ├── log4j2.xml
    └── MNSCli*.jar
└── /scripts (scripts inside are not mandatory)
    ├── `<script>`.bat /`<script>`.sh
    └── `<scriptXXX>`.bat /`<scriptXXX>`.sh
└── /dbs (created at runtime)
    ├── api.db
    ├── chart.db
    ├── exec.db
    ├── metrics.db
    ├── monitor.db
    ├── script1.db
    ├── script2.db
    ├── url.db
    └── /backup (created at runtime)
        ├── api`<xxx>`.db
        ├── chart`<xxx>`.db
        ├── exec`<xxx>`.db
        ├── metrics`<xxx>`.db
        ├── monitor`<xxx>`.db
        ├── script1`<xxx>`.db
        ├── script2`<xxx>`.db
        └── url`<xxx>`.db
└── /log (created at runtime)
    ├── monitor.log
    └── monitor`<xxx>`.log.gz
└── /data (created at runtime)
    └── /`<monitor>` (created at runtime)
        ├── `<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 if video are enabled)
            ├── `<monitor>`_videoOnError_`<xxx>`.gif
            └── `<monitor>`_videoOnOK_`<xxx>`.gif

the /sec folder contains the private and public key to encrypt password
the /ssl/certificates folder contains the certificate
the /ssl/private folder contains the certficate 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 Windows Usage