When you package your task as a J2EE session EJB, the task name is given to a method which performs the task when invoked. The Attachmate EJB interface contains one method per task in each task file for which an EJB is generated.
To integrate your J2EE session EJB with an application |
---|
|
In this example, you set task inputs, execute the task, and get task outputs.
//create inputs object, define outputs variable AccountQueryStateful.AccountLookupTaskInput.CICSInputs si= new AccountQueryStateful.AccountLookupTaskInput.CICSInputs(); AccountQueryStateful.AccountLookupTaskOutput.CICSOutputs so = null; // set task input(s) si.setAccountNumber(AccountNumber); // execute task with inputs and collect outputs so = ejb.AccountLookupTask(si); // get task output(s) Balance = so.getBalance();
Alternatively, you may access the J2EE resource adapter directly. For details, see the help topic, Accessing Data with the Attachmate J2EE Resource Adapter
This sample illustrates how to create a web-based application that sends input to and receives output from your Synapta Services Builder for CICS task, deployed to a WebLogic app server as a session EJB generated from MCS.
This sample illustrates how to create a web-based application that sends input to and receives output from your Synapta Services Builder for CICS task, deployed to a WebLogic app server as a J2EE resource adapter generated from MCS.
![]() |
|
![]() |
Using J2EE Architecture |
![]() |
Deploying J2EE Session EJBs |
![]() |
Accessing Data with the Attachmate J2EE Resource Adapter |
![]() |
How to Provide Tasks in a J2EE App Server |
![]() |