Using Tasks in Your Applications
The task interface objects generated by Task Builders 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. For information about the available interfaces, see Choosing an Attachmate API.
For important information about configuring your development environment, see Configuring Your Development Environment.
You can learn more about the available environments by following the links below:
- Using XML. XML-based application can access your task through the task file generated by Task Builder.
- Using Java Beans. Task Builder can generate two kinds of Java beans which can integrate your task into a Java application.
- Using J2EE Architecture. Using the management tools in MCS, you can deploy your tasks as J2EE Session EJBs, which are packaged in an enterprise application. Use this option to integrate with BEA WebLogic.
- Using Apache Axis Web Services. Apache Axis is a free SOAP (Simple Object Access Protocol) implementation and provides a base on which to implement Java Web services.
- Using .NET. .NET components are generated in the designer and can be deployed to a .NET runtime environment as Web services, or as remotable .NET objects.
- Using Native Win32 Technologies. A COM interface is provided for developers who prefer native Win32 environments (such as ASPs, VisualBasic, or C#).