IBM Tivoli Intelligent Think Dynamic Orchestra Tor Pre Proof-Of-Concept Cookbook for Business Partners Redp3830

7/31/2019 IBM Tivoli Intelligent Think Dynamic Orchestra Tor Pre Proof-Of-Concept Cookbook for Business Partners Redp3830

1/140

ibm.com/redbooks Redpaper

IBM Tivoli IntelligentThinkDynamic OrchestratorPre Proof-of-Concept Cookbook for Business Partners

Edson Manoel

Tony French

Installation and customization

Data center modeling

Workload simulation

Front cover
http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/


2/140


3/140

IBM Tivoli Intelligent ThinkDynamic OrchestratorPre Proof-of-Concept Cookbook for BusinessPartners

February 2004

International Technical Support Organization


4/140

Copyright International Business Machines Corporation 2004. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP

Schedule Contract with IBM Corp.

First Edition (February 2004)

This edition applies to IBM Tivoli Intelligent ThinkDynamic Orchestrator Version 1.1.0 and IBM

Tivoli Provisioning Manager Version 1.1.0.

Note: Before using this information and the product it supports, read the information inNotices on page vii.


5/140

Copyright IBM Corp. 2004. All rights reserved. iii

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Recommended reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

The team that wrote this Redpaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2. Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.1 Interviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.2 General questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.3 ITITO components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.3.1 Power units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.3.2 Network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.3.3 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3.4 Spare pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.3.5 Applications and customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.3.6 Other devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.3.7 Scoping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 3. Installing the demonstration systems . . . . . . . . . . . . . . . . . . . 253.1 Installation process overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.1.1 Recommended installation directories . . . . . . . . . . . . . . . . . . . . . . . 28

3.1.2 User IDs and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2 Installing and configuring TIOdbsrv - Windows . . . . . . . . . . . . . . . . . . . . . 30

3.2.1 Creating the required user IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.2.2 Installing and configuring Cygwin . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.2.3 Configuring SSH communications . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.2.4 Installing and configuring IBM DB2 UDB V8.1.2 on Windows . . . . . 34

3.2.5 Installing and configuring IBM Directory Server V5.1 . . . . . . . . . . . . 39

3.3 Installing and configuring TIOsrv - Windows . . . . . . . . . . . . . . . . . . . . . . . 45

3.3.1 Creating the required user IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.3.2 Installing and configuring Cygwin . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.3.3 Configuring SSH communications . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.3.4 Installing IBM DB2 Universal Database V8.1.2 Client. . . . . . . . . . . . 48

3.3.5 Installing and configuring IBM Directory V5.1 Client . . . . . . . . . . . . . 50


6/140

iv Pre Proof-of-Concept Cookbook for Business Partners

3.3.6 Installing IBM WebSphere Application Server Base V5.0. . . . . . . . . 52

3.3.7 Install the IBM WebSphere fixpack 1 and required fixes. . . . . . . . . . 55

3.3.8 Installing IBM Tivoli Intelligent ThinkDynamic Orchestrator . . . . . . . 67

Chapter 4. Creating the demonstration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 754.1 Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4.1.1 WordPad or Notepad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4.1.2 Cooktop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4.1.3 XMLSpy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

4.2 Designing the data center model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

4.2.1 ITITO GUI method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

4.2.2 The XML method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

4.2.3 DOCTYPE element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

4.2.4 Power supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824.2.5 Network components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

4.2.6 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

4.2.7 Spare pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

4.2.8 ITITO configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

4.2.9 Customers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

4.3 Sample XML files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

4.3.1 Cookbook example DCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

4.3.2 Redbook example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

4.4 Loading the data center model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934.4.1 Tip for creating XML files using text editors . . . . . . . . . . . . . . . . . . . 94

4.5 Configuring the simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

4.5.1 Data center model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

4.5.2 The tdnetworks file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

4.6 Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 5. Demonstration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

5.1 Introduction to ITITO and the scenario . . . . . . . . . . . . . . . . . . . . . . . . . . 108

5.1.1 ITITO: A quick overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

5.2 Data center assets and resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

5.2.1 Show the switch fabric and inventory resources . . . . . . . . . . . . . . . 110

5.2.2 Show the customer the resource pools. . . . . . . . . . . . . . . . . . . . . . 111

5.3 Customer applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

5.4 Real-time performance monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Appendix A. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

System requirements for downloading the Web material . . . . . . . . . . . . . 120

How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120


7/140

Contents v

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Product manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123


8/140

vi Pre Proof-of-Concept Cookbook for Business Partners


9/140

Copyright IBM Corp. 2004. All rights reserved. vii

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consultyour local IBM representative for information on the products and services currently available in your area.Any reference to an IBM product, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the user'sresponsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document.The furnishing of this document does not give you any license to these patents. You can send license

inquiries, in writing, to:IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisionsare inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDESTHIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimerof express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically madeto the information herein; these changes will be incorporated in new editions of the publication. IBM may

make improvements and/or changes in the product(s) and/or the program(s) described in this publication atany time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirm

the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions onthe capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate themas completely as possible, the examples include the names of individuals, companies, brands, and products.All of these names are fictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrates programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing application

programs conforming to the application programming interface for the operating platform for which thesample programs are written. These examples have not been thoroughly tested under all conditions. IBM,therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment to IBM for the purposes ofdeveloping, using, marketing, or distributing application programs conforming to IBM's applicationprogramming interfaces.


10/140

viii Pre Proof-of-Concept Cookbook for Business Partners

Trademarks

The following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both:

AIXDB2 Universal Database

DB2

IBM

ibm.comOS/390

Redbooks

Redbooks (logo)

RS/6000Tivoli

WebSphere

z/OS

The following terms are trademarks of other companies:

Intel, Intel Inside (logos), and Pentium are trademarks of Intel Corporation in the United States, othercountries, or both.

Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States,

other countries, or both.

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

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


11/140

Copyright IBM Corp. 2004. All rights reserved. ix

Preface

IBM has changed the provisioning paradigm from just-in-case to just-in-time

on demand provisioning with IBM Tivoli Intelligent ThinkDynamic Orchestrator(ITITO) and IBM Tivoli Provisioning Manager, for managing resource information

and enhancing automation.

IBM Tivoli Intelligent ThinkDynamic Orchestrator and IBM Tivoli Provisioning

Manager automate the traditional manual provisioning process, performancemeasurement, capacity planning, and infrastructure deployment. IBM Tivoli

Intelligent ThinkDynamic Orchestrator operates in a closed loop that performs

automatic resource requirements prediction, based on predefined service levelobjectives and agreements, and automates infrastructure deployment. This

just-in-time cycle ensures that each application has the resource it needs, whenit needs it without static over provisioning.

The primary objective of this IBM Redpaper is to provide step-by-step

instructions about how to set up a stand-alone IBM Tivoli provisioning solutionenvironment to be used for demonstrating the functions and features of the

products, using customer data and mapping customer infrastructure and

workloads.

General knowledge is assumed of communication network architecture anddesign, network security architecture and design, data center environment

infrastructure and operations, Java and XML coding, database and Webapplication servers.

This document is intended to be read and used by pre-sales systems engineersand services personnel to build customized demonstrations of the IBM Tivoli

Intelligent ThinkDynamic Orchestrator. A significant amount of knowledge ofITITO is expected, and the reader should ideally have attended the ITITO basic

and advanced training classes.

The reader should be familiar with the following topics:

XML and XML concepts Network topologies Switch, router, firewall, and load balancer configuration Software packaging

Distributed systems architectures and configuration

This Redpaper is a valuable addition to and can be read in conjunction with the

existing product documentation. See the following recommended reading.


12/140

x Pre Proof-of-Concept Cookbook for Business Partners

Recommended reading

The publications listed in this section are considered particularly suitable for a

more detailed discussion of the topics covered in this Redpaper.

Product manuals: IBM Tivoli Intelligent Orchestrator and Tivoli Provisioning Manager Release

Notes, SC32-1422

IBM Tivoli Intelligent Orchestrator and Tivoli Provisioning Manager Operators

Guide, SC32-1421

IBM Tivoli Intelligent Orchestrator and Tivoli Provisioning Manager Installation

Guide, SC32-1420

IBM Tivoli Provisioning Manager and Intelligent Orchestrator Overview Guide,SC32-1419

Online resources: IBM Tivoli Intelligent ThinkDynamic Orchestrator Product Web page:

http://www.ibm.com/software/tivoli/products/intell-orch/

IBM Tivoli Provisioning Manager Product Web page:

http://www.ibm.com/software/tivoli/products/prov-mgr/

IBM Redbooks: Provisioning On Demand: Introducing IBM Tivoli Intelligent ThinkDynamic

Orchestrator, SG24-8888

http://www.redbooks.ibm.com/redbooks/pdfs/sg248888.pdf

IBM Web Infrastructure Orchestration, SG24-7003

http://www.redbooks.ibm.com/redbooks/pdfs/sg247003.pdf

The team that wrote this Redpaper

This Redpaper was produced by a team of specialists from around the worldworking at the International Technical Support Organization, Austin Center.

Edson Manoel is a Software Engineer at IBM Corporation, InternationalTechnical Support Organization, Austin Center, working as an IT Specialist in the

Systems Management area. Prior to joining the ITSO, Edson worked in the IBMSoftware Group as a Tivoli Technology Ambassador and within IBM Brazil

Professional Services Organization as a Certified IT Specialist. He was involvedin numerous projects, such as designing and implementing systems
http://www.ibm.com/software/tivoli/products/intell-orch/http://www.ibm.com/software/tivoli/products/prov-mgr/http://www.redbooks.ibm.com/redbooks/pdfs/sg248888.pdfhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247003.pdfhttp://www.redbooks.ibm.com/redbooks/pdfs/sg248888.pdfhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247003.pdfhttp://www.ibm.com/software/tivoli/products/prov-mgr/http://www.ibm.com/software/tivoli/products/intell-orch/


13/140

Preface xi

management solutions for IBM customers and Business Partners. Edson holds a

bachelors degree in Applied Mathematics from Universidade de Sao Paulo,Brazil.

Tony French is a Tivoli Services Consultant in the U.K. He has 21 years of

experience in the IT industry, including six years experience in Tivoli Software.His areas of expertise include IBM Tivoli Intelligent ThinkDynamic Orchestrator,IBM Tivoli Business Systems Manager, and the Tivoli Framework suite of

products. He has written extensively about IBM Tivoli Business SystemsManager.

Thanks to the following people for their contributions to this project:

Morten Moeller ITSO Austin Center

Sara C. Brumfield ITITO Level 2 Support, IBM Software GroupTheo Winkelmann On Demand Sales Enablement, IBM Software Group

Leonard Hand Senior Consulting I/T Architect, IBM Global eBusinessSolution Center

Become a published author

Join us for a two- to six-week residency program! Help write an IBM Redbook

dealing with specific products or solutions, while getting hands-on experiencewith leading-edge technologies. You'll team with IBM technical professionals,

Business Partners and/or customers.

Your efforts will help increase product acceptance and customer satisfaction. Asa bonus, you'll develop a network of contacts in IBM development labs, andincrease your productivity and marketability.

Find out more about the residency program, browse the residency index, and

apply online at:

ibm.com/redbooks/residencies.html

Comments welcome

Your comments are important to us!

We want our papers to be as helpful as possible. Send us your comments about

this Redpaper or other Redbooks in one of the following ways:

Use the online Contact us review redbook form found at:

ibm.com/redbooks
http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/http://www.ibm.com/redbooks/http://www.ibm.com/redbooks/http://www.ibm.com/redbooks/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.html


14/140

xii Pre Proof-of-Concept Cookbook for Business Partners

Send your comments in an Internet note to:

[email protected]

Mail your comments to:

IBM Corporation, International Technical Support Organization

Dept. JN9B Building 003 Internal Zip 283411400 Burnet RoadAustin, Texas 78758-3493
http://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/contacts.html


15/140

Copyright IBM Corp. 2004. All rights reserved. 1

Chapter 1. Introduction

This document describes a method to build a customized demonstration of IBMTivoli Intelligent ThinkDynamic Orchestrator (ITITO) for any customer. It is

expected that such a task can be achieved over a period of three working days,consisting of the following major activities:

Planning

Interviewing the customer and the customers technical specialists todetermine which of the customers applications are suitable to be automatedwith ITITO and the nature and extent of the components that make up these

applications.

Negotiating with the customer to remove components that are either not

necessary to demonstrate the product or would be too time-consuming tobuild.

Data center modeling

Some discussion of the software tools that might be useful.

Installation instructions for installing the IBM Tivoli Intelligent ThinkDynamic

Orchestrator management servers on Microsoft Windows Server 2000.

Using the information gathered in the interviews to create a data center model

definition in XML format for loading into ITITO.

Some examples of data center elements that can be used as templates.

1


16/140

2 Pre Proof-of-Concept Cookbook for Business Partners

Guidance on configuring the ITITO simulator for the customized data center

model.

Demonstration

Guidelines demonstrating the key features of the ITITO product.

Provisioning and orchestrating, including:

Data center assets and resources

Customer applications Real-time performance monitoring


17/140


Chapter 2. Planning

In this chapter, we discuss the planning required to build a customizeddemonstration of ITITO. Planning typically involves interviewing the customer to

obtain a fairly detailed audit of the environment that they would like to automatewith ITITO. Obviously, the customers expectations and requirements are often

significantly greater than can be achieved in the time frame usually permitted tobuild a demonstration, so the planning process should involve negotiations to

reveal elements of the customers requirements. This chapter contains someguidelines to help in this area.

2


18/140


2.1 Interviews

To demonstrate to a customer how ITITO can be used in their environments, it is

necessary to conduct a number of interviews with various specialists. Building an

ITITO data center model can require a detailed level of information including, forexample, MAC addresses and information about which ports on the networkswitch to which each network interface card (NIC) connects. For the purposes ofa demonstration, however, it is not strictly necessary to gather the finest detail,

but it may be advisable so that any subsequent Proof of Concepts (POC) projecthas a head start.

The initial interviews should determine if the customer has any applications that

are suitable for automating with ITITO and selecting a number that can be used

to build the demonstration system. We recommend that at least two applications,but no more than four, be selected to build the demonstration.

2.2 General questions

During the initial interview with the customer, these questions may be useful togain an overview of the customers environment and operating practices:

1. Does the customer have any applications that use clusters of similar servers

to provide a service?

2. Do the servers in these clusters run single applications or many?

3. Typically, how many servers make up these clusters?

4. Do these clusters of servers use load balancers or application servers tocontrol the utilization of each server?

5. Does the customer provide sufficient servers to meet peak loads? What is theaverage utilization of the servers in these application clusters?

6. How does the customer plan for peak loads (for example, year-endaccounting, special promotions, or sales)? Does the customer:

Tip: If the customer has mainly mainframe-based computing and is not

planning to change to a distributed architecture, they are not an idealcandidate. ITITO fits very well for applications that support horizontalscaling (that is, Web, application servers).

Tip: If the customer runs more than one application in each server, this

application might not be suitable for automation by ITITO.


19/140

Chapter 2. Planning 5

Wait for the load to materialize and then take action as above?

Build extra servers for each application and incorporate these into theclusters?

Do nothing? (Longer response times at peak times are normal!)

7. How does the customer handle peak loads in their applications? Does thecustomer:

Have a number of extra servers dedicated to each application?

Reconfigure other application servers? Have a spare pool of servers that can be built to order?

8. When the peak loads subside, does the customer:

Return any servers that were added to the application cluster to their

previous state?

Leave the servers in place for the next peak?9. If the customer returns servers to their previous state, how long does this

typically take?

10.Do the customers applications have peak loads at different times?

11.Could the customer conceivably use servers that are idle for one application

in another application that is undergoing a peak load?

12.Does the customer maintain a large number of dedicated test servers for

each application, or does the customer use a general pool of test servers?

13.Typically, what is the utilization of the test server environments?

14.Are the applications written in-house or are they 100% shrink-wrapped from

the software vendor (that is, no customization)? Does the customer performtheir own development and testing?

15.Does the customer operate applications over multiple data centers?16.Does the customer have control over their network environment, or is it

outsourced to a network provider?

Tip: The more the better: ITITO provides a great starting point in anon-production environment and allows the customer to recover, redeploy,

or eliminate redundant servers in the test environment.

Tip: ITITO can enhance the management and maintenance of customized

or homegrown applications. If the customer has a 100% shrink-wrappedenvironment and rarely makes changes to their production/staging

environments, they are less qualified as a prospective customer.


20/140


17.What are the customers predominant operating systems (for example, AIX,Solaris, HP/UX, Microsoft Windows, or Linux)?

18.Does the customer have any blade servers? If so which types/makes (HP,

IBM, and so on)?

19.How many and what type of network switches is the customer using (that is,

Cisco, Extreme, Foundry, and so on)?

20.What level of redundancy is provided for at the network equipment level, if

any?

21.What type of network and systems management software is the customerusing (OpenView, Tivoli, CA UniCenter, and so on)?

22.What kind of storage infrastructure is in place (that is, Storage Area Network,

or SAN, Network Attached Storage, Redundant Array of Independent Disks,or RAID)?

23.What are the customers dominant relational database management systems(Oracle, DB2, Microsoft SQL Server, MySQL, or other)? And, are clustered

database solutions being used?

24.What is the application server software, if any (WebSphere, Weblogic,

Resin, Jboss, or other)?

The ideal outcome of these questions is to locate two to four applications thathave the following characteristics:

Clustered architecture

Tip: If the customers network is totally outsourced, they might not havesufficient access to perform the dynamic reconfiguration that ITITO is

capable of providing.

Tip: If the customer uses mainly OS/390 or non UNIX/Intel operatingsystems, they might be less qualified as a prospect.

Tip: Our application is better suited forLevel 3 (network layer) switches,but we can also work with Level 2 (data layer) switches.

Tip: Helps determine the level of sophistication present in the networkoperations center.


21/140


A low average utilization with idle servers available for peak demand

Or,A pool of spare servers that are provisioned for peak demand

Use similar hardware and operating system platforms

Operate in a network that the customer has control over

Alternatively, if the customer wants to provision application test environments

from a pool of common servers rather than maintain separate test environmentsfor each application, ITITO can be a suitable tool for this, too.

The following table can be used to collect and summarize the data from thesequestions:

Table 2-1 Capturing customer planning information skeleton

2.3 ITITO components

After a limited number of suitable applications are identified, it is necessary to

gather additional technical details in order to build an ITITO data center model.To simplify the data center model building, these components have been broken

down into the following categories:

Power units Network configuration Software configuration Spare pools Customers, applications, and clusters Other devices

The following sections contain tables showing the required attributes that need to

be collected for each component type. The shaded cells in these tables are foradditional data that is not essential for a demonstration but is necessary for a full

ITITO build or Proof of Concept.

Applic-

ation

#

Servers

Operating

systems

#

Web

servers

#

Data-

bases

Avg.

util

%

#

Spare

servers


22/140


2.3.1 Power units

For the purposes of a demonstration, power units are optional in ITITO. It is

possible to define the power units and to associate devices with these powerunits. It is also possible to manage the power units through an IP connection. For

a demonstration, it will usually only be necessary to collect the names of the unitsfor later reference by other devices:

Table 2-2 Power units data collection skeleton

Table 2-3 Power units data collection example

2.3.2 Network configuration

The ITITO network configuration consists of the following main components:

Switch fabric Subnetworks Switches Load balancers Virtual IPs Access control lists (ACLs)

Each of the main components is addressed separately.

Most devices in ITITO require a number of service access points that define the

mechanisms and authentication information (user IDs and passwords) that areused to communicate with the device. For a demonstration, these are not

Power unit name Manufacturer Model Device model

Note: The only devices that are supported by Version 1.1 of ITITO are as

follows:

Manufacturer Model Device model

APC 7901 APC-7901-SNMP

APC 9606 APC-9606-SNMP

Note: It is also possible to define network interface cards (NICs) on a power

unit and associate it with a port on a network switch, but it was found that thedata center model would not load if this were done. However, it is possible to

define the interface from the ITITO GUI.


23/140


required. However, if the customer is willing to provide this information, and if the

demonstration is likely to lead to a Proof of Concept or implementation, theinformation can be collected in advance. This is addressed in the last segment of

this section.

Switch fabricThe switch fabric is an ITITO concept. For most customers, it will normally onlybe necessary to define one switch fabric. All that is needed is the name of the

fabric. The customers name is recommended to be included here. This name willbe used in a number of other components later.

Table 2-4 Switch fabric data collection skeleton

SubnetworksEvery subnet in use by the applications defined in Section 2.2 on page 4 must bedefined to ITITO. In addition, the VLAN that is associated with the subnet mustbe recorded.

Table 2-5 Subnet data collection skeleton

It is possible to define a name for each subnetwork, but we recommend that thisnot be specified so that the name defaults to the subnet address, because this is

easier to understand while using the GUI.

When ITITO is used to provision servers, it can assign an IP address to a newserver from the next available within a subnet. In this way, ITITO acts in a similarway as a DHCP server, although technically, it assigns a permanent address.

For subnets where ITITO is permitted to assign addresses, it will usually benecessary to block certain addresses. Otherwise, ITITO will assign a duplicate

address. In particular, each subnet will have a gateway address that should beblocked, and any permanent servers on the subnet should also be blocked. A

number of ranges can be defined if necessary.

Switch fabric name

Subnet address Netmask VLAN


24/140


SwitchesEach network switch device that is used by the applications determined in

Section 2.2 on page 4 should be recorded here:

Table 2-6 Switch data collection skeleton

Switches often have separate modules containing a number of ports. Every portthat connects a device in the ITITO environment must be defined here and will beused later in the device definitions. It is not necessary to define every port on

every switch, just the ones to be controlled by ITITO.

Table 2-7 Switch port data collection skeleton

The valid types of ports for ITITO Version 1.1 are:

Ethernet Fast Ethernet Gigabyte

Subnet address Blocked range start Blocked range end

Switch

name Manufacturer Model

IP

address

Switch

fabric Device model

Switch name Switch modules Switch port VLAN Port type


25/140


VLAN Unknown

It is not essential to define the port types, because this does not affect the

demonstration, although the ports will show up as unknown type in the GUI.

If any switch is connected to any of the power units identified in 2.3.1, Powerunits on page 8, the attached power unit should be recorded here:

Table 2-8 Switch/power units data collection

The following switches are supported by ITITO Version 1.1:

Table 2-9 Switch data collection example

If the customer has other switches than these, it will be necessary to codecustom device drivers during any Proof of Concept or implementation.

Fortunately, for a demonstration, it is only necessary to use the dummy switchdevice model for all devices. This allows the switch operations to be simulated

during the demonstration.

Routers and firewallsRouters are defined as switches in ITITO, but they also require networkinterfaces, route definitions, and access control lists.

Switch name Power unit Power outlet


Cisco 6500 Cisco 6500 Switches Hybrid Mode

Cisco 6500 Cisco 6500 Switches Native IOS Mode

Cisco 3548 Cisco 3548


IBM Blade Center

4port GB

Blade Center 4p GB Eth

Extreme 48i Extreme 48i

Foundry Foundry Switch Foundry Switch

Others Dummy Switch Dummy Switch


26/140


The basic definition table for a router is as follows:

Table 2-10 Router data collection skeleton

Routers will usually have a number of interfaces that control the routing betweensubnets. The data required for these components is as follows:

Table 2-11 Router interface data collection skeleton

Each interface can support a number of routes, which need to be specified in thefollowing table:

Table 2-12 Router interface route data collection skeleton

The following router is a valid device in ITITO Version 1.1:

Table 2-13 Router information data collection example

Access control listsFor each router or firewall that controls traffic between subnetworks, an accesscontrol list (ACL) should be defined. These appear on the GUI as a distinctive

icon that connects subnetworks. Each ACL can have multiple rules that areunidirectional. Usually at least two rules will be defined, permitting traffic in both

directions between a pair of subnets.

Router

nameManufacturer Model IP address

Switch

fabric

Device

modelFirewall

Router name Interface name IP address Managed

Router name Interface name Route Gateway ACL




27/140


Table 2-14 Access Control List data collection skeleton

The Target column contains the operational mode of the rule: either permit ordeny.

Each rule can specify protocols or port ranges to permit or deny, but for the

purposes of a demonstration, this should not be necessary.

Load balancersLoad balancers require the following information to enable them to be defined toITITO:

Table 2-15 Load balancer data collection sample

The following load balancers are valid devices in ITITO Version 1.1:

Table 2-16 Load balancer data collection example

Each load balancer can have existing virtual IP addresses defined to it. When

ITITO is operational, it will create and delete vir tual IPs as it provisions serversinto application clusters on demand.

Load balancers can also be used as switches. In this case, they will need to be

defined as switches in Switches on page 10.

ACL name Rule # Target Source subnet Destination subnet

Name Manufacturer Model Type Device model

Manufacturer Model Device model Type

Cisco 11000 Cisco CSS arrowpoint-load-balancer

Alteon LoadBalancer Alteon LoadBalancer

Dummy LB Dummy LB


28/140


Virtual IPsAny pre-existing virtual IPs can be defined to ITITO if required, although they willusually take no part in the demonstration. The information required is shown in

the following table:

Table 2-17 Virtual IP data collection skeleton

Each application cluster (see 2.3.5, Applications and customers on page 16)

that ITITO is to provision automatically will need a unique virtual IP definition forthe cluster.

2.3.3 Software

Software configuration in ITITO is divided into three categories:

Software package Software patch Software stack

We address each of these in the following sections.

Software packageEach single piece of software or data that the customers applications require to

be provisioned must be defined to ITITO as a software object. This typicallyincludes operating systems, databases, middleware, applications, data, and soon.

For each software package that is to be automatically deployed, it is necessary

to collect the following information:

Table 2-18 Software package data collection skeleton

Virtual IP

name

Load

balancer

Virtual IP

address

First input

port in range

Last input

port in range

Output

port

Software name Version Type Package path Install path


29/140


There are two valid entries for type:

OPERATING_SYSTEM SOFTWARE

For the purposes of the demonstration, package and install paths are optional.

Software patchesSoftware patches are optional for the demonstration. If any patches or servicepacks are required by the customer, they need the following basic information forthe demonstration:

Table 2-19 Software patch data collection skeleton

As with the software packages, package path and install path are optional for a

demonstration.

Software stacks

Software stacks are an ITITO concept to group together a number of softwarepackages and software patches so that the stack represents all of the software

that must be installed on each type of server when it is provisioned into anapplication cluster. Each distinct type of server required by any application

cluster needs a corresponding software stack. In addition, if any spare pool hasto have an initial set of software defined, the software stack should be defined for

this state, too. Typically, this could mean that a base operating system isinstalled on servers in a spare pool with no applications.

Software stacks require the following information:

Table 2-20 Software stack data collection skeleton

The software stack names must match the software products or patches, or both,

defined in the previous sections. The Position column determines the installationorder.

Patch name Type Package path Install path

Software stack name Software product Position


30/140


2.3.4 Spare pools

If the customer has pools of spare servers already available for their applications,

information about the names, connections, and types of these machines needsto be determined and entered in the following tables. If the customer does not

have any existing pools of machines, for the demonstration, a number of serverswill need to be defined to create a spare pool. The customer should be advisedthat this is a fundamental principle behind ITITO.

These pools require the following definitions:

Table 2-21 Spare pool network data collection skeleton

Any number of servers can be defined for each pool with the following attributes:

Table 2-22 Spare pool data collection skeleton

For ITITO to operate correctly with pooled servers, we strongly advise that each

server has at least two network interface cards (NICs), one of which is dedicatedto the management LAN. If any NIC has multiple IP addresses, these should berecorded here, too.

MAC addresses are optional for the demonstration, but will show up as unknownin the GUI if not specified.

2.3.5 Applications and customers

In this section, it is necessary to gather information about the various

applications that a customer wants to provision with ITITO. The basic data

Spare pool name VLAN Switch fabric

S

parepool

n

ame

S

ervername

N

etwork

interfacecard

C

onnected

toswitch

C

onnectedto

s

witchmodule

C

onnectedto

s

witchport

IPaddress

M

anaged

M

ACaddr.


31/140


required is shown in the following table. For a demonstration, at least two

applications should be defined.

Table 2-23 Customer/application data collection skeleton

Each ITITO implementation can have many customers defined, each of which

can have multiple applications, each of which can have multiple applicationclusters. An application cluster is defined to be a set of servers that provide thesame service to an application. The servers are expected to be virtual clones of

each other. The priority of each application should be set according to thefollowing table:

Table 2-24 Application priority data collection example

Each application cluster requires the following additional definitions:

Table 2-25 Cluster information data collection skeleton

Customer name or

business unitApplication Priority Application cluster

Service plan Priority Interpretation

Platinum Better priority service

Gold Medium priority service

Silver 10 Poorer priority service

Application

cluster

Min.

servers

Max.

servers

VLAN

Switch

fabric

Pool

Load

balancer

VirtualIP

Managed


32/140


In this table, Pool is the server pool from which the application cluster provisions

and returns servers (resource pool). Each application cluster can be managed orunmanaged. This value should be set to true or false. If the cluster is

unmanaged, ITITO will make no attempt to provision servers for this cluster.Typically, this option is used for clusters that provide database facilities. It is

usually desirable to show these clusters in the ITITO GUI, but not to actuallymake changes to them automatically. The Load Balancer column is used toidentify the load balancer that is associated with the clusters servers. The Virtual

IP column refers to the virtual IPs defined in Virtual IPs on page 14.

If any cluster has any dedicated servers assigned to it (and usually there will beat least one), these must also be defined. The data required for these is shown inthe following table:

Table 2-26 Cluster network data collection skeleton

For servers that are permanently assigned to a cluster, the network interfacecards should usually not be managed by ITITO. As with pool servers, the MAC

addresses are optional, but will show up as unknown in the GUI if not specified.

Note: It is also possible to configure the service level agreement properties:maximum response time and maximum time available. We recommend that

you talk about this during the demonstration.

Application

cluster

Ser

ver

nam

e

Net

work

inte

rface

card

Managed

Connected

tos

witch

Connected

tos

witch

module

Connected

tos

witch

por

t

IPa

ddress

MAC

add

ress

2 3 6 Oth d i


33/140


2.3.6 Other devices

ITITO supports a number of other data center management devices including:

Boot servers Terminal servers

Blade center management servers

These devices might be essential for the operation of a data center, but do not

really play any part in a demonstration of ITITO. If it is desirable to show theconfiguration and that the product supports these devices, they should be

included.

Boot serversIf any servers are to be provisioned by bare-metal builds, it will be necessary to

define a boot server for each set of servers that are configured to use the sameboot server. Boot servers require the following information to be defined:

Table 2-27 Boot server data collection skeleton

Each boot server can also have a network interface card and network interfaces

as with other servers in spare pools and clusters:

Table 2-28 Boot server network information collection skeleton

The following boot servers are valid devices in ITITO Version 1.1:

Table 2-29 Boot servers supported by ITITO V1.1

Name Manufacturer Software IP address Device model

Boot

server

name

Network

interface

card

Connected

toswitch

Connected

toswitch

module

Connected

toswitch

port

IPaddress

Managed

MACaddr.

Manufacturer Software Device model

Rembo Auto-Deploy Rembo Boot Server

IBM Remote Deployment Manager RDM Server


34/140


If a boot server is used to deploy an operating system, this attribute can be

added to the corresponding software stack for the operating system. This is

optional for the demonstration.

Table 2-30 Boot server/operating system data collection skeleton

Terminal serversTerminal servers can be defined to ITITO like boot servers except that there areno supplied device drivers for terminal servers in Version 1.1 of the product:

Table 2-31 Terminal server data collection skeleton

Network interface cards and network interfaces can be defined as with otherservers:

Table 2-32 Terminal server network information data collection skeleton

IBM Network Installation Manager NIM Server

IBM zVM Boot Server zVM Boot Server

IBM Cluster Systems Management CSM Management Server

Sun Jump Start JumpStart Server

HP Rapid Deployment Pack RDP Server

Software stack name Boot server

Name IP address

Te

rminal

se

rver

na

me

Network

interface

ca

rd

Connected

to

switch

Connected

to

switch

module

Connected

to

switch

po

rt

IP

address

Managed

MACaddr.

Blade center management servers


35/140


Blade center management serversEach blade system is managed by a central management server that controls allaspects of the blade servers. ITITO uses the blade center management server to

perform operations on the blade servers such as reboot, power on, andreconfiguration. If the customer uses blade servers, it might be desirable to show

the blade center management server, although the demonstration will make novisible changes to the blade center management server itself. The blade centermanagement server can be defined like the boot server and terminal servers:

Table 2-33 Blade center management server data collection skeleton

The following blade systems have device drivers in Version 1.1 of ITITO:

Table 2-34 Blade center management servers supported by ITITO V1.1

Network interface cards and network interfaces can also be defined if required:

Table 2-35 Blade server network information data collection skeleton

Servers in spare pools or in clusters can be associated with the relevant bladecenter management server. This information can be appended to servers in therelevant spare pools and clusters:

Name Manufacturer Software IP address Device model

Manufacturer Blade system Device model

RLX Technologies ServerBlades RLX Blade Server

HP Proliant Blade Servers Proliant BL Server

Blade

server

name

Network

interface

card

Connected

toSwitch

Connected

toswitch

module

Connected

toswitch

port

IPaddress

Managed

MACaddr.

Table 2-36 Blade servers data collection skeleton


36/140


Table 2 36 Blade servers data collection skeleton

2.3.7 Scoping

This section discusses the process of settling the scope of the demonstration.This should be agreed with the customer prior to beginning work on the

development of the demonstration system.

The main objective of a customized demonstration is to show the customer whatITITO can do for them in their environment. It will not usually be necessary toshow the full extent of their environment, and indeed, could be

counter-productive if attempted. From the data gathered, a representativesample of components should be chosen to be used in the demonstration. For

example, if a customer has an application that has 100 servers working as acluster, it is only really necessary to show a few.

Also, if a customer has platforms that are not ideal for ITITO such as Tandems or

z/OS, it would be better to focus on the ones that are.

Ultimately, if two applications can be agreed on with one, two, or three clusters ineach and one to five servers for each cluster, the demonstration should be

feasible, representative, and worthwhile.

Provided with this document and included in the text is an XML file that containsthe following:

One customer

Two applications Two clusters in each application One dedicated server in each cluster One common resource pool One switch One router One load balancer Three software stacks Six software packages

This should be sufficient to demonstrate the key features of ITITO and could

perhaps be used simply by changing the names of the applications clusters andpools to the customers own names.

Server name Blade admin server Blade slot

The files provided with this document are described in 4.3, Sample XML files on


37/140


p , p

page 91.


38/140



39/140


Chapter 3. Installing the demonstration

systems

This chapter describes the installation procedures to get IBM Tivoli IntelligentThinkDynamic Orchestrator installed for our pre-POC demonstration scenario.

Our installation consists of two servers, one hosting an IBM DB2 database serverand LDAP Directory, and the second being the IBM Tivoli Intelligent

ThinkDynamic Orchestrator server. This is considered a typical two serverscenario.

In the case of a two server installation, as described in this chapter, both serversmust be running the same operating system. In this chapter, we provide

instructions for installing IBM Tivoli Intelligent ThinkDynamic Orchestrator onMicrosoft Windows 2000 Server.

The instructions given in this chapter are very detailed and explicit. These

instructions are not the only way to install IBM Tivoli Intelligent ThinkDynamicOrchestrator and its related prerequisites, and are meant to be followed tosuccessfully install and set up a IBM Tivoli Intelligent ThinkDynamic Orchestrator

environment.

3

3.1 Installation process overview


40/140


p

Our installation scenario is to be considered as an example only. The following

are the names of both servers used during the installation process. These namesmost likely should be changed to the naming standards of the customer.

The server hosting both the IBM DB2 Server and the IBM Directory server willbe named TIOdbsrv.

The server hosting the IBM Tivoli Intelligent ThinkDynamic Orchestratorserver will be named TIOsrv.

The following table provides the recommended hardware for each server. This isthe hardware we used in the ITSO lab environment and we recommend it as a

minimum configuration.

Table 3-1 Recommended hardware for Windows 2000 Server

The following table provides a list of the various products that will need to be

installed and configured on each server during the installation procedure per

operating system. Please note that both servers must be running the sameoperating system.

Table 3-2 Required software - Windows 2000

Note: The values provided in the following table may differ form theinformation provided in the IBM Tivoli Intelligent Orchestrator and Tivoli

Provisioning Manager Release Notes, SC32-1422. They represent thehardware used at the time of writing this Redpaper and serve as our

recommendation for a minimum of a two server configuration.

IBM Compatible Server:

2.4 GHz Intel Pentium processor or equivalent

2GB RAM

30 GB disk

TIOdbsrv TIOsrv

Windows 2000 Server Windows 2000 Server

Cygwin Version 1.3.22 or later Cygwin Version 1.3.22 or later

IBM DB2 Universal DatabaseWorkgroup Unlimited Edition V8.1.2 IBM DB2 Universal Database V8.1.2 Client

IBM Directory Server, V5.1 IBM Directory Server V5.1 Client

TIOdbsrv TIOsrv


41/140

Chapter 3. Installing the demonstration systems 27

The following picture provides an overview of the entire installation process andcan be used as reference during the installation.

Figure 3-1 ITITO installation overview

IBM WebSphere Application Server Base

Edition V5.0.1


Edition V5.0.1 Client

IBM Tivoli Intelligent ThinkDynamic

Orchestrator V1.1.0

Define user tioadmin user ID with Administrator / root a uthority on both servers

Define user tioldap user ID with Administrator / root authority on both servers

UNIX only: define the mqm user ID in the mqm group. Also create mqbrkrs groupand ensure that tioadmin, root and mqm users IDs belongs to it.

Phase 1

TIO

Database

Server

Install all the prerequisite packages for SSH communication between Servers (CygWin forWindows, openssh for AIX) on both Servers

Configure SSH and generate a RSA key on the TIO Server

Configure SSH on the TIO database Server

Copy the RSA key to the TIO database Server

Test SSH communication from the TIO Server to the TIO database Server

Repeat the process forall servers in the Data Center to be managed by IBM Tivoli IntelligentThinkDynamic Orchestrator

Phase 2

Install the remaining prerequisite packages

Install IBM DB2 Universal Database Workgroup Unlimited Edition V8.1.2

Create the database to be used by IBM Tivoli Intelligent ThinkDynamic Orchestrator

Populate the database using the provided tablesapce.sql file

Install IBM Directory Server, V5.1

Create the LDAP database a nd configure IBM Directory Server, V5.1 with the provided suffixes

and ldap.ldif fileVerify the installation

Phase 3

Define the User IDs

Prepare SSH communications

Prepare the TIO database Server

Phase 4 Prepare the TIO Server

TIO

Server

TIO

Database

Server

SSH

TIO

Database

Server

Central Data

WarehouseTIO DB

Data sourceLDAP DB

Install the remaining prerequisite packages

Install IBM DB2 Universal Database V8.12 Client

Install IBM Directory Server V5.1 Client

Install IBM Websphere Application Server Base Edition V5.0

Install IBM Websphere Application Server Base Edition V5.0 Fixpack 1

Apply the MQ CSD03 patch to IBM Websphere

Apply the MQ fixes for embedded messaging to IBM WebSphere (IY43610 and IY44803)

Install IBM Websphere Application Server Base Edition V5.0 Client

Install IBM Tivoli Intelligent ThinkDynamic Orchestrator V1.1.0

Verify the installation

TIO

Server

SSH

TIO

Database

Server

TIO

ServerCentral DataWarehouseTIO DB

Data sourceLDAP DB

3.1.1 Recommended installation directories


42/140


The following table provides a list of recommended installation directories for

each product used during the installation process. Note that file paths containingspaces must not be used, as it will cause problems during the installation andconfiguration process.

Table 3-3 Recommended installation directories

3.1.2 User IDs and passwords

The following table illustrates the user IDs that will be either created during theapplication install process or created by you, the implementer, before the actualinstall process begins.

Table 3-4 User IDs and passwords

Product Installation Directory

Cygwin Version 1.3.22 c:\cygwin

IBM DB2 Universal Database Workgroup

Unlimited Edition V8.1.2

c:\IBM\sqllib

IBM Directory Server, V5.1 c:\IBM\ldap

IBM DB2 Universal Database V8.12 Client c:\IBM\sqllib

IBM Directory Server V5.1 Client c:\IBM\ldap


Edition V5.0.1

c:\IBM\WebSphere\AppServer


Edition V5.0.1 Client

c:\IBM\WebSphere\AppClient

IBM Tivoli Intelligent ThinkDynamicOrchestrator V1.1.0

c:\cygwin\home\thinkcontrol

User name Password Description Comment

tioadmin Used to log onto the OS

to install IBM Tivoli

Intelligent

ThinkDynamic

Orchestrator

This user ID must be

created manually on

both servers prior to

the installation

User name Password Description Comment


43/140


tioldap Used by IBM Tivoli

Intelligent

ThinkDynamic

Orchestrator to connect

to the Directory Server


created manually on

the machine hosting

the IBM Directory

Server prior to the

installation

tiodb This user ID will be the

instance owner of the

IBM Tivoli Intelligent

ThinkDynamic

Orchestrator database

Created during the

IBM DB2 installation

on the server hosting

the IBM Tivoli

Intelligent

ThinkDynamic

Orchestrator

database

mqm Used by WebSphere

MQ


created manually on

both servers prior to

the installation

wasadmin wasadmin Used by WebSphere as

administration account

Defined

automatically by the

WebSphere

installation process

tioappadmin tioappadmin This is the IBM Tivoli

Intelligent

ThinkDynamic

Orchestrator

superadmin and is used

to log into the Web

console

Defined on the

Directory Server



ThinkDynamic

Orchestrator


tiointernal internal Used by IBM TivoliIntelligent

ThinkDynamic

Orchestrator for system

initiated actions

Defined on theDirectory Server



ThinkDynamic

Orchestrator


cn=root root user ID for the IBM

Directory LDAP Server

Created during the

IBM Directory


3.2 Installing and configuring TIOdbsrv - Windows


44/140


In this section we describe the steps to setup the machine hosting database and

the LDAP directory used by the IBM Tivoli Intelligent ThinkDynamic Orchestratoron Microsoft Windows 2000 Server. The high level install steps are presented in

the following figure.

Figure 3-2 TIOdbsrv installation steps

The following sections explain each step of the above flow in detail.

3.2.1 Creating the required user IDs

Create a local user accounts tioadmin and tioldap as follows:

1. Under Computer Management choose System Tools -> Local users and

groups -> Users and add the users tioadminand tioldap.

2. Select the newly created users and make both of them members of the

Administrators group.

3. Select the user ID tioadmin and set its Local Path to:

C:\Cygwin\home\thinkcontrol

4. Select the user ID tioldap and set its Local Path to:

C:\IBM\ldap

Create tioldap user id

Download and installCygwin

Install and configureDB2

Install and configureIBM Directory Server

Create tioadmin userid

3.2.2 Installing and configuring Cygwin


45/140


Cygwin is used as an Open SSH environment for the IBM Tivoli Intelligent

ThinkDynamic Orchestrator application to communicate with all otherapplications through the use of Cygwins BASH Shell and can be obtained at thefollowing URL:

http://www.cygwin.com/

Ensure you are logged on to the TIOdbsrv machine using the tioadmin useraccount specified above.

1. Open a browser and go the Cygwin home page: http://www.cygwin.com

Select the Install or Update now! option.

2. Choose to open the setup.exe application from its current location

3. The Cygwin Setup window starts the installation wizard, select Next

4. Select Install from Internet

5. Accept default installation directory (C:\Cygwin), All Users and DOS options

6. Accept default Package directory

7. Choose the appropriate internet settings. We selected Direct Connection.

8. Select a FTP site from the available list

9. During the Cygwin installation, on the Select Package panel, it is important toselect the correct Categories. The installation wizard provides a series of

pre-selected packages as default for installation. However, IBM TivoliIntelligent ThinkDynamic Orchestrator requires additional packages under the

Lib and Net categories. The following table describes the required packagesthat need to be installed in addition the default selection. To select thosepackages, click the + sign of the Libs and Net categories, and click the Skip

button next to the desired package to change the installation option from SkiptoInstall.

Attention: Cygwin Version 1.3.22 or higher must be installed. At the time of

writing this Redpaper, Cygwin Version 1.5.5-1 was the current versionavailable for downloading and it was used during our install process.

Important: Before you download Cygwin ensure you are logged on using the

tioadmin user account specified above and that the tioadmin user has thecorrect profile properties and is a member of Administrators.

Tip: Werecommend selecting and installing all of the Cygwin packages.
http://www.cygwin.com/http://www.cygwin.com/http://www.cygwin.com/http://www.cygwin.com/


46/140


10.When the installation completes, select to create icon on desktop. Select

Finish.

3.2.3 Configuring SSH communications

When the Cygwin installation completes click on the Cygwin icon to open a bash

shell window and perform the following steps to configure SSH:

1. Move to the /usr/bin directory and issue the host configuration ssh-host-configcommand, as shown in the following example. When prompted forenvironment variables, press Enter to accept the defaults.

$ cd /usr/bin$ ./ssh-host-config -yGenerating /etc/ssh_host_keyGenerating /etc/ssh_host_rsa_keyGenerating /etc/ssh_host_dsa_keyGenerating /etc/ssh_config file

Privilege separation is set to yes by default since OpenSSH 3.3.However, this requires a non-privileged account called 'sshd'.For more info on privilege separation read/usr/doc/openssh/README.privsep.Warning: The following function requires administrator privileges!Generating /etc/sshd_config fileAdded ssh to /cygdrive/c/WINNT/system32/drivers/etc/servicesAdded ssh to /etc/inetd.confDo you want to install sshd as service?Which value should the environment variable CYGWIN have when

sshd starts? It's recommended to set at least "ntsec" to beable to change user context without password.Default is "binmode ntsec tty". CYGWIN=The service has been installed under LocalSystem account.

Additional Cygwin packages

Cygwin Package Action

Libs Accept default packages PLUS Regex

Net Accept default packages PLUS OpenSSH and OpenSSL

Important: Verify that all servers in your configuration are setup correctly ineither DNS and or /etc/hosts.

Host configuration finished. Have fun!

2. Export the CYGWIN variable.


47/140


p

$ export CYGWIN=ntsec

3. Move to the /var directory and change the attributes of the directory namedempty.

$ cd /var$ chmod 700 empty

4. Start the SSH service as follows:

$ cygrunsrv -S sshd5. Move to the home directory of the tioadmin user ID and issue the ssh-keygen

command to generate the RSA key. You should have an output similar to the

following example.

$ cd$ pwd/home/thinkcontrol$ ssh-keygen -t rsa -N ""Generating public/private rsa key pair.

Enter file in which to save the key (/home/thinkcontrol/.ssh/id_rsa):Created directory '/home/thinkcontrol/.ssh'.Your identification has been saved in /home/thinkcontrol/.ssh/id_rsa.Your public key has been saved in /home/thinkcontrol/.ssh/id_rsa.pub.The key fingerprint is:fd:ca:21:d3:3f:db:fd:d9:56:b2:30:68:16:43:1c:11 tioadmin@tio12

6. Move to the .ssh directory and create the authorized_keys file:

$ pwd/home/thinkcontrol

$ cd .ssh$ cat id_rsa.pub > authorized_keys

7. To configure SSH to accept connections from new hosts without prompting for

confirmation, create a file in the /home/thinkcontrol/.ssh directory calledconfig. Edit the config file and add the line StrictHostKeyChecking no as

follows:

# cd /home/thinkcontrol/.ssh# touch config

# vi configAdd in the following line:

StrictHostKeyChecking no

Tip: This command will set an environment variable for products to reference

as a global variable.

Type the config file. The output should read as follows:

StrictHostKeyChecking no


48/140


8. To verify that SSH is configured properly, try to access your own machineusing the ssh command as shown in the following example.

$ ssh tioadmin@localhostWarning: Permanently added 'localhost' (RSA) to the list of known hosts.Fanfare!!!You are successfully logged in to this server!!!$ exitlogoutConnection to localhost closed.

3.2.4 Installing and configuring IBM DB2 UDB V8.1.2 on Windows

This section describes the installation and configuration of IBM DB2 UniversalDatabase, Workgroup Unlimited Edition V8.1.2 on Windows. It also shows the

required configuration steps required by IBM Tivoli Intelligent ThinkDynamicOrchestrator.

Use the DB2 installation media provided with the IBM Tivoli Intelligent

ThinkDynamic Orchestrator product. This ensures that you get the correctversion and level of DB2 installed.

1. Logged on as tioadmin, move to the drive where the IBM DB2 CD is mounted

and run the setup.exe command to start the installation. From the installationwindow, select Install Product.

2. Select the product we want to install: IBM DB2 Workgroup Server UnlimitedEdition and click Next.

3. The Welcome to the DB2 Setup wizard window opens. Click Next.

4. Accept the License Agreement by selecting I accept the terms in thelicense agreement option.

5. The Select the installation type window opens. Select the Custom Installoption.

6. Select Install DB2 Workgroup Server Unlimited Edition on this computer.

7. The Select features window opens, as shown in the next figure. Select the

following packages:

Client support

Administration tools Server support

Note: Ensure you perform the IBM DB2 installation logged on as tioadmin.

Also select the installation path. Ensure there are no spaces in the installation

path. We used C:\IBM\SQLLIB.


49/140


Figure 3-3 Select DB2 Server components

8. Choose Language of choice - English is default.

9. The Set user information for DB2 Administration Server window open, as

shown in next figure. Here you have to specify the user ID tiodb as it will bethe instance owner of the IBM Tivoli Intelligent ThinkDynamic Orchestrator

database. The user ID tiodb will be created with the proper authority by theDB2 installation process. Make sure you record the password as you will be

prompted for this password during the IBM Tivoli Intelligent ThinkDynamicOrchestrator installation.


50/140


Figure 3-4 Set the DB2 administrator user to tiodb

10.The Set up administration contact list window opens. Select Local - Create a

contact list on this system.

11.Click Next at the Configure DB2 instances window.

12.At the Prepare the DB2 tools catalog choose Prepare the DB2 tools catalogin a local database.

13.Accept the default values at the Specify a local database to store the DB2tools catalog window.

14.At the Specify a contact for health monitor notification choose Defer the taskuntil after installation is complete.

15.At the Request satellite information screen choose Defer this task until after

installation is complete.

16.At the Start copying files window you have the chance to review the

installation options. Click on Install to initiate the installation.

17.Then the installation completes, open a DB2 command window: Start -> IBM

DB2 -> Command Line Tools -> Command Window.18.Issue the db2licmcommand to add the license provided by IBM Tivoli

Intelligent ThinkDynamic Orchestrator:

C:\IBM\SQLLIB\BIN>d: cd \db2\licenseD:>db2licm -a ./db2wsue.lic


51/140


DBI1402I License added successfully.DBI1426I This product is now licensed for use as specified in theLicense Acceptance and License Information documents pertaining to the

licensed copy of this product. USE OF THE PRODUCT CONSTITUTESACCEPTANCE OF THE TERMS OF THE IBM LICENSE ACCEPTANCE AND LICENSEINFORMATION DOCUMENTS, LOCATED IN THE FOLLOWING DIRECTORY:"C:\IBM\SQLLIB\license\en"

19.Reboot the system

Create database and database schema

After installing IBM DB2 perform the following steps to create the database andthe database schema used by IBM Tivoli Intelligent ThinkDynamic Orchestrator.

1. Logon to the system as the tiodb user ID.

2. Open a DB2 command window.

3. Create the database for IBM Tivoli Intelligent ThinkDynamic Orchestrator by

entering the following command:db2 create database

Where, is the name of the database you want to create.

Make sure the database name follow the DB2 naming conventions and that

you record it as you will require it when installing IBM Tivoli IntelligentThinkDynamic Orchestrator.

You can confirm the creation of the database by issuing the followingcommand:

db2 list database directoryC:\IBM\SQLLIB\BIN>db2 create database ITITODBDB20000I The CREATE DATABASE command completed successfully.C:\IBM\SQLLIB\BIN>db2 list database directorySystem Database DirectoryNumber of entries in the directory = 2Database 1 entry:

Database alias = ITITODBDatabase name = ITITODB

Database drive = C:\DB2Database release level = a.00Comment =

Important: You must logon to your system using the tiodb user ID to be

successful with the DB2 configuration.

Directory entry type = IndirectCatalog database partition number = 0

Database 2 entry:


52/140


Database alias = TOOLSDBDatabase name = TOOLSDBDatabase drive = C:\DB2

Database release level = a.00Comment =Directory entry type = IndirectCatalog database partition number = 0C:\IBM\SQLLIB\BIN>

4. Copy the tablespace.sql script located in the /samples directory on the IBMTivoli Intelligent ThinkDynamic Orchestrator CD to your IBM DB2 installation

directory (in our case C:\IBM\SQLLIB\BIN).

5. Create the tablespace for the database by performing the following steps:

db2 connect to user tiodb using

Where, is the name of the database you created in the previous

step, and is the password for user ID tiodb.

Then run the following command:

db2 -tvf tablespace.sqlC:\IBM\SQLLIB\BIN>db2 connect to ITITODB user tiodbEnter current password for tiodb:

Database Connection InformationDatabase server = DB2/NT 8.1.2SQL authorization ID = TIODBLocal database alias = ITITODBC:\IBM\SQLLIB\BIN>db2 -tvf tablespace.sqlCREATE BUFFERPOOL IBM16K SIZE 250 PAGESIZE 16K NOT EXTENDED STORAGEDB20000I The SQL command completed successfully.CREATE BUFFERPOOL IBM8K SIZE 250 PAGESIZE 8K NOT EXTENDED STORAGEDB20000I The SQL command completed successfully.CREATE REGULAR TABLESPACE IBM8KSPACE PAGESIZE 8K MANAGED BY SYSTEM USING

('IBM8KSPACE') BUFFERPOOL IBM8K DROPPED TABLE RECOVERY OFFDB20000I The SQL command completed successfully.CREATE REGULAR TABLESPACE IBM16KSPACE PAGESIZE 16K MANAGED BY SYSTEMUSING ('IBM16KSPACE') BUFFERPOOL IBM16K DROPPED TABLE RECOVERY OFFDB20000I The SQL command completed successfully.CREATE TEMPORARY TABLESPACE IBM8KTEMPSPACE PAGESIZE 8K MANAGED BY SYSTEMUSING ('IBM8KTEMPSPACE') BUFFERPOOL IBM8K DROPPED TABLE RECOVERY OFFDB20000I The SQL command completed successfully.CREATE TEMPORARY TABLESPACE IBM16KTEMPSPACE PAGESIZE 16K MANAGED BYSYSTEM USING ('IBM16KTEMPSPACE') BUFFERPOOL IBM16K DROPPED TABLE

RECOVERY OFFDB20000I The SQL command completed successfully.C:\IBM\SQLLIB\BIN>

3.2.5 Installing and configuring IBM Directory Server V5.1

In this section we show the installation and configuration steps of IBM Directory

S V5 1 I IBM Ti li I t lli t Thi kD i O h t t i t


53/140


Server, V5.1. In a IBM Tivoli Intelligent ThinkDynamic Orchestrator environmentthe IBM Directory Server can be installed on any system using any supportedoperating system. In our case study scenario, we decided to install IBM Directory

Server on the same machine as the IBM DB2 server. In any case, an LDAP clientmust be installed on the IBM Tivoli Intelligent ThinkDynamic Orchestrator

machine to allow it to communicate with the IBM Directory server.

To install and configure IBM Directory Server 5.1, perform the following steps:

1. Log on to the system as tioadmin.

2. Ensure that the user ID tioldap has been created using the guidelinespresented in 3.1.2 User IDs and passwords on page 30.

3. Insert the IBM Directory Server, 5.1 CD in the drive and start the setup.exelocated in the \ids_ismp folder to start the installation.

4. Select Language of choice for the installation process. English is set to

default.

5. The installation wizard starts the installation process click Next.

6. Accept the License Agreement by selecting I accept the terms in thelicense agreement option.

7. Because this installation process occurs in the IBM DB2 server machine, theinstall should detect that IBM DB2 is already installed.

8. Select the installation path. Ensure there are no spaces in the installation

path. We used C:\IBM\LDAP.9. Choose a language of choice for the IBM Directory Server. English is set to

default.

10.The Select the installation type window opens. Select the Custom Installoption.

11.The Select features window opens, as shown in next figure. Select thefollowing packages:

Client SDK Web Administration

Server IBM WebSphere Application Server - Express

Important: This implementation of LDAP can be in a shared environment butit will still need to have a dedicated LDAP ID (tioldap) created to service the

IBM Tivoli Intelligent ThinkDynamic Orchestrator application.

GSKit

Attention: If you are installing IBM D

Documents

IBM Tivoli Intelligent Think Dynamic Orchestra Tor Pre Proof-Of-Concept Cookbook for Business Partners Redp3830