Redwood Documentation

Product Documentation

 

›Upgrade

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
← Upgrading Redwood ServerMigrating Redwood Platform →

on-site-related topic Upgrading Redwood Platform

You want to upgrade your existing Redwood Platform installation. You should backup the software-tree and your database prior to upgrading Redwood Platform, to do so, please follow the instructions of your database vendor.

Preparation

Redwood recommends you unzip the new version over the old. Special care has been taken to preserve your changes in files. The system automatically handles changes to the following files:

  • <install_dir>/j2ee/cluster/server<n>/conf/Catalina/localhost/scheduler.xml (customers who upgraded from 9.1.4 or earlier)
  • <install_dir>/j2ee/cluster/server<n>/conf/Catalina/localhost/redwood.xml (new installations of 9.1.5 or higher)
  • <install_dir>/j2ee/cluster/server<n>/conf/server.xml
  • <install_dir>/j2ee/cluster/server<n>/bin/setvars.{sh|cmd}

If you have changed any other configuration files, such as <install_dir>/j2ee/cluster/server<n>/bin/platform.{sh|cmd} for example, you will need to take manual steps.

For <install_dir>/j2ee/cluster/server<n>/bin/platform.{sh|cmd}, simply put your changes into <install_dir>/j2ee/cluster/server<n>/bin/setvars.{sh|cmd} - note that you might have to create that file. For other files, identify the changes you made as they will be overwritten.

note

You should not change <install_dir>/j2ee/cluster/server<n>/bin/platform.{sh|cmd}.

Deliverables

FileDescriptionRequired
redwood-platform.zipScheduler administration tool with GUIAlways

Procedure

Unzip the New Deliverable

  1. Unzip the deliverable over the existing installation.
  2. On UNIX-based systems.
  3. $ cd <install_dir> (make sure the directory contains the j2ee directory).
  4. $ unzip redwood-platform.zip.
  5. On Windows.
  6. C:\\Users\\Example> cd /d <install_dir> (make sure the directory contains the j2ee directory).
  7. <install_dir>> 7z x redwood-platform.zip (Here we use 3rd party software (7zip) to illustrate the procedure, you can also use the built-in graphical extraction tool in Windows).

Redeploy the Adminserver1 and Server1

Windows:

%install_dir%/j2ee/cluster/adminserver1/bin/redeploy.cmd
%install_dir%/j2ee/cluster/server1/bin/redeploy.cmd

UNIX:

${install_dir}/j2ee/cluster/adminserver1/bin/redeploy.sh
${install_dir}/j2ee/cluster/server1/bin/redeploy.sh

Upgrade the Database Schema

Start up the Scheduler admin tool by running the start command.

Windows:

%install_dir%/j2ee/cluster/adminserver1/bin/start.cmd

UNIX:

${install_dir}/j2ee/cluster/adminserver1/bin/start.sh
  1. Connect to the Scheduler admin tool with a web browser by going to the /scheduler-admin path on the server (for example http://localhost:10185/scheduler-admin/) and login with the user admin. The default password is admin.
  2. On the Database Connection Configuration page confirm database connection details.
  3. Choose Update and Connect.
  4. On the Database Installation/Upgrade page choose Upgrade to upgrade the database.

Upgrade the Database and Start the Scheduler

Start up the Scheduler by running the start command.

Windows:

%install_dir%/j2ee/cluster/server1/bin/start.cmd

UNIX:

${install_dir}/j2ee/cluster/server1/bin/start.sh
note

The upgrade of the database can take some time, as quite a lot of data is written to the database.

onsiteTopic

← Upgrading Redwood ServerMigrating Redwood Platform →
  • Preparation
  • Deliverables
  • Procedure
  • Unzip the New Deliverable
  • Redeploy the Adminserver1 and Server1
  • Upgrade the Database Schema
  • Upgrade the Database and Start the Scheduler
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 |