차의중 ([email protected]) ibm websphere field technical sales … · 2005-10-28 · websphere...

®

IBM Software Group

© 2005 IBM Corporation

WebSphere Extended Deployment v6.0

차의중 ([email protected])IBM WebSphere Field Technical Sales Support2005. 9. 13

IBM Software Group | WebSphere software

2

52

69

77

41

47

55

정보자산의보호, 데이터의통합및무결성보장

신뢰성및가용성향상

비즈니스정보의안전한교환

자원의활용도향상

시스템구조및운영방식의복잡성감소

자원의모니터링및운영의단순화

Infr

astr

uctu

re M

anag

emen

t

문제의발견, 방지, 진단, 해결의고속화

자원의실시간배치및자동화된최적화

Source: IBM Corporate Market Intelligence

28

27

Infrastructure Management 에대한기업들의요구

% of respondents rating high

비용절감, 서비스수준의향상, 비즈니스환경의변화에빠르게대처


3

WebSphere XD의사상

Dynamic OperationsWAS의구동환경가상화목표지향(Goal Directed) 자원운영

High Performance Computing

High End Data Processing

Extended Manageability통합된관리및모니터링환경제공


4

Extended Quality of Service for the WebSphere Platform

WebSphere Application ServerNetwork Deployment (WAS ND)

WAS for z/OS

WebSphere Application ServerNetwork Deployment (WAS ND)

WAS for z/OS

WebSphere Platform Productsi.e., WBI, WebSphere Portal, etc.WebSphere Platform Productsi.e., WBI, WebSphere Portal, etc.

ISV ApplicationsISV Applications

• WAS의 add-on 으로설치되며, WAS의관리환경과통합(Admin console에관련메뉴가추가됨)

WebSphere Extended DeploymentWebSphere Extended Deployment

WebSphere XD extends the WebSphere Platform


5

Mixed Version Support

A WebSphere XD Version 6.0 cell can contain

WebSphere XD Version 6.0 nodes

WebSphere Application Server Version 6.0 nodes

WebSphere Application Server Version 5.1 nodes

A WebSphere XD Version 6.0 cell can not contain

WebSphere XD Version 5.1 nodes


6

Platform Support

Supported Platforms

AIX

HP-UX (32-bit, 64-bit)

Linux Intel (32-bit, 64-bit)

Linux on zSeries

Microsoft Windows (32-bit, 64-bit)

Solaris


7

WS XD’s functions

Dynamic Operations

High performance computing

ObjectGrid

Business Grid

Application Versioning

Scale Out

Visualization

®

IBM Software Group


WebSphere Extended Deployment Version 6.0

Dynamic Operation


9

기존환경

100%

0%50

%

15%Utilized Servers

Account Management

100%

0%50

%

20%Utilized Servers

StockTrading

100%

0%50

%

10%Utilized Servers

PortfolioForecasting

100%

0%50

%

55%Utilized Servers

100%

0%50

%

75%Utilized Servers

100%

0%50

%

100%Utilized Servers

100%

0%50

%

100%Utilized Servers

Challenges클러스터간자원공유불가 => 자원활용률저조

관리자에의한자원관리=>관리가복잡하며실시간대응이어려움


10

Account Management

StockTrading

RESOUCE POOL

CustomerSupport

RiskManagement

100%

0%50

%

55%Utilized Servers

PortfolioForecasting

XD’s Dynamic Operation

가상화(Virtualization)서버풀링

동적클러스터링

자동화

어플리케이션별로서비스정책(서비스목표치및중요도) 할당

Autonomic Manager가서비스정책및부하상황에따라서버자원할당

결과

자원활용도증가

QoS향상TCO 절감


11

XD’s Autonomic Management

Node 1

Node 3

Node 2

Node 4

A

Scheduling andFlow Control

Routing andLoad BalancingClassification

Business PoliciesAnd Performance Goals

CPUMeasurements

B

B

A B

A

C

C

C

Flow ControlAuto-Manager

WLMAuto-Manager

ApplicationProvisioning

Auto-Manager

On demand Router

WebSphere Resource Pool

B

C


12




CPUMeasurements

B

B

A B

A

C

C

C

Node 1

Node 3

Node 2

Node 4


On demand Router



WLMAuto-Manager


Auto-Manager

A

B

C


13




CPUMeasurements

B

B

A B

A

C

C

C

Node 1

Node 3

Node 2

Node 4


On demand Router



WLMAuto-Manager


Auto-Manager

A

B

C


14




CPUMeasurements

B

B

A B

A

C

C

C

A

Node 1

Node 3

Node 2

Node 4


On demand Router



WLMAuto-Manager


Auto-Manager

A

B

C


15




CPUMeasurements

B

B

A B

A

C

C

C

A

Node 1

Node 3

Node 2

Node 4


On demand Router

A

LandingZone



WLMAuto-Manager


Auto-Manager

A

B

C


16

Service PoliciesDrive the decisions of the On-Demand Router

A service policy is a grouping for work which has similar performance goals and business requirements

Has Transaction Classes as members which then define which requests should be processed using the given performance goals


17

서비스정책설정Types of goals:

Average Response Time (e.g. 2 seconds)Percentile Average Response Time (e.g. 80% at 2 seconds)Discretionary (best effort)Queue time (e.g. 2 seconds)

Importance Levels 7 levelsHighest to LowUsed in times of contention

Transaction ClassesUse to map Service Policies to applications


18

Work Classes (WC) 설정WC = 공통적인서비스정책에연결되는 URI 들의집합

Example: /stock/trade/* -> Platinum Tran. Class (Work Class Trade)/stock/quote/* -> Bronze Tran. Class (Work Class Quote)/AccountManagement/* ->Gold Tran (Work Clas AcctMgmt)

하나의WC는조건에따라하나이상의서비스정책에매핑될수있다.

IP, User, Group, Cookie

®

IBM Software Group



High Performance Computing


20

WebSphere Servers

Database

기존환경

Transaction requests are spread evenly

across servers All servers require real-time shared database

access

Challenges:DB에서의병목 => 확장성제한성능향상을위한 DB재구성필요=> 관련시스템의재구성을유발

Database eventually becomes a bottleneck


21

XD’s High Performance Computing

High End Data CachingDB의데이터를WAS에캐싱DB의병목현상제거

Dynamic Data partitioningDB의데이터를분할하여캐싱2GB 이상의대용량데이터캐싱가능

Results선형적인확장성

지속적인고성능

WebSphere Servers

Database

High performance, availability and scalability

®

IBM Software Group



Object Grid

IBM Software Group

WebSphere Extended Deployment V6.0 | Sales Technical Enablement Workshop © 2005 IBM Corporation23

Overview

자바 객체들을 저장하기 위한 분산 캐싱 프레임웍

An Object Grid = key/value 쌍을 저장하는 Map 들의 집합.

It has the following qualities of service:

Securable

Fault tolerance through replication

Shareable between different application clients

대량의 Dataset을 담은 자바 객체를 여러 JVM에 분산 저장

Transactional (1 Phase Commit )


24

Object Level integration of data

ObjectGrid

DB MessageFeed Backend

J2SE 1.4App A

J2EE 1.4App B

WASApp C

OfficeApplication

데이터베이스 등의 영구 저장소와 연동 가능

다양한 컴포넌트에 의해 접근 가능

POJOs, SDOs, JDBC, CMP EJBs, HTTP Session 등...

IBM Software Group


Runtime environment

WS XD v6.0 에서 제공하지만, J2EE Container 뿐만 아니라 J2SE JVM 위에서도 실행 가능

1개 jar 파일로써, classpath 에 이 jar를 추가하고 XML 파일을 설정하면 됨.

ObjectGrid clients can run on:

WebSphere 5.1 or higher

J2SE 1.4

J2SE 1.5

.Net using JuggerNet from CodeMesh (JuggerNet = Java APP와 .NET Application 을 연동시켜주는제품)

®

IBM Software Group



Business Grid

IBM Software Group


Long-running work

1개 요청에 대한 실행 시간이 긴 어플리케이션<->OLTP

Time-sensitive 한 프로토콜이나 이나 프로그래밍 모델은 사용 불가

요청의 영속성(persistence) 필요

관리자는 단위 작업의 실행 상태를 모니터링 할 수 있어야 함.

일반적으로, 별도의 실행 환경이 필요

Long-running work = Batch / CI


28

BatchJob.ear

JobStateless Session BeanTools Generated

Job StepEntity Beanaka "Batch Bean "Customer WrittenTools Wrapped

Second Job Step"Batch Bean "

Long running workload : Batch

record-processing model

컨테이너는 transaction, checkpoint/restart mechanism 등을 제공

어플리케이션은 1개 레코드를 처리하는 로직을 제공


29

CPU를 많이 사용하는 작업컨테이너는 실행 환경을 제공, 나머지는 대부분 어플리케이션에 의해 제공

Long running workload : Computing Intensive


30

Computational Grid - Long Running Workloads

Computational Grid for Long-Running Workloads

Long Running Work <-> OLTP일반적으로, 별도의실행환경이필요

응답시간감소를위해병렬작업환경제공

일시적또는이벤트기반스케쥴링가능


31

Transactional Grid – OLTP workloadsComputational Grid – LR Workloads

WebSphere XD Combines LR and OLTP NodesLong Running Work <-> OLTP

일반적으로, 별도의실행환경이필요


32

Long running work 와 OLTP 워크로드사이에서공유되는자원들을필요에따라적절히배분

Autonomics manager는요청을분석하고 Long running work 일경우, 수행에적당한 Capacity의노드가남아있는지를확인Application placement manager는선택된노드에서어플리케이션실행수행상황은관리콘솔에서통합모니터링

WebSphere Business Grid

®

IBM Software Group



Application Versioning


34

Application Versioning/Continuous Availability

어플리케이션의 갱신 시 변경 사항을 지속적으로추적, 저장 – 다수 버전 보관 가능관리콘솔에서의조작만으로이전버전으로복구가능

갱신과복구는운영도중, 서비스중단없이수행(Rollout)

Group RolloutAtomic Rollout (Divide & Switch)

Validation mode동일어플리케이션의서로다른버전이동시수행

관리자가지정한규칙에따라필요버전으로라우팅

Ex) 특정테스터나지점들만을새로운버전으로라우팅

IBM Software Group

IBM Confidential | WebSphere Extended Deployment V6.0 © 2005 IBM Corporation35

quiesce & stop

Rollout

Edition 1.0

Edition 1.0

Edition 1.0

On-demand routers

Dynamic cluster

Edition 2.0

restartapplication

requests

Group Rollout : 하나 이상의 서버를 선택하여 명시적으로 Rollout 명령을 내림

IBM Software Group


quiesce & stop

Atomic Rollout

Edition 1.0

Edition 1.0

Edition 1.0

On-demand routers

Dynamic cluster

Edition 1.0

application

requests

Edition 2.0

Edition 2.0

quiesce & stop

Edition 2.0

Edition 2.0request

request

request

restart

restart

IBM Software Group


Validation Mode – 라우팅 규칙 설정

IBM Software Group


Validation Mode

Edition 1.0

On-demand routers

Dynamic cluster‘DC1’

Edition 2.0

Dynamic cluster‘DC1-Validation’

clone

Routing rules

Legend:

Edition 1.0 Requests

Edition 2.0 Requests

®

IBM Software Group



Deployment Manager Failover

IBM Software Group


Functional Objectives

Provide a highly available (HA) deployment manager function.

Continuity of administrative services if deployment manager fails

Important for automated administration of robust, non-stop computing environments

Provide configuration repository checkpoint/restore function.

Improved preparedness for disaster recovery

Undo-capability to unwind the last ‘n’ configuration updates

IBM Software Group


On-Demand Routers

SAN FS• wsadmin

• scripting

• admin client

administrativeconsole

activedmgr

standbydmgr

HA Deployment Manager

“Hot-standby Model”

IBM Software Group


Highly Available Deployment Manager

SAN FS• wsadmin

• scripting

• admin client


Standbydmgr

Standbydmgr

On-Demand Routers

Activedmgr

Take-over after primary failure…

IBM Software Group


Repository Checkpoint/Restore

WAS의 구성 정보 변경 시 변경 내용을 추적, 저장

Checkpoint = 변경된 내용들의 복사본

다수의 Checkpoint 저장 가능

Full Configuration 백업도 가능

필요 시 변경 이전의 상태로 복구 가능

Checkpoint에는 변경 내용들만 저장되므로 원하는 Checkpoint까지 역순으로 복구

IBM Software Group


HA Deployment Manager Console Support

System Administration > Deployment manager

IBM Software Group


masterrepository


dmgr

checkpointrepository

• wsadmin

• scripting

• admin client

configurationchanges

auto

mat

ic(d

elta

) che

ckpo

ints

full

chec

kpoi

nts

administrativedirective

Repository Checkpoint/Restore

IBM Software Group


Repository Checkpoint/Restore Console Support

System Administration > Extended Repository Service

IBM Software Group


Repository Checkpoint/Restore Console Support…

System Administration > Extended Repository Service > Repository Checkpoints

IBM Software Group


Repository Checkpoint/Restore Console Support…

System Administration > Extended Repository Service > Repository Checkpoints > Delta-2004067110839

®

IBM Software Group



Scale-out


50

Scale Out (From XD v6.0.1)

WAS의 QoS보장기능을WAS 이외의어플리케이션서버에도적용Dynamic Operation - ODR, 정책기반WLMObject Grid새로운서버의추가, 설정이용이어플리케이션서버의관리와 QoS관리 (WLM, HA, session mgmt, etc.)를분리


51

Scale Out Topology

®

IBM Software Group



Visualization


53

Runtime Topology다음과같은것들을보여줌

어디에서무엇이실행되는가

무엇이실행준비상태에있는가

CPU 사용량

세가지뷰포인트제공 (선택적)어플리케이션관점

노드그룹관점

서비스정책관점

“Quick Glance” Hover-overs마우스포인터가위치한컴포넌트의간략한정보를표시

Example - Server Instance: PID, dWLM Weight, Node Name

HA Managed Item Running LocationsHealth Management ControllerApplication Placement ControllerdWLM Controller


54

TreeMap전체환경의실행상태에대한요약화면

전체시스템상태를한번에파악

각사각형의크기와색깔은특별한의미를가짐

크기 : 동시트랜잭션수색깔 : 서비스상태

Ex)빨간색 : 이상발생

필터링을통해특정서버,클러스터,노드그룹만을표시가능

필터링조건 : 이름, 응답시간, 동시요청수등

“Quick Glance” Hover-over 제공

팝업메뉴를통해필요한관리화면으로이동


55

Custom Charting서버,클러스터,어플리케이션등의실행상태모니터링

다양한조건의조합에의해차트내용선택가능 :

서버, 클러스터, 노드그룹, 서비스정책, 어플리케이션, 트랜잭션그룹등평균응답시간, 동시요청수, 평균큐잉시간, 스루풋(TPS/TPM) 등

하나의차트내에서서로다른데이터조합을비교가능

Ex)어플리케이션의응답시간과서비스정책을한화면에서표시=>목표만족여부관찰

Multi-chart layering동시에여러차트 Open 가능

차의중 ([email protected]) ibm websphere field technical sales … · 2005-10-28 · websphere...

Documents