Configuring Your Development Environment

The task interface objects generated by the designer can be used in a variety of development environments to add host access tasks to your applications. Depending on the type of task interface object generated, you can call your tasks from applications that use Java, XML, COM interfaces, J2EE session EJBs, or remotable .NET objects; or your applications can send inputs and make calls to published Web services.

To integrate tasks with your applications, your development environment must be configured properly.

If you plan to...	Then this
Develop your applications on the computer on which Task Builder is installed	No additional configuration is necessary. However, if you are developing or running a Java client application you must edit your class path to include the items described below.
Develop your applications on a computer other than the computer on which Task Builder is installed	Copy the appropriate client installer for your environment and run it on the computer you will use. If you are developing or running a Java client application you must edit your class path to include the items described below.

Using the Client Installer

The client installer installs the JARs and libraries your application requires. The client installers are located in the following directory on the computer where Task Builder for Screens is installed:

Attachmate\EAI\ScreenConnectors\ClientInstall

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

SC_Client_Installer.exe, which contains the JARs and properties files required for Java clients and the COM Interface required for native Win32 clients
-or-
SC_ProxySvc_Installer.exe, which is identical to the SC_Client_Installer.exe, with the addition of a Windows service required for .NET Web services and remotable objects.

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:

client_installer.tar.gz, which contains the JARs and properties files required for Java clients. This is a binary executable that will only run on Solaris at a console using X Windows.

Editing Your Class Path

When you are developing or running a Java client application, in addition to running the appropriate client installer, you need to add the following JARs to the class path of your IDE, or on the Java client:

In the folder installdir\attachmate\EAI\ScreenConnectors\lib\, where, by default, installdir is c:\program files:
- ScreenTaskClient.jar
- common.jar
- metadata.jar
- ra-client.jar
- util.jar
In the directory, ..\EAI\Common\mcs:
- mcsagent.jar
- mcs-rpc.jar
The EAI\Common\config directory
If you are running an earlier JDK version than 1.4.x, in the folder installdir\attachmate\EAI\ScreenConnectors\lib:
- xml-apis.jar
- xalan.jar
- xerxes.jar


	Using Tasks in Your Applications, Overview
	Configuring a .NET Environment
	Choosing an Attachmate API