Step1: Verify Pre-requisites for Windows Installation

System Requirements

• We recommend installing Skedler Alerts in a separate VM or Docker container or server.
• Windows operating system - 64bit
• Minimum of 2 CPU cores and 8 GB of RAM is recommended for deploying Skedler.
• Skedler Alerts requires Java 7, 8 or 9

Configure environment variables JAVA_HOME and PATH

• Configure Java_Home as User Variable.

• Add JAVA_HOME\bin to PATH

• Add JAVA_HOME\jre\bin\server to PATH

Note: For Jave 9 setting the PATH as JAVA_HOME\jre\bin\server not required.

Windows dpi settings

Dpi setting in Windows should be set to 96dpi for Skedler to generate the report in an aligned manner. By default, the value is set at 96dpi.

Go to Control Panel > Appearance and Personalization > Display to check the dpi settings.

Elasticsearch and Kibana version

Skedler Alerts supports Elasticsearch version from 2.0 to 6.2.4

Step 2: Download

• Download the latest version of Skedler Alerts from Free Trial page
  

Step 3: Extract

• Extract the skedler-alerts.zip file to the desired folder (e.g., C:\Program Files\Skedler-Alerts).

Step 4: Configure Permission

Provide read/write permissions to the following folders, if they are configured in alertconfig.yml

• Skedler-Alerts folder storing JSON file configured for the alerts_path parameter in alertconfig.yml
• UI files folder configured for the parameter ui_files_location

Step 5: Configure alertconfig.yml

• Go to config folder using the command cd config.
• Open alertconfig.yml

      ElasticSearch  URL configuration

• Add Elasticsearch URL with the port (even if the port is 80) in the alertconfig.yml file in the following format

  

  
  

      Proxy server basic authentication configuration

• If you are using Nginx, follow the steps below.
  

  If Nginx is configured as a reverse proxy for Elasticsearch, configure Nginx username and password for Elasticsearch as shown:

  

• Note: If you are using Shield then refer to Step-by-Step Configuration Guide for Shield.
• Save changes to alertconfig.yml

For more configuration options please refer alertconfig.yml configuration.

Step 6: Start Skedler Alerts

Starting Skedler Alerts manually from $alert_home

 bin\alert.bat

Starting Skedler Alerts in debug mode from $alert_home
bin\alert.bat debug

Starting Skedler Alerts as service from $alert_home

bin\alertsevice.bat start

Restarting Skedler Alerts as service from $alert_home

bin\alertsevice.bat restart

Stoping Skedler Alerts as service from $alert_home

bin\alertsevice.bat stop

Step 8: Access Skedler Alerts

Skedler-Alerts is accessed from the following URL http://<yourServer>:3001.  The License Activation page is displayed on successful installation.

Step 9: Activate Skedler Alerts

Skedler-Alerts can be activated Online or Offline. Refer the following articles to activate the license

• Step-by-Step Guide for Online License Activation of Skedler-Alerts
• Step-by-Step Guide for Offline License Activation of Skedler-Alerts

Step 10: Configure Settings for Alerts

To configure Skeldler-Alerts settings, refer to How to configure time zone settings, index pattern settings, email settings, Webhook settings for skedler-alerts

Step 11: Schedule Alerts

To create alerts, refer to Step-by-Step User Guide for Creating Skedler-Alerts  

References

• Step-by-Step Shield Configuration Guide for Skedler-Alerts
• Step-by-Step Guide for Offline License Activation for Skedler-Alerts
• Step-by-Step Guide to Move Skedler-Alerts from One Machine to Another