When you publish to a Management & Control Services (MCS) server, all of the files related to the selected project are published. When additional tasks are created in the same project and published to MCS, they are added to the tasks already contained in the compressed files in the MCS repository.
The following table lists the files that are available for each type of task interface object.
If you've generated | To local directory | To MCS |
---|---|---|
Task beans | NavMapClientBeans.jar *readme.txt |
The unjarred contents of the NavMapClientBeans.jar ** The Javadoc.jar is created only if you selected the Generate Javadocs box when you configured options for generating task beans. |
Service bean | tasknameservicebean.class , Java bean class file for the generated task,
contains: tasknameservicebean.java and a data bean for each set of task inputs or outputs |
tasknameservicebean.class |
Java beans for the Apache Axis environment | NavMap.jar build.xml deploy.wsdd NavMapbean.java undeploy.wsdd Databean.java , one for each set of task inputs or outputstasknameservicebean.class |
The unjarred contents of the NavMap.jar tasknameservicebean.class |
Enterprise Java beans for BEA WebLogic Integration 7.0 | appProperties.properties NavMapmappings.xml , which maps the NavMap to an Attachmate Adapter for 3270 & 5250 for WebLogic application viewNavMapservice.ear deploy.cmd
|
NavMapservice.ear |
.NET components | NavMap.msi |
NavMap.msi |
In addition, the task file is always included:
To local directory | To MCS |
---|---|
NavMapclientTaskFiles.jar readme.txt |
The unjarred contents of the NavMapclientTaskFiles.jar |
Testing your generated task beans and task files
You can test your generated task beans and task files using simple Java Server Page (JSP) applications. The test applications are available in the following directories:
.../attachmate/eai/documentation/connector_screens/sdk/client/samples/bean
.../attachmate/eai/documentation/connector_screens/sdk/client/samples/xml
There is a text file containing complete instructions on how to use the test application in each directory.
![]() |
|
![]() |
Creating Task Interface Objects, Overview |
![]() |
Generating Task Interface Objects |
![]() |
Testing Generated Task Interface Objects |
![]() |