Top Banner
Page 1 Architectural Flexibility - Distributed and Centralized
26

Page 1 Architectural Flexibility - Distributed and Centralized.

Dec 18, 2015

Download

Documents

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 1

Architectural Flexibility - Distributed and Centralized

Page 2: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 2

ClearPath Java: Total Flexibility Mix and Match Tiers

Distributed / Composite

Data server

Data server

Web server

Web server

App server

App server App server

Data server

Or

Applications and data distributed across multiple ClearPath systems

Centralized

All tiers on one ClearPath

infrastructure

Web serverApp serverData Server

Web server

Page 3: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 3

Choice of Centralized and Distributed Heterogeneous Java Environments

Windows

ES7000

Linux

Centralized Distributed / Composite

OrClearPath

Web server

Web server

Web server

App server

App server

Data server

Data server

All tiers on one ClearPath

infrastructure

Web serverApp serverData Server

SUN

HP

App server

Unix

IBM

Data server

ClearPath

Page 4: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 4

Available Today: Many ClearPath Multi-tier Java Architecture Options

Web ServerWeb Server Any ServerAny Server ClearPathClearPath

Client tierClient tier

Web tierWeb tier

JSPsJSPs

ServletsServlets

Business tierBusiness tier

BeansBeans

EIS tierEIS tierData-baseData-base

Trans-actionsTrans-actions

n-tier: spread across multiple servers

Any ServerAny Server ClearPathClearPath

Client tierClient tier

Web tierWeb tier

JSPsJSPs

ServletsServlets

Business tierBusiness tier

BeansBeans

EIS tierEIS tierData-baseData-base

Trans-actionsTrans-actions

3-tier: J2EE server & ClearPath

ClearPathClearPath

Client tierClient tier

Web tierWeb tier

JSPsJSPs

ServletsServlets

Business tierBusiness tier

BeansBeans

EIS tierEIS tierData-baseData-base

Trans-actionsTrans-actions

2-tier: ClearPath direct to client

Web ServerWeb Server ClearPathClearPath

Client tierClient tier

Web tierWeb tier

JSPsJSPs

ServletsServlets

Business tierBusiness tier

BeansBeans

EIS tierEIS tierData-baseData-base

Trans-actionsTrans-actions

3-tier: Tomcat or Windows IIS with JBoss on ClearPath

WebsphereWeblogic

JBoss

WebsphereWeblogic

JBoss

WebsphereWeblogic

JBoss

WebsphereWeblogic

JBoss

WebServiceWebService

Page 5: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 5

Rapid Application Development with Industry Standard Tools

Page 6: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 6

Develop ClearPath Java Applications - Use Industry Standard Skills and Tools

ClearPath non-Java

Applications and Data

Eclipse IDE :• Open Source (free)

• Most popular

Easy with Eclipse plug-ins:

1. Unisys-built plug-ins

2. Open Source plug-ins(Hundreds)

3. 3rd Party plug-ins

ClearPath Java

Applications

Unisys Value Add: Tight integration with ClearPath non-Java

Applications and Data

Page 7: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 7

Security

Page 8: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 8

ClearPath Java Role-Based Security

• Unisys value add integration

• Role-based Java Security between JBoss and ClearPath

• Access permission assigned to roles, new users get access permissions based on their role

• Provides simplified administration

• Unified authentication between Java and ClearPath

Page 9: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 9

SOA-enabling software for ClearPath OS 2200

Page 10: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 10

OS 2200 software SOA enablers

• Java– Native JVM implementation

– JBoss application server

– Resource adapters for RDMS, DMS, TIP/HVTIP, DTP services, BIS

– Eclipse plug-ins

• Other OS 2200 SOA-enabling software– OpenDTP (Open Distributed Transaction

Processing)

– MQseries

– DTI (Distributed Transaction Integrator)

– MSMQI (Interface to Microsoft Message Queuing)

– NTSI (Messaging Integration Services)

– CITA (Communications Interface for Transaction Applications)

– Third-party products for screen-scraping and ODBC access

The right tool

for every job

Page 11: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 11

Java on OS 2200

• Java Virtual Machine– Native implementation on OS 2200

– Integrated with OS 2200 security and file systems

• JBoss– Open source Java EE application server

– Validated, prepackaged and enhancedfor 2200 with security, transactionintegration and more

– Redhat-JBoss offers additional open source products, including JBoss Enterprise Middleware Suite (JEMS) – “The open source platform for SOA.” They are also developing an open source enterprise service bus.

Page 12: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 12

Java on OS 2200: Resource adapters

ResourceManagers

ResourceAdapters

RDMSRDMS

DMSDMS

BISBIS

TIPHVTIP

TIPHVTIP

TIPResource Adapter

TIPResource Adapter

BISResource Adapter

BISResource Adapter

DMSResource Adapter

DMSResource Adapter

DTPSvcsDTPSvcs

Open DTPResource Adapter

Open DTPResource Adapter

RDMSResource Adapter

RDMSResource Adapter

“Duke” Java mascot

WebService

WebService

Page 13: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 13

Page 14: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 14

Page 15: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 15

Page 16: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 16

Page 17: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 17

Page 18: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 18

Page 19: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 19

Page 20: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 20

Eclipse for SOA and composite apps

From the open source community:

1. Eclipse 3.1.22. EMF-SDO-XSD SDK 2.1.23. GEF 3.1.1 4. JEM SDK 1.1.0.1 5. SQL Explorer 2.2.4 6. WTP 1.0.3

Unisys Composite Applications 3.1.1:

1. OS 2200 Project Perspective2. Telnet client and library3. Version of Eclipse COBOL plug-in feature modified by

Unisys for OS 2200COBOL Dialects4. JAI The Java Application Integrator (JAI) – OS 2200

TIP/HVTIP Resource Adapter tools5. Eclipse JDT APT - Provides Java 5.0 annotation

processing support6. PLUS Editor 7. CDT - Eclipse CDT feature, providing a C/C++ editor for

OS 2200 C/C++ files and a full C/C++ project development environment.

Eclipse Dorado All-In-one package: Unisys developed plug-ins and open source tools

WTP = Web Tools ProjectNext release will include a version of WTP with direct

support of web services

2200-specific tools

All-in-one downloadable from website ftp://ftp.support.unisys.com/pub/2200/IDE/

Page 21: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 21

Web Services

• Standardized way to implement SOA over the Internet (or any network)

• Based on XML files and messages

– WSDL (Web Service Description Language) to describe services

– SOAP (Simple Object Access Protocol) to format messages

– Dozens of other standards at varying levels of maturity

• When you want the highest degree of standardization, platform independence, and future flexibility

• When functionality is needed by business partners, clients, and suppliers who operate in a wide variety of computing environments

• When you have technology that supports them, such as the Java EE environment on OS 2200

What are Web Services? When should you use them?

Page 22: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 22

Native OS 2200 middleware

• Described in the OS 2200 modernization white paper:

– OpenDTP – MQseries– DTI– MSMQI – NTSI – CITA

• When you have no need to extend the services outside the data center and your internal, active networks

• When you have real-time performance needs that cannot be met in a Web Service environment

• When you have specific platform and technology integration needs

• When you do not have Java expertise but do have expertise in direct use of these middleware solutions

• When you are using distributed transactions that span services

Remember: SOA and Web Services are NOT

synonymous!

Use native middleware…

Page 23: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 23

SOA-enabling Unisys Professional Services

Page 24: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 24

Unisys services are based on 3D Blueprinting

The next generation business and systems modeling architecture that integrates business vision and IT execution, to drive organizational agility.

BUSINESSARCHITECTURE

SERVICES-BASEDTECHNICAL

ARCHITECTURE — INFRASTRUCTURE MODEL

— APPLICATION MODEL

— BUSINESS PROCESS MODEL

— BUSINESS STRATEGY MODEL

Reduce Cost by Eliminating Application

& Infrastructure Redundancy

Reduce Business Process “Cycle Times”

For Competitive Advantage

Increase Agility by Assessing Impacts and

Reacting more quickly to Change

Page 25: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 25

SOA provides the “Structural Abstraction” that links Business Architectures to traditional IT Architectures (Application & Infrastructure)

A robust

approach to

service

orientation

leverages

services at the

Process,

Application, &

Infrastructure

tiers

3D Blueprinting provides methods and frameworks to structure “services” at the Business Process layer, Application Layer, and Infrastructure layer, providing a robust

and “aligned” SOA implementation across an implementation

Co

ns

um

er

Pro

vid

er

Business Process Architecture

Service Architecture

Component Architecture

Business

Technology

3D Blueprinting and SOA

Page 26: Page 1 Architectural Flexibility - Distributed and Centralized.

Page 29