Since more than 15 years we have been very happy to work with JCAPS and its predecessors. When Oracle announced to cease support for the platform, we created a task force with the mission to assess which platform provides the best assets to become a true successor for JCAPS. We finally selected WSO2 which is a great, stable, flexible and performing SOA platform. Our experience confirmed it to be the best fit for successful migration projects. We have written a complete set of migration tools for JCAPS (5.x) and eGate (4.x) to WSO2 ESB. This helps really to speed up the migration and keeping the quality and even improve the performance.

1. :: eGate / JCAPS migration to WSO2
or other ESB’s ::
AVINTIS JCAPS-Migration Tools Overview
Philipp Brügger
Head of Development and Architecture
January 2013
:: avintis sa :: route du tir-fédéral 10 :: CH-1762 Givisiez :: info@avintis.com :: www.avintis.com ::
:: tel +41 26 469 71 11 :: fax +41 26 469 71 10 ::

2. Introduction
Since more than 15 years we have been very happy to work with JCAPS and its
predecessors. When Oracle announced to cease support for the platform, we created
a task force with the mission to assess which platform provides the best assets to
become a true successor for JCAPS. We finally selected WSO2 which is a great,
stable, flexible and performing SOA platform. Our experience confirmed it to be the
best fit for successful migration projects. We have written a complete set of migration
tools for JCAPS (5.x) and eGate (4.x) to WSO2 ESB. This helps really to speed up the
migration and keeping the quality and even improve the performance.
:: migration tools JCAPS -> WS02
:: Janvier 2003 :: S. 2

3. JCAPS extract
> Advanced Extract of JCAPS project
> All necessary information for the migration are mapped in one XML format
> Complementary libraries are also extracted
:: migration tools JCAPS -> WS02
:: Janvier 2003 :: S. 3

4. Component Migration to WSO2
• Based on the JCAPS extract
• JCAPS components migrated to WSO2 components
• Java libraries can be reused
JCAPS WSO2
JCD (Java) Custom Mediator (Java)
XSD OTD XSD
WS OTD WSDL
Flat file OTD Custom XSD, Smooks or Java
Connectivity Map Synapse Proxies, Sequences,
Endpoints
:: migration tools JCAPS -> WS02
:: Janvier 2003 :: S. 4

5. Component Migration to WSO2
tPatient HL7 pAdjumed_in Adjumed qAdjumed_out Adjumed qAdjumed_out Adjumed FTP
:: migration tools JCAPS -> WS02
:: Janvier 2003 :: S. 5

6. JCD Migration: most code is just reused
> WSO2 is also Java based, so most of the JCD Code can be re-used without
modification.
> The JCD Business Logic will not be modified
> Only the Getter/Setter of the JCD depending of the used OTD may need some
modification.
> Existing external Java libraries are reused
:: migration tools JCAPS -> WS02
:: Janvier 2003 :: S. 6

7. Migration of Datatyp-Definitions ETD / OTD
> The JCAPS Object Type Definitions (OTD / ETD) can represent many different types
of data.
> Depending on the type we provide different migration paths: e.g.
• XSD will be reused completely – as WSO2 works with XML
• Fix length/Delimited files can be migrated to a XSD definition with custom Builder and
Formatter
• Fix length/Delimited can be migrated to Smooks definitions
• WebServices transformed to WSDL
• HL7 definitions migrated to HAPI XML structures
• ..
:: migration tools JCAPS -> WS02
:: Janvier 2003 :: S. 7

8. Summary
> Effective and highly reusable migration from JCAPS to WSO2
> Nearly no influence on the business logic
> JCD code reused as much as possible
> JCAPS Data Structures migrated to reusable XML based structures
:: migration tools JCAPS -> WS02
:: Janvier 2003 :: S. 8