LegacyJ
Transaction Platform Capabilities
COBOL - The LegacyJ Transaction Platform provides the CICS
subsystem for the J2EE Application Server. CICS Cobol, compiled with
PERCobol, will execute on the Application Server, on the Java Virtual
Machine, as a first class Servlet, EJB, or Message Driven Bean.
The Cobol program has not changed and is running in the Application Server,
but continues function as if it is running in CICS.
BMS maps - LegacyJ Transaction Platform converts your BMS to HTML.
The Cobol program still thinks that it is using BMS.
VSAM - The COBOL accesses the VSAM as if it were VSAM, but the VSAM
is really in the database. LegacyJ has a small xml file that maps the
elements in the VSAM record to columns in a database table.
JCL - Nothing is done with JCL. The equivalent on UNIX would be a
shell script or something similar. LegacyJ does provide deploy tools
for deploying your application.
|
|
|
Grid
Computing
LegacyJ Transaction Platform and
Clustering -- An overview of the
technical environment involved with clustering.
Bring
together your Application Silos
J2EE technologies can be incorporated in the mix, as now you are fully
in the J2EE environment. Cobol programmers need not learn Java and
Java programmers need not learn Cobol to use LegacyJ products.
LegacyJ Transaction Platform supports all major Application Servers
(Websphere, WebLogic, SunONE, OracleAS, JBoss, Trifork), and is a
platform independent solution limited only by the license you have.
The hardware requirements are similar to the Application Server's
requirements for developing/deploying J2EE applications.
|
|
