Previous Step   Previous Step Next Step   Next Step

Develop an EJB application.

Map Step 2 towards the goal: Using optimized local adapters for inbound support

About this task

You can develop an EJB application or prepare an existing application. If you are calling to or from a Cobol or C/C++ program, you might want to use the IBM® Rational® Application Developer assembly tools, such as Rational® Application Developer, to create a Java class with getter and setter helper methods that correspond to the Cobol copybook or C/C++ structure, as well as create an EJB application to invoke with the optimized local adapter native APIs.

For more information on using the assembly tools to convert a Cobol copybook or C structure into a Java data binding helper class, see the assembly tool information center.

The assembly tools are shipped with the WebSphere® Application Server for z/OS® and contain the Java archive (JAR) file that contains the package, com.ibm.websphere.ola, that you will need to identify your enterprise bean as a potential target of an optimized local adapter call. This package contains the ExecuteHome and Execute classes that hold the abstract interfaces that are needed to call the adapter. You must create a stateless session bean that implements a method called execute() which accepts a byte array as input and returns a byte array as output and specifies the name com.ibm.websphere.ola.ExecuteHome for the EJB home interface and com.ibm.websphere.ola.Execute for the remote interface. The enterprise bean that you want to invoke from an external address space, must include a method called execute that accepts a byte array as input and returns a byte array as output. This is the method that you will receive control in when an external address space uses one of the adapter API calls such as Invoke or Send Request. The execute method is defined on the remote interface, com.ibm.websphere.ola.Execute and contains the business logic for the application.

Attention: Your EJB implementation must not modify or augment the home and remote interfaces in any way. Application exceptions are not supported on the execute method of the remote interface. If your application must throw an exception, it must throw an EJBException, which can optionally wrap the original exception encountered.

Before you begin

Enable the server environment.

Supporting information (generally applicable)

What to do next

Deploy the EJB application.

Previous Step   Previous Step Next Step   Next Step


Terms and conditions for information centers | Feedback

Last updated: Feb 5, 2014 9:41:54 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=tdat_useola_in_step2
File name: tdat_useola_in_step2.html