Client - Server Applications and AutoCAD
Visitor # 8230 since 14.SEP.2003
Introduction.
Unix workstations offer a built-in ability to run applications in a client-server arrangement. Quite often, this capability goes unused, either due to a lack of need or understanding of how to accomplish it. This application note will attempt to present a scenario and solution based on a client-server architecture.
Implementation.
In this case, I will examine a situation in which an older version of an application needs to be run for compatibility purposes, in this case AutoCAD R12. Unfortunately, the older version of AutoCAD will not run on systems running Irix 6.0 or above, nor will it run on any non-SGI workstations. However, all is not lost.
It is possible to set up a newtwork of two or more machines, including at least one SGI workstation that is running Irix 5.3. Then, AutoCAD R12 and any required third-party AutoCAD applications are installed on the server. An AutoCAD R12 startup script (i.e. acadr12) is created with all necessary environment variable settings and is placed in the main AutoCAD R12 directory (i.e. /usr/acad/acad). Up to this point, there is nothing to distinguish this installation from a typical standalone workstation installation.
In order to complete the client-server setup, client and a server shell scripts must be created and installed on the respective machines. The AutoCAD R12 client shell script (acadr12_client) is nothing more than a thin wrapper over the Irix remote shell (rsh) command in which the name of the AutoCAD R12 server is identified. The AutoCAD R12 server shell script (acadr12_server) is a slightly less thin wrapper over the AutoCAD R12 startup script that serves to redirect the AutoCAD display windows to the client nachine as well as start AutoCAD inside of a shell window. Refer to the diagram below for an overview:
Client - Server Block Diagram
Once set-up, it is now possible to run the AutoCAD R12 client program from any workstation (or PC) capable of running an remote shell command and an Xserver.
Note that you can also use the "rlogin" command to log into the server and run the "acadr12_server" script directly if you prefer. In any event, you need to be aware that you are running the application on the server, using the server's file system. If you have files on your client workstation that you want to edit, you'll either have to copy them to the server machine, or better yet install the Network File System (NFS) and use the "automount" feature to access files on the client.
Distributed processing.
Since you are dividing the computational work from the display work over two systems, you'll find that the server will be able to handle several sessions simultaneously. You may need to do some experimentation and tuning to find the best machines to use for the client(s) and server. Since the server will be doing the computation and file I/O, a fast CPU, file system and lots of RAM are key resources. The client machine(s) will be doing the display task and will not need as fast a CPU or as much RAM as the server. All the display requests will be going over your network, so you may find it beneficial to place the client and server machines on a separate network segment if your network traffic gets too high.
If you intend to run multiple remote (and/or local) AutoCAD R12 sessions on a single server, you might want to experiment with the ACADMAXMEM environment setting to control system memory usage per session. By default, AutoCAD will determine the maximum amount of free memory and swap space available (and try it best to use as much of it as it can :-). So, in order to have better performance when running multiple sessions, use ACADMAXMEM to limit AutoCAD's use of system memory resources. When an AutoCAD session has used the memory specified in ACADMAXMEM it will revert to its internal memory paging feature which makes use of free disk space in a manner similar to swap. You can consult the AutoCAD Installation and Performance Guide for detailed information on setting ACADMAXMEM but here's a simplified approach:
-
Determine your system's physical memory capacity:
- > hinv -t memory
- Main memory size: 96 Mbytes (on this example machine).
-
Determine the number of sessions of AutoCAD you wish to run:
- Assume 4 for this example.
-
Allow ~24 Mb of RAM for the operating system and other processes:
- 96 - 24 = 72 Mb available RAM.
-
Divide available RAM by number of AutoCAD sessions:
- 72 / 4 = 18 Mb per session.
-
Set ACADMAXMEM to the per session value in your AutoCAD startup script:
- ACADMAXMEM=18874368; export ACADMAXMEM
- Hint: 18 Mb = 18 * 1024 * 1024 = 18874368 bytes.
- Note: You should avoid setting ACADMAXMEM below about 12-16 Mb.
Troubleshooting tips.
-
When installing and testing this setup, be sure to edit all the shell
scripts to conform to your site.
- Specifically, the server and directory names.
-
Try cutting and pasting one command line at a time into a shell window
to isolate problems.
- The supplied shell scripts use /bin/sh.
- This approach requires that an X Window display connection can be established between the client and server. If you get a "connection refused" error, you'll need to run the "xhost +$R12SERVER" command on the client machine to allow the server access.
-
If you are running from a non-SGI workstation, you will be limited to
using either the X/Motif or NULL
display driver.
- The IrisGL driver will only function with other SGI workstations.
- You'll get a "dgl not supported" error with non-SGI machines.
- While the IrisGL display driver is capable of running remotely over the network, you may find the X/Motif driver is better suited for this task.
- From other Unix workstations, you can directly run the "acadr12_client" program.
-
In the case of a PC solution, I successfully tested this configuration
with PC-NFS Pro (for the network and rsh) and
Exceed/W Xserver from Hummingbird.
- As PC-NFS Pro's rsh command is accessible only from the GUI "Remote Command" program, I had to manually enter "acadr12_server" and my server and user name in the dialog.
-
You'll also need to manage user name, logins and passwords on the
client and server machines.
===>> 