An ICA (IConnectorAccess) Task File uses an Attachmate API to generate an XML task file which can be easily used for Web applications. Task files contain metadata about client operations created in Transaction Designer. They are used during run-time to help parse the client-supplied instance XML for an ICA call. The parsing and processing of the input XML with the help of the metadata in the task file is what allows Transaction Integrator to create a COMMAREA image of data to send to the host in order to run a host program.
NOTE: In the Transaction Integrator you cannot generate ICA task files from client operations containing REDEFINES clauses. You can generate Java-based beans using the Attachmate ITask interface. There are Javadocs available on REDEFINE fields.
This is an example of a general synchronous workflow:
|Instantiate the connector class for your Transaction Integrator. The examples create the instance "myconnector."||CICSConnectorAccess myconnector = new
|Initialize your connector by opening your task file. The argument is the path to the file.||myconnector.open (path\to\my_connector.xml);|
|Get the metadata for your task. If the task id is -1, then all tasks are returned.||String xmlString = myconnector.getMetaData(-1);|
|Optionally, set a timeout for the task execution. The default is "-1", indicating no timeout is set.||myconnector.setTimeOut("-1");|
|Optionally, set the maximum return data size. The default is -1, indicating all data is returned.||myconnector.setMaxSize(-1);|
|Execute the task. The argument is the task id and the task inputs as xml.||myconnector.execute(task_id, inputXML);|
|Retrieve the data.||String outputXML = myconnector.getData
|Close the runtime service.||myconnector.close();|
|Startup and Settings|
|IConnectorAccess (ICA) Sample Application|
|Java Bean Input and Output Examples|