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 Server:
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, use the actual computer and software names.
In this first configuration example, the EASA Server itself will also be a Compute Server. In this example, the EASA Server runs under Windows XP, with a hostname of easaserver, and uses the working directory below:
The mycode software will be run on easaserver and the environment variable, Path, must be modified to find and run mycode properly on the Compute Server.
Note: At this point a LOCAL COMPUTE SERVER object may be used. However, the standard COMPUTE SERVER object provides more control. To avoid too long a path name, which could cause certain underlying software applications to encounter errors, explicitly specify Local Working Path:
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 is assumed to run 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.
Set the Password: parameter 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.
Set the Password: parameter 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.