Homepage | About EASA | Contact
The following sections provide examples of configuring compute servers that contain step-by- step instructions. The examples cover the following three types of compute servers:
Note: In the following examples, fictitious names are used both for computer names of the compute servers (easaserver, CS2, CS3) and the software to be run on them (mycode). In reality, you will be using the actual names of your computers and your software.
In this first example of configuring a compute server, the EASA Server itself will be set up as a compute server. For this case, the EASA server is running under Windows XP, has a hostname of easaserver, and will use
C:\easawork
as its working directory. The software to be run on easaserver is called mycode and the environment variable, Path, must be modified to find and run mycode properly on the compute server.
Note: Again, easaserver and mycode are fictitious names used as examples. You should use the actual hostname of your EASA Server and the actual name(s) of any software you intend to run on this computer.
Note: At this point, you could also use the Local Compute Server object. However, the standard compute server object provides more control. For example you may want to explicitly specify the Local Working Path to avoid too long a path name, which could cause certain underlying software applications to encounter errors.
The final step required before EASA can use the compute server is to make it ‘active’ by running an ‘Update and Retest Compute Servers’ process as described at Updating and Testing Compute and Excel Servers.
In this example, the compute server is running under Windows 7 and has a hostname of CS2. The EASA server will be assumed to also be running under Windows 7. The chosen communication approach is to use the Web Service Compute Server (WSCS). The software to be run on CS2 is again called mycode, which is to have a license limit invoked. Finally, the environment variable, Path, must be modified to find and run mycode properly on the compute server.
Note: Again, CS2 and mycode are fictitious names used as examples. You should use the actual hostname of your Windows computer and the actual name(s) of any software you intend to run on this computer.
NOTE: The Password parameter should be set to the default value of ‘abGG673’.
The final step required before EASA can use the compute server is to make it ‘active’ by running an ‘Update and Retest Compute Servers’ process as described at Updating and Testing Compute and Excel Servers.
In this example, the EASA Server is running under Linux, while the compute server is running under UNIX, has a hostname of CS3, and has an ssh server running under the userid of user1. The software to be run on CS3 is again called mycode.
Note: Again, CS3, user1 and mycode are fictitious names used as examples. You should use the actual hostname of your UNIX computer, the actual userid on the computer and the actual name(s) of any software you intend to run on this computer.
Note: The Password parameter should be set to the password for user1.
The final step required before EASA can use the compute server is to make it ‘active’ by running an ‘Update and Retest Compute Servers’ process as described at the Updating and Testing Compute Servers page.
In this example, the computer to be the Excel Server is running under Windows XP and has a hostname of ES1. The Remote Server software has been installed on ES1 with the Excel service using the defaults for Port Number, User name and Password.
The final step required before EASA can use the excel server is to make it ‘active’ by running an ‘Update and Retest Compute Servers’ process as described at Updating and Testing Compute and Excel Servers.