|
|
|
|
|
|
|
|
|
|
|
|
The BEA eLink JAM product software includes the following major components: SNA Communications Resource Manager The SNACRM runs as a separate native process. It enables APPC conversations and IMS protocols to flow into and out of the Java environment. It normally runs on the same platform as the SNA stack. It obtains its configuration from the JCRMGW. If the Java gateway is running on a platform other than the one on which the SNACRM is running, the SNACRM should be started before the WLS is started so it is listening to the address specified in the JCRMGW configuration. The SNACRM supports non-transactional IMS programs using the implicit APPC support for IMS. Implicit APPC is similar to the CICS/ESA DPL. Any IMS program that sends and receives messages to and from the IMS message queue can be used without change as either a client or a server. To use the implicit APPC capabilities of IMS, you must modify the APPCM file in the SYS1.PARMLIB Partitioned Data Set (PDS) under OS/390. The configuration parameters in this file associate the Logical Unit (LU) with the IMS scheduler. You must identify the LU representing the application name used by JAM to access the IMS region and IMS system ID that provides scheduling for inbound requests. Consult with your mainframe support personnel before making changes to the APPCM file. Java Communications Resource Manager Gateway The JCRMGW is a Java application that manages sessions providing access into and out of the Java environment. It is configured using a text file named jcrmgw.cfg residing in the WLS directory. Requests coming from the mainframe are mapped to an EJB which services the request while requests going to the mainframe are mapped to a mainframe program which can be executed using a CICS DPL. The JCRMGW also supports IMS operations. EgenCobol Code Generator The EgenCobol code generator is a utility that generates Java source code from a COBOL copybook. A base Java application is provided so you can enhance it to create custom Java applications. The generated code is dependent on the generation model chosen: Servlet only Client EJB (with optional servlet) Server EJB Java Class The generated code provides for data accessors and conversions as well as miscellaneous functions. The generated servlet provides a basic form that matches the copybook. You can use this servlet for testing or proof of concept. To complete the environment, the BEA eLink JAM product requires WebLogic Server and a third-party SNA stack (both purchased separately): WebLogic Server The WLS application server provides the environment for running Java Servlets and Enterprise Java Beans (EJB). The Java gateway is launched during the WLS startup using a startup class called gwboot. Configuration requirements for the server to start the gateway are limited to identifying the startup class along with any start-up arguments in the weblogic.properties file. Supported Third-Party SNA Stack A properly configured SNA protocol stack is required for the SNACRM to communicate with a mainframe. (Refer to the BEA eLink Java Adapter for Mainframe 4.0 WLS Edition Release Notes for complete lists of supported stacks.)
|
|
|