WEB Communication

This appendix describes the structure and characteristics of the OpenFrame GW RMI server to support AAD (AIM Application Director) in the OpenFrame GW.

1. Overview

The OpenFrame GW RMI server performs to replace the AAD module of Interstage, and the RMI server receives the data, which was exchanged with AAD using Java’s RMI communication method previously, and plays a role of sending and receiving data with AIM’s WEBAIM service.

2. Structure

OpenFrame GW is implemented as a web server on WAS and its RMI server is not a separate product like OpenFrame GW, but a function included in GW.

OpenFrame GW receives data coming from the TN3270E emulator and web browser and transmits it to OpenFrame. In addition, the RMI server operates to deliver data coming from the WEBON RMI client to the WEBAIM service of OpenFrame AIM.

figure rmi structure
OpenFrame GW RMI Server Structure

  • Web Application Server (WAS)

    OpenFrame GW operates on WAS (JEUS).

  • DB

    Stores the currently connected terminal, VTAM, online region information and the client information received through RMI.

  • CLH

    A client handler of Tmax. It relays between the client and the server, requests a service from the business processing server that provides the service, and connects and manages the server. It forwards the incoming client’s request to the server through functions such as tpcall.

  • REGION

    Runs the application program and communicates with OpenFrame GW through CLH.

  • WEBON RMI Client

    The RMI client of the module communicates with the OpenFrame GW RMI server.

3. Operation Process

The following describes the operation process of logging on from the WEBON RMI client to the RMI server and performing a transaction with the WEBAIM service of the Online Region. (Currently, only AIM supports the Online Region.)

figure rmi action1
OpenFrame GW RMI Server Operation

  1. When WEBON module encounters the logic that was communicating with the existing AAD while executing business logic, it transmits data to the RMI server.

  2. After accepting the connection, the RMI server accesses the DB, checks the consistency of RMI Client A, and allows to log on.

  3. The RMI server delivers the transaction along with the received data using the smqn name and procedure name set in ofgw.properties to the Online Region, and receives the execution result.

  4. After finishing the transaction with the OpenFrame Online Region, the RMI server accesses DB and deletes the login information for RMI Client A.

  5. After delivering the data received from OpenFrame Online Region to RMI Client A, the server terminates connecting with RMI Client A.