When adding a new Compute Server, there are two main questions to answer first before determining the rest of the configuration settings. The questions are:
The first choice determines which object is set in the Server Processing: parameter of a COMPUTE SERVER object.
The second answer will defined additions to SOFTWARE LIST, ENVIRONMENT LIST and LICENSING branches of the Tree. These objects will then be referred to in the Software: and Environment: parameters of a COMPUTE SERVER object.
When configuring a Compute Server running Windows, you have two communication approaches to choose from:
When configuring a computer to be an Excel Server, there are three requirements for the computer:
The EXCEL SERVER PROCESSING object, which is specifically designed for configuring Excel Servers, is the only approach available for establishing the communication between the EASA Server and Excel Server. For an example of configuring an Excel Server, please see Configuring Compute Servers.
Tip: When configuring an Excel Server, you can usually use the existing default EXCEL SERVER PROCESSING object under DEFAULT SERVER PROCESSING. Exceptions include use of a 'Port Number' within the Remote Server software other than 80 or a change in the 'Username' and 'Password' for authenticating communications with Remote Servers.
Note: Excel Add-ins are disabled by default in the Excel processes used by EASA. This is due to avoid unnecessary performance impacts as in most cases, full functionality is available without Add-ins.
If Excel Add-ins need to be enabled, it can be done by modifying the
context.properties file found under
<EASA Server Data Folder>\excel\admin\config\ by adding the following line:
Excel 2016 requires an interactive user to close a popup that appears at the first innvocation, and by default an Excel Server runs as SYSTEM. We need a new second user, EASA-user that can actually log in and close this initial popup and then we run the Excel Server as that user. Follow the steps below if you are using Excel 2016.
When configuring UNIX or Linux compute servers, you have three communication approaches to choose from:
If the third choice is selected, you can select from existing SERVER PROCESSING objects under DEFAULT SERVER PROCESSING. The table below provides guidance on the selection of the existing SERVER PROCESSING objects.
|EASA Server Operating System||Compute Server Operating System||Template Server Processing Object|
|Windows||UNIX or Linux||windows to unix csh|
|Linux||UNIX or Linux||linux to linux|
Also, with the third choice above and the use of rsh, there are a few important issues to be aware of:
.rhostsfile containing the hostname or IP address of the EASA Server and the Username used to run it must be present on the Compute Server in the home directory of the User ID on the UNIX computer (See # 2 below).
Note: The settings for the owner, group and file permissions on the .rhosts file are also important. Set the owner to the User ID being used and the group to same group that the User ID belongs to. Finally, use file permissions of 600 or
rw- --- ---.
With Linux computers, one issue for concern is that rsh may not be activated and available for use by default in Linux. You can check whether rsh has been turned on by typing the following command in a shell window:
You should then see a list of available services and their status. Look for the line corresponding to rsh. You will need to turn rsh on if you see the following in a shell window:
You can turn rsh on by logging on the Linux computer as root and then typing the following command:
chkconfig rsh on
To aid you in configuring your Compute Servers, a flow diagram of the configuration process is provided: