In this chapter:
In this chapter you will be using VisualAge for Java Enterprise Edition to develop the CICS Java component together with the Enterprise Toolkit/390 (ET/390) that comes with it. The procedure is based on VisualAge for Java Version 2. The panels and screens in Version 3 are different.
Before you can complete the procedure in this chapter you need to install the COBOL application and have all the definitions outlined in Appendix A set up.
The IIOP client/server programming model starts with interface definitions. Here are the steps for developing a CORBA application:
Write a definition for each object using IDL.
Compile the IDL code using an IDL-to-Java compiler to produce server skeleton code and client stub code.
Create and add the Java implementation classes.
Build the server application (Export and bind to a CICS region).
Build the client application.
The main tool detailed in this chapter is VisualAge for Java for Windows NT, Enterprise Edition, which is an end-to-end Java application development tool that lets you develop Java code on the workstation and deploy it on OS/390. It provides a comprehensive Integrated Development Environment (IDE) that supports browsing, editing, compiling, testing, debugging, and deployment. The Enterprise Toolkit for OS/390 (ET/390), a feature of VisualAge for Java Enterprise Edition, provides OS/390 support. It provides a SmartGuide to export class files to the OS/390 Hierarchical File System (HFS) for native compilation and debugging. Native code built on PDSEs is a dynamic link library (DLL) that, while not portable, is suited for high-performance server programs.