Creating a Manager Server for Unified Collaboration Administration

Last Updated : May 06, 2026 |
Prolog information
Unified Collaboration Administration (UCA) is an Avaya Breeze® platform service that stores the static administration data for Avaya Oceana®. Control Manager uses the UCA REST API to add agent, attribute, provider, and resource information to the Avaya Breeze® platform components in Avaya Oceana®. Therefore, you must configure the Avaya Oceana® server URL connection information for Control Manager.
  1. Log on to Control Manager.
  2. Navigate to ConfigurationAvaya Oceana™Server Details.
  3. On the Oceana Server List page, click Add.
  4. In the Primary Server tab, perform the following steps:
    1. In the Alias field, enter an alias name for the server.
    2. In the API URL field, enter the URL of the UCA ReST interface.
      ADDITIONAL INFORMATION:
      For example: https://<AvayaOceanaCluster1_FQDN>/services/UCAStoreService/uca
      Important:
      • If the Avaya Oceana® and Avaya Analytics™ server use the same UCA server (Common setup), the API URL configured on both must match, including using matching address formats. For example, you must not use an IP address on one and FQDN on the other.
    3. In the Version field, select the Avaya Oceana® release that you are managing through Control Manager.
    4. Select the Enable Authorization option. For more information about the Enable Authorization option and its related parameters, see Configuring token-based access between Control Manager and Avaya Oceana, Avaya Analytics, or Avaya Workspaces for Call Center Elite.
    5. In the Deployment type field, select any of following deployment types that shows correct type for Avaya Oceana® server that you configure. Each deployment type enforces respective guardrails for the total number of attributes assigned to all agents in the system. You can move the mouse over the field and view the guardrail details for the selected deployment type.
  5. Click Save.
  6. Click Test to validate the connection details and interoperability configurations required to communicate with the system.
    ADDITIONAL INFORMATION:
    Note:
    • After you upgrade Control Manager, the Avaya Oceana® system that you configured sets Blank as the deployment type by default. Ensure that you change the deployment type to the appropriate value.
    • Avaya Oceana® 3.8.2 and later supports the 4X Large deployment type. If the 4X Large deployment type is already selected, you cannot select an Avaya Oceana® version earlier than 3.8.2 as they do not support this deployment type.
    • There is a guardrail/threshold value for a maximum number of attributes you can assign to an agent. The default value is 500.
      Similarly, there is a guardrail/threshold value for maximum assigned agent attributes in the system. The threshold value depends on the Oceana system's deployment type configured in the location.
      The system restricts the attributes assignment operation if the assigned attributes exceed any of the above threshold values.
    • You must assign the system to a location before administering the system through Control Manager.
    The following table details the total assigned attributes threshold values:
    Deployment Type
    Total Assigned Agent Attributes Limit in system
    Small
    16500
    Large
    165000
    Extra Large
    330000
    3X Large
    742500
    4X Large
    1237500