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...
|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.|
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:
If you are running Windows, there are two client installers to choose from:
|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:
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:
|Using Tasks in Your Applications, Overview|
|Configuring a .NET Environment|
|Choosing an Attachmate API|