Page Comparison

Prerequisites

...

Anchor
HA_1Server_Prepare_Database HA_1Server_Prepare_Database

Preparing the Database

Include Page
ENLITEUMSP:_Icon_handlungsaufforderung.png ENLITEUMSP:_Icon_handlungsaufforderung.png

 Create a database schema and a user for the UMS. Use the relevant DBMS program and its documentation. See also Connecting External Database Systems.

...

1. Verify that each server can "see" the other servers via the network.
   

   Include Page
   ENLITEUMSP:_UMS HA: No NAT or Proxies ENLITEUMSP:_UMS HA: No NAT or Proxies

   
   
   
2. Verify that the time on all servers is synchronized.
   

   Include Page
   ENLITEUMSP:_UMS HA: No Time Difference Warning ENLITEUMSP:_UMS HA: No Time Difference Warning

   
   
   
3. For Linux systems, make the directory /root writable for the user root.

...

1. Launch the UMS installer.

   Info
   You need administration rights to install the IGEL UMS HA.

   
   
   

2. Read and confirm the License Agreement.
   
   

3. Read the Information regarding the installation process.
   
   

4. Select a path for the installation.
   
   

5. Depending on your desired HA network configuration, select the components to be installed: UMS Server + UMS Load Balancer or UMS Server. 

   Note
   title Installing UMS Server and UMS Load Balancer on Separate Servers
   If you install HA network components on separate servers, UMS Server must always be installed first. In this case, the IGEL network token, which is required for the integration of further servers into the HA network, will be created. Additionally, the UMS Administrator application, necessary for the further management of the installation, will be installed too. After configuring and enabling the database via the UMS Administrator, the UMS Server will be available in the HA network. If you install an individual UMS Load Balancer, neither the IGEL network token nor UMS Console nor UMS Administrator will be installed. Only the option for uninstalling the UMS will then be set up in the Windows start menu.

   Include Page
   ENLITEUMSP:_UMS Components Installation ENLITEUMSP:_UMS Components Installation

   
   
   
   

6. Confirm the system requirements dialog if your system fulfills them.
   
   
7. Select the UMS data directory, in which Universal Firmware Updates and files are to be saved.
   
   
8. Enable the option for creating an IGEL network token.
   
   
   

9. Specify a directory for saving the IGEL network token. The directory must be writeable for the administrator.
   

   Note
   Be sure to keep the IGEL network token in a safe place! It will be needed for all subsequent server installations. If the IGEL network token is lost, the complete installation must be started again.

   
   
   

10. Optional: Under Import existing keystore, you can load the tc.keystore file from an existing UMS installation.

    Warning
    This function can destroy your UMS installation. Do not import this file unless you know exactly what you are doing.

    
    
    

11. If the internal Windows firewall is active on your host: Review the settings under Windows firewall settings and change them where necessary. Each port that is activated here will be set as rule in the Windows firewall. 

    Info
    Include Page ENLITEUMSP:_SvIncludePlusContent-_UMS 12 Communication Ports ENLITEUMSP:_SvIncludePlusContent-_UMS 12 Communication Ports For more information on UMS ports, see IGEL UMS Communication Ports.

    
    
    

12. Under Select Start Menu Folder, specify a folder name for the shortcut.
    
    
13. Under Select Additional Tasks, specify whether you would like to create shortcuts for the UMS Console and UMS Administrator on the desktop.
    
    
14. Read the summary and start the installation process.
    
    

15. Close the UMS installer once the installation is complete.
    The UMS installer creates entries in the Windows software directory and the start menu. If this was selected, shortcuts for the UMS Console and UMS Administrator will also be placed on the desktop.
    

    Info

    If SQL If SQL Server AD Native is Native is used, you must also set the correct startup type and logon settings for the "IGEL RMGUIServer" service and restart the service. This must be done on ALL UMS Server hosts. For details, see "Configuring the UMS Server Windows Service" under "Setting Up the UMS for SQL Server AD Native". more information, see Microsoft SQL Server/Cluster with Native Active Directory (AD) Authentication.

    
    

Anchor
HA_1Server_DefineDB HA_1Server_DefineDB

Defining the Database Connection

1. Open the UMS Administrator.
   

   Include Page
   ENLITEUMSP:_Path for the UMS Administrator ENLITEUMSP:_Path for the UMS Administrator

   
   
   
2. Select Datasource > Add.
   
   
   
3. Enter the connection properties of the prepared database schema. See also How to Set Up a Data Source in the IGEL UMS Administrator.
   
   
4. Click Activate to enable the data source. See also Activating a Data Source.

...

Anchor
HA_1Server_Save_NetworkToken HA_1Server_Save_NetworkToken

Saving the IGEL Network Token

Include Page
ENLITEUMSP:_Icon_handlungsaufforderung.png ENLITEUMSP:_Icon_handlungsaufforderung.png

 Save the IGEL network token, i.e. the file IGEL-Network.token, on a storage medium which will be accessible when installing further HA servers (e.g. on the network or on a portable storage medium such as a USB stick). Always keep the IGEL network token well protected.

...