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 UrbanCode™ Deploy servers, agents, or both.
Important: Regardless of the license scenario that applies to your environment, each licensed agent requires a connection from each server to the Rational® Common Licensing server. Therefore, the license server must be able to have enough open connections for your topology. The total number of connections to the license server depends on how many agents and servers are running.
If you are using the License Metric Tool to monitor license usage, you must ensure that agents are connected to the server so that the correct license usage is reported. The agents get their license type from the connection to the UrbanCode Deploy server. Therefore, if the agents cannot connect to the UrbanCode Deploy server, the .swtag files in the agent directory might be incorrect, and as a result, the license usage reports from the License Metrics Tools might not reflect actual usage. Check firewalls and other agent connectivity issues to be sure that licenses are available and accurately accounted for.
The following license scenarios are available.
Virtual server and managed virtual server (Server Agent) licensing#
In this scenario, the server and agents require separate licenses. You apply the
HCL URBANCODE DEPLOY SERVER AGENT VIRTUAL SERVER license to the server and
HCL 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. The licenses are released when the agents are deleted.
UrbanCode Deploy is configured with a finite number of Server Agent licenses for an organization. When the maximum number of licenses are in use, any additional agents configured will become unlicensed and cannot run processes. Any process run on an unlicensed agent will log an error message. To resolve licensing warnings, additional licenses must be obtained, or existing licenses must be reassigned among the agents.
Licenses for use with high-availability servers#
If you use a high-availability server configuration, you might require a different license server configuration. See High-availability options for Rational License Key Server.
If you have an UrbanCode Deploy Clustered HA configuration, each of the UrbanCode Deploy Servers in that configuration will need to have an 'HCL URBANCODE DEPLOY SERVER AGENT VIRTUAL SERVER' license available for it.
Licenses for use with the blueprint design server#
The blueprint designer can be used with all 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 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:
HCL URBANCODE DEPLOY MANAGED CAPACITY PVU SYS Z LIC
HCL URBANCODE DEPLOY SERVER AGENT VIRTUAL SERVER SYS Z LICand
HCL URBANCODE DEPLOY SERVER AGENT MANAGED VIRTUAL SERVER SYS Z LIC
HCL URBANCODE DEPLOY SESSION PER SIMULTANEOUS SESSION SYS Z LIC
HCL URBANCODE DEPLOY AGENT FOR Z/OS WORKLOADS PER MVS LIC: One license permits one agent to run deployments on z/OS.
HCL URBANCODE DEPLOY SESSION FOR SIMULTANEOUS SESSION FOR Z/OSWORKLOADS LIC: 155 tokens permit one agent to run deployments on z/OS. As with token licensing on other platforms, the agent retains the tokens for 15 minutes after the deployment is complete.
Parent topic: License management