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
← Configuring Platform Agents on Microsoft Cluster ServiceUpgrading Redwood Platform →

on-site-related topic Upgrading Redwood Server

If you have a previous version of Redwood Server and would like to keep all data, you will need to upgrade. When you upgrade, the database is also upgraded, it is advised to back up the database prior to upgrading, to be on the safe side. An upgrade also allows you to keep all you existing settings. It is advised to read the following sections before you upgrade:

  • New Features that were implemented
  • Release Notes of the current release; improvements that can potentially change the behavior are listed here; this list is by no means complete, as not all implementations can be taken into account.

Prerequisites

  • Redwood Server version 9.1.5 or later
  • If you are on a version below 9.0.22, you must first upgrade to 9.0.22 prior to upgrading to 9.1.5 and, finally, upgrading to 9.2 or later.

Process Flow

Service Pack Installation

  1. You backup the database and the file system of your application server.
  2. You download and extract the redwood-platform-9_2_10_<n>.zip.
  3. Unzip redwood-platform-9_2_10_<n>.zip.
  4. On Windows with a Windows service handling Redwood Server:
  5. Run tomcat8w //MS//<Service_Name> (defaults to Scheduler) and copy any JVM arguments into a text file.
  6. Delete the service, sc delete <server_name>, run <install_dir>/j2ee/cluster/global/bin/rw_service.bat to install and start a new service.
  7. On UNIX or Windows without server:
  8. Copy <old_install_dir>/j2ee/cluster/adminserver1/bin/setvars.bat (setvars.sh on UNIX) to the equivalent path in <new_install_dir>, do the same for <old_install_dir>/j2ee/cluster/server1/bin/setvars.bat,
  9. Run <new_install_dir>/j2ee/cluster/adminserver1/bin/start.cmd, navigate to http://<server>:10185 and connect to the database, choose Update to update the database, and start the new server <new_install_dir>/j2ee/cluster/server1/bin/start.cmd, ensure it is running properly, if so, stop the admin server <new_install_dir>/j2ee/cluster/adminserver1/bin/stop.cmd.

If you have SAP Systems and are upgrading from 9.1 or earlier, you have to edit each of them to ensure new destinations are created.

  1. Navigate to "Environment > SAP".
  2. Choose Edit from the context-menu of each SAP System go to XBP tab and make a small change such as adding a word to the Description or Documentation field.
  3. Choose Save & Close.

Hotfix Installation

Follow the procedure as outlined by Redwood Support. In general, a hotfix is either a JAR or CAR file; JAR files are copied to <install_dir>/j2ee/cluster/global/tomcat/lib, CAR files are imported using imports (Promotion > Imports).

Procedure

  • Upgrading Redwood Platform

onsiteTopic

← Configuring Platform Agents on Microsoft Cluster ServiceUpgrading Redwood Platform →
  • Prerequisites
  • Process Flow
    • Service Pack Installation
    • Hotfix Installation
  • Procedure
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 |