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 Automatically with InitStarting Redwood Platform Automatically on Solaris →

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

Launchd was first shipped with macOS version 10.4 and is also available on FreeBSD as well as other systems. Below are a pair of example files you can use with launchd. You adjust the paths in the files to your installation path, which should point to the directory containing j2ee. In that directory, you create a directory named bin and create a shell script as outlined below; adapt the paths and user in the PLIST file accordingly.

Launchd Shell Script Wrapper

#!/bin/bash

# PATH to installation directory

RW_INSTALL=/opt/redwood
SERVER=${RW_INSTALL}/j2ee/cluster/server1
CATALINA_PID=${SERVER}/logs/process.pid

#Source your environment

if [ -e ${SERVER}/bin/setvars.sh ]; then
. ${SERVER}/bin/setvars.sh
fi

function stopInstance() {

date

echo "Shutting down Redwood"

${SERVER}/bin/start.sh

}

function startInstance() {

date

echo "Starting Redwood"

${SERVER}/bin/stop.sh

}


function restartInstance() {

date

echo "Restarting Redwood"

${SERVER}/bin/restart.sh

}

startInstance

# trap signal to quit/terminate

trap stopInstance INT QUIT ABRT KILL ALRM TERM TSTP

# trap HUP
trap restartInstance HUP

echo "Waiting for `cat ${CATALINA_PID}`"

wait `cat ${CATALINA_PID}`

PLIST File Contents

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>Label</key>
    <string>com.redwood.scheduler</string>
    <key>OnDemand</key>
    <false/>
    <key>RunAtLoad</key>
    <true/>
    <key>Program</key>
        <string>/opt/redwood/bin/launchd_wrapper.sh</string>
    <key>ServiceDescription</key>
    <string>Redwood Platform</string>
    <key>StandardErrorPath</key>
    <string>/opt/redwood/j2ee/cluster/server1/logs/launchd.err</string>
    <key>StandardOutPath</key>
    <string>/opt/redwood/j2ee/cluster/server1/logs/launchd.out</string>
    <key>UserName</key>
    <string>nobody</string>
  </dict>
</plist>

Procedure

  1. Create a directory named <install_dir>/bin and create a file named launchd_wrapper.sh containing the above shell script code.
  2. Make the file executable by issuing the following command chmod +x <install_dir>/bin/launchd_wrapper.sh.
  3. Copy the contents for the PLIST file into /Library/LaunchDaemons/com.redwood.scheduler.plist.
  4. Adapt any paths and change the user (default in this example is nobody).
  5. Issue sudo launchctl load /Library/LaunchDaemons/com.redwood.scheduler.plist.
  6. Issue sudo launchctl list and make sure your process has a PID.

See Also

  • Starting Redwood Platform Automatically

onsiteTopic

← Starting Redwood Platform Automatically with InitStarting Redwood Platform Automatically on Solaris →
  • Launchd Shell Script Wrapper
  • PLIST File Contents
  • 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 |