CREDIT SUISSE's Java Application Platform

(1)

CREDIT SUISSE's Java Application Platform

JUGS Presentation March, 27

th

₂₀₀₈

Robert Bennek KIRO 6

(2)

Text Text integrated Tool-chainShared HWResources

Agenda

5

1 JAP facts and figures

Application Platform

Business Case

4

3

2

6 JAP history

Lessons learned

Roadmap

(3)

Text Tex Text Tex Automated, integrated Tool-chain Hosting on Shared HW Resources

Agenda

5

1 JAP facts and figures

Application Platform

Business Case

4

3

2

6 JAP history

Lessons learned

Roadmap

(4)

JAP Facts & Figures

JAP

Hub Zurich

400 servers (120 prod, 1:7 consolidation)

190 applications

169'000 users (intranet & internet)

14 MLines of effective code

360 mio requests per month

43 FTEs for Hub Zurich for

190 apps and 30+ concurrent projects

Hub Singapore

12 servers (4 prod.)

4 PB applications

6 FTEs for Hub SG

Hub New York (Q2/08)

5 servers (2 prod.)

1 PB pilot application + prospect applications from PB and IB

71

5.5 _2.7

9.3

11.5 PB

IB

AM

TIS CoS

% of apps. on JAP

Productive Application Statistics

0

20

40

60

80

100

120

140

160

180 Jan 05

Mr

z 0

5 Ma

i 0

5 Ju

l 0

5 S

ep 05

_No

v 0

5 Jan 06

Mr

z 0

6 Ma

i 0

6 Ju

l 0

6 S

ep 06

_No

v 0

6 Jan 07

Mr

z 0

7 Ma

i 0

7 Ju

l 0

7 S

ep 07

# A

ppl

ic

at

io

ns

Tower 4/5

Tower 1/2

JAP: Java AP

MF: Mainframe

SE: Special Eng.

Average

Min

Max

-50%

Days/UCP of projects and platform (time-to-market)

(5)

Agenda

5

1 JAP facts and figures

Application Platform

Business Case

4

3

2

6 JAP history

Lessons learned

Roadmap

(6)

JAP History

STARTING SITUATION (1999 – 2002)

Hand crafted heterogeneous servers

Multiple variants => expensive testing

Numerous application servers with different versions

Each application needed to organize component providers

Applying component patches systematically to all servers was

a major challenge

Audit and regulatory compliancy was at risk.

(7)

STARTED WITH SIMPLE SERVLET APPLICATIONS (1999-2002)

JAP History

Started with servlet and mainframe integration (Corba)

Added additional middleware and integration topics (DB, MQ, Mail,

...)

Scalability via HW Load Balancer and multiple WLS instances

Two active sides/data centers for Disaster Recovery (BCP)

First technical stack including all necessary basic components

(8)

JAP History

DISTRIBUTED EJB APPLICATIONS CHALLENGED THE PROCESS (2002/3)

Due to additional needs from Internet applications separation of

presentation and business logic and additional non mainframe logic

was required Æ EJB

Started with Session, Message and finally a limited number of

Entity Beans

Clear technical structure and architectural blue prints, as well as

fully adherence to J2EE standards

(9)

JAP History

AUTOMATE AND SUPPORT THE PROCESS (2004, ongoing)

Development Tool-Chain for compilation and packaging

Automated generation of AppServer configuration reduced the

error rate drastically.

Application configuration DB contains setup of all JAP applications.

Rebuild (for additional deployments or upgrades) of identically

configured WLS instances on a click.

(10)

Agenda

5

1 Credit Suisse facts and figures

Application Platform

Business Case

4

3

2

6 JAP history

Lessons learned

Roadmap

(11)

Managed Stack, no Dependency Explosion, increased Stability,

less maintenance costs, less support, capacity mgt (CHP)

Explosion of dependencies and support and maintenance

costs, un-coordinated lifecycles in technical stack

Hardware

Core OS

Applications

Infrastructure

SW

components

Server Model 1

Server Model 2

Server Model 3

Server model ...

OS Core Version 1

Component a

Version ...

Component a

Version 2

Component a

Version 1

Component a

Version ...

Component a

Version 2

Component b

Version 1

Component a

Version ...

Component a

Version 2

Component c

Version 1

Component ...

Version ...

Component ...

Version 2

Component ...

Version 1

OS Core Version 2 OS Core Version 3 OS Core Version ...

Component a

Release ...

Component a

Release 2

Application a

Release 1

Component a

Release ...

Component a

Release 2

Application b

Release 1

Component a

Release ...

Component a

Release 2

Application c

Version 1

Component ...

Release ...

Component ...

Release 2

Application ...

Version 1

Hardware

Core OS

Applications

Infrastructure

SW

components

Server Model 1

Server Model 2

Server Model 3

Server model ...

OS Core Version 1

Component a

Version ...

Component a

Version 2

Component a

Version 1

Component a

Version ...

Component a

Version 2

Component a

Version 1

Component a

Version ...

Component a

Version 2

Component b

Version 1

Component a

Version ...

Component a

Version 2

Component b

Version 1

Component a

Version ...

Component a

Version 2

Component c

Version 1

Component a

Version ...

Component a

Version 2

Component c

Version 1

Component ...

Version ...

Component ...

Version 2

Component ...

Version 1

Component ...

Version ...

Component ...

Version 2

Component ...

Version 1

OS Core Version 2 OS Core Version 3 OS Core Version ...

Component a

Release ...

Component a

Release 2

Application a

Release 1

Component a

Release ...

Component a

Release 2

Application a

Release 1

Component a

Release ...

Component a

Release 2

Application b

Release 1

Component a

Release ...

Component a

Release 2

Application b

Release 1

Component a

Release ...

Component a

Release 2

Application c

Version 1

Component a

Release ...

Component a

Release 2

Application c

Version 1

Component ...

Release ...

Component ...

Release 2

Application ...

Version 1

Component ...

Release ...

Component ...

Release 2

Application ...

Version 1

Hardware

Core OS

Applications

Infrastructure

SW

components

Server Model 1

Server Model 2

OS Core Version 1

Component a

Version 1

Component b

Version 1

Component c

Version 1

Component a

Release ...

Component a

Release 2

Application a

Release 1

Component a

Release ...

Component a

Release 2

Application b

Release 1

Component a

Release ...

Component a

Release 2

Application c

Version 1

Component ...

Release ...

Component ...

Release 2

Application ...

Version 1

Runtime

Platform

Release

RTP Release 1

RTP Release 2

RTP Release 3

Server Model 2

Server Model 3

OS Core Version 2

Component a

Version 1

Component b

Version 2

Component c

Version 2

Server Model 3

Server Model ...

OS Core Version 3

Component a

Version 2

Component b

Version 3

Component ...

Version 1

Virtualization

VM Layer Version 1

Hardware

Core OS

Applications

Infrastructure

SW

components

Server Model 1

Server Model 2

OS Core Version 1

Component a

Version 1

Component b

Version 1

Component c

Version 1

Component a

Release ...

Component a

Release 2

Application a

Release 1

Component a

Release ...

Component a

Release 2

Application a

Release 1

Component a

Release ...

Component a

Release 2

Application b

Release 1

Component a

Release ...

Component a

Release 2

Application b

Release 1

Component a

Release ...

Component a

Release 2

Application c

Version 1

Component a

Release ...

Component a

Release 2

Application c

Version 1

Component ...

Release ...

Component ...

Release 2

Application ...

Version 1

Component ...

Release ...

Component ...

Release 2

Application ...

Version 1

Runtime

Platform

Release

RTP Release 1

RTP Release 2

RTP Release 3

Server Model 2

Server Model 3

OS Core Version 2

Component a

Version 1

Component b

Version 2

Component c

Version 2

Server Model 3

Server Model ...

OS Core Version 3

Component a

Version 2

Component b

Version 3

Component ...

Version 1

Virtualization

VM Layer Version 1

WHY WE INVEST IN PLATFORMS?

Platform

Release Mgt

Application Platform

Key Benefits of Platform Lifecycle Mgmt

Applications (and platforms) stay in technology lifecycle and

mainstream (no "rotten" components)

Technical upgrades due to lifecycle mgmt of platform are

combined with update on business functionality

Constant decommissioning of out-dated platform releases

identifies no longer used applications

New releases of platforms (with new features) have no impact on

productive applications (no need to migrate; no stability impact

due to changes)

Key Benefits of Platform Lifecycle Mgmt

Applications (and platforms) stay in technology lifecycle and

mainstream (no "rotten" components)

Technical upgrades due to lifecycle mgmt of platform are

combined with update on business functionality

Constant decommissioning of out-dated platform releases

identifies no longer used applications

New releases of platforms (with new features) have no impact on

productive applications (no need to migrate; no stability impact

due to changes)

year

year+1

year+2

year+3

year+4

AR i-2

AR i-1

AR i

requirements &

project setup

release engineering

pilot applications

phase-out

application migration

standard release

new applications

EOL

(12)

TECHNICAL DRIVERS

Price

design/build/test once, operate and automate

centrally, amortize across many applications

Quality

shared tested components, common monitoring &

stability measures (including bug fixes/patches)

Risk

pre-defined infra security, IT-DR, accountability

established and enforced for platform

Capability

defined operational characteristics, performance

and capacity

Price

design/build/test once, operate and automate

centrally, amortize across many applications

Quality

shared tested components, common monitoring &

stability measures (including bug fixes/patches)

Risk

pre-defined infra security, IT-DR, accountability

established and enforced for platform

Capability

defined operational characteristics, performance

and capacity

From custom building

→ platform:

Integrated and tested components in runtime stack

Fixed component versions per platform release

Defined and largely automated processes for ordering,

provisioning, configuration management, software

distribution, change management, performance & capacity

management, monitoring, IT DR, auditing, etc.

Platform management for platform as a whole:

requirements management, release management, life cycle

management, technology strategy & architecture, end to

end service, pricing, business case, KPIs, etc.

Application Specific Work

Graphical User Interface (GUI)

Business Logic

Database Schemas

Configuration

Infrastructure Design / Implementation

Runtime Stack

HW, OS, Middleware, Network

Systems Management/Operation, Security,

Development Tools, etc.

(13)

WHAT IS A PLATFROM?

Platform Types

• Runtime Platform (RTP)

generic

• Hosting Platform (HP)

added services like capacity mgt

(virtualization) for OS build, DB build,

etc.

• Application Platform (AP)

added services specialized for areas of

similar applications

Tex

t

Tex

t

Tex

t

Tex

t

Tex

t

Tex

t

Managed,

high-quality

Technical

Components

Automated,

integrated

Tool-chain

Hosting on

Shared HW

Resources

Architecture,

Guidelines &

Documentation

A set of integrated technical components and processes for the

development and operation of applications

(14)

Application Platform

HIGH-LEVEL MODEL

Services provided by an Application Platform

–

Platform Product Mgmt & Governance:

drives product

development and release & lifecycle management adhering to a

well-defined governance model

–

Platform Operations:

operates applications cost-efficiently

with standardized processes according to OLA

–

Application Development Support:

guides projects

through entire development process and shields projects from

low-level infrastructure issues

Infrastructure needed to provide these services

–

Technical Components:

providers supply high-quality and

well-managed technical components that are tested and

integrated into readily deployable packages (so-called TIP)

–

Hosting:

applications are hosted on shared hardware resources

according to production guidelines; applications may also run on

dedicated servers if required

–

Tool-chain:

automates key processes of solution delivery such

as configuration management and deployment in a reliable,

repeatable manner

–

Architecture, Guidelines & Documentation

: defined,

standardized architecture based on open standards for various

needs, and information to implement applications for the platform

Tex

t

Tex

t

Tex

t

Tex

t

Tex

t

Tex

t

Managed,

high-quality

Technical

Components

Automated,

integrated

Tool-chain

Hosting on

Shared HW

Resources

Architecture,

Guidelines &

Documentation

(15)

TOOL-CHAIN OVERVIEW

Tool-chain supports typical

create-edit/configure-build-deploy-run-debug functionality

Tool-chain automates key processes of solution delivery such as

configuration mgmt and deployment

JAP enables repeatable deployment of applications to any system

at any time (in accordance to CMMI/SOX)

Main elements are:

–

TIPD

(technical infrastructure package for development)

create application & components structures

collaboration / configuration mgmt of source code

build-deploy-run-debug on local machine

–

Configuration Mgmt

(required by CMMI / SOX) for source code,

components, deployment units, and documentation

–

Build Server

: automatically compile code and package deployment units

–

WLS Instance Creation:

create configuration of runtime environment

(instance) of WebLogic Server

–

Debugging, Testing:

start/stop instance, inspect log-files, perform load

tests, monitor application behavior

–

Software Deployment:

configuration of profiles of target machines,

package repository and installation of packages

Developer Machine

IDE

TIPD

Browser

Tool-chain

Configuration

Management

Server

Build

WLS Instance

Creation

Software

Deployment

Debugging

Testing

Hosting environment

(Shared) Test Servers

(Shared) Production Servers

SCM

(16)

(17)

OVERVIEW TECHNICAL COMPONENTS

Layer 1

(Hardware, Disk, Network, OS Build, Core Systems Mgmt / Security / Integration)

Monitoring

JMX TAP

1 Tr@Log

Oracle TAP

1 Notify Core

WLS TAP

1 Performance

(Introscope)

J2EE Monitoring

Probe

Enterprise Perf.

Agent

Security

Web Entry

Integration

Public Key Infra. &

API

PKI Certificates

Integration

Java Corba Bridge

Corba Infra.

Java Mail API

JMS Wrapper

Middleware

Batch Framework

Batch Libraries

Oracle DB Client

Runtime

BEA WebLogic Server (WLS)

Java Developer

Kit (JDK)

Java Runtime Env.

(JRE )

Java Core Framework (JCF)

JCF Extension

CS Application Interface

(Tivoli Adapter)

JAP defines the runtime stack in three layers

–

Layer 1 subsumes infrastructure elements provided by a

Runtime Platform (OS Build & Services)

–

Layer 2 contains application server and APIs to access

infrastructure (security, integration, systems mgmt)

–

Layer 3 subsumes configuration, code, and resources of

applications (some libraries are standardized)

Applications only access interfaces provided by Layer

2 →

JAP may exchange Layer 1 components without affecting

applications (e.g., cheaper hardware)

JAP owns no components but reuses already existing

components from various providers; components are

engineered once for the platform

JAP provides a bundle of layer 2 components as TIP

(Technical Infrastructure Package) that runs on a well

defined layer 1

Layer 3

Layer 2:

Technical Infrastructure Package (TIP)

Applications

(Code, Configuration)

Standard Libraries

(18)

Application Platform

ARCHITECTURE, GUIDELINES & DOCUMENTATION

JAP supports Java applications that

are built according to the CS Tower

architecture

JAP provides the necessary

information to facilitate the

application development for and

operation on JAP

–

Architectural & Process Guidelines

–

Manuals & Training Material

–

...

The information are centrally available

through the JAP Homepage

JAP ensures the configuration

management of the relevant

documents

Architectural Guidelines

Platform Documentation

Operations Manual

Training Material

Support Material

JAP Customers

JAP

Organization

Component

Providers

Support

Java

(Platform)

Architects

(19)

Application Platform

HOSTING ON SHARED HW RESOURCES

Typical J2EE application requires up to

20 servers with traditional hosting

including test stages and BCP

JAP provides the necessary

infrastructure; applications share server

but are still isolated at the system level

Each platform release may require its

own resources

→ but only 3 releases in parallel

Quantitative Benefits:

–

JAP hosts 190 applications on 400 servers.

Traditional hosting would require more than

2800 servers

–

More efficient operations support

→ critical mass of applications required

Qualitative Benefits:

–

Standardized OLA, multi-rail, BCP solution,

fail-over

(20)

Complex Applications

JAP DEPLOYMENTS

(21)

Agenda

5

1 JAP facts and figures

Application Platform

Business Case

4

3

2

6 JAP history

Lessons learned

Roadmap

(22)

Text Text Automated, integrated Tool-chain Hosting on Shared HW Resources

Business Case

APPLICATION COST MODEL (CUSTOM DEVELOPMENT)

Business Engineering

Analysis & Design

Implementation

Testing

Configuration

Project Mgmt

Stack Engineering

Integration into

Surrounding Systems

Deployment

BFD

II

D

Application Maintenance

Application Monitoring

3 rd

_{Level Support (App)}

70%

(A1)

30%

60%

(A4)

Infra. Maintenance

Infra. Monitoring

3 rd

_{Level Support (Infra)}

1 st

_{and 2}

nd

_{Level Support}

1&

2 IL

AL

30%

(A6)

10%

Recurring Costs (Run the Bank)

–

Maintenance Costs at Application Level (AL),

i.e.

Application Maintenance, Monitoring, Support (3

rd

₎

–

Maintenance Costs at Infrastructure Level (IL)

i.e.

Infrastructure Maintenance, Monitoring, Support (3

rd

₎

–

1 st

_{and 2}

nd

_{Level Support (1&2LS)}

, i.e., only

infrastructure support excluding business support

–

Assumptions:

A4:

60% of all RTB costs at application level

A6:

30% of all RTB costs at infrastructure level

One time Costs (Change the Bank)

–

Business Functionality Development (BFD)

incl.

Business Engineering, Analysis & Design,

Implementation, Testing, Configuration, Project Mgmt

–

Infrastructure Integration & Deployment (IID)

Stack Engineering (Systems Engineering,

Infrastructure Testing, Configuration)

Integration into Surrounding Systems (Security,

Systems Mgmt, SOA, Legal & Compliance)

Deployment

–

Assumptions:

(23)

Text Text Text Text Technical Components Automated, integrated Tool-chain Hosting on Shared HW Resources Guidelines & Documentation

Business Case

SAVINGS FOR DEVELOPMENT ON JAP

custom

on JAP

IID

70%

(A1)

30%

100%

BFD

IID

ª10%

(A2)

ª80%

(A3)

63%

6%

69%

AL

60%

(A4)

30%

(A6)

IL

1&2LS

10%

100%

AL

IL

55%

10%

65%

custom

ª8%

(A5)

ª66%

(A7)

ª100%

(A8)

Savings on Recurring Costs (RTB)

–

Maintenance Costs at Application Level (AL)

Savings:

High quality reduces problems in prod.;

periodic review & decommissioning of applications

Residual Costs:

3 rd

level support & maintenance

–

Maintenance Costs at Infrastructure Level (IL)

Savings:

Infrastructure lifecycle mgmt does not

involve applications (e.g., DST handling)

–

1 st

_{and 2}

nd

_{Level Support (1&2LS)}

Savings:

JAP provides full 1

st

and 2

nd

level

support

–

Assumptions:

A5:

8% savings for maintenance on AL

A7:

66% savings for maintenance on IL

Savings on One time Costs (CTB)

–

Business Functionality Development (BFD)

Savings:

Reuse of common framework and

components (Facades, JSF, ...) provided by JAP

Residual Costs:

development of business func.

–

Infrastructure Integration & Deployment (IID)

Savings:

complete stack from JAP; integration

into infrastructure done; servers up and running

Residual Costs:

extensions of infrastructure;

infrastructure configuration; JAP E2E consultant

–

Assumptions:

A2:

10% savings for BFD in solution delivery

BFD

(24)

Text Text Text Text Automated, integrated Tool-chain Hosting on Shared HW Resources

BENEFITS OF A JAVA AP

Business Case

Provision of significant quality attributes (e.g. security, failover,

operability, auditability,…) is ensured.

Lifecycle is in place.

Release 1 and 2 of the platform are already phased out, currently 3 &

4. Shared servers improve utilization.

Unit prize constantly reduzed (-15% per year)

Increased efficiency of application products.

Standardization improves QoS.

Toolchain makes upgrade or extension of applications much more

efficient.

Documentation of processes and organisation enables a steep

learning curve for new IT-PLs.

(25)

Agenda

5

1 JAP facts and figures

Application Platform

Business Case

4

3

2

6 JAP history

Lessons learned

Roadmap

(26)

Lessons learned

Processes

9 organizational change from silos to value chains

9 new discipline Platform Management

9 establish adequate governance system

9 introduce key metrics

Services

9 Competence Center & Support

9 Platform Consultancy

9 Automation and tool support

9 Communication & Information

Product Management

9 Sustainable value creation requires a

product-oriented approach

9 Flexibility must be part of the architectural product

line design

Culture and organizational readiness

9 Stakeholder Management

9 Management Attention

9 Politics

It is much more than Technology, prepare for heavy

investments in Processes and Value Chain coordination

Complexity increases, platform consultancy for

application development is required (processes and

services)

Tool Chain Automation reduces error rate and prevents

manual interventions

Decouple infrastructure standardization from

application-driven approach otherwise a sustainable

cost efficiency may be corrupted

Standardization is important, but controlled flexibility as

well

More transparency makes you vulnerable, be prepared

for heavy fights

Agree on Platform Development Strategy in advance

and tailor approach to your specific environment,

organization and culture

Prepare your stress hormones for unbelievable huge

numbers of organizational interfaces. There is always

lot's of politics...

(27)

Lessons learned

It is much more than Technology, prepare for heavy

investments in Processes and Value Chain coordination

Complexity increases, platform consultancy for

application development is required (processes and

services)

Tool Chain Automation reduces error rate and prevents

manual interventions

Decouple infrastructure standardization from

application-driven approach otherwise a sustainable

cost efficiency may be corrupted

Standardization is important, but controlled flexibility as

well

More transparency makes you vulnerable, be prepared

for heavy fights

Agree on Platform Development Strategy in advance

and tailor approach to your specific environment,

organization and culture

Prepare your stress hormones for unbelievable huge

numbers of organizational interfaces. There is always

lot's of politics...

Processes

9 organizational change from silos to value chains

9 new discipline Platform Management

9 establish adequate governance system

9 introduce key metrics

Services

9 Competence Center & Support

9 Platform Consultancy

9 Automation and tool support

9 Communication & Information

Product Management

9 Sustainable value creation requires a product-oriented

approach

9 Flexibility must be part of the architectural product line

design

Culture and organizational readiness

9 Stakeholder Management

9 Management Attention

9 Politics

It is much more than Technology

,

prepare for investments in Processes and Value Chain coordination

It is much more than Technology

,

(28)

Lessons learned

It is much more than Technology, prepare for heavy

investments in Processes and Value Chain coordination

Complexity increases, platform consultancy for

application development is required (processes and

services)

Tool Chain Automation reduces error rate and prevents

manual interventions

Decouple infrastructure standardization from

application-driven approach otherwise a sustainable

cost efficiency may be corrupted

Standardization is important, but controlled flexibility as

well

More transparency makes you vulnerable, be prepared

for heavy fights

Agree on Platform Development Strategy in advance

and tailor approach to your specific environment,

organization and culture

Prepare your stress hormones for unbelievable huge

numbers of organizational interfaces. There is always

lot's of politics...

Processes

9 organizational change from silos to value chains

9 new discipline Platform Management

9 establish adequate governance system

9 introduce key metrics

Services

9 Competence Center & Support

9 Platform Consultancy

9 Automation and tool support

9 Communication & Information

Product Management

9 Sustainable value creation requires a product-oriented

approach

9 Flexibility must be part of the architectural product line

design

Culture and organizational readiness

9 Stakeholder Management

9 Management Attention

9 Politics

Complexity increases

, platform consultancy

for application development is required (processes and services)

Complexity increases

, platform consultancy

(29)

Lessons learned

It is much more than Technology, prepare for heavy

investments in Processes and Value Chain coordination

Complexity increases, platform consultancy for

application development is required (processes and

services)

Tool Chain Automation reduces error rate and prevents

manual interventions

Decouple infrastructure standardization from

application-driven approach otherwise a sustainable

cost efficiency may be corrupted

Standardization is important, but controlled flexibility as

well

More transparency makes you vulnerable, be prepared

for heavy fights

Agree on Platform Development Strategy in advance

and tailor approach to your specific environment,

organization and culture

Prepare your stress hormones for unbelievable huge

numbers of organizational interfaces. There is always

lot's of politics...

Processes

9 organizational change from silos to value chains

9 new discipline Platform Management

9 establish adequate governance system

9 introduce key metrics

Services

9 Competence Center & Support

9 Platform Consultancy

9 Automation and tool support

9 Communication & Information

Product Management

9 Sustainable value creation requires a product-oriented

approach

9 Flexibility must be part of the architectural product line

design

Culture and organizational readiness

9 Stakeholder Management

9 Management Attention

9 Politics

Standardization is important,

but controlled flexibility as well

Standardization is important,

(30)

Agenda

5

1 JAP facts and figures

Application Platform

Business Case

4

3

2

6 JAP history

Lessons learned

Roadmap

(31)

Roadmap

WRITE AN APPLICATION ONCE, RUN IT EVERYWHERE

First international hub established in Singapore.

Hub New York is currently rolled out.

Global JAP Governance

Centralized Platform Product Management

provides JAP

JAP 3rd level support for other JAP

locations

Same location as a JAP Hub

JAP Global

Platform

Mgmt

JAP Hub

Support JAP application development and

running

One per region

First contact for satellite locations in the

(32)

PORTAL FUNCTIONALITY IN JAP 5

Roadmap

Weblogic Portal enables a new class of applications.

Integration driven portals allow decoupling of complex applications

Portal functionality is focused on application integration

–

Decouple portlet applications from portals

–

Allow reuse of portlet providers in different portals

–

Update of single portlet apps at runtime

Support campaign management

Challenges include:

–

provide registry and repository

–

development, packaging und distribution support

–

ensure operability and maintainability

–

manage new dependencies between applications

(33)

FIRST STEP FOR ENTERPRISE READY TRANSACTION SUPPORT

Roadmap

A new dimension for the Java platform: get ready to host applications and data

with massive transaction requirements

Challenges include:

–

development, packaging und distribution support

–

guidelines needed for data modelling, DB engineering, programming, migration, testing,….

–

ensure operability and maintainability

–

interaction with existing systems

–

….

JAP 5 is the first step towards a Java transaction platform

–

delivers basic architectural & engineering principles

–

PoC by building a prototype for applications with massive transaction requirements

CREDIT SUISSE's Java Application Platform