Using Universal Query to Display License Information

Owned by Stonebranch (Deactivated)
Last updated: Feb 01, 2024

Overview

Starting with 6.9.0.0, Universal Query can display license information for Universal Agent 6.9.0.0 and later. The information can be used to quickly confirm the source and status of a Universal Agent's license.

UQUERY Output for a Universal Controller-Obtained License

The following information is returned when license information is obtained from a Universal Controller.

This information shows the following:

  • The Agent was granted a license by Universal Controller.
  • An unlimited number of distributed agents (that is, Linux and Windows) and z/OS agents are permitted, along with an unlimited number of concurrent USAP and UPPS connections.
  • The Universal Agent for SOA is licensed and permits HTTP outbound connections and inbound and outbound JMS and SOAP connections.
  • The license expires on December 31, 2029 at 23:59:59 local time.

Note

If the licenses were expired, the expiration date would be followed by an (EXPIRED) tag.


UQUERY Output for Locally-Configured Licenses

The following information is returned when license information is obtained from local configuration files.

This information shows the following:

  • The Agent is still using locally-configured licenses. In this case, the Agent is connected to a pre-6.9.0.0 Controller, which cannot provide an Agent with a remote license.
  • The UCMD Manager, UDM Manager, and UPPS have valid licenses that will expire at midnight on December 31, 2029.
  • USAP is not licensed on this Agent.
  • Universal Agent for SOA is licensed for the Agent and will allow connections for all supported protocols.

Note

If any of the licenses were expired, the expiration date would be followed by an (EXPIRED) tag.


UQUERY Output for an Un-Acquired License

The following information is returned when a Universal Agent has not yet acquired its license.

This information shows the following:

  • The Agent expects to receive a license from Universal Controller, but has not received a response to its HELLO message. In this case, the auto_start value in the uag component definition was set to yes, but the oms_servers value in the UAG Server configuration file did not contain a valid port number for the OMS Server.