Configuring the Client Environment

To run client applications that reference tasks, your client application environment must be configured properly.

If you plan to
Then do this
Run a server-based application, and you can run it on the same server where you have Runtime Service for Screens installed Edit your class path to include the support files, and then no additional configuration is necessary.
Run your applications on a computer other than the computer on which the Runtime Service is installed Copy the appropriate client installer for your environment and run it on the computer you will use.

Using the Client Installer to Configure Your Client Environment

The client installer installs the support files (the ScreenTaskClient and all its support JARs) your application requires. The client installers are located in the following directory on the computer where Task Builder for Screens is installed:

install location/Attachmate/EAI/ScreenConnectors/ClientInstall

If you are running Windows, there are two client installers to choose from:

Note The SC_Client_Installer and the SC_ProxySvc_Installer cannot be installed on the same computer. Doing so may result in an unstable system.

If you are running Solaris, there is a single option:

Editing Your Class Path

When you are developing or running a Java client application, in addition to running the appropriate client installer, you may need to add the following files to the class path on the computer where you will write your applications, for example your IDE, or on the Java client, where your applications will be served from:

Once you've configured your client application environment, the next step is to associate your tasks with a runtime server. For information about associating tasks with runtime servers, see Associating Tasks with Run-time Servers, Overview.

Related Topics
Bullet Configuring Your Run-time Environment, Overview
Bullet Associating Tasks with Run-time Servers, Overview
  Attachmate