DCOM Explained
The "big picture" of DCOM architecture for system designers and technical managers.
TABLE OF CONTENTS DCOM Explained
Chapter 8: Cedar
Overview
MS RPC provides access to other platforms via its links with the DCE RPC. But what if a company has an IBM mainframe with CICS or IMS and does not want to use DCOM on the mainframe? The answer is to use Cedar a product integrated within the DCOM architecture providing nonintrusive links to programs in CICS or IMS on the mainframe. Remember that Cedar is now called COM TI (Transaction Integrator), but as it is still widely referred to by its code name, I have used Cedar instead of COM TI.
What Is Cedar?
Cedar (Cedar is the internal code name for the technology) provides clients component-based application access to programs written using IBM's CICS and IMS.
Developers using MTS can include CICS programs within an MTS transaction; however, Cedar does not currently support transactional involvement of IMS programs. Where developers need to access IMS/DB databases under
What does it consist of?
Cedar consists of three main components:
-
runtime which intercepts the method calls to the mainframe and uses the Cedar-type library to perform the actual conversion and formatting of the method parameters
-
Interface Builder provides application developers with a GUI tool for creating Windows-based-type libraries. The IB also enables the developers to start from or create the COBOL data declarations used in the mainframe CICS and IMS programs. The developer can install the Interface Builder as an...
Copyright Butterworth-Heinemann 1998 under license agreement with Books24x7
