Several different license scenarios are available. Depending
on the scenario, you might need to apply licenses to IBM® UrbanCode Deploy servers,
agents, or both.
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:
- Processor value unit (PVU) licensing
- Virtual server and managed virtual server (Authorized) 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 PVU license. If another
IBM UrbanCode Deploy server
starts and no more PVU licenses are available, that server does not
receive a license and does not use the other types of license.
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 a certain number of agents concurrently. The number of concurrent
agents may 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 a
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 http://pic.dhe.ibm.com/infocenter/tivihelp/v53r1/topic/com.ibm.lmt75.doc/ic-homepage_lmt.html
Virtual server and managed virtual server (Authorized)
licensing
In this scenario, 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.
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. 30
minutes after the process is complete, the server returns the license
to the license server. In this scenario, the
IBM UrbanCode Deploy 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 could not be
obtained for the IBM UrbanCode Deploy server
or an agent. If you replenish the licenses on the license server,
the IBM UrbanCode Deploy server
can run processes, but the warning message stays visible for 24 hours.
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 a certain number of these 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 could not be
obtained for the IBM UrbanCode Deploy server
or an agent. If you replenish the licenses on the license server,
the IBM UrbanCode Deploy server
can run processes, but the warning message stays visible for 24 hours.
For
this type of licensing, the Server License Type field
shows Session.
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 and the server and agents do not
require a new license.