Gen 8.6 EJB Java server and server-to-server Flows

Products

• Gen
• Gen - Run Time Distributed

Issue/Introduction

How to implement the following scenarios for server-to-server flows from a Gen 8.6 EJB Java server:

1. Gen generated EJB invoking another Gen generated EJB using the Java RMI Communications Runtime.
2. Gen generated EJB invoking another Gen generated Web Services server using the new Java Web Services Middleware Runtime.
3. Gen generated EJB invoking a Gen generated COBOL server on CICS or IMS using TCP/IP.

WebSphere Application Server is used for our EJBs.

Environment

Release :Gen 8.6

Component: Gen Enterprise Java Beans

Resolution

The commcfg.properties file packaged with the deployed EJBs will control the server-to-server flow. See the comments in that file for syntax details.
For the scenarios below assume server1 calls server2 which has trancode SVR2:

1. A Gen generated EJB invoking another Gen generated EJB using the Java RMI Communications Runtime.
   SVR2=EJBRMI {Initial Factory Class} {Name Manager URL}
   (If EJBs are in deployed in the same Appserver instance the parameters {Initial Factory Class} and {Name Manager URL} may not be required)
   
   
2. A Gen generated EJB invoking another Gen generated Web Services server using the new Java Web Services Middleware Runtime.
   Assuming the called EJB has been generated with TP monitor ="EJB Web Services":
   SVR2=WS http://hostname:port L
   (assumes WebSphere being targeted so using 'L')
   
   
3. A Gen generated EJB invoking a Gen generated COBOL server on CICS or IMS using TCP/IP.
   SVR2=TCP hostname port N
   (N means non-persistent connection which is required for Gen CICS Multi Sockets Server. For IMS Direct Connect no value should be used or Y can be used - no value defaults to Y i.e. persistent connection)

Additional Information

Please refer to Gen 8.6 doc. page Technical Requirements for Generated Applications and section "EJB Distributed Processing Servers" to learn more about EJB server-to-server flow possibilities.