Tutorial: Web-enabled CICS Acting as a Web Client

Walks you through the process of building and running a version of the sample ACCT CICS application that acts as a Web client.

As with Tutorial: Web-enabled CICS Acting as a Web Server, This tutorial covers many of the concepts covered in Tutorial: CICS Support in that the project and enterprise server region setup is much the same. However the sample ACCT application has been modified and extended to use the CICS Web client APIs to act as a Web client that converses with a Web server to submit and retrieve account information. For this reason, a server program is also included that acts as the back end for the demonstration application.

Prerequisite

Review the Assumptions and Before you begin a tutorial sections in the Tutorials: CICS topic to ensure that your environment is set up properly.

Demonstration application - Web-enabled client ACCT

This Web-enabled ACCT demonstration application is an extended and modified version of the standard example application that IBM supplies with CICS systems. It includes the following source code files, supplied with Enterprise Developer:

ACCT00.cbl
The program associated with the ACCT transaction. It displays a menu screen for the on-line account file application, which prompts the user for input. Transaction AC01 is invoked when that input is received.
ACCT01.cbl
The program associated with the AC01 transaction. Analyzes all requests, and completes those for name inquiries and record displays. For update transactions, it sends the appropriate data entry screen and sets the next transaction identifier to AC02, which completes the update operation. For print requests, it starts transaction AC03 to do the actual printing.
ACCT02.cbl
The program associated with the AC02 transaction. It completes requests for account file updates (adds, modifies, and deletes), after the user entered the update information.
ACCTCLNT.cbl
Opens a Web conversation with the server, constructs and sends requests to the server, and receives responses from the server.
ACCTSVR.cbl
Initializes data, receives and processes requests from the client, and sends responses back to the client.
acctset.bms
The BMS mapset used by the ACCT application.
ACCTCI.cpy
The record definition for client response codes
ACCTREC.cpy
The record definition for the ACCTFIL VSAM file used by the application.
CLNTREQT.cpy
The record definition for client request types.
HTTPSC.cpy
The record definition for status codes.
INREQT.cpy
The record definition for input request types.

Sequence

To complete this tutorial, progress through these topics in the order presented here. The bottom of each topic provides Next topic and Previous topic navigational links to help you proceed in the proper sequence:

  1. Set up the ACCTCLNT Project
    Guides you through all of the project-centric steps of this tutorial, including creating the ACCTCLNT project, importing the ACCTCLNT demonstration files, and configuring the project in Eclipse.
  2. Set Up the ESACCTCL Enterprise Server Region
    Provides step-by-step instructions to complete the creation and configuration of the ESACCTCL enterprise server region on which to run the ACCT Web-enabled client and server.
  3. Run the ACCTCLNT Application in TN3270 Mode
    Provides instructions for running the ACCTCLNT application on the ESACCTCL enterprise server region from the Rumba+ Desktop TN3270 terminal display, and add two data records.
  4. Debug the ACCT Transaction
    Guides you through the process of creating a debug configuration for the ACCTCLNT project and debugging the ACCT transaction using the Enterprise Developer debugger in Eclipse.
Parent topic: Tutorials: CICS