Testing Generated Task Interface Objects

Synapta Services Builder for Screens provides simple Java Server Page (JSP) applications that you can use to test your generated task beans and task files. This is an optional feature and is not part of the standard task creation workflow. However, these generic JSP samples are a useful alternative to creating your own applications to test your interface objects.

Prerequisites

To successfully run the JSP test samples, you must have:

• A Web server running JDK 1.4 (or greater) with JSP support (minimum version 1.2)

• Internet Explorer 5.0 or greater

• MCS for Screens installed on the computer where you will run the samples.

  -or-

  You have copied screenconnectors.zip, located in the same directory as the JSPs, to a separate computer and extracted it below the Web server's webapps folder. There may be additional task resource configuration required.

• Published your tasks and created a session pool. Task resources must be configured to run against the Runtime Service for Screens.

How the samples work

The JSPs automatically search your Recordings directory (when Task Builder is installed), and make available the published task resources from within the JSP sample user interface. You choose the task you want to test, fill in the input values, and execute the task. The JSP will return a list of task outputs.

Accessing the samples

The test applications are available in the following directory:

.../attachmate/eai/documentation/connector_screens/sdk/client/samples/screenconnectors_webapp

To run the sample task testers, on the same machine where you have installed MCS, point your browser to the following URL: <http://localhost:8086/screenconnectors/index.htm>. You may have to change the default port number (8086) to match your installed configuration.

You can also launch the sample JSPs individually by running beantester.bat or connectortester.bat from the same directory or by pointing your browser to

<http://localhost:8086/screenconnectors/BeanTester.jsp> or <http://localhost:8086/screenconnectors/ConnectorTester.jsp>.

Alternatively, you can run these samples on any web server that meets the prerequisite requirements by copying screenconnectors.zip to a separate machine and extracting it below the Web server's webapps folder. When extracted, the JAR files necessary to run the samples are made available to the test applications. These JAR files include:

• ScreenTaskClient.jar
• xerces.jar
• soap.jar
• common.jar
• metadata.jar
• util.jar
• xalan.jar
• sampleapps.jar
• mcsagent.jar

Points to remember

• There is help available on each sample JSP to provide additional instructions and troubleshooting information. There is also a readme.txt file containing information on using the test applications.

• The sample JSPs were developed and tested using Windows XP and the default Web server installed with MCS for Screens.

• After installing or upgrading, you must restart your application server.

• You cannot execute stateful tasks — tasks which require context to be preserved.

• You cannot specify null inputs for your tasks.

• You can access more information on JSPs in general by referring to JSP programming books or visiting the JSP home page.

	Creating Task Interface Objects, Overview
	Generating Task Interface Objects