After the evaluation period, you must acquire a license
before you can use all product features. Several different license
scenarios are available. Depending on the scenario, you might need
to apply licenses to IBM® UrbanCode™ Deploy servers,
agents, or both.
IBM UrbanCode Deploy is supported on z/Linux. However, the licensing component is not supported on z/Linux, so in this
case, you must use an alternative means of proving your compliance with your licenses.
The following license scenarios are available. You can see the type of license that the server is
using by logging in to the IBM UrbanCode Deploy server,
clicking , and looking at the Server License Type field.
Note: IBM UrbanCode Deploy does
not support mixing license types. If more than one of these license
types are available on the license server,
IBM UrbanCode Deploy uses
the type of license with the highest priority. The license scenarios
have the following priority, from highest to lowest:
- Virtual server and managed virtual server (Authorized or Server
Agent) licensing
- Processor value unit (PVU) licensing
- Concurrent sessions (floating licenses)
- Concurrent sessions (token licenses)
For example, if the license server has each type of license,
when an
IBM UrbanCode Deploy server
starts, it retrieves a virtual server and managed server license.
If another
IBM UrbanCode Deploy server
starts and no more licenses of this type are available, that server
does not receive a license and does not use the other types of license.
The
IBM UrbanCode Deploy server
applies licenses to agents with the following order of precedence:
- Virtual server and managed virtual server (Authorized or Server
Agent) licensing
- Concurrent sessions (floating licenses)
- Concurrent sessions (token licenses)
If none of these license types are available, the server cannot assign licenses to agents.
Virtual server and managed virtual server (Authorized
or Server Agent) licensing
In this scenario, the server and
agents require separate licenses. You apply the
IBM URBANCODE
DEPLOY SERVER AGENT VIRTUAL SERVER license to the server
and
IBM URBANCODE DEPLOY SERVER AGENT MANAGED VIRTUAL SERVER licenses
to the agents. If an agent does not have a license, it cannot run
processes.
In this scenario, you can either allow the server to
assign licenses to agents automatically or you can assign licenses
to agents manually. See Applying licenses to servers and agents.
For
this type of licensing, the Server License Type field
shows Server Agent.
Processor value unit (PVU) licensing
In this
scenario, you apply the
IBM URBANCODE DEPLOY MANAGED CAPACITY
PVU LIC license to the
IBM UrbanCode Deploy server.
Then, the server can run processes. In this case, the agents do not
require a license; instead, each PVU license allows the server to
use some agents concurrently. The number of concurrent agents might
be limited or unlimited, depending on the terms of the PVU license.
If you are using this license scenario and the license server does
not have any PVU licenses for an
IBM UrbanCode Deploy server,
the server cannot run processes.
For this type of licensing, the Server
License Type field shows Managed Capacity.
You
can track your use of the PVU licenses with the IBM License Metric Tool. See IBM License Metric Tool.
Concurrent sessions (floating licenses)
In this scenario, the
IBM
URBANCODE DEPLOY SESSION PER SIMULTANEOUS SESSION LIC license is available to the
agents. When an agent runs a process, the
IBM UrbanCode Deploy
server retrieves a license from a license server. If the first license server does not have
available licenses, the
IBM UrbanCode Deploy
server attempts to retrieve a license from the other license servers. Regardless of whether
the process succeeds or fails, 30 minutes after the process is complete, the server returns
the license to the license server. The same agent that ran the process can reuse that license
immediately; however, the license is not available to any other agent until the 30-minute
waiting period is complete.
In this scenario, the IBM UrbanCode Deploy
server does not require a separate license.
When the license
server or servers run out of licenses, the agent runs the process but adds warnings in the
log. Also, a warning message appears on the server web interface. This message says that a
license cannot be obtained for the IBM UrbanCode Deploy
server or an agent. The message is shown to all users until an administrator closes
it.
For this type of licensing, the Server License Type field
shows Session.
Concurrent sessions (token licenses)
In this
scenario, the
IBM URBANCODE DEPLOY SESSION INITIAL TOKEN 2
YEAR license is available to the agents. When an agent runs
a process, the
IBM UrbanCode Deploy server
retrieves some token licenses from a license server. If the first
license server does not have enough available licenses, the
IBM UrbanCode Deploy server
attempts to retrieve licenses from the other license servers. 30 minutes
after the process is complete, the server returns the licenses to
the license server. In this scenario, the server does not require
a license.
When the license
server or servers run out of licenses, the agent runs the process but adds warnings in the
log. Also, a warning message appears on the server web interface. This message says that a
license cannot be obtained for the IBM UrbanCode Deploy
server or an agent. The message is shown to all users until an administrator closes
it.
For
this type of licensing, the Server License Type field
shows Session.
Licenses for use with the blueprint design server
The blueprint designer can
be used with all IBM UrbanCode Deploy license
scenarios and does not require separate or extra licenses. Process requests that you initiate by
provisioning a blueprint from the blueprint designer use the same agent licensing rules as requests
that you initiate from the server.
Licensing for upgraded servers
If you upgraded the server from a licensed
version 4.8.5, 5.0, or 6.0 to version 6.0.1 or later, the Server License
Type field is set to Disabled until you install a license
server and configure a license.
Licensing for z/OS
Agents on z/OS
use different licensing scenarios than agents on distributed systems.
(Agents on z/Linux use the same licensing scenarios as agents on distributed
systems.) Each agent requires a license, even if multiple agents
are running on a single LPAR. One agent is required on each environment,
even if the environments are on a single sysplex. To
run deployments, agents on z/OS must have one of the following licenses:
- IBM UrbanCode Deploy Agent for z/OS Workloads:
One license permits one agent to run deployments on z/OS.
- IBM UrbanCode Deploy Session for z/OS Workloads:
155 tokens permit one agent to run deployments on z/OS.