Redwood Documentation

Product Documentation

 

›Tuning Redwood Platform

RunMyJobsRedwoodScript Development

Developing Applications

  • Developing Applications

RedwoodScript

  • RedwoodScript
  • Scripting in the Shell
  • Mixing REL and RS Code in a Library
  • Controlling Process Servers with RedwoodScript
  • Controlling Queues with RedwoodScript
  • Managing Applications with RedwoodScript
  • Substitution Parameters
  • Date Formatting and Parsing
  • Impact of Modified Process Definitions or Chain Definitions on Processes and Chains
  • Using the RedwoodScript Definition Type
  • Using RedwoodScript in Processes
  • Using Eclipse to Create and Edit Process Definitions

Debugging Your Code

  • Changing Process Logging Levels

Triggering Custom Code

  • Triggering Custom Code
  • Using Triggers
  • Trigger and Action Examples
  • Using Actions
  • Executing Your Own Classes from a Library
  • Library Examples
  • Extending Redwood Server Functionality with Extension Points
  • Extending Edit Pages with ObjectPageExtensionPoint
  • Creating Extension Points
  • Extending Redwood Server Functionality with Extension Points

Using Tables

  • Using Tables to Store Frequently Used Values

PL/SQL API

  • Cronacle PL/SQL API Module
  • Creating the OracleJob Process Server
  • Using the OracleJob Definition Type
  • Packages
  • RS/JCS Views

Tuning Redwood Platform

  • Tuning Redwood Platform

Memory Tuning

  • Tuning Memory Usage and Garbage Collection

Reference

  • Using SQL to Query the Data Model
  • Embed Redwood Server Overviews into Extension Points with the Embed API
  • API Documentation
  • Script Date Formats
  • Datamodel
  • Redwood Expression Language Functions and Implicit Objects
  • RedwoodScript Scripting Contexts and Implicit Objects
← RS/JCS ViewsTuning Memory Usage and Garbage Collection →

Tuning Redwood Platform

When you install Redwood Platform, the installer creates a Redwood Platform service named Scheduler that controls Redwood Server. You can stop and start the service from the Windows Services Manager. Redwood Platform runs in a JVM, which gets configured with the tomcat9w.exe in the <install_directory>/j2ee/global/tomcat/bin folder. However, since the default service name for Redwood Platform 8 is Scheduler you need to provide the service name Scheduler on the command line:

<install_directory>/j2ee/global/tomcat/bin>tomcat9w.exe //ES//Scheduler

The tomcat9w.exe executable accepts the following switches:

  • //ES//<service_name> - gui for the configuration of the service
  • //MS//<service_name> - system-tray application which allows you to stop and start the service as well as configure the service.
tip

Create a shortcut to "<install_directory>/j2ee/global/tomcat/bin/tomcat9w.exe //ES//Scheduler" in the startup folder of your startup menu. That way, you can easily control and configure the service.

Great care needs to be taken when you change settings, please consult Redwood Platform documentation online prior to making any changes not described in this document. Redwood does not recommend you change settings on the Startup and Shutdown tabs on the configuration gui unless Redwood Support staff request you to do so.

Increasing the memory allocated to the JVM

By default, the amount of memory allocated to the JVM is 512 MB, this can be changed in the configuration gui in the Maximum memory pool field on the Java tab. Redwood recommends you set it to at least 1024MB if you experience performance issues.

Changing the log level

When you encounter issues and logging of the scheduler web application does not suffice, you might want to try and enable logging in Redwood Platform, this is recommended if the main issue has been identified as Redwood Platform-related.

By default, the verbosity level of Redwood Platform service is set to Error and should suffice; if you need to troubleshoot a problem in Redwood Platform, however, you might want to change that to Warning. Redwood recommends you gradually increase the verbosity level, as you might run out of disk-space, besides, it is easier to find information when the log files are smaller.

← RS/JCS ViewsTuning Memory Usage and Garbage Collection →
  • Increasing the memory allocated to the JVM
  • Changing the log level
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 |