User Tools

Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
wiki:guides:admins:easa_cluster_installations [2016/12/01 09:25]
Brian Collins
wiki:guides:admins:easa_cluster_installations [2016/12/01 09:26] (current)
Brian Collins
Line 5: Line 5:
 In a default installation,​ all components of the EASA system are installed to a single EASA Server. In addition to the possibility of configuring a remote **Compute Server** and a remote **Excel Server**, it is possible to configure one or more Web Browser Client servers separately from the **EASA Server**. This may be a preferable solution in cases where EASA is deployed to a large number of users. With multiple Web Browser Client servers in operation, the EASA system features load balancing technology which is able to detect and select the server with the most available resources to provide Web Browser Client access to a user at any given time. This process is automatic and requires no input from the user. In a default installation,​ all components of the EASA system are installed to a single EASA Server. In addition to the possibility of configuring a remote **Compute Server** and a remote **Excel Server**, it is possible to configure one or more Web Browser Client servers separately from the **EASA Server**. This may be a preferable solution in cases where EASA is deployed to a large number of users. With multiple Web Browser Client servers in operation, the EASA system features load balancing technology which is able to detect and select the server with the most available resources to provide Web Browser Client access to a user at any given time. This process is automatic and requires no input from the user.
  
-Like compute server ​configuration,​ this functionality brings with it a broad range of configuration options. Depending on the needs of your organization,​ you may wish to add a single supporting Web Browser Client server to your main **EASA Server**, or you may wish to configure multiple Web Browser Client servers while relieving the main EASA Server of this role altogether.+Like ** Compute Server** ​configuration,​ this functionality brings with it a broad range of configuration options. Depending on the needs of your organization,​ you may wish to add a single supporting Web Browser Client server to your main **EASA Server**, or you may wish to configure multiple ​**Web Browser Client** servers while relieving the main EASA Server of this role altogether.
  
 ===== Cluster Installation Setup ===== ===== Cluster Installation Setup =====
  
-Configuration of an EASA cluster installation involves the addition of extra EASA servers to handle Web Browser Client load. These additional servers do not require a full EASA installation,​ only a partial installation through use of advanced mode in the EASA installer. In the following example scenario, we will configure a cluster with a central **EASA Server**, and two Web Browser Client servers. Users will only need to directly access the main EASA server. Upon the launch of an EASAP, their browsers will be directed to one of the two Web Browser Client servers, depending on their available resources. The following example steps assume that you are performing a fresh EASA installation on your main server. This would be the preferred method, since we are able to omit certain components from the main server, thereby maximizing available resources. This cluster installation example will consist of four stages:+Configuration of an EASA cluster installation involves the addition of extra EASA servers to handle Web Browser Client load. These additional servers do not require a full EASA installation,​ only a partial installation through use of advanced mode in the EASA installer. In the following example scenario, we will configure a cluster with a central **EASA Server**, and two **Web Browser Client** servers. Users will only need to directly access the main EASA server. Upon the launch of an EASAP, their browsers will be directed to one of the two Web Browser Client servers, depending on their available resources. The following example steps assume that you are performing a fresh EASA installation on your main server. This would be the preferred method, since we are able to omit certain components from the main server, thereby maximizing available resources. This cluster installation example will consist of four stages:
  
   * Installing a central **EASA Server** configuration on the **EASA Server**   * Installing a central **EASA Server** configuration on the **EASA Server**
Line 94: Line 94:
 To set the property on each server machine, go to the file system, edit:  To set the property on each server machine, go to the file system, edit: 
  
-  * [[server_data_jsf_easa_admin_config_context_properties|\<​EASADATA>​\jsf-easa\admin\config\context.properties]] ​+  * [[server_data_jsf_easa_admin_config_context_properties|<​EASADATA>​\jsf-easa\admin\config\context.properties]] ​
  
 Remove the # character from the beginning of the following line: Remove the # character from the beginning of the following line: