Redwood Documentation

Product Documentation

 

You are currently viewing the legacy RunMyJobs documentation site. This site will be taken down later this month.
All current and future RunMyJobs documentation, including versions 2023.3 and later, can be found here.
Please update your bookmarks. Use the version dropdown menu to select the documentation you need.

›Reference

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
← Uninstalling Redwood ServerAdmin Server →

on-site-related topic Standard setvars script

#!/bin/sh
#
# Template for customizing environment variables for tomcat execution.
# platform.sh should not be edited, rename this file (setvars.sh.example) to setvars.sh instead
#
# This script will be called twice once at the beginning of platform.sh and once at the end.
# To distinguish between the calls the environment variable P_STAGE will be set to 'pre' and 'post'
# respectively. It is important to distinguish between the stages otherwise the values will be duplicated
# as the setvars.sh script is called twice during startup and shutdown.
#
# Additionally the environment variable P_ACTION will be either 'start' or 'stop' depending on whether
# the platform is being started, or stopped.
# NOTE: if platform.sh is being invoked without a command then P_ACTION will default to 'run'.
#
# For 'stop' action JAVA_OPTS will always be cleared and cannot be set via this script.
#
# $Id$
#


# Uncomment the following to define a P_STAGE pre only action
#if [ $P_STAGE = "pre" ]
#then
# Customize JAVA_HOME - this should only be set in the pre stage
#  JAVA_HOME=
#fi # [ $P_STAGE = "pre" ]

# Uncomment the following to define a P_STAGE post only action (and the closing fi below)
#if [ $P_STAGE = "post" ]
#then
# To customize java system properties.
# NOTE: this should only be set in the post stage
#  JAVA_OPTS="$JAVA_OPTS "
#
# JMX support for log4j2 has been disabled using LOGGING_OPTS, to reenable it clear this variable
#  LOGGING_OPTS=""

# The following define the memory settings for the JVM. These values are appended to the JAVA_OPTS parameter
# after the post stage is called, so they should be defined via the following variables and not in the JAVA_OPTS.
#  JAVA_OPT_MAXMEM=-Xmx512m

# If for example you only wanted to set the a JAVA_OPTS on startup/run
#  if [ "$P_ACTION" != 'stop' ]
#  then
#    JAVA_OPTS="$JAVA_OPTS -Dsome.special.startup=true"
#  fi

# To customize the working directory - this should only be set in the post stage
#SERVER_LOGDIR=

#fi # [ $P_STAGE = "post" ]

# To customize the LD_LIBRARY_PATH - this will be called in both pre/post stages
#LD_LIBRARY_PATH="$LD_LIBRARY_PATH: "

onsiteTopic

← Uninstalling Redwood ServerAdmin Server →
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 |