About the RunMyJobs License
A RunMyJobs license consists of a list of license keys, each of which has a value that can be a date, number, true/false, or a string. If you do not have a license for a given feature, that license key will have a value of false.
You can have multiple copies of a given license key. RunMyJobs will always use the license key with the highest value (as long as it has not expired). For example, assume you have installed a license to connect to five SAP instances and five Platform Agents, and you have received a license for three more SAP instances for a period of three months. You will be able to connect to eight SAP instances until the expiration date on the license has been reached. Once the expiration has been reached, no further actions are required to enable the previous five SAP instances. Note, though, that you will have to delete the three SAP instances before the expiration period has been reached.
Note: Licenses are valid only on the system for which they were generated. A given license is valid only on the system with the same hostname and port on the RunMyJobs server or the same SID on SAP NetWeaver.
To request a license, create a support ticket in the Support Portal and paste the complete license request into the ticket. You can use the License Manager (Configure > Admin > Configuration > License Keys) to install the new license.
A sample list of license keys is provided below:
Note: In the above license, the licensee can create 100 external workload schedulers in total. That could be 100 OS Job Servers (UNIX, Windows and HP OpenVMS) and no SAP Job Servers, or 98 OS Job Servers and 2 SAP Job Servers, for example. It does not mean that the licensee can create 102 (100 OS and 2 SAP) Job Servers.
Note: Monitoring-only Job Servers do not use a ProcessServerService.OS.limit key.
The following table illustrates some of the license keys that are available.
| Name | Description | Type |
|---|---|---|
Contract.Subscription
|
Pricing based on Robot Usage | Boolean |
Module.Alerting
|
Active Monitoring module | Boolean |
Module.Archiving
|
Active Archiving module for archiving process output to an Archive Server | Boolean |
Module.Auditing
|
Auditing allows tracking of changes to objects and restoration of objects from a previous iteration. | Boolean |
Module.Forms
|
Can (runtime) forms be used in any form | Boolean |
Module.Hosting
|
Hosting module for increased environment isolation | Boolean |
Module.ImportExport
|
Import/Export of objects | Boolean |
Module.IsolationGroup
|
The IsolationGroup module allows creating isolation groups in the full version. | Boolean |
Module.LoadBalancing
|
Load balancing capabilities. | Boolean |
Module.Mail
|
Can the System_Mail_Send process be used to send email | Boolean |
Module.ProcessMonitor
|
ProcessMonitor support | Boolean |
Module.Reconciliation
|
Activate the reconciliation interface. | Boolean |
Module.RemoteEvent
|
Remote Event module that allows the jevent tool to be used. | Boolean |
Module.Scripting
|
Scripting module for Redwood Script support and advanced REL functions | Boolean |
Module.Security
|
Security allows custom non-rank privileges and import/export for grants. | Boolean |
Module.SNMP
|
Can System_SNMP_Send process to used to send SNMP traps | Boolean |
Module.UserMessage
|
UserMessage support | Boolean |
Module.WebServices.Inbound
|
Module that allows the inbound web services to be published and called. | Boolean |
PricingModel.Job
|
Process Based Pricing | Boolean |
ProcessServerService.AgentInitiated
|
Whether agents can use reversed communication where the agent connects to the server instead of the server connecting to the agent. | Boolean |
ProcessServerService.AS400.limit
|
Maximum number of AS400 process servers that can be configured. | Limit |
ProcessServerService.External.limit
|
Maximum 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.limit
|
Maximum number of concurrent customer jobs in an active state. Step jobs are not included in the count. | Limit |
ProcessServerService.JCL_FTP
|
Running JES processes via a UNIX or Windows platform agent that contacts the host via its FTP server. | Boolean |
ProcessServerService.JDBC.limit
|
Maximum number of JDBC process servers that can be instantiated | Limit |
ProcessServerService.LowVolume.limit
|
Maximum number of Low Volume process servers that can be configured. | Limit |
ProcessServerService.LowVolume.threshold
|
Maximum number of processes that a LowVolume process server can process in one day. | Limit |
ProcessServerService.MailConnector.limit
|
Maximum number of concurrent customer Mailboxes in an active polling state. | Limit |
ProcessServerService.OraApps.limit
|
Maximum number of Oracle Application Servers that can be configured. | Limit |
ProcessServerService.OracleJob
|
Allow activation of the OracleJob service and the PL/SQL API. | Boolean |
ProcessServerService.OraOhi.limit
|
Maximum number of Oracle Health Insurance Servers that can be configured. | Limit |
ProcessServerService.OS.limit
|
Maximum 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 ProcessServerService_External_limit and ProcessServerService.External.limit if both keys exist,
both must be honored. The most restrictive applies.
|
Limit |
ProcessServerService.PeopleSoft.limit
|
Maximum number of Oracle PeopleSoft Servers that can be configured. | Limit |
ProcessServerService.Publish.limit
|
Maximum number of Publish process servers that can be instantiated | Limit |
ProcessServerService.SAP.ApplicationsAPI
|
Is 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.limit
|
Maximum number of SAP BAE connectors that can be configured. | Limit |
ProcessServerService.SAP.CalendarSync
|
Can SAP calendars be synchronized | Boolean |
ProcessServerService.SAP.cc
|
Is Closing Cockpit integration enabled (requires ProcessServerService.SAP.ApplicationsAPI and optionally Module.Mail) | Boolean |
ProcessServerService.SAP.iDoc
|
Support for iDocs. | Boolean |
ProcessServerService.SAP.JRFC
|
Can jRFC be used to retrieve the output of SAP jobs | Boolean |
ProcessServerService.SAP.limit
|
Maximum number of SAP process servers that can be instantiated. If the value is 0, then you can create an
unlimited number of SAP Systems, however, each must reside in its own isolation group. Note that this license
key can be further restricted by ProcessServerService_External_limit and ProcessServerService.External.limit if both keys exist, both must be honored.
The most restrictive applies.
|
Limit |
ProcessServerService.SAP.MassActivities
|
Processing of mass activities. | Boolean |
ProcessServerService.SAP.ProcessChainRestart
|
Restart of SAP BW Process Chains / Processes. | Boolean |
ProcessServerService.SAP.SolutionManager
|
Is Solution Manager Integration enabled (requires ProcessServerService.SAP.ApplicationsAPI) | Boolean |
ProcessServerService.SAP.XBPAllVersions
|
Can the Redwood transports that allow full functionality in all XBP versions be used | Boolean |
ProcessServerService.SAP.XBPExternal
|
Can SAP external commands and programs be used | Boolean |
ProcessServerService.SAP.XBPVariant
|
Is support for working with variants enabled | Boolean |
ProcessServerService.SAP.XMBMessageMonitoring
|
Support for XMB message monitoring. | Boolean |
ProcessServerService.SAPBOBJ.limit
|
Maximum number of SAP Business Objects process server services that can be configured
Note that this license key can be further restricted by ProcessServerService_External_limit and ProcessServerService.External.limit
if both keys exist, both must be honored. The most restrictive applies.
|
Limit |
ProcessServerService.VMS.limit
|
Running VMS (DCL) processes via a platform agent. | Limit |
System.BusinessUsers.limit
|
Maximum number of active business users. | Limit |
System.NamedUsers.limit
|
Maximum number of active named users. | Limit |
System.Production
|
Is this license for a production system? If this is false then only non-production systems can be connected to. | Boolean |
WebServices.OutboundServer.limit
|
Maximum number of HTTP process servers that can be configured. HTTP process servers process both HTTP and SOAP requests.
In releases older than 9.2.6 this used to be a limit on the number of distinct SOAP Credential Endpoints.
This has been changed to make this limit work the same way as ProcessServerService limits.
Note that this license key can be further restricted by ProcessServerService_External_limit and 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.
Special Restrictions
Job Server Licensing
The maximum number of external Job Servers is specified by the ProcessServerService.External.limit license key. This license key should have the same number as ProcessServerService.OS.limit, WebServices.OutboundServer.limit and ProcessServerService.SAP.limit. You can create as many OS, web service, and SAP (AS ABAP, JAVA, BusinessObjects) Job Servers as you want, as long as the grand total (OS Job Servers + web services + SAP Job Servers) does not exceed 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 one SAP system. If you have only ProcessServerService.External.limit and not ProcessServerService.SAP.limit, you can still create SAP systems, provided the grand total (OS Job Servers + web services + SAP Job Servers) does not exceed the value defined in ProcessServerService.External.limit.
At any time, you can shut down and delete a Job Server to make room for another.
Note: Monitoring-only Platform Agents on Microsoft Windows and UNIX are free of charge. You can create as many of them as you require.
License Expiration
If 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 (Undefined variable: General.SubmitFrame), if applicable. However, you will not be able to access the system via its user interface. If you are in this situation and you want to stop RunMyJobs, you must stop the RunMyJobs application running on its application server.