To configure a GUI client login form to list multiple NFM-P systems

Purpose

By default, an NFM-P GUI client login form lists the main servers in one NFM-P system. If you manage multiple NFM-P systems at the same release, you can configure one login form to list the main servers in each system as login options.

Note: You cannot configure a client delegate server to display multiple server options on the client login form. If you need client connections to multiple NFM-P systems through a client delegate server, you must install one client delegate server software instance for each system.

Observe the following.

  • All main servers to which the client connects must be at the same NFM-P release.

  • The TLS truststore of the client must trust each NFM-P system in the multi-system configuration, which requires that the certificate of each system is signed by the same CA.

  • You can choose among multiple main servers only if you open the client using the desktop icon.

  • Performing a client download from the NFM-P https://server:port/client/ page overwrites the multiple-server configuration.

  • Uninstalling the client removes the client from the configuration of each main server listed on the login form.

Steps
 

Click on Application→Exit to close the NFM-P client GUI, if it is open. The client GUI closes.


Navigate to the client configuration directory, which by default is /opt/nsp/client/nms/config on RHEL, and C:\nsp\client\nms\config on Windows.


Open the nms-client.xml file using a plain-text editor.


Find the lines that begin with the <j2ee> and <systemMode> tags.

By default, the lines contain the IP address and port of each main server in the NFM-P system specified during the client installation.


For each standalone main server or redundant main server pair to display on the client GUI login form, perform the following steps:

  1. Copy the <j2ee> and <systemMode> sections.

  2. Paste the sections after the original <j2ee> and <systemMode> sections.

  3. Change the ejbServerHost IP address to the IP address or hostname of either main server in the system.

  4. Change the haJndiServerIpAddressOne and haJndiServerIpAddressTwo to the IP address or hostname of the main servers in the system.

    Note: For a standalone system, leave haJndiServerIpAddressOne and haJndiServerIpAddressTwo blank.

  5. Optionally, change the nameOne parameter for a standalone system, or the nameOne and nameTwo parameters for a redundant system.

    Note: Optionally, the nameOne and nameTwo values can be used as labels to help identify the NFM-P system. The nameOne and nameTwo parameters do not need to match the network domain of the main servers, and may be the same for the primary and standby main servers in a redundant system. In a standalone system, leave nameTwo blank.

  6. Save the changes and close the file.


Log in to the client GUI. The Server drop-down menu lists the multiple main servers.

End of steps