ibm systems and technology group ibm confidential presentation subtitle: 20pt arial regular, teal...

IBM Systems and Technology Group

IBM Confidential © 2005 IBM Corporation

Resource Dependency Service& Resource Modeling

Derik Pereira, Thomas Harrer, Yann GuerinIBM Solutions, Systems Architect & SpecialistsMark Cathcart, Distinguished Engineer, as Advisor

Page A

Template release: Oct 02

© 2005 IBM CorporationVE V2R1 RDS/RM T3 Education IBM Confidential

VE

Co

nso

le

Dire

ctor M

ulti-p

latfo

rm

eW

LM

Re

sou

rce D

ep

en

de

ncy

Se

rvice

Protecting information assets, confidentiality and data integrity

Infrastructure reliability & availability to support business ops

Maximizing utilization of existing computing resources

Consolidating computing resources to reduce complexity of ops

Simplifying monitoring and management of IT infrastructure

Enabling infrastructure to anticipate, prevent, diagnose and fix problems

Automatically deploying and optimizing IT resources real-time

Virtualization Engine - Value Matrix

Page B



RDS Methodology

Persistent Datastore

• Discover & mine data from disparate sources, including existing customer repositories

• Create a common representation of resources based on ODOE models

• Format information for RDS data store

• Correlate between representations of the same asset across different data sources

• Analyze, determine and represent relationships

• Populate resource model registries with discovered resources, relationships, and instrumentation

• Provide WS-RF compliant access to topologies via Topology Service

• Allow for customer input / update of topology

Web based presentation / Update client

Programmatic Consumers:

• On Demand Operating Environment

• User queries

• Etc, etcWeb services

Dis

cove

r

eWLM

Other Discovery mechanism

Tivoli

TBSM

TAM

DB2 udb,z,i

Director CICS

WAS

OS Specific

Vendor

Interfaces

ManageableResource

Web ServiceImplementation

Resource Model (WSDL)

Page C



Virtual Resources

Virtual management

Workload & performance managers Resource management, modeling, mapping

Vir

tual

pla

nn

ing

to

ols

Resource virtualizers

IBM Server & Storage Systems

Virtual management

Virtual access

Virtual resources

Virtual access

Virtual viewProgrammatic Interface

Resource Dependency Service positioning

Page D


IBM Confidential © 2005 IBM Corporation

Resource Dependency Service& Resource Modeling

Derik Pereira, Thomas Harrer, Yann GuerinIBM Solutions, Systems Architect & SpecialistsMark Cathcart, Distinguished Engineer, as Advisor

Page 1



Agenda continued:

1 RDS and RM Overview

RDS Usage Scenarios3

RDS Installation and Configuration4

RDS and RM Architecture and Design2

IBM’s Strategy in Resource Modeling and VE V2R1 Positioning5

0 Preface: Learning Objectives & Target Audience

Wrap up - information sources and Q&A7

RDS and RM Selling Strategy6

Page 2



Learning Objectives

At the conclusion of this material, you should be able to:

Explain the purpose & functions of the Resource Dependency Service (RDS) including the Resource Modeling (RM) component

Describe the architecture of the RDS and its integration with other VE components

Understand which client pain points are addressed by the RDS and RM

Articulate and justify the client benefit and business value of the RDS

Articulate Resource Modeling landscape, IBM’s strategy in it and the innovation brought by VE V2R1

Use this presentation foil set and web lecture to present to Clients and other IBM people.

Page 3



Target Audience

Aimed at building skills necessary to sell and support the implementation of IBM’s Virtualization Engine, with particular emphasis on the function and capabilities of the Resource Dependency Service.

Target audience is professionals in the following types of job roles: Systems Group Systems Architects (SA)

Systems Group Field Technical Sales Support (FTSS)

Systems Group Advanced Technical Support (ATS)

Systems Group TechLine

IGS technical professionals involved in planning, installing and configuring Systems Group’s products & solutions

Non-IBM personnel with similar job roles & responsibilities (e.g., Business Partners)

Page 4



Agenda continued:









Page 5



Which Clients should develop a Strategy for Virtual Resource Management?

Companies who leverage IT to achieve competitive advantage

Who develop a service oriented architecture (SOA) for their business applications

Who invest in a standardized, simplified, virtualized IT infrastructure

Who plan the layout of data centers anticipatory

IT service providers who need to differentiate themselves from competitiors

Who need highly efficienct and effective operations

Who are highly innovative

Page 6



Some specific Challenges for IT Service Providers?

Increasing effort for operating IT instead of using IT to innovate the business High complexity of IT infrastructure

Many manual task involved in order to provision resources for new IT applications

Too many different management tools involved in managing IT

Challenges from virtualization Large number of virtual resources

Dynamic changing resources

Difficult to perform budgeting, accounting and charging

No sub capacity Software Licenses for virtualized environment

Page 7



Resource Dependency Service (RDS) in a nutshell Automatic Discovery of IBM and

non-IBM resources

Identifies dependencies and relationships

Generates WS-RF compliant resource model

Graphical display of topology via VE Console

Customer may

logically group resources to reflect business objectives.

View resource properties & status

Zoom, pan, etc.

Customer can view relationships to discover side effects of problem resources or operator actions

Page 8



RDS discovers resources and their relationships

Understand the side effects associated of a change in a resource’s status.

iSeries

zSeries

WAS

DB2

TBSM

TCM

And more…

Correlate

Resource Modeling Framework

Topology web services

IDD

Network

Scanner

User can group into business process

Resource-Specific

Data Collectors VE Console

Page 9



An IBM ZRL developed tool used to discover and capture all IP network attached devices

Non-intrusive. No modifications to device discovered

No software agents or special User/Admin rights required

Network directed packets and “smart pings”

Network device discovery includes

PC’s

Intel and Unix Servers

LAN Printers

Network Devices (routers, hubs, etc…)

Intelligent Device Discovery (IDD) Tool

Page 10



Data Collectors discover and collect information from existing customer applications and repositories, databases and domain managers

Connect with the existing remote target through JDBC, JMX, and ODBC

Targets can be:

Repositories

Applications

domain managers (EWLM)

specific platform / OS implementations

Discover, acquire data specific to RDS

Analyze, transform, correlate the data into RDS resource model

Store appropriate information in the RDS datastore (repository)

RDS Data Collectors and Parsers

Configuration &Change Management Software Configuration

"Desired State"

Inventory Base"Actual State"

LDAP Tables

InventoryPeripherals

RelationshipRegistry

Application ServicesData

BusinessSystems

Events

HealthMonitors

NetworkTopology

PersonCredentials

RolesData Source Objects

Configuration SettingsSoftware ComponentsVersion ManagementDependency ManagementPolicy Definitions

Computer SystemSoftware ElementsVersion ManagementInstalled Software

Disk DrivesProcessorsMemory

Event InstancesExtended Attributes

StorageDevices

Operations, tasks,Mapping to "plug-ins"Endpoint ManagementMapping of plug-ins,protocols, and applicationcontext.

Business System HierarchyGroups of ResourcesMapping to Resource details

Resource IdentityStatistics/MeasurementsTime-based data

"Product Knowledge Base"

Configuration &Change Management Software Configuration

"Desired State"

Inventory Base"Actual State"

LDAP Tables

InventoryPeripherals

RelationshipRegistry

Application ServicesData

BusinessSystems

Events

HealthMonitors

NetworkTopology

PersonCredentials

RolesData Source Objects

Configuration SettingsSoftware ComponentsVersion ManagementDependency ManagementPolicy Definitions

Computer SystemSoftware ElementsVersion ManagementInstalled Software

Disk DrivesProcessorsMemory

Event InstancesExtended Attributes

StorageDevices

Operations, tasks,Mapping to "plug-ins"Endpoint ManagementMapping of plug-ins,protocols, and applicationcontext.

Business System HierarchyGroups of ResourcesMapping to Resource details

Resource IdentityStatistics/MeasurementsTime-based data

"Product Knowledge Base"

Page 11



RDS Data Sources and Application EnvironmentsWhat RDS Scans… and How

eWLM Incorporate information derived from ARM instrumented components

WebSphere Application Server and MQ

Mine metadata about WAS and WAS MQ applications and associated data stores

DB2 for zSeries, Distributed (UDB), and iSeries

Mine metadata about database instances, and associated volumes

IBM Director Incorporate physical topology information found in Director inventories

CICS Mine metadata about applications, programs, transactions and associated data stores – leverages CPSM interfaces

Tivoli TBSM and TAM Incorporate business function, server, and storage information from TBSM and TAM repositories

OS Specific and other discovery mechanisms

Mine OS services as required to fill gaps, and employ new discovery mechanisms for baseline discovery of IT infrastructure

Page 12



Discovered and Collected Resource TypesWhat RDS Finds…

Applications Runs within a hosting container or an operating system instance.

Data Containers Collections of files and attributes associated with those files.

Database Instances A collection of interrelated or independent data items stored together to serve one or more applications.

Hosting Containers Programs or applications that host other applications (e.g., WAS).

Network Devices Routers and load balancers that help manage network traffic.

Network Interfaces Interface between a system and an external high-speed network.

Network Subnets Interconnected, but independent segment of an entire network

Operating Systems A collection of system programs that control the overall operation of a computer system.

Services A process or sub-process used to automate common tasks such as verifying security credentials or calibrating system clocks.

Storage Volumes Represents a medium used for storage of data on a computer.

Systems Represents physical computers or virtual computers, such as logical or physical partitions.

Page 13



Resource Topology view with VE Console

VE Console Resource Dependency Service 2.1 with Resource models

Graphical resource topology:

Manages the discovery engine within RDS.

The discovery of resources ultimately populates the resources and relationships shown in the topology view.

Understand the side effects associated with a change in a resource’s status

Page 14



VE V2R1 Topology View

Page 15



VE V2R1 Topology View

Page 16



Resource Modeling Framework in VE V2R1

In the heart of IBM’s strategy for standard-based resource modeling

Define Web Service Interfaces for Manageable Resources and Resource Management Functions in a standard and interoperable way.

Resource Modeling Framework is introduced in VE V2R1

Used under the cover to interface RDS discovered resource database to VE Console Topology view for Managed Resources

Not externalized in VE V2R1 for direct customer or ISV exploitation

Resource Modeling Framework is an implementation of a set of Web Services related specifications on top of a WebSphere 6.0 base

Page 17



Agenda continued:









Page 18



ArchitectureCustomer IT Environment Clients

Virtualization Engine Management Server

RDS Server

UI User

Customer Networks

IBM eServer xSeries

Linux

ODI:RM Framework

Websphere Application Server

ISC/VEC

Virtualization Engine Based Runtime

DB2

Resource Dependency Services

RDS Database

Analytics Engine

IDD Scanners,

Probes

Discovery Web

Services

ODI:RM - based

Resources

Data Collectors::

1. EWLM2. z/OS 3. Director4. DB25. UDB6. WAS7. TBSM8. TAM9. DCM10. ...

Programmatic Callers:

1. On-demand2. BR3. Tivoli4. Vendors5. EWLM6. Provisioning

Java

IDDDatabase

IDD Parser

1. Existing Repositories2. Application Environments3. DB2 Instances4. Domain Managers5. Instrumentation

Topology Service Web

ServicesCorrelation Engine

VE Console

Admin/Config User

Database Web

Services

FederatedDatabase

Federated Database

Federated Database

Page 19



Resource Model

ResMapNetworkSubnet

ResMapNetworkDevice

OS Container

ResMapHostingContainer

ResMapDatabaseInstance

OperatingSystem

ApplicationNetworkInterfaceResMap

DataContainerStorageVolume

hosts

uses uses

hosts

hosts hostshosts

federates hosts

federates

hosts

hosts

installedOS

hosts

hosts

hosts

uses

uses

uses

uses

uses

uses

uses

uses

hosts

Service

hosts

federates

federates

uses

uses

hosts (IMS)

Page 20



Resource Modeling Framework Design

Uses standard web services patterns as prescribed by WebSphere development tools

Web Services interface is provided via a Stateless Session EJB.

EJB Entity beans are used to store ‘state’, backed by DB2, a DB2 database and a set of DB2 tables.

Packaged as deployable applications to WebSphere in the form of Enterprise Archives (EARs).

RM Applications are J2EE applications that consist of: Implementation jar files. Web Archive (WAR) files that provide the web services interface. Deployment Descriptors that describe the application to the

WebSphere runtime. All packaged in a zip file called an Enterprise Archive, or EAR and

deployed to WebSphere

Page 21



Agenda continued:









Page 22



1. Bring up the VE Console, select RDS, and go to IDD administration

2. Populate the RDS database using the data collectors, federation, and Web Services Select which ranges of TCP/IP addresses you want to scan (and which to exclude) Use of IDD or tapping into an existing store such as TBSM, TAM, or IBM Director is an

easy way to get a base set of resources If IDD finds resources that it can auto-configure data collectors for, it will immediately

start those data collectors (iSeries server, zSeries server, WAS, DB/2) Schedule collectors for endpoints that may not have been collected by another

collection product Use Federation to map existing data stores into the RMS data model

3. Configure data collectors to run on a schedule – keeping the RDS database in synch with endpoints

4. Launch Resource Topology View: Left Menu bar - Virtualization Engine Console -> Hardware and Software -> Resource

Topology

5. Choose Managed Resources View

6. Use the VE Console Topology UI to define additional relationships over resources

7. Use topology and query capabilities for resource/business process analysis

Basic RDS Usage Scenario

Page 23



Resource Topology Introduction

Component of the Virtualization Engine Console

Graphical topology viewer.

Two distinct data sources:

Virtualization Engine Environment

Managed Resources discovered by Resource Dependency Services

For managed resources data source, the following operations are available:

Creating/deleting resources Creating/deleting relationships Editing resource properties Creating logical groups of resources Launching the RDS Admin and Configuration GUI for fine tuning RDS

Page 24



Resource Topology Introduction — Launching

Located at Virtualization Engine Console -> Hardware and Software -> Resource Topology

Page 25



Managed Resources Home Page

The Managed Resources “home” topology contains icons representing all of the managed resource types that RDS can discover.

Page 26



Sample RDS Usage Scenario: Using the topology viewer to determine the impact of a lost resource

RDS collects information that clients can use to determine the impact of lost resources.

Task 1:

View the servers and network devices and their relationships through the resource topology viewer.

Task 2:

Evaluate the managed resources to determine possible bottlenecks or device failures

Task 3:

Determine if the bottleneck can be corrected by rerouting network traffic, repairing or replacing network devices, installing new network devices.

Task 4:

Determine the impact to the network if the network device is taken down to be repaired or replaced.

Page 27



Agenda continued:









Page 28



Installation of RDS

RDS only runs on Linux SLES 9 or RHEL 4 ! (x,i,p, & z Linux)

VE Installable Unit

Integrated install covers the installation of all dependent products/componentsWebSphere Application Server using VE Management Server

ProfileDB/2 8.2Tivoli Directory ServerVE ConsoleJREResource Virtualization Service (Resource Modeling)RDS Server

Now1 -

Page 29



Configuration of RDS – IDD

Page 30



Optional Windows Server component

Better discovery of resources on Windows servers can be achieved by installing the IDD Windows server

After installation, sign into RDS Administration portlet, and navigate to IDD configuration

Choose the option to install the IDD Windows server component onto that server

Configure it to point to the appropriate RDS server

Page 31



Configuration of RDS – Data Collectors

Page 32



Configuration of RDS – Data Collectors

Page 33



Configure Logging and Tracing

RDS Administration links to RDS server WebSphere Administration Console

Logging and tracing all configured through the WebSphere Administration console

Configurable per RDS component

Can specify log/trace level

Can specify which file to use for trace output

Resource Modeling Logging is enabled using the standard WebSphere logging mechanisms

Resource Modeling uses java package names as the component logging string

Logs wind up in the location specified on the WebSphere Diagnostic Trace Service Configuration page.

Page 34



Security Details Security can not be changed by the customer (in VE V2R1)

The Secure* environment is created when the VEMS WebSphere profile is created.

LTPA Tokens and Username/Password are the supported and configured authentication mechanisms.LTPA keys will be imported from the GCR for a given “VE Deployment” at install time.Changes to the keys post installation, will require the user to regenerate, publish to LDAP and require each application server profile to re-import using the WebSphere Admin console.

Messages between the exploiting components in the framework are signed and encrypted.

The Certificates used are the default certificates shipped with WebSphere. This can be changed

DB credentials used at install time are configured as J2C Authentication Entries

If these ever change, we will need to use the WAS Admin console locally to update the data source.

Scripts are provided by VE security team to configure WAS security and are left on the file system

Enable Global Security, Enable LTPA as authentication mechanism, Enable LDAP as user registry

The wsadmin userid/pw that is used at install time is saved in the GCR* Refers to activation and implementation of the specified features and does not imply that the environment is secure or similar

Page 35



Agenda continued:









Page 36



Why do we care about open standards ?

Customers Freedom of choice Exploit existing assets Construct / integrate solution from multiple providers

IBM Ensure our products can interoperate with

offerings from other vendors. Focus on our strengths and assets Lead the industry and innovate

Other companies Other IT providers are participating broadly Web services is the leadership “space” Lots of competiting proposals

Page 37



On demand Operating Environment ArchitectureB

US

INE

SS

US

ER

Enterprise Service Bus

BusinessServices

Infrastructure Services

Business Performance Management

Application Services

Business Process Choreography Services

User Interaction Services

InformationManagement

Services

Resource Virtualization Services

Service Level Automation and Orchestration

Utility Business Service

The On Demand Operating Environment is based upon the concept of a Service Oriented Architecture (SOA). Each element of the architecture is a service that together implement the Operating Environment capabilities.

Page 38



XML

Non-Web Services Web Services

Web Services Profiles

ODOE

Enterprise Service Bus

Resource Virtualization Services

Business Function Services

Business Process Services

Common Services

UserAccess

Services

Service Level Automation and Orchestration

User Interaction Services

InformationManagement

Services

Application Services

Busin

ess

Servi

ces


BUSINESS

Utility Business Services

Non XML

BPM

Web Services Base Protocol

Web Services Description

Common Web Services

Web Services

Policies

SOA Pla

tform

Technolo

gy Pla

tform

USER

J2EE

Legacy

ODI-RM

Pla

tform

On Demand Operating Environment Standards

DMTF-CIMWSDM Mngmt Of WSWSDM Mngmt Using WSWSDM CBE

Key: IBM Spec SDO spec STANDARD

WS-SecurityPolicyXACMLWS-Agreement

SOAP 1.1 & SOAP 1.2MTOM and XOPSOAP with Attachments

WS-I Basic Profile 1.0 & 1.1WS-I Attachments Profile 1.0WS-I Simple SOAP Binding Profile 1.0WS-I Basic Security Profile 1.0

XML 1.0 & XML 1.1Namespaces 1.0 & 1.1XML Schema 1.0 & 1.1XML C14NXSL 1.0

OGSA

UDDI 1.0 & UDDI 2.0WS-ServiceGroupWS-CoordinationWS-MetadataExchangeWS-NotificationWS-AtomicTransactionWS-Business ActivityWS-Resource Lifetime

WSDL 1.1 & WSDL 2.0WS-BaseFaultsWS-AddressingWS-PolicyBPEL4WSWS-Security 1.0WS-SecureConversationWS-TrustWS-FederationSAML 1.0 & SAML 2.0WS-ReliableMessagingWS-Resource Properties

J2EE 1.4JSR-3 (JMX)JSR-77

Page 39



What is WS-Resource Framework (WS-RF)

WS-B

ase

Faults

WS-RenewableReferences

WS

-Res

ou

rce

Pro

pe

rtie

s

Modeling Stateful Resources with Web

Services

Publish-Subscribe Notification for

Web services

WS-Service

Groups

WS-T

opics

WS-BaseNotification

WS

-Res

ou

rceL

ifetim

e

WS-Brokered

Notification WSRF is an evolution of OGSI (Open Grid Services Infrastructure).

WSRF assumes stateful resources addressed using WS-Addressing EPR.

WSRF assumes WSDL 1.1 and exploits copy-n-paste interface aggregation.

WSRF defines and standardizes. WS-ResourceProperties

Defines mechanism for describing and exposing state of a resources as properties expressed using XML and XML schema.

Defines operations to read and query the state of the resource.

WS-ResourceLifetime Defines operations for explicit and

scheduled resource destruction. WS-ServiceGroups

Defines grouping and registration semantics for WSRF Web Services.

Used for resource discovery in a SOA. WS-BaseFaults

Defines base fault XML Schema and rules for its use.

Page 40



The Anatomy of a Manageable Resource

Manageable

Resource

Web ServiceImplementation

NativeResource

Instrumentation

Resource Model (WSDL)

proprietarycommunication

ExternalWeb Services

Interface

InternalImplementation

From the perspective of the client, the manageable resource is a single encapsulated instance exposed through the external web services interface.

Internal implementation provides mapping and federation of resource state, management operations, events and relationships.

Existing resource implementations are extended and adapted to allow the integration with the On Demand management infrastructure.

Investment protection - reuse of the existing management systems and infrastructures.

Isolation from Implementation

Page 41



Standardization of the Layers of a Manageable Resource

ResourcesResources

Resources

Mapping of CIM data model to XML (WS-CIM)

Management using Web Services (WSDM MUWS)

WS-ResourceFramework (WSRF)WS-Notification (WS-N)WS-RelationshipsWS-AddressingWS-Security…..

Management Domain Interfaces

ResourceInstrumentation

Manageable ResourceInterface (WSDL)

Common Manageability

Web ServicesComponents

ManagementApplications

XML Complex Type

Overall Composed Manageability InterfaceResource

SpecificManageability

Common Manageability

Web ServicesPlatform

2005

ODI:RM TierUsing Web Services for Management

2006

VE V2

WSDM MUWS (WSDM-CIM mappings)

Future

Page 42



Standards Body Cooperation OASIS

WSRF and WS-Notification

WS-Security, etc.

WSDM

DMTF

Utility Computing

CIM

Server management

W3C

WS-Addressing

XML/SOAP/WSDL and others

Page 43



Context Services Info

Services

InfraServices

SecurityServices

Rsrc Mgmt Services

Execution Mgmt

Services

DataServices

PolicyMgmt

VOMgmt

Access

Integration

Provisioning

Cataloging

BoundaryTraversal

Integrity

Authorization

Authentication

WSRF WSN WSDM

EventMgmt

Trouble-shooting

Discovery

JobMgmt

Logging

ExecutionPlanning

WorkflowMgmt

WorkloadMgmt

Provisioning

ApplicationMgmt

DeploymentConfigurationReservation

Naming

Self MgmtServices

HeterogeneityMgmt

Service LevelAttainment

QoSMgmt

Optimization

Information Services


SelfMgmtServicesSecurity

Services

Resource Mgmt Services

Execution Mgmt Services

DataServices

Context Services

Open Grid Services Architecture (OGSA)

Page 44



Open Standards & Implementations Are Moving Forward

alphaW rks– Websphere Emerging Technology Toolkit (ETTK)Permits early implementation of WS-RF / Notification using Websphere hosting

– Small-footprint prototype of WS-RF / Notification implementation in a portable device (Blackberry)Demonstrates the scalabilty and ease of implementation of WS-RF / Notification

Websphere– Implementation of WS-RF / Notfication in next full release of WebsphereIntegrated with Websphere programming models & development tools

Apache– Open source project implementation as part of Apache/Axis

Open source implementation of WS-RF / Notification in open-source / lightweight hosting environment

WS-RF/Notification

– Cooperation between Web Services Standards bodiesMOU on cooperation around Web Service Management

Open Grid Service Architecture– OGSA has become the “flagship” architecture of the Global Grid Forum

– OGSA “Profiles” are being specified which relate OGSA to other web services specificationsWS-RF/N, WS-Security, WS-I, WS-Addressing etc.

– Higher level concrete specification are being developed for important Grid functionsBasic Execution Services, Data Services, etc.

– IBM Particpating in new GGF Board of Directors, Working Group / Technical Committee chairs in GGF and OASIS.

IBM Leadership

Page 45



Agenda continued:









Page 46



How does RDS solve the Infrastructure Challenges for our clients?

RDS and Topology view are the first concrete step into open standard based resource models

If the client has high effort for documenting existing resources and their dependencies RDS will help reduce the manual

tasks of documenting resources and dependencies

RDS with VE Topology View will provide insights into the relationship between business processes, IT applications and IT resources.

Page 47



Components of an RDS project

Software

VE Console

RDS and underlying Resource Model

Hardware

Management Servers for RDS and VE Console

Services

Architecture and Planning

Proof of concept

Implementation

+ +

An RDS project will probably be part of an VE project

An RDS solution will contain:

Page 48



Concept of a business case

Gains Customer gets a better

understanding of their environment

By viewing dependencies between resources, customer can easily understand the impact of a specific resource failure.

Customer saves the expense of doing physical inventories Inventory can be easily kept

current

Increased Quality of Service

Reduced cost of creating inventories

Effort

Customer has costs for

Hardware of Management Server

Software licenses for RDS and VE Console

Support and Maintenance

Implementation and operation cost

RDS can be set up with minimal configuration

RDS operation will require some administration effort which will be less that the effort to do inventories.

Page 49



Tivoli Support for CCMDB - Discovery and Mapping Tools and the Discovery Library

Discover IT Resources and their Relationships

Visualize how IT supports the business

Discovery Library

CCMDB

Other Apps

Discovery Technologies

IT environment

CCMDB

Page 50



Tivoli CCMDB and Virtualization Engine RDS working together

`

•Portal UI•Process•Federation•Reconciliation•Data Scheme•Topology view•Discovery+•WSDM Resource Models

RDS

CCMDB

•Topology view•Discovery•WSDM Resource models + Broader discovery

RDS makes it easy to see basic relationships among a

client’s IBM systems resources. This capability

can be leveraged by CCMDB (*).

RDS

CCMDB

RDS

Resource Dependency Service

Bootstrapping the infrastructure for SOA IT

management.

CCMDB

Common Configuration Management Database

Setting up the Foundation for ITIL

(*) RDS and Resource Modeling Service interfaces are not externalized and published in V2.1. The only way a customer using CCMDB can take advantage of RDS-discovered resources is by having IBM Lab Services write to the web services using internal documentation

Page 51



Other Discovery Products

There are some products on the market with discovery functionsAs part of a provisioning solution (Veritas OpForce)

As part of a enterprise systems management Solution (Microsoft, IBM)

As standalone products (nLayers, Relicore, InfoVista)Provider Product Internet Address

Veritas OpForce www.veritas.com

nLayers InSight www.nlayers.com

Relicore Clarity www.relicore.com

InfoVista VistaDiscovery www.infovista.com

Microsoft MS Management Server www.microsoft.com

IBM IBM Director www.ibm.com

IBM Tivoli Configuration Management www.ibm.com

Page 52



Key differentiations and importance of covered components in virtualization strategy and roadmap

RDS compared to other discovery and dependency tools Uses a proposed open standard for

its resource model

In the future, the resource model can be leveraged for programmatic access to resources and for standard based management of virtual resources

RDS compared to Configuration Management solutions: With the topology view of VE

console, the actual dependencies of IT resources can be used to simulate changes

Page 53



Sales Engagement for RDS

Notice / Identify Validate

Is the client‘s IT infrastructure complex and heterogeneous with many undocumented dependencies between resources?

Is configuration management already in place?

Is a tool for discovery of resources already in place

Are there problems with change management or with high availability due to unknown dependencies of IT resources?

Decide about solution approach: either

Lead with VE and RDS if client is strategically approaching virtualization and if open standards for the resource model will play an important role in the future.

Lead with Tivoli Configuration Management if client is concerned with configuration management processes for manual changes in the environment.

Qualify

Develop custom demo to client

Develop preliminary solution

Start evaluation / proof of concept

Propose

Create final Solution Blueprint

Describe the value proposition of using RDS within VE

Propose solution to client

Page 54



Packaging/Pricing/Ordering

Packaging

Ordering

Pricing: tbd at announcement

VE Mgt. Servers i5/OS AIXLinux

POWERWindow

Linux

xSeries

Linux

zSeries

Media for Mgt. Svr’s

EWLM AIX + i5/OS + Linux on POWER

Domain Managers Windows + Linux on xSeries

Domain Managers Domain Manager 3 CDs, 3 DVDs

Group 1 agents AIX, i5/OS, Linux, HPUX agents 1 CD

Group 2 agents Solaris + Windows agents 1 CD

RDS Linux on POWER, xSeries, zSeries (Linux only) 1 CD

Directori5/OS Mgt Servers,

Consoles

AIX + Linux on Power Mgt Server, Consoles, Agents

Windows + Linux on xSeries Mgt Server, Consoles, Agents

Linux on zSeries Mgt Server, Consoles

4 CDs

Director AgentsAll Director

AgentsAll Director

Agents

1 CD

Page 55



Summary of Sales topics

What are the low hanging fruits and sweet spots for RDS and the Resource Model?

For Clients with high effort in documenting IT components and their dependencies, RDS could improve the efficiency and quality of gaining information about the resources of the IT infrastructure.

It automates server inventory tasks that are normally full of errors and labor intensive.

It will be a road into an open standard based approach to model resources.

Page 56



Agenda continued:









Page 57



IBM Virtualization Engine ™ is all-encompassing

Virtualized view

Virtualized management

Virtualized resources

Virtual View

Programmatic Interface

Virtual Resource Access

Workload & performance managersResource management, modeling,

mapping

Virtual Resource Management

Virtual Resources

Resource virtualizersPartitioning, virtual machines, I/O,

networks, VTS

IBM Server & Storage Systems

Vir

tual

Pla

nn

ing

To

ols

Page 58



Summary

RDS is designed to discover the resources in your environment, and how they are related.

By viewing dependencies between resources, customer can easily understand the impact of a specific resource failure.

RDS can be set up with minimal configuration

RDS can help keep an up-to-date inventory

Resource Modeling is an implementation of a set of WS-RF related specifications

Resource Modeling is delivered in VE V2R1 under the cover to interface RDS with the VE Console

Page 59



Additional Resources for RDS & RM

RDS in IBM InfocenterURL Available at a later date

IDD Homepage at Zurich Research Labshttps://idd.zurich.ibm.com/idd2/web/index.jsp

Virtualization Engine console (prior to GA)

https://w3.rchland.ibm.com/projects/infocntr/buildpages/v1r2m0f_software.htm

OASIS Specifications:

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrf

WebSphere Infocenter:

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp

Search for ‘Enabling Tracing and Logging’ to find the article that instructs how to build trace strings.

Page 60



Questions

Page 61



Notices

Produced in the United States of America, 08/04, All Rights Reserved

IBM, IBM eServer logo, IBM logo, e-business on demand, DB2, DB2 Connect, DB2 Universal Database, HiperSockets, Enterprise Storage Server, Performance Toolkit for VM, Tivoli, TotalStorage, VM/ESA, WebSphere, z/OS, z/VM and zSeries are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries or both.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Intel is a trademark of Intel Corporation in the United States, other countries or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation

Other company, product and service names may be trademarks or service marks of others.

Page 62



Notices – cont’d

Information concerning non-IBM products was obtained from the suppliers of their products or their published announcements. Questions on the capabilities of the non-IBM products should be addressed with the suppliers.

IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.

IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area.

All statements regarding IBM’s future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios

Page 63



End Of Presentation

Page 64

ibm systems and technology group ibm confidential presentation subtitle: 20pt arial regular, teal...

Documents