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 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 Masalan Inc
product.expiry 20100630
request.requesting_version M37
signature 1;a300a310a300600a318a319a320a321a330a330400a330200a330600a340a340400a340600a350a380a380800
system.id prd1
Note
In the above license, the licensee can create 100 external schedulers in total, that could mean 100 OS process servers 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.
The following table illustrates some of the license keys that are available.
License key |
Description |
company.contract |
Contract number. |
Module.Scripting |
Scripting using RedwoodScript. |
Module.Security |
The security module allows individual grants for system and object privileges. |
Module.ImportExport |
Import/export repository objects. |
Module.Mail |
Use the System_ConfigureMail and System_SendMail jobs to send email. |
Module.SNMP |
Use the System_SendTrap job to send SNMP traps. |
Module.PermaLink |
Allows third-party software to interface with SAP CPS. |
ProcessServerService.External.limit |
Total number of external process servers (for example OS and SAP process servers) |
ProcessServerService.OS.limit |
Number of platform agent on UNIX/Windows. |
ProcessServerService.SAP.ApplicationsAPI |
The SAP Applications API is available |
ProcessServerService.SAP.cc |
Closing Cockpit features are available. |
ProcessServerService.SAP.CalendarSync |
SAP Calendar synchronization is available |
ProcessServerService.SAP.MassActivities |
Mass activity scheduling is available |
ProcessServerService.SAP.ProcessChainRestart |
Process chain restart is available |
ProcessServerService.SAP.SolutionManager |
Solution manager integration is available. |
ProcessServerService.SAP.XBPAllVersions |
Use the Redwood transports that allow full functionality in all XBP versions. |
ProcessServerService.SAP.XBPExternal |
Use the SAP external command jobs. |
ProcessServerService.SAP.XBPVariant |
Support for working with variants using our user interface. |
ProcessServerService.SAP.limit |
Number of SAP process servers/SAP Systems that can be created, 2 in this example. If the value is 0, then you can connect to an unlimited amount of SAP Systems, however, you can only interact with one at any given time, see the licence restrictions below. |
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/scheduler/ui/licence/manager.jsp.
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 and 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:
Prefix |
Description |
n, name |
name of the license key (case sensitive) |
con, contract |
contract name (case sensitive) |
Note
You may be restricted to connecting to a single SAP System from within SAP CPS at any given time; this depends on your license, your privileges and the value of the ProcessServerService.SAP.limit license key.
If the ProcessServerService.SAP.limit license key is limited to 0, the following restrictions are in place:
one SAP System may be created per partition with one XBP client.
any partition with a null isolation group is read-only.
only the system can create partitions with a null isolation group.
all monitors from SAP (via XAL) will be created in the appropriate isolation group.
SAP batch event will raise events in the isolation group only.
job control rules will function only for jobs from the defined XBP client, child jobs will be picked up regardless in which client they were created.
variant management will be limited to the defined XBP client.
BW restart will be possible, however, it requires the ProcessServerService.SAP.ProcessChainRestart license key
Mass activities will be possible, however, they require the ProcessServerService.SAP.MassActivities license key
Redwood transports will be available for mass activities
SAP Applications API will be available, however, they require the ProcessServerService.SAP.ApplicationsAPI license key
SAP_AbapRun, SAP_BW_ProcessChainRun, and all the other SAP job definitions that run jobs will only allow ABAP reports, variants, and process chains that have been imported into SAP CPS
The maximum amount of external process servers is specified by the ProcessServerService.External.limit license key, it would normally be coupled with two other license keys that share the same number which are ProcessServerService.OS.limit and ProcessServerService.SAP.limit. To allow you the greatest flexibility, SAP allows you to create as many OS and SAP process servers as you want, as long as the grand total OS process servers + 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 either being an SAP or OS process server. Note, however, that to delete a process server all dependent objects, such as jobs that ran on that process server, need to be deleted first.
Not all vendors distribute the same functionality, please see the Different Versions section for more information.