Redwood Documentation

Product Documentation

 

›Configuration

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
← Installing and Configuring Redwood Platform Service on WindowsConfiguring the HTTP or HTTPS Interface of Redwood Platform →

on-site-related topic Submitting Processes and Licensing on Startup

Redwood Platform supports executing a autoexec files at the time of startup of the application server. The autoexec file can be either a CAR file (to be imported/executed) or a license file; in this case the license is installed automatically. The CAR file can contain a specially crafted XML file that submits a process.

You license a system automatically by copying the license text into a autoexec.license file located in <install_dir>/j2ee/cluster/global/conf.

Likewise, the autoexec.car is located in <install_dir>/j2ee/cluster/global/conf.

The CAR file is only executed once at startup, a checksum for the autoexec.car file is generated, if it matches the checksum saved in the Redwood Server registry, the CAR file will not be executed, if it does not match, the checksum registry entry is updated with the new checksum.

You can use any CAR file, all objects in the CAR file will be imported. To submit a process from the CAR file, create a directory named Submit at the root of the CAR file and place an XML file into that directory. The name of the XML must match the following syntax: <partition>.<definition>, where <definition> is the name of a process definition or chain definition; furthermore, the contents of the XML must at the very least contain the following:

<Submit JobDefinition="<partition>.<job_definition>" />

You can specify process notes, process parameters.

Registry Keys

  • /configuration/boot/car/checksum - checksum of the autoexec.car file
  • /configuration/boot/car/error - if this registry entry is set to abort, any error that occurs when you import the CAR file will cause the startup of the application server to abort.
  • /configuration/boot/car/location - location of the autoexec.car file, <install_dir>/j2ee/cluster/global/conf by default.

Example

Example creating a car file from the command line:

$ cd /tmp
$ mkdir car
$ cd car
$ mkdir Submit
$ echo '<Submit JobDefinition="GLOBAL.System_Sleep.xml">
  <JobNote String="Automatically submitted on startup" />
</Submit>' > Submit/GLOBAL.System_Sleep.xml
$ jar -cf $RW_INSTALL/j2ee/cluster/global/conf/autoexe.car *
$ $RW_INSTALL/j2ee/cluster/server1/bin/restart.sh
$

The contents of the XML file in the CAR file:

<Submit JobDefinition="GLOBAL.System_Sleep.xml">
  <JobNote String="Automatically submitted on startup" />
</Submit>

See Also

Installing Redwood Platform

onsiteTopic

← Installing and Configuring Redwood Platform Service on WindowsConfiguring the HTTP or HTTPS Interface of Redwood Platform →
  • Registry Keys
  • Example
  • 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 |