Administer > Configure Multiple UCMDB Servers

Configure Multiple UCMDB Servers

It is possible to configure the CMS UI to work with multiple UCMDB Servers. This is done by replicating the section <ucmdb_configuration>…</ucmdb_configuration> in the ucmdb_browser_config.xml file, as shown in the following example:

<ucmdb_configuration name="configuration-1">
    <protocol>https</protocol>
    <host_name>ucmdb-server-1</host_name>
    <host_port>8443</host_port>
    <context_name>/</context_name>
    <customer>
        <customer_name>company_a</customer_name> 
        <customer_number>1</customer_number> 
    </customer>
</ucmdb_configuration>
<ucmdb_configuration name="configuration-2">
    <protocol>https</protocol>
    <host_name>ucmdb-server-2</host_name> 
    <host_port>8443</host_port>
    <context_name>/</context_name>
    <customer>
        <customer_name>company_b</customer_name> 
        <customer_number>6</customer_number> 
    </customer>
</ucmdb_configuration>

There is no limit to the number of UCMDB Servers that you can add in this manner.

Note  

  • The value of the name attribute in each configuration (for example, configuration-1 or configuration-2 in the example above) is optional, but if it is defined it must be a unique value.
  • You can specify a default customer by name, ID, or both. If you include the <customer>...</customer> tag, you must provide details for it. On the login page of the CMS UI, only the customer that you defined as the default customer for a particular UCMDB server will be visible in the drop-down list.

  • Configuring multiple UCMDB servers is not relevant to the embedded CMS UI since the embedded CMS UI can connect to only one server. For more information, see Multiple Customer Support for the Embedded CMS UI.

For each configuration section, the customers for that UCMDB server are retrieved automatically at the moment that the application server starts, and a connection for each customer is formed using the value from the name attribute in the ucmdb_configuration tag (if the name attribute is not defined, the value from the host_name tag is used) and the name of the customer. All these connections appear in the drop-down list in the login screen. For example, in the case of the xml example above, if configuration-1 has two customers and configuration-2 has three customers, then the drop-down list will contain five connections, in the form of:

  • configuration-1 – CustomerName1
  • configuration-1 – CustomerName2
  • configuration-2 – CustomerName1
  • configuration-2 – CustomerName2
  • configuration-2 – CustomerName3

If the UCMDB server defined in configuration-2 is inaccessible, then the connection for it is still visible in the drop-down list (without any customer information), even if the user cannot login using that server. In that case, the list will contain the connections:

  • configuration-1 – CustomerName1
  • configuration-1 – CustomerName2
  • configuration-2

If only one server is available, then the server name does not appear in the connection name.

Caution If you have launched the CMS UI with a given UCMDB server, you cannot open another instance of the CMS UI with a different UCMDB server with the same web browser. You can, however, open another instance of the CMS UI with a different UCMDB Server if you use a different web browser. For example, if you opened the CMS UI with Internet Explorer with a given UCMDB server, you can open the CMS UI using Google Chrome with another UCMDB server.

Note The same LW-SSO settings from the ucmdb_browser_lwsso_config.xml file are used for all UCMDB configurations.

Retrieving Customer States

You can specify whether to retrieve the state(s) for each customer so that the state appears next to the customer name in the login drop-down list. Currently, the possible states are Actual and Authorized. The default value for this setting is false, meaning that the customer state does not appear in the login drop-down list. If you change it to true, the state(s) for each customer is also retrieved, in addition to the customer name. So if the server host has two customers, Customer-1 with an Actual state and an Authorized state, and Customer-2 with an Actual state, then the connections will be host – Customer-1 (Actual), host – Customer-1 (Authorized), and host – Customer 2 (Actual).

This setting also applies to the embedded CMS UI, as described below.

To specify whether to retrieve the state for each customer:

In UCMDB, go to Administration > Infrastructure Settings > UCMDB Browser Settings, and set the value for Enable customer states.

Multiple Customer Support for the Embedded CMS UI

The embedded CMS UI can connect to only one UCMDB server and so configuration for multiple UCMDB servers is not relevant. The information regarding the server is automatically sent by the UCMDB server into which the CMS UI is embedded. Similar to the case of login for the non-embedded CMS UI, the embedded CMS UI searches for all the customers for that server, and for each customer it creates a different connection. For example, if the host server has two customers, customer1 and customer2, then the connection names customer1 and customer2 appear in the drop-down list on the login page.

Also, if the setting to receive customer states has been set to true (as described above), then the customer state appears next to the customer name in login drop-down for the embedded CMS UI.

Send Help Center feedback