In the Task Builder Generate process, you create interface objects, such as XML, Java beans, or Web services, which enable an application to interact with the tasks that communicate with the Runtime Service. The input and output values, parameters, and field properties for the task interface objects you create are based on the values specified in the task definitions you create.
Using the Task Builder, you can generate two types of task interface objects: Java bean and Web services.
A service bean is a Java bean, but unlike a task bean, a service bean can include multiple tasks in a single Java bean. A service bean has a method for each task. Service beans can be used by an application in any Java application development environment.
A task bean is a Java bean that contains a single task. Task beans are published to Attachmate MCS and downloaded to the machine with the Attachmate Run-time engine, where they can be accessed by an application.
When you generate Web services for Apache Axis, a bean is generated, which is essentially identical to a service bean, but includes a Web Service Deployment Descriptor (WSDD) for deployment to the Apache Axis server. An ANT script is also generated for installing the Java beans in the Runtime environment.
Applications that use .NET components implement the Synapta Services Builder object. The components can be published to MCS or deployed to a .NET run-time environment, where they will run as Web services.
|
|
|
Synapta Services Builder Overview |
|
Generating Service Bean Interface Objects |
|
Generating Task Bean Interface Objects |
|
Generating Apache Axis Web Services |
|
Creating Tasks Files |
 |