Redwood Documentation

Product Documentation

 

›Starting Automatically

RunMyJobsRunMyJobs On-Premises Installation

Preparing Installation

  • Preparation for Redwood Server Installation
  • Database Prerequisites
  • Basic Sizing Guidelines
  • Planning

Installation

  • Installation
  • Download and Extract redwood-platform.zip
  • Installing Redwood Platform
  • Redwood Platform Application Server
  • Licensing Redwood Server

Security Overview

  • Security Overview
  • Security in Redwood Platform
  • External Security Systems
  • Lightweight Directory Access Protocol (LDAP)
  • Configuring LDAP Manually
  • Configuring LDAP With the LDAP Wizard
  • Database Authentication
  • Database Authentication - Enforcing Password Policies
  • Configuring JEE Security

Configuration

  • Installing and Configuring Redwood Platform Service on Windows
  • Submitting Processes and Licensing on Startup
  • Configuring the HTTP or HTTPS Interface of Redwood Platform
  • Configuring the APR HTTPS Interface of Redwood Platform
  • Configuring the NIO HTTPS Interface of Redwood Platform
  • Importing a Certificate Authority
  • Checking Your License
  • Managing Your Licenses with the License Manager
  • Configuration
  • Configuration Entries

Starting Automatically

  • Starting Redwood Platform Automatically
  • Starting Redwood Platform Automatically with Systemd
  • Starting Redwood Platform Automatically with Init
  • Starting Redwood Platform Automatically with Launchd
  • Starting Redwood Platform Automatically on Solaris

High Availability

  • High Availability
  • Configuring Web Application Clusters for High Availability
  • Creating Redwood Platform Clusters
  • Configuring Web Application Clusters on Microsoft Cluster Service
  • Configuring Platform Agents for High Availability
  • Configuring Platform Agents on Microsoft Cluster Service

Upgrade

  • Upgrading Redwood Server
  • Upgrading Redwood Platform

Migration

  • Migrating Redwood Platform

Uninstall

  • Uninstalling Redwood Server

Reference

  • Standard setvars script
  • Admin Server
  • Checking Your License
← Starting Redwood Platform AutomaticallyStarting Redwood Platform Automatically with Init →

on-site-related topic Starting Redwood Platform Automatically with Systemd

You configure Redwood Platform to start automatically on UNIX systems using systemd by specifying a unit file that is compatible with your platform. Create a systemd unit file in /etc/systemd/system. If the database is running on the same host, check to see which unit file starts it. You specify the database unit in the Wants= directive.

The following example unit can be used to start Redwood Platform on UNIX systems using systemd. Note that you must customize it according to your needs.

Systemd Unit

Create a file named /etc/systemd/system/redwood-platform.service with the following contents:

[Unit]
Description=central Redwood Server
Wants=network-online.target
After=network-online.target

[Service]
Type=forking
LimitCORE=infinity
User=redwood
Group=redwood
EnvironmentFile=/opt/redwood/j2ee/cluster/server1/bin/setvars.sh
PIDFile=/opt/redwood/j2ee/cluster/server1/work/tomcat.pid
ExecStart=/opt/redwood/j2ee/cluster/server1/bin/start.sh
ExecStop=/opt/redwood/j2ee/cluster/server1/bin/stop.sh
ExecReload=/opt/redwood/j2ee/cluster/server1/bin/restart.sh

[Install]
WantedBy=multi-user.target

warning

Ensure the user you specify exists! The service will be started as user root if you specify an invalid user; this is a feature of systemd.

tip

If you have exported variables in your setvars.sh file, you will have to remove the export keyword as systemd does not support that. In this case it is advised to duplicate setvars.sh to setvars.systemd and remove the export keywords in the latter file, allowing you to start Redwood Platform both using systemd and manually.

Procedure

  1. Adapt the script to your environment and save it to a file named redwood-platform.service in the /etc/systemd/system/ folder.
  2. If the database is on the same host, you must locate the name of the start unit for your database and add it to the After=.
  3. Run chmod +x /opt/redwood/j2ee/cluster/server1/bin/*sh to make the scripts executable.
  4. Run sudo systemctl --system daemon-reload to install the unit; you will have to perform this after every modification of the unit file.
  5. Run sudo systemctl start redwood-platform.service to start the service.

See Also

  • Starting Redwood Platform Automatically
  • Systemd - Execution environment configuration

onsiteTopic

← Starting Redwood Platform AutomaticallyStarting Redwood Platform Automatically with Init →
  • Systemd Unit
  • Procedure
  • See Also
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |