Building Applications Using Native Win32 Technologies

Both the COM Interface and the Proxy Service enable native Win32 implementations to interact with the Java-based service builders.

For the pros and cons of using each of the Synapta Services Builder APIs, see Choosing an Attachmate API.

The COM Interface

The COM Interface is a native wrapper for IConnectorAccess. It functions as a translator, allowing COM applications to work with Java-based services builders.

The following code samples show how to get data from a Services Builder for Screens from within different Windows development environments.

• C# Code Sample. Executes a task and extracts a single output from the results.

• ASP Sample. Executes a task and displays the results.

• Sample task file. This is the task file used in the samples.

The Screen Connector Proxy Service

Screen Connector Proxy Service is a proxy service that maintain a single instance of the Java Virtual Machine and services DCOM requests for task execution via IConnectorAccess. The Screen Connector Proxy Service is required for .NET Web services and remotable objects.

Each Synapta Services Builder installs its own Screen Connector Proxy Service.

It may be necessary to adjust the amount of memory that is available to the Screen Connector Proxy Service, especially on servers where a heavy load is anticipated. The default maximum heap size for the Screen Connector Proxy Service is 128 MB. You can change this value by using the following optional registry entry: HKEY_LOCAL_MACHINE\Software\Attachmate\ScreenConnector\MaxHeap. The value is a string that defines the number of megabytes; for example, "256".

The following code samples are simple applications using different Windows development environments.

• C# Code Samples
  • Stateful task execution sample

  • Stateless task execution sample

• ASP Code Samples.
  • Stateful task execution sample

  • Stateless task execution sample

See the Screen Connector Proxy Service API Reference for detailed information.

Code Samples for .NET Remotable Objects

• Server-activated client sample. Including a corresponding configuration file.

• Server-activated, server sample. Including a corresponding configuration file.

• Client-activated, IIS-hosted, client sample. Including a corresponding configuration file.

	Using Tasks in Your Applications, Overview
	Choosing an Attachmate API
	COM Interface API Reference
	Proxy Service Interface API Reference