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
← Importing a Certificate AuthorityManaging Your Licenses with the License Manager →

on-site-related topic Checking Your License

A license enables certain licensed features, features that require a license item include:

  • Scripting module
  • Mail module
  • SNMP module
  • Import/Export module
  • Expiration date
  • Number of SAP Systems
  • Number of platform agents

A license is made of license keys that have a value, the value can be a date, number, boolean or string.

When you lack a license key, that license key will automatically have the value of false.

Navigate to "Configuration > License Keys" to inspect your license.

Your license should look similar to the one below:

Module.Scripting                         true
Module.ImportExport                   true
ProcessServerService.External.limit      100
ProcessServerService.OS.limit           100
ProcessServerService.SAP.limit     2
company.contract                   SLA-MSLN-PROD-1
company.name                           Example Inc
product.expiry                           20100630
request.requesting_version           9.2.10
signature  1;a300a310a300600a318a319a320a321a330a330400a330200a330600a340a340400a340600a350a380a380800
system.id                           prd1
note

In the above license, the licensee can create 100 external workload schedulers in total, that could mean 100 OS process servers (UNIX, Windows and HP OpenVMS) and no SAP process servers or 98 OS process servers and 2 SAP process servers, for example. It does not mean that the licensee can create 102 (100 OS and 2 SAP) process servers.

note

Monitoring-only process servers do not use a ProcessServerService.OS.limit key.

The following table illustrates some of the license keys that are available.

NameDescriptionType
Contract.SubscriptionPricing based on process usageBoolean
Module.AlertingActive Monitoring moduleBoolean
Module.ArchivingActive Archiving module for archiving process output to an Archive ServerBoolean
Module.AuditingAuditing allows tracking of changes to objects and restoration of objects from a previous iteration.Boolean
Module.FormsCan (runtime) forms be used in any formBoolean
Module.ImportExportImport/Export of objectsBoolean
Module.LoadBalancingLoad balancing capabilities.Boolean
Module.MailCan the System_Mail_Send process be used to send emailBoolean
Module.ProcessMonitorProcessMonitor supportBoolean
Module.ReconciliationActivate the reconciliation interface.Boolean
Module.RemoteEventRemote Event module that allows the jevent tool to be used.Boolean
Module.ScriptingScripting module for Redwood Script support and advanced REL functionsBoolean
Module.SecuritySecurity allows custom non-rank privileges and import/export for grants.Boolean
Module.SNMPCan System_SNMP_Send process to used to send SNMP trapsBoolean
Module.UserMessageUserMessage supportBoolean
Module.WebServices.InboundModule that allows the inbound web services to be published and called.Boolean
PricingModel.JobProcess Based PricingBoolean
ProcessServerService.AgentInitiatedWhether agents can use reversed communication where the agent connects to the server instead of the server connecting to the agent.Boolean
ProcessServerService.AS400.limitMaximum number of AS400 process servers that can be configured.Limit
ProcessServerService.External.limitMaximum number of external process servers that can be configured. If this is defined, then the sum of defined Windows/Unix platform agents, distinct web service endpoints, and SAP (AS ABAP, AS JAVA, BusinessObjects) systems cannot exceed this value. The external process servers are also constrained by their respective keys; if defined, the most restrictive applies. Note that this key does not allow/affect HP OpenVMS platform agents.Limit
ProcessServerService.GlobalExecution.limitMaximum number of concurrent customer jobs in an active state. Step jobs are not included in the count.Limit
ProcessServerService.Java.limitMaximum number of Java agents that can be configuredLimit
ProcessServerService.JCL_FTPRunning JES processes via a UNIX or Windows platform agent that contacts the host via its FTP server.Boolean
ProcessServerService.JDBC.limitMaximum number of JDBC process servers that can be instantiatedLimit
ProcessServerService.LowVolume.thresholdMaximum number of processes that a LowVolume process server can process in one day.Limit
ProcessServerService.MailConnector.limitMaximum number of concurrent customer Mailboxes in an active polling state.Limit
ProcessServerService.OraApps.limitMaximum number of Oracle Application Servers that can be configured.Limit
ProcessServerService.OracleJobAllow activation of the OracleJob service and the PL/SQL API.Boolean
ProcessServerService.OraOhi.limitMaximum number of Oracle Health Insurance Servers that can be configured.Limit
ProcessServerService.OS.limitMaximum number of Unix and Windows platform agents that can be configured. HP OpenVMS and AS/400 are not affected by this license key. Note that this license key can be further restricted by {@link #ProcessServerService_External_limit ProcessServerService.External.limit}; if both keys exist, both must be honored. The most restrictive applies.Limit
ProcessServerService.PeopleSoft.limitMaximum number of Oracle PeopleSoft Servers that can be configured.Limit
ProcessServerService.Publish.limitMaximum number of Publish process servers that can be instantiatedLimit
ProcessServerService.SAP.ApplicationsAPIIs support for the Applications API aka Business Automation Enabler (BAE) enabled. Used for Closing Cockpit, Solution Manager Integration, and SAP BW process chain type CPS.Boolean
ProcessServerService.SAP.BAEConnector.limitMaximum number of SAP BAE connectors that can be configured.Limit
ProcessServerService.SAP.CalendarSyncCan SAP calendars be synchronizedBoolean
ProcessServerService.SAP.ccIs Closing Cockpit integration enabled (requires ProcessServerService.SAP.ApplicationsAPI and optionally Module.Mail)Boolean
ProcessServerService.SAP.iDocSupport for iDocs.Boolean
ProcessServerService.SAP.JRFCCan jRFC be used to retrieve the output of SAP jobsBoolean
ProcessServerService.SAP.limitMaximum number of SAP process servers that can be instantiated. Note that this license key can be further restricted by ProcessServerService.External.limit; if both keys exist, both must be honored. The most restrictive applies.Limit
ProcessServerService.SAP.MassActivitiesProcessing of mass activities.Boolean
ProcessServerService.SAP.ProcessChainRestartRestart of SAP BW Process Chains / Processes.Boolean
ProcessServerService.SAP.SolutionManagerIs Solution Manager Integration enabled (requires ProcessServerService.SAP.ApplicationsAPI)Boolean
ProcessServerService.SAP.XBPAllVersionsCan the Redwood transports that allow full functionality in all XBP versions be usedBoolean
ProcessServerService.SAP.XBPExternalCan SAP external commands and programs be usedBoolean
ProcessServerService.SAP.XBPVariantIs support for working with variants enabledBoolean
ProcessServerService.SAP.XMBMessageMonitoringSupport for XMB message monitoring.Boolean
ProcessServerService.SAPBOBJ.limitMaximum number of SAP Business Objects process server services that can be configured Note that this license key can be further restricted by {@link #ProcessServerService_External_limit ProcessServerService.External.limit}; if both keys exist, both must be honored. The most restrictive applies.Limit
ProcessServerService.VMS.limitRunning VMS (DCL) processes via a platform agent.Limit
System.BusinessUsers.limitMaximum number of active business users.Limit
System.NamedUsers.limitMaximum number of active named users.Limit
System.ProductionIs this license for a production system? If this is false then only non-production systems can be connected to.Boolean
WebServices.OutboundServer.limitMaximum number of servers that can be contacted via SOAP calls. Limited by the number of distinct SOAP Credential Endpoints. Note that this license key can be further restricted by {@link #ProcessServerService_External_limit ProcessServerService.External.limit}; if both keys exist, both must be honored. The most restrictive applies.Limit
note

When you install a new license from a different contract, the old license keys remain in place and have no effect. You can use the license manager to remove old licenses by deactivating the contract. The license manager is available at: http://<server>:<port>/redwood/ui/licence/manager.jsp.

note

Licenses are valid only on the system for which they were generated; a license is valid only on the system with the same hostname and port on Redwood Platform or same SID on SAP NetWeaver.

Searching License Keys

You can search for license keys using the Search License Keys box located under your username on the top right-hand side of the user interface. This is known as IntelliSearch and allows you to specify complex queries in a simple way using prefixes. Prefixes are used to specify which property you are searching in and have short as well as long syntaxes. For example, if you want to display all license keys for contract SGO-FR-0210-008-P you would use the following search criteria:

c:SGO-FR-0210-008-P

You can search more than one property, as follows:

c:SGO-FR-0210-008-P n:Module.SNMP
note

No spaces should be entered before or after the colon (: ).

See the Advanced Object Search for more information.

The following table illustrates the available prefixes for license keys:

PrefixDescription
n, namename of the license key (case sensitive)
con, contractcontract name (case sensitive)

Special Restrictions

License Expiration

When a license has an expiration date, usually for testing purposes, and it expires, all scheduled processes will continue to run and be rescheduled by their submit frame, if applicable. You will, however, not be able to access the system via its user interface. If you are in this situation and you want to stop Redwood Server, you need to stop the Redwood Server application running in the application server. How you do this depends on your application server. You might wish to remove Redwood Server completely. See the Uninstalling Redwood Server topic for more information.

Process Server Licensing

The maximum amount of external process servers is specified by the ProcessServerService.External.limit license key, it would normally be coupled with other license keys that share the same number which are ProcessServerService.OS.limit, WebServices.OutboundServer.limit and ProcessServerService.SAP.limit. To allow you the greatest flexibility, Redwood allows you to create as many OS, web service, and SAP (AS ABAP, JAVA, BusinessObjects) process servers as you want, as long as the grand total OS process servers + web services + SAP process servers does not exceed the value defined in ProcessServerService.External.limit.

The most restrictive license key applies; this means that even if ProcessServerService.External.limit is set to a high number, if ProcessServerService.SAP.limit is set to 1 you will only be able to create a maximum of 1 SAP system in other words, if a license key is present, it has to be honored. If you only have ProcessServerService.External.limit and not ProcessServerService.SAP.limit, you may still create SAP systems, provided the grand total OS process servers + web services + SAP process servers does not exceed the value defined in ProcessServerService.External.limit.

At any time, you may shutdown and delete a process server to make room for another, regardless of being an SAP, web service or OS process server. Note, however, that to delete a process server all dependent objects, such as processes that ran on that process server, need to be deleted first.

note

Monitoring-only platform agents on Microsoft Windows and UNIX are free of charge. You can create as many of them as you require.

onsiteTopic

← Importing a Certificate AuthorityManaging Your Licenses with the License Manager →
  • Searching License Keys
  • Special Restrictions
  • License Expiration
  • Process Server Licensing
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 |