LegacyJ CICS and COBOL technology for the J2EE Enterprise Environment

Products     Services     Support     Sales     News     Partners

Academic
Programs

Customer
Information

News &
Information

Technical
Information

White
Papers

About Us

LegacyJ Transaction Platform FAQs

Overview
Migration Process
Fact Sheet
Technical Description
Documentation
Restrictions
FAQ
LegacyJ Transaction Platform is a robust enterprise sub-system permitting CICS based COBOL applications to migrate to and execute in the J2EE environment. 

LegacyJ Transaction Platform integrates business applications into a cohesive, flexible, enterprise solution that allows existing business processes to use and exploit J2EE based technologies.

Questions 

Is LegacyJ Transaction Platform CICS?

What is the difference between LegacyJ Transaction Platform and other transaction sub-systems?

The cost of running a CICS sub-system is a major issue will LegacyJ Transaction Platform help address this business issue?

Can I stage my migration and move an application at a time onto the Transaction Platform?

My application will be redeployed on J2EE Application Server with the Transaction Platform; what manual changes are required to migrate?

Are there any incompatibilities between CICS behavior and LegacyJ Transaction Platform?

How should a LTP project be defined in the LegacyJ IDE?

Does the COBOL transaction program get generated as an EJB,  and, if so, what kind of EJB?

What SQL Databases can be used?

File Control and SQL both use JDBC for access to relational databases; does this mean that file access such as VSAM uses JDBC?

Does the LegacyJ Transaction Platform support IBM MQSeries?

Are there any tips for debugging LTP projects?

In the LTP project deploy settings file, under programs, do all programs need to be put in there manually? 

How should our business start using the LegacyJ Transaction Platform? What Transactions would be ideal?

If the application is moved between architectures, what actions are required for EBCDIC and ASCII data? 

Will my batch programs work with the data files created by transactions running under LegacyJ Transaction Platform?

What should I do with my BMS maps used as an interface to my CICS COBOL applications?

What should be done if in our business a screen scraper has been used?

Will the function keys my CICS applications use still work in a browser?

Using the LegacyJ Transaction Platform, is it possible to add Java (J2EE) components to my application?

High Level Assembler (mainframe assembler) is used to add functions to our CICS sub-system; how will this Assembler code be handled with the LegacyJ Transaction Platform?

Job Control Language (JCL) and PROCLIBs have been created to submit batch jobs; are these relevant?

What are the Services and commands supported by the LegacyJ Transaction Platform?

Are there any restrictions in the support available that I might have used with CICS?

What special information do I need to deploy onto Websphere?

How do I debug with Jboss?

More Information

LegacyJ Transaction Platform Checklist (Setup Worksheet)

contact LegacyJ...
sales@legacyj.com

 


 

Home         About Us         Privacy        Legal        
© Copyright LegacyJ Corp. 1998, 2008
All Rights Reserved.

All trademarks are the properties of their respective owners or licensers.