Version Differences for High Availability

Line 1:
    + == HA Configuration ==  
       
    + The following activities should be performed in the order presented.  
       
    + 1. Provision the uDeploy Server Machines  
       
    + 2. Install and Configure Load-Balancer: The LB should forward to the machine provisioned in step 1.  
       
    + 3. Install Database: The database should be installed on a separate machine and before the servers are installed.  
       
    + 4. Install the the first uDeploy server: Use the host name for the top of the load-Balancer. Start it, then stop it. This will populate the directories for the next step.  
       
    + 5. Install a shared directory: Link the following server directories to a shared network drive and place the contents of these directories on the currently installed uDeploy server to the concurrent shared directories:  
       
    + :server_install_directory/logs  
    + :server_install_directory/var/config  
    + :server_install_directory/var/email  
    + :server_install_directory/var/plugins  
    + :server_install_directory/var/repository  
       
    + 6. Install subsequent uDeploy servers: In the installation, you will skip the DB installation this time. Just as in the installation for the first server, use the url for the top of the load-Balancer. Make sure to mount the shared directories to the corresponding directories on the server. DO NOT START THEM  
       
    + 7. Give the servers the same encryption key: Copy the server_install_directory/conf/encryption.keystore from the first server to the other servers, replacing theirs.  
       
    + 8. Configure the JMS connection between the servers: In the uDeploy UI, navigate to the Settings>Network link to configure the inter-server JMS connection by defining for all of the servers in the cluster:  
       
    + *Name  
    + *Host/IP  
    + *Port  
    + *check the Active check box  
       
    + 9. You may now have all of the servers running. Any connection should be balanced between all of your servers, and any changes made should be reflected in any connection to any server.