Technology Reference Guide
5. Network Applications
B. Networked Application Sharing

What is it?
To a user on a client workstation, the network file services generally appear as another hard drive, or group of hard drives, that can be accessed just as though they were physically attached to the workstation. Because of this, the workstation can be directed to those network drives. It can download into memory and execute applications stored there. An extreme example of this is the diskless workstation, which has no local hard drives, and must pull even its base operating system off a network drive.

What does it do?
For an application to be shared across the network, it must be designated as a shareable file, and the users must have access to the directories where the program resides. In some cases, the users have the right to both read and write to the directory, if the program needs to write to its files during execution. The local workstation must also have the required memory, drivers, and other configuration settings that will allow the program to run.

The location of various files used by the application, as well as files produced by the application can be very important. A local application user may put their files in the same directory as the application, but in a networked environment, this may make their files available to anyone who has access to the application. For this reason, networked applications generally dictate that the users to store their data files in a protected home directory or on their local drive, if they dont want to share them. Under MS-Windows, applications generally have initialization or configuration files that Windows expects to find in its own directory. These need to be downloaded to each users local Windows directory if they are to execute properly.

Network-aware applications may have some additional considerations. For example, some Lotus applications have the option to do a network or standalone install. When installed on the network, these applications make use of a directory containing user profiles. When a user accesses the application, they are asked to supply a user ID that directs the application to reference their user profile, and set up certain defaults.

How is it used?
Network application sharing has both advantages and disadvantages. The advantages are that it simplifies installation, in that one copy of the application can be installed, instead of individual copies at each workstation. It saves considerable storage space on the workstations. It also simplifies the process of upgrading, and can provide some measure of control, in that only users with rights to the application can use it.

One disadvantage of networked applications is that they can cause considerable traffic across the network and may run slower. Also, if the network is unavailable, so is the application. The fact that many applications are not network-aware means that users cannot save defaults or setups. Either the application setups change each time someone new accesses them, or the ability to change them may be disabled, reducing the users control of the application environment.

Licensing is also an issue. Licensing has traditionally focused on a one-machine, one-user per copy model. This works fine on standalone systems, but with networked applications, the right to use the software becomes a complex issue involving site licenses, estimations of numbers of concurrent users, and the constant risk of unlicensed use or copying.

Where do I get more information?
Contact your local CBV Office.



©1997 CBV Communications Co., Ltd.