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.

›PL/SQL API

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
← Using Tables to Store Frequently Used ValuesCreating the OracleJob Process Server →

Cronacle PL/SQL API Module

The PL/SQL API module was added to allow to act as a compatibility layer for Redwood Server version 2023.3.0 in order to support legacy Cronacle version 7 calls. Cronacle version 7 is Oracle-based and allows calls to PL/SQL packages, use Oracle objects such as tables and views directly. This functionality has now been ported to version 2023.3.0 using the PL/SQL API module for which a specific license is required.

You use the 2023.3.0 JDBC framework combined with the version 7 API implementation, which is not yet complete, to migrate your processes to version 2023.3.0. The following chapter lists packages, views and their implementation status - some features have been permanently removed from version 2023.3.0 and replaced with new implementations, other features have been improved upon. The migration to a mostly database-independent platform has caused some features to vanish, these are meant to be filled by this module.a

REL functions have been added to provide functionality used in preconditions.

See Also

  • JCS Views
  • JCS PAckages
← Using Tables to Store Frequently Used ValuesCreating the OracleJob Process Server →
  • 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 |