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:

• Windows EASA Server as compute server

• Windows compute server from Windows EASA Server

• UNIX compute server from Linux EASA Server

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.

• Open a web browser on your computer and go to the EASA web address.

• Log in to EASA and then set your mode to Administrator.

• Select Compute Servers under the Configure menu.

• Click on the compute server configuration link to initiate the Compute Server Configuration tool.

• Select SOFTWARE LIST and add a new Software object to the list. Then, name the new object mycode.

• You will next set up mycode’s environment variable. Expand ENVIRONMENT LIST and add a new Environment object to the list. Then, name the new object env_mycode.

• Expand the env_mycode object, select the existing Environment variable object and rename it to home. Then fill in its Parameter Values as shown below:

• At this point, you are ready to add the Compute server object. With COMPUTE SERVER LIST selected, add a Compute server object and rename it to cs1. Then fill in its Parameter Values as shown below.

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.

• Save the compute server configuration by selecting Save under the File menu.

• Exit the Compute Server Configuration tool.

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.

• Install the EASA Remote Server with the Compute Server service on the Windows compute server per the instructions given at Installing Remote Server Software on Compute Server. When installing, use the default port number and password configuration.

• Open a web browser and go to the EASA web address.

• Log in to EASA and then set your mode to Administrator.

• Select Compute Servers under the Configure menu.

• Click on the compute server configuration link to initiate the Compute Server Configuration tool.

• Expand the SERVER PROCESSING LIST branch, then add a Web Service Server Processing object to CUSTOM SERVER PROCESSING by right-clicking on CUSTOM SERVER PROCESSING and selecting Child → Add WEB SERVICE SERVER PROCESSING. Fill in the new object’s Parameter Values as shown below.

NOTE: The Password parameter should be set to the default value of ‘abGG673’.

• Next, expand LICENSING and then LICENSE LIST. Add a new License object to the list, name it lic_mycode and fill in its Parameter Values as shown below.

• Next, select SOFTWARE LIST and add a new Software object to the list. Then, name the new object mycode. With the mycode object selected, add a Use license object and set its Select From and Number Required parameters to lic_mycode and 1, respectively.

• You will next set up mycode’s environment variable. Expand ENVIRONMENT LIST and add a new Environment object to the list. Then, name the new object env_mycode.

• Expand the env_mycode object, select the existing Environment variable object and rename it to home. Then fill in its Parameter Values as shown below.

• At this point, you are ready to add the Compute server object. With COMPUTE SERVER LIST selected, add a Compute server object and rename it to cs2. Then fill in its Parameter Values as shown below.

• Save the compute server configuration by selecting Save under the File menu.

• Exit the Compute Server Configuration tool.

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.

• Open a web browser on your computer and go to the EASA web address.

• Log in to EASA and then set your mode to Administrator.

• Select Compute Servers under the Configure menu.

• Click on the compute server configuration link to initiate the Compute Server Configuration tool.

• Expand the SERVER PROCESSING LIST branch, then add a SSH Server Processing object to CUSTOM SERVER PROCESSING by right-clicking on CUSTOM SERVER PROCESSING and selecting Child → Add SSH SERVER PROCESSING. Fill in the new object’s Parameter Values as shown below.

Note: The Password parameter should be set to the password for user1.

• Next, select SOFTWARE LIST and add a new Software object to the list. Then, name the new object mycode.

• At this point, you are ready to add the Compute server object. With COMPUTE SERVER LIST selected, add a Compute server object and rename it to cs3. Then fill in its Parameter Values as shown below.

• Save the compute server configuration by selecting Save under the File menu.

• Exit the Compute Server Configuration tool.

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.

• Open a web browser on your computer and go to the EASA web address.

• Log in to EASA and then set your mode to Administrator.

• Select Compute Servers under the Configure menu.

• Click on the compute server configuration link to initiate the Compute Server Configuration tool.

• At this point, you are ready to add the Excel server object. With COMPUTE SERVER LIST selected, right-click and add a child Excel server object and rename it to es1. Then fill in its Parameter Values as shown below.

• Save the compute server configuration by selecting Save under the File menu.
• Exit the Compute Server Configuration tool.

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.