1a practical experience on model-driven heterogeneous systems integration a practical experience on...

1A practical experience on model-driven heterogeneous systems integration

A practical experience onmodel-driven heterogeneous

systems integration


systems integration

11th July 2006Bilbao, Spain

Marko Txopitea


ScriptScriptScriptScript

BOA

FileNet

IZFE Framework

Integration

CICS

Difficulties

Methodology

The project

Results


The projectThe projectThe projectThe project

Participants Participants

Start up a high productivity system

for J2EE applications development using IZFE Framework

and their integration with the content manager FileNet

and with the transactional monitor CICS

Start up a high productivity system

for J2EE applications development using IZFE Framework

and their integration with the content manager FileNet

and with the transactional monitor CICS

Objective Objective


BOABOABOABOA

BOA Cartridge for J2EE

Templates

UML Model J2EE Application

BOA Engine

XMI

XSLT

Generated files:.javabuild.xml.properties.jsp

Interface by an Eclipse plug-in

• Class diagrams• Sequence diagrams• State diagrams

• Stereotypes• Tagged values


MethodologyMethodologyMethodologyMethodology


Synchronous

Listeners Subsystem

GUI Subsystem

Base Subsystem

Control Subsystem

Business Subsystem Connector Subsytem

IZFE FrameworkIZFE FrameworkIZFE FrameworkIZFE Framework

Task 1: Architecture study Task 1: Architecture study

Synchronous

Listeners Subsystem

HTTP Listener

Remote Validation Management

Abnormal Navigation

Session/Data Management

Generic Validations

GUI Subsystem

GUI Components

GUI Operatio ns

(OP)

Navigation Flow Engine JSPs

Security Management

Navigation Logger

Debug

Problem Logger

Message Management

Code Table

Management

Transaction Logger

Pools/Cache Management

Print Management

Connector Logger

Base Subsystem

JMS Co nnector

Connector Subsytem

Control Subsystem Startup and

Configuration Management

Exception Management

Remote Event Management

Business Subsystem

Internal Operations

(OI) Integration

Functions (FI)

Business Services (SN) Monitoriz ing

Bean

Channel Manag ement

Stack Management

JDBC Connector

Access Logger

Utilities

Invocation Adaptor



Task 2: Use case development Task 2: Use case development– Analisys of two sample applications

• R09, framework administration application• R17, framework test application

– Identification of unitary components

Task 3: Metamodel creation Task 3: Metamodel creation– Description of the framework following a MVC pattern

– Aspects of the framework:• Initialization• View• Business logic• Persistence

Task 4: Cartridge construction Task 4: Cartridge construction– Action Specific Language (ASL) in the State Diagrams



IZFE Framework Metamodel piece IZFE Framework Metamodel piece


CICSCICSCICSCICS


Task 2: Use case development Task 2: Use case development

Task 3: Metamodel creation Task 3: Metamodel creation

Task 4: Cartridge construction Task 4: Cartridge construction

– No similar programs available– 1st problem: Comunication with CICS– 2nd problem: Formatting data types

– 1st solution:• J2EE Connector Architecture (JCA)• IBM CICS Transaction Gateway (CTG)

– 2nd solution: Java Record I/O (JRIO)

– Identificate general functional components– Identificate information to be parametrized

– Templates that generate the source code


FileNetFileNetFileNetFileNet


Task 2: Use case development Task 2: Use case development

Task 3: Metamodel creation Task 3: Metamodel creation

Task 4: Cartridge construction Task 4: Cartridge construction

– Document management, not workflow

IZFE APIFileNet API

– Identificate general functional components– Identificate information to be parametrized

– Templates that generate the source code

– Two samples from different applications– Identification of common functions


FileNetFileNetFileNetFileNet

FileNet Metamodel FileNet Metamodel


IntegrationIntegrationIntegrationIntegration

Steps Steps1.1. Metamodels unificationMetamodels unification

1.1.1.1. CICS CICS

1.2. FileNet1.2. FileNet

2.2. Cartridges unificationCartridges unification

2.1.2.1. CICS CICS

2.2. FileNet2.2. FileNet

3.3. Test with a sample modelTest with a sample model

IZFE Framework as the baseIZFE Framework as the base


DifficultiesDifficultiesDifficultiesDifficulties

IZFE Framework immature

Hibernate component for IZFE Framework

No previous source code for CICS

FileNet interfaces

Dependencies between 71 JAR libraries

IZFE Framework immature

Hibernate component for IZFE Framework

No previous source code for CICS

FileNet interfaces

Dependencies between 71 JAR libraries

– Difficulties to set up the development environment– Bugs in the current version

– How to call transactions and get the results? JCA and CTG– How to format data types? JRIO

IZFE API FileNet API


ResultsResultsResultsResults

Integration of software developments for the target systems

Capability to generate complete J2EE applications

Models turn in corporate assets for IZFE

Normalization of the systems through UML-based models

Shorter requirement capture cycles

Rise in the quality of the systems to be developed

Integration of software developments for the target systems

Capability to generate complete J2EE applications

Models turn in corporate assets for IZFE

Normalization of the systems through UML-based models

Shorter requirement capture cycles

Rise in the quality of the systems to be developed

IZFE Framework

CICS FileNet

IZFE’s development productivity improvementthanks to the model-driven methodology

IZFE’s development productivity improvementthanks to the model-driven methodology



systems integration


systems integration

11th July 2006Bilbao, Spain

Marko Txopitea

1a practical experience on model-driven heterogeneous systems integration a practical experience on...

Documents

practical experience

metamodel creation task

architecture study task

architecture study slide

use case development

source code slide

j2ee applications development

spain marko txopitea