CCF-to-J2C Architecture migration / [Tamas Vilaghy ... et al.].

Format:

Book

Contributor:

Vilaghy, Tamas.

International Business Machines Corporation. International Technical Support Organization.

Series:

IBM redbooks.

IBM redbooks

Language:

English

Subjects (All):

Application software.

Computer architecture.

Java (Computer program language).

WebSphere.

Physical Description:

xii, 202 p. : ill.

Edition:

1st ed.

Other Title:

Common Connector Framework to J2EE Connector Architecture migration

Place of Publication:

White Plains, NY : IBM, International Technical Support Organization, c2005.

Language Note:

English

System Details:

text file

Summary:

This IBM Redbooks publication will help you design a solution to migrate an application from the Common Connector Framework (CCF) to the J2EE Connector Architecture (J2CA). As CCF is phased out and the new technology replaces it, customers will find that migration must be planned and executed carefully. The idea behind this book is to show the architectural differences between the two technologies and help with planning and executing a smooth migration. We show the routes, either automatic or manual migration, and document the tools and tricks that can be used to perform the migration. The automatic migration tool used in this book is the CCF Migration Assistant (CMA) developed by IBM to help customers in their migration efforts. In both cases, automatic and manual, certain preparation and post-processing steps must be performed, and we also show how to accomplish them. We also include a chapter about migrating a real-life application using the tools and ideas listed in the other chapters of the book. The book is an extension of the original Redpaper REDP-3784, published in 2003.

Contents:

Front cover

Contents

Notices

Trademarks

Preface

The team that wrote this redbook

Become a published author

Comments welcome

Chapter 1. Introduction

1.1 From CCF to J2CA

1.2 J2CA vs. CCF at a glance

1.3 Migration options

1.4 Application model considerations

1.4.1 Scenario 1: applications using EAB CCF artifacts directly

1.4.2 Scenario 2: applications using EAB session beans

1.4.3 Scenario 3: applications using business objects and mappers

1.5 Automated migration versus manual migration

1.6 Known limitations imposed by the new environment

Chapter 2. Preparation for migration

2.1 The migration steps

2.2 Preparing CCF in VisualAge for Java for migration

2.3 Preparing WebSphere Studio for migration

2.3.1 Importing a resource adapter

2.3.2 Creating a service project

2.3.3 Adding a server and server configuration

2.4 Migrating the CCF artifacts to J2CA artifacts

2.5 Migrating non-CCF artifacts

deploying the application

Chapter 3. Automated migration using CCF Migration Assistant

3.1 What is CMA?

3.2 Features of CMA

3.3 Limitations and restrictions of CMA

3.4 How to obtain CMA

3.5 How to install CMA

3.6 Migrating CCF artifacts to J2CA artifacts using CMA

Chapter 4. Manual migration

4.1 Migration steps

4.1.1 Importing the COBOL files

4.1.2 Generating the enterprise service

4.1.3 Generating deploy code

4.1.4 Creating the service proxy

Chapter 5. Post-migration steps

5.1 Common post-migration steps

5.1.1 Updating references from CCF to J2CA

5.1.2 Record compatibility

5.1.3 Exception types

5.1.4 Transactions

5.2 Post-migration steps for automatically converted applications

5.2.1 Command compatibility

5.2.2 Resolving generation option discrepancies

5.2.3 Migrating multiple segment messages for IMS.

5.3 Running an enterprise application in the test environment

Chapter 6. Special considerations

6.1 Programming considerations

6.1.1 Exposing InteractionSpec / ConnectionSpec properties as data

6.1.2 Programmatically reading and setting InteractionSpec values

6.1.3 Programmatically reading and setting ConnectionSpec

6.2 Security considerations

6.2.1 Extracting embedded exceptions from the WSIF exceptions

6.3 Co-existence of CCF and J2CA applications

6.4 Exploring WebSphere Studio 5.1 Batch Importer

6.5 Migrating CMA-generated code from WebSphere Studio 5.0.x to 5.1

Chapter 7. Migrating a real-life application

7.1 Describing and analyzing the application

7.1.1 Functionality of the application

7.1.2 Model assessment

7.1.3 Implementation assessment

7.1.4 Numerical analysis of the application

7.1.5 Applying the analysis

7.1.6 Other considerations

7.1.7 Migration starting point

7.2 CMA-based migration of the CCF artifacts

7.2.1 Preparing CCF artifacts

7.2.2 Preparing the migration environment

7.2.3 Performing automated migration

7.2.4 Application post-processing

7.3 Manual migration of the CCF artifacts

7.3.1 Preparing the J2CA artifacts

7.3.2 Application post-processing

7.3.3 Server settings modification

7.3.4 Problems

7.3.5 Result of the manual migration

7.4 Evaluation of the migration

7.4.1 Performance

7.4.2 Numerical comparison of the results

7.4.3 How much time did it take?

7.4.4 Conclusion

Chapter 8. Comparing CCF to J2C Architecture

8.1 Common Connector Framework

8.1.1 The CCF client interfaces

8.1.2 CCF Infrastructure interfaces

8.1.3 VisualAge for Java EAB commands

8.1.4 Implementing the QoS with the RuntimeContext

8.1.5 Setting up the QoS for a sample IMS CCF application

8.2 Making the CCF artifacts J2EE compliant.

8.3 J2EE Connector Architecture (J2CA)

8.3.1 The Common Client Interface

8.3.2 The System Programming Interface and QoS implementation

8.3.3 WebSphere Studio Enterprise Services, WSIF implementation

8.3.4 Setting up the QoS for an IMS J2CA/WSIF application

Abbreviations and acronyms

Related publications

IBM Redbooks

Other publications

Online resources

How to get IBM Redbooks

Help from IBM

Index

Back cover.

Notes:

"January 2005."

"SG24-6362-00."

Includes bibliographical references and index.

OCLC:

80244187