After you have created and defined a task, you need to generate the task interface objects you want to use in an application. Task interface objects are generated for each task in your project. A task interface object is the code generated by the Task Builder through which an application interacts with a task. An application that is created to run your task uses the task interface object to communicate with the Runtime Service.
There are various types of task interface objects.
|Type of Task Interface Object||Description|
|Task files||Task files are XML files that map tasks to systems. Applications that run tasks in a task file use the IConnectorAccess interface. Task files can be published to MCS and downloaded to the runtime machine where they are accessed by your application. A task file can contain more than one task.
Regardless of the task interface objects you choose to generate, a task file is also generated. Task files are used in the runtime environment in combination with all other task interface objects.
|Task beans||Task beans are Java beans that contain a single task for each bean. Applications that make use of task beans use the ITask interface. The beans preserve and copy context, which includes the host connection or session allocated for a task. A pool of sessions is created in Management & Control Services for Screens, and your task is assigned one of these sessions at run-time. If you set the bean to preserve context, the session won't disconnect after executing the task. Context can be copied from one bean to another. Beans are published to MCS and downloaded to the runtime machine where they can be accessed by your application.|
|Service beans||Service beans are also Java beans but, unlike task beans, they can include multiple tasks in a single bean. Service beans have a method for each task. Task inputs and outputs are arguments to the method. Service beans can be used to create applications in any Java application development environment.|
|Web services||Synapta Services Builder can provide host-based data and logic as XML-based Web services, with full support for SOAP over HTTP. These services can be consumed by existing applications that follow the Web services model.
Beans are generated for both the Apache Axis environment and the BEA WebLogic Integration enviroment. BEA WebLogic 8.1 and 7.03 are supported via J2EE Session EJBs and connectors. .NET components, once generated in the designer, can be deployed to a .NET runtime environment as Web services or as remotable .NET objects.
|J2EE Session EJBs||J2EE support, which is available with all Attachmate Synapta Services Builders, provides J2EE Enterprise JavaBean version 1.1 (EJB) and connector functionality. The J2EE connector is written to the Sun J2EE Connector Architecture Specification, version 1.0.
An application that is created to run your tasks makes use of the task interface objects to communicate with the Runtime Service.
When you generate task interface objects, additional files that are needed to install your objects in the specified environment are also generated. All generated files are copied to
For a list of files that are generated for each type of task interface object, see Generated and Published Files.
|Designing Tasks, Overview|
|Specifying Compilation Options|
|Specifying Generation Options|
|Generating Task Interface Objects|
|Generated and Published Files|
|Testing Generated Task Interface Objects|