Rundeck Docs

# Installing on Windows

# Prerequisites

Before proceeding to install Rundeck, check all system requirements (opens new window) to make sure that the server can run Rundeck, also, make sure that the Windows user has sufficient rights to install software.

Be sure to install the appropriate Java Software Development Kit per the requirements (opens new window).

# Installing Rundeck on Windows based systems and first run

Download the Rundeck WAR file and save it to a main working directory, e.g. C:\rundeck, you can download Community (opens new window) version or Enterprise (opens new window). Set the Rundeck path environment variable, by typing the following command at a Powershell command prompt :

set RDECK_BASE=C:\rundeck

When Rundeck is started for the first time, it generates the configuration files and folders structure. Open a Powershell command prompt, go to c:\rundeck, and execute for Enterprise:

java -jar rundeckpro-enterprise-3.4.10-SNAPSHOT.war

or this for the community edition:

java -jar rundeck-3.4.10-SNAPSHOT.war

This step may take up to 1-2 minutes depending on system performance. When Rundeck is ready, it will be indicated in the Powershell window:

Windows launcher
Windows launcher

After generation is complete, stop the process with <Crtl+C> keys and continue with configuration.

# Folder Structure

+---etc
|       admin.aclpolicy => Administrator access control policy defined with a [aclpolicy] document.
|       apitoken.aclpolicy => Default API ACL policies.
|       cli-log4j.properties => This file defines the logging configuration for the Commandline tools.
|       framework.properties => Configuration file used by shell tools and core Rundeck services.
|       preferences.properties
|       profile
|       profile.bat => Shell environment variables used by the shell tools.
|       project.properties =>Rundeck project configuration file when using Filsystem based project defintions.
+---libext => Plugin folder.
+---projects => Projects data (eg: resource files, project properties, etc)
+---server
|   +---config
|   |       jaas-loginmodule.conf
|   |       log4j.properties => This file defines the logging configuration for rundeck.
|   |       realm.properties => Property file user directory when PropertyFileLoginModule is used.
|   |       rundeck-config.properties => This is the primary Rundeck webapp configuration file. Defines default loglevel, datasource configuration, and GUI customization.
|   |       ssl.properties => To enable SSL access to rundeck.
|   +---data => H2 default database
|   |       grailsdb.mv.db
|   +---lib
|   |       rundeck-core-3.0.X.jar => rundeck core
|   +---logs => Rundeck logging
|   |       rundeck.access.log => access to rundeck.
|   |       rundeck.api.log => API calls
|   |       rundeck.audit.log => Authorization messages pertaining to aclpolicy.
|   |       rundeck.executions.log => Logs of all executions.
|   |       rundeck.jobs.log => Log of all job definition changes.
|   |       rundeck.log=> General Rundeck application messages.
|   |       rundeck.options.log=> Logs remote HTTP requests for Options JSON data.
|   |       rundeck.project.log
|   |       rundeck.storage.log=> Standard input and output generated during runtime.
|   +---sbin
|   \---work
+---tools=> rd-acl client (to manage ACL validation).
\---var   => Executions Logs folder.

# Configuring Rundeck

After installing Rundeck, the first run and know the files/folders structure, you need to configure it. Basically publish Rundeck to be available on the network and generate a .bat script to launch Rundeck and use some parameters depending on our needs.

To publish Rundeck to be available in your network, open C:\rundeck\server\config\rundeck-config.properties with your favorite text editor and change this line:

server.address=yourhostname

to:

server.address=0.0.0.0

Create a file called start_rundeck.bat with your favorite text editor with the contents shown below. Make sure the .war filename matches the war file you downloaded:

Rundeck Enterprise version:

set CURDIR=%~dp0
call %CURDIR%etc\profile.bat
java %RDECK_CLI_OPTS% %RDECK_SSL_OPTS% -jar rundeckpro-enterprise-3.4.10-SNAPSHOT.war --skipinstall -d  >> %CURDIR%\var\logs\service.log  2>&1

for community:

set CURDIR=%~dp0
call %CURDIR%etc\profile.bat
java %RDECK_CLI_OPTS% %RDECK_SSL_OPTS% -jar rundeck-3.4.10-SNAPSHOT.war --skipinstall -d  >> %CURDIR%\var\logs\service.log  2>&1

To launch, type start_rundeck.bat at the command prompt. To stop Rundeck, you can press <Crtl+C> keys.

# Login to the GUI

By default, Rundeck will be available on TCP port 4440. To access, go to the following URL on your web browser: http://servername:4440 (when "servername" is the name of your Windows server).

Login page
Login page

The default username and password is "admin".

# Run Rundeck as a Service

This section will install Rundeck as a Windows Service so it runs in the background even when a user is not logged in.

  • Install Rundeck.
  • Download nssm.exe (opens new window)
  • Place the executable under %RDECK_BASE% (you can place it elsewhere, but for the sake of the example, use this base dir)
  • Open a prompt and type these commands (Administrator user is required to install a service)
    cd C:\rundeck
    nssm.exe install RUNDECK
  • The GUI pops up, set "path" as %RDECK_BASE%\start_rundeck.bat, startup directory as %RDECK_BASE% (optionally set "low" on the process tab, under priority, to avoid server CPU spiking when starting Rundeck)
NSSM Installer
NSSM Installer
  • Go to the Windows Service Management Console (services.msc) to start the rundeck service. You can also stop or restart Rundeck here.
Service Management Console
Service Management Console
  • set JVM memory heap on %RDECK_BASE%\etc\profile.bat.

Replace the RDECK_CLI_OPTS variable with the amount of memory that you need, for example:

....

set RDECK_CLI_OPTS=-Xms1024m -Xmx4096m
set RD_LIBDIR=%RDECK_BASE%\tools\lib

Now, Rundeck is configured as a Service and will automatically start when Windows starts.

← Installing from Source →