7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
1/280
ibm.com/redbooks Redpaper
Composite ApplicationProvisioning with IBM TivoliProvisioning Manager V3.1
Morten Moeller
Understand the Tivoli Provisioning
Manager software model
Automate the creation of
virtualized resources
Control the
application clusters
Front cover
http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
2/280
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
3/280
Composite Application Provisioning with IBM TivoliProvisioning Manager V3.1
November 2006
International Technical Support Organization
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
4/280
Copyright International Business Machines Corporation 2006. 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 (November 2006)
This edition applies to Version 3, Release 1, Modification 03 of IBM Tivoli Provisioning Manager(product number 5724-L09) and IBM Tivoli Intelligent Orchestrator (product number 5724-L10).
This document created or updated on November 22, 2006.
Note: Before using this information and the product it supports, read the information in
Notices on page xvii.
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
5/280
Copyright IBM Corp. 2006. All rights reserved. iii
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
The objective of this workshop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
The technical environment of the workshop. . . . . . . . . . . . . . . . . . . . . . . . . . xxii
An outline of the exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Chapter 1. Exercise 1: Introducing the IBM Tivoli Intelligent Orchestrator
V3.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 The objective of this exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Verifying the Tivoli Intelligent Orchestrator operations . . . . . . . . . . . . . . . . 2
1.2.1 Verifying the Tivoli Intelligent Orchestrators operational status . . . . . 2
1.2.2 Logging in to the Tivoli Intelligent Orchestrator Server system. . . . . . 2
1.2.3 Verifying the connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.4 Starting the Tivoli Intelligent Orchestrator Server . . . . . . . . . . . . . . . . 5
1.2.5 Signing in to the Tivoli Intelligent Orchestrator console . . . . . . . . . . . 7
Chapter 2. Exercise 2: Preparing the environment . . . . . . . . . . . . . . . . . . 112.1 The objective of this exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2 Importing the IBM Software University automation packages. . . . . . . . . . 122.2.1 Importing the tcdriver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 3. Exercise 3: Discovering and configuring the data center
infrastructure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1 Setting up a NetView discovery policy . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.1.1 Shortcut: Defining the NetView discovery technology. . . . . . . . . . . . 17
3.1.2 Exercise: Creating the NetView discovery technology . . . . . . . . . . . 17
3.2 Discovering the servers and the network infrastructure . . . . . . . . . . . . . . 19
3.2.1 Shortcut: Executing a discovery technology . . . . . . . . . . . . . . . . . . . 203.2.2 Exercise: Discovering the resources. . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2.3 Viewing the discovered resources . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.2.4 Accepting and ignoring the changes. . . . . . . . . . . . . . . . . . . . . . . . . 24
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
6/280
iv Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
3.3 Defining the access points and the credentials . . . . . . . . . . . . . . . . . . . . . 26
3.3.1 Shortcut: Setting the credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3.2 Exercise: Defining the credentials. . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.4 Installing the Tivoli Common Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.4.1 Shortcut: Installing the Tivoli Common Agent . . . . . . . . . . . . . . . . . . 313.4.2 Exercise: Installing the Tivoli Common Agent. . . . . . . . . . . . . . . . . . 32
3.5 Discovering the server hardware and software . . . . . . . . . . . . . . . . . . . . . 37
3.5.1 Viewing the hardware resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.5.2 Viewing the software resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Chapter 4. Exercise 4: Configuring the SWU networking environment . . 414.1 The objective of this exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.1.1 Shortcut: Creating the network objects . . . . . . . . . . . . . . . . . . . . . . . 43
4.2 Defining the networking components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.2.1 Exercise: Defining the network objects . . . . . . . . . . . . . . . . . . . . . . . 44
4.3 Defining the virtual local area networks. . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.3.1 Exercise: Defining the virtual local area networks. . . . . . . . . . . . . . . 46
4.4 Defining the subnets and the switches . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.4.1 Exercise: Defining the subnets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.5 Switch definitions for the SWU environment . . . . . . . . . . . . . . . . . . . . . . . 48
4.5.1 Exercise: Defining a switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.6 Defining firewalls for the SWU environment . . . . . . . . . . . . . . . . . . . . . . . 50
4.6.1 Exercise: Defining a firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.7 Verifying the network infrastructure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Chapter 5. Exercise 5: Configuring the SWU provisioning infrastructure53
5.1 The objective of this exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.1.1 Shortcut: Boot server and file repository . . . . . . . . . . . . . . . . . . . . . . 55
5.2 Creating a simulated boot server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.2.1 Shortcut: Creating a boot server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.2.2 Exercise: Defining a boot server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.3 Defining the SWU_FileRepository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.3.1 Shortcut: Creating a file repository . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.3.2 Exercise: Defining a file repository . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.4 Verifying the provisioning infrastructure components . . . . . . . . . . . . . . . . 62
Chapter 6. Exercise 6: Preparing the software-related objects for thePristine systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6.1 The objective of this exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.1.1 Shortcut: Pristine pool, server template, and software . . . . . . . . . . . 67
6.2 The SWU Windows 2000 Server SP4 software definitions . . . . . . . . . . . . 69
6.2.1 Shortcut: Creating an operating system . . . . . . . . . . . . . . . . . . . . . . 69
6.2.2 Exercise: Defining the operating system. . . . . . . . . . . . . . . . . . . . . . 70
6.3 Importing the software objects for the installation of IBM Java Runtime
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
7/280
Contents v
Environment V1.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.3.1 Exercise: Importing the SWU IBM Java Runtime 1.4.1
software objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
6.4 Creating the SWU_Pristine_Server_Stack . . . . . . . . . . . . . . . . . . . . . . . . 79
6.4.1 Shortcut: Defining the SWU_Pristine_Server_Stack. . . . . . . . . . . . . 796.4.2 Exercise: Creating the SWU_Pristine_Server_Stack . . . . . . . . . . . . 80
6.5 Creating the SWU_Pristine_Server_Pool . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.5.1 Creating the SWU_Pristine_Server_Template . . . . . . . . . . . . . . . . . 85
6.5.2 Exercise: Creating the Pristine Server Template . . . . . . . . . . . . . . . 86
6.5.3 Shortcut: Defining the SWU_Pristine_Server_Pool . . . . . . . . . . . . . 87
6.5.4 Exercise: Creating the SWU_Pristine_Server_Pool . . . . . . . . . . . . . 88
6.6 Verifying the creation of the objects for the Pristine servers . . . . . . . . . . . 89
Chapter 7. Exercise 7: Creating virtual servers . . . . . . . . . . . . . . . . . . . . . 917.1 The objective of this exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
7.1.1 Shortcut: Creating the host platform server and the Virtual Server
Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
7.2 Creating a host platform server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
7.2.1 Shortcut: Creating the host platform server . . . . . . . . . . . . . . . . . . . 97
7.2.2 Exercise: Defining the host platform server . . . . . . . . . . . . . . . . . . . 98
7.3 Creating the server template for the operating system installation . . . . . 102
7.3.1 Shortcut: Creating the SWU_New_Windows_Server_Template . . 103
7.3.2 Exercise: Defining the SWU_New_Windows_Server_Template . . 1037.4 Creating the Virtual Server Template . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
7.4.1 Shortcut: Creating the Virtual Server Template . . . . . . . . . . . . . . . 107
7.4.2 Exercise: Defining the Virtual Server Template . . . . . . . . . . . . . . . 108
7.5 Creating the virtual servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
7.5.1 Shortcut: Creating the virtual servers . . . . . . . . . . . . . . . . . . . . . . . 111
7.5.2 Exercise: Defining the virtual servers . . . . . . . . . . . . . . . . . . . . . . . 111
7.6 Verifying the creation of the virtual servers . . . . . . . . . . . . . . . . . . . . . . . 114
Chapter 8. Exercise 8: Defining the composite application infrastructureenvironment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
8.1 The objective of this exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
8.1.1 Shortcut: Creating all the infrastructure software objects . . . . . . . . 122
8.2 Creating the SWU_DB2_Server_Stack. . . . . . . . . . . . . . . . . . . . . . . . . . 123
8.2.1 Shortcut: Creating the DB2 software definitions and the
SWU_DB2_Server_Stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
8.2.2 Exercise: Creating a software definition for the DB2 Server using the
wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1248.2.3 Exercise: Creating a software stack . . . . . . . . . . . . . . . . . . . . . . . . 132
8.3 Creating the SWU_WAS_Server_Stack . . . . . . . . . . . . . . . . . . . . . . . . . 134
8.3.1 Shortcut: Create WebSphere Application Server software definitions
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
8/280
vi Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
and SWU_WAS_Server_Stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
8.4 Creating software definitions for the application server. . . . . . . . . . . . . . 136
8.4.1 Exercise: Manually creating the application layer software objects 136
8.5 Creating the software definitions for the database client. . . . . . . . . . . . . 140
8.6 Creating a software stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1448.7 Creating the SWU_HTTP_Server_Stack . . . . . . . . . . . . . . . . . . . . . . . . 145
8.7.1 Shortcut: Creating the SWU_HTTP_Server_Stack. . . . . . . . . . . . . 146
8.7.2 Exercise: Defining the SWU_HTTP_Server_Stack. . . . . . . . . . . . . 146
8.8 Installing the prerequisite software on the host platform server . . . . . . . 149
8.8.1 Shortcut: Installing the software on the SWU_HostPlatformServer 149
8.8.2 Exercise: Installing the SWU IBM Java Runtime Environment and
registering the SWU IBM Hypertext Transfer Protocol Server . . . . 150
8.9 Verifying the infrastructure software definitions. . . . . . . . . . . . . . . . . . . . 158
Chapter 9. Exercise 9: Defining the composite application software . . 1619.1 The objective of this exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
9.1.1 Shortcut: Creating all the composite application software objects . 164
9.2 Creating the SWU_Composite_Database_Stack . . . . . . . . . . . . . . . . . . 165
9.2.1 Shortcut: Creating the composite application database layer software
definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
9.2.2 Exercise: Creating the SWU Composite Database Module software
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
9.3 Exercise: Creating the software stack. . . . . . . . . . . . . . . . . . . . . . . . . . . 1719.4 Reviewing the SWU_Composite_Application_Stack. . . . . . . . . . . . . . . . 173
9.5 Creating the SWU_Composite_Application_Stack . . . . . . . . . . . . . . . . . 175
9.5.1 Shortcut: Creating the composite application layer
software definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
9.5.2 Exercise: Manually defining the application layer software objects 176
9.6 Reviewing the SWU_Composite_Application_Stack. . . . . . . . . . . . . . . . 177
9.7 Creating the SWU_Composite_Web_Stack . . . . . . . . . . . . . . . . . . . . . . 178
9.7.1 Shortcut: Creating the composite application Web layer software
definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
9.7.2 Exercise: Manually defining the composite application Web layer
software objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
9.8 Reviewing the SWU_Composite_Web_Stack. . . . . . . . . . . . . . . . . . . . . 180
9.8.1 The software product: SWU Composite Web Module. . . . . . . . . . . 180
9.8.2 The software package: SWU Composite Web Module Server
Configuration Installable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
9.8.3 The software package: SWU Composite Web Module Server Pages
Installable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1859.8.4 The SWU_Composite_Web_Stack. . . . . . . . . . . . . . . . . . . . . . . . . 186
9.9 Verifying the infrastructure software definitions. . . . . . . . . . . . . . . . . . . . 187
9.10 Exercise: Installing the SWU composite software products . . . . . . . . . 187
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
9/280
Contents vii
Chapter 10. Exercise 10: Defining the composite application load balancerand the virtual IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
10.1 The objective of this exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
10.1.1 Shortcut: Creating a load balancer and a virtual IP. . . . . . . . . . . . 196
10.2 Defining and initializing the SWU_LoadBalancer . . . . . . . . . . . . . . . . . 197
10.2.1 Shortcut: Creating the load balancer. . . . . . . . . . . . . . . . . . . . . . . 198
10.2.2 Exercise: Defining the load balancer. . . . . . . . . . . . . . . . . . . . . . . 199
10.3 Adding the www.swu.com virtual IP to the load balancer . . . . . . . . . . . 201
10.3.1 Shortcut: Creating a virtual IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
10.3.2 Exercise: Defining a virtual IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
10.4 Verifying the load balancer configuration . . . . . . . . . . . . . . . . . . . . . . . 203
Chapter 11. Exercise 11: Defining the SWU composite application
production environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20711.1 The objective of this exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
11.1.1 Shortcut: Creating composite application tiers and templates . . . 209
11.2 Creating a customer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
11.2.1 Exercise: Defining the SWU_Customer . . . . . . . . . . . . . . . . . . . . 210
11.3 Creating an application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
11.3.1 Exercise: Defining the SWU_Composite_Application . . . . . . . . . . 211
11.4 Creating the application tier for the database layer. . . . . . . . . . . . . . . . 212
11.4.1 Exercise: Defining the SWU_Composite_Database_Tier . . . . . . . 212
11.4.2 Exercise: Defining the SWU_Composite_Database_Template . . 21311.5 Creating the tier for the application layer. . . . . . . . . . . . . . . . . . . . . . . . 215
11.5.1 Exercise: Defining the SWU_Composite_Application_Template . 216
11.5.2 Exercise: Defining the SWU_Composite_Application Tier . . . . . . 216
11.6 Creating the tier for the Web layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
11.6.1 Exercise: Defining the SWU_Composite_Web_Tier . . . . . . . . . . . 217
11.6.2 Exercise: Defining the SWU_Composite_Web_Template . . . . . . 218
11.6.3 Verifying the production environment . . . . . . . . . . . . . . . . . . . . . . 220
Chapter 12. Exercise 12: Defining the cluster domain for the Web layer22312.1 The objective of this exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
12.2 Creating the cluster domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
12.2.1 Shortcut: Creating the cluster domain. . . . . . . . . . . . . . . . . . . . . . 227
12.3 Defining the SWU_Composite_VIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
12.3.1 Shortcut: Creating the cluster domain virtual IP . . . . . . . . . . . . . . 228
12.3.2 Exercise: Defining the cluster domain virtual IP . . . . . . . . . . . . . . 229
12.4 Creating the cluster domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
12.4.1 Shortcut: Creating the cluster domain. . . . . . . . . . . . . . . . . . . . . . 229
12.4.2 Exercise: Defining the SWU_Composite_Web_ClusterDomain . . 230
12.5 Verifying the cluster domain definition. . . . . . . . . . . . . . . . . . . . . . . . . . 231
12.5.1 Exercise: Verifying the cluster domain definitions. . . . . . . . . . . . . 231
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
10/280
viii Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
Chapter 13. Exercise 13: Deploying the composite application . . . . . . . 23513.1 The objective of this exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
13.2 Deploying the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
13.2.1 Exercise: Changing the maintenance mode . . . . . . . . . . . . . . . . . 236
13.2.2 Exercise: Viewing the recommendations . . . . . . . . . . . . . . . . . . . 237
13.2.3 Exercise: Setting the operation mode for a tier . . . . . . . . . . . . . . . 237
13.2.4 Exercise: Using the automatic operation mode. . . . . . . . . . . . . . . 238
13.2.5 Exercise: Using the semiautomatic operation mode. . . . . . . . . . . 241
13.2.6 Exercise: Using the manual operation mode . . . . . . . . . . . . . . . . 243
Appendix A. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
System requirements for downloading the Web material . . . . . . . . . . . . . 250How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
11/280
Copyright IBM Corp. 2006. All rights reserved. ix
Figures
1-1 Starting VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1-2 The SWU2006-3759 VMware image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1-3 The SWU2006-3759 desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1-4 Starting the Tivoli Intelligent Orchestrator using TIO_Start. . . . . . . . . . . . . 5
1-5 Opening the Services window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1-6 Signing in to the Tivoli Intelligent Orchestrator . . . . . . . . . . . . . . . . . . . . . . 7
1-7 The Tivoli Intelligent Orchestrator console . . . . . . . . . . . . . . . . . . . . . . . . . 8
1-8 The Tivoli Intelligent Orchestrator help environment. . . . . . . . . . . . . . . . . 10
2-1 SWU workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133-1 The tutorial logical networking infrastructure. . . . . . . . . . . . . . . . . . . . . . . 15
3-2 Defining the discovery technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3-3 NetView discovery technology policies . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3-4 Running NetView discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3-5 NetView discovery task execution confirmation . . . . . . . . . . . . . . . . . . . . 21
3-6 NetView discovery successful execution . . . . . . . . . . . . . . . . . . . . . . . . . 22
3-7 The network resources discovered by NetView . . . . . . . . . . . . . . . . . . . . 23
3-8 Changes discovered by NetView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3-9 Discovered subnets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253-10 Subnet change accepted and defined to the DCM . . . . . . . . . . . . . . . . . 25
3-11 Discovered resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3-12 Creating an SSH host service access point . . . . . . . . . . . . . . . . . . . . . . 28
3-13 Adding RSA credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3-14 New RSA authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3-15 Service Access Point device driver associations . . . . . . . . . . . . . . . . . . 29
3-16 Setting default access points for standard operations . . . . . . . . . . . . . . 30
3-17 Defining the client service access point . . . . . . . . . . . . . . . . . . . . . . . . . 303-18 Service access points required to communicate with a server using SSH31
3-19 Selecting targets for the Tivoli Common Agent installation. . . . . . . . . . . 33
3-20 Defining credentials for the Common Agent installation . . . . . . . . . . . . . 34
3-21 Common Agent Installation summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3-22 Common Agent installation task running. . . . . . . . . . . . . . . . . . . . . . . . . 35
3-23 Searching for objects by name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3-24 Tivoli Common Agent variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3-25 Tivoli Common Agent credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3-26 The discovered network interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383-27 The discovered hardware resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3-28 Hardware resource details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3-29 The discovered software resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
12/280
x Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
4-1 Networking exercise: Starting and ending environments . . . . . . . . . . . . . 42
4-2 VLAN definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4-3 Subnet definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4-4 Blocking the IP ranges for the subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4-5 Subnet inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4-6 Adding a switch definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4-7 Assigning router capabilities to a switch . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4-8 Switch interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4-9 Adding a switch that will host the firewall . . . . . . . . . . . . . . . . . . . . . . . . . 51
4-10 Switch interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4-11 SWU tutorial network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5-1 Provisioning infrastructure implementation: Starting and ending
environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5-2 Defining a boot server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575-3 Boot server interface parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5-4 Boot server device driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5-5 File repository properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5-6 File repository interface parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5-7 File repository device driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5-8 Verifying boot server creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
5-9 Verifying file repository creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6-1 Software preparation: Starting point and goal. . . . . . . . . . . . . . . . . . . . . . 64
6-2 Virtual server: Basic software components. . . . . . . . . . . . . . . . . . . . . . . . 65
6-3 SWU Windows 2000 Server SP4 software image properties . . . . . . . . . . 70
6-4 SWU Windows 200 Server SP4 OS properties. . . . . . . . . . . . . . . . . . . . . 71
6-5 Linking the SWU Windows 2000 SP4 image to the operating system . . . 71
6-6 SWU Windows 2000 SP4 operating system installables . . . . . . . . . . . . . 71
6-7 SWU 2000 Server SP4 OS capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6-8 SWU Windows 2000 SP4 OS capability summary . . . . . . . . . . . . . . . . . . 73
6-9 Categorizing the SWU Windows 2000 SP4 OS . . . . . . . . . . . . . . . . . . . . 73
6-10 SWU Windows 2000 Server SP4 installation template . . . . . . . . . . . . . . 746-11 Pristine software resource template . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6-12 Creating a template parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6-13 Software resource template with parameters . . . . . . . . . . . . . . . . . . . . . 75
6-14 Creating a software stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6-15 Adding predefined requirement values . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6-16 IBM Java Runtime V1.4.1 software components . . . . . . . . . . . . . . . . . . 77
6-17 The SWU_Pristine_Server_Stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6-18 Searching for software definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6-19 Selecting a software resource template when adding a stack entry . . . . 816-20 Software stack entry with customized parameters . . . . . . . . . . . . . . . . . 82
6-21 Software stack with one software definition . . . . . . . . . . . . . . . . . . . . . . 82
6-22 Software stack with multiple entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
13/280
Figures xi
6-23 Adding an iterator to the software stack . . . . . . . . . . . . . . . . . . . . . . . . . 84
6-24 Creating the SWU_Pristine_Server_Template . . . . . . . . . . . . . . . . . . . . 86
6-25 Associating a software stack to a template. . . . . . . . . . . . . . . . . . . . . . . 86
6-26 SWU_Pristine_Server_Template properties . . . . . . . . . . . . . . . . . . . . . . 87
6-27 Creating the SWU_Pristine_Server_Pool . . . . . . . . . . . . . . . . . . . . . . . . 88
6-28 Listing the SWU_Pristine objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
7-1 Virtual server creation: Starting and ending environments . . . . . . . . . . . . 93
7-2 Creating a host platform server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
7-3 Host platform server: Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
7-4 Host platform server: Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
7-5 Host platform server: Management interface . . . . . . . . . . . . . . . . . . . . . . 99
7-6 Host platform server: Shared NIC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
7-7 Associating the OS with the host platform server . . . . . . . . . . . . . . . . . . 101
7-8 Host platform server: Software properties. . . . . . . . . . . . . . . . . . . . . . . . 1017-9 Host platform server: Device driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
7-10 Creating a new server template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
7-11 Assigning VLAN to the server template . . . . . . . . . . . . . . . . . . . . . . . . 104
7-12 Associate subnet with VLAN in server template . . . . . . . . . . . . . . . . . . 104
7-13 The server template interface definitions . . . . . . . . . . . . . . . . . . . . . . . 105
7-14 Adding the software stack to the server template . . . . . . . . . . . . . . . . . 105
7-15 Server template properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
7-16 The server template device driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
7-17 Virtual Server Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087-18 Virtual Server Template properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
7-19 Adding resource requirements to the Virtual Server Template . . . . . . . 109
7-20 Virtual Server Template with new resource requirements . . . . . . . . . . 109
7-21 Virtual Server Template variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
7-22 Creating a new virtual server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
7-23 Virtual server inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
7-24 Virtual servers hosted by the SWU_HostPlatformServer . . . . . . . . . . . 114
7-25 Servers (virtual) in the SWU_Pristine_Server_Pool . . . . . . . . . . . . . . . 1157-26 Virtual server hardware properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
7-27 Virtual server software associations . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
8-1 Application infrastructure implementation: Starting and
ending environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
8-2 SWU_DB2_Server_Stack software components . . . . . . . . . . . . . . . . . . 123
8-3 Import Software Package: Welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
8-4 Import Software Package: Define Software Product. . . . . . . . . . . . . . . . 125
8-5 Import Software Package: Select Package. . . . . . . . . . . . . . . . . . . . . . . 125
8-6 Import Software Package: Choose Installation Method . . . . . . . . . . . . . 1268-7 Import Software Package: Fill properties . . . . . . . . . . . . . . . . . . . . . . . . 126
8-8 Import Software Package: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
8-9 SWU Software Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
14/280
xii Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
8-10 SWU IBM DB2 Server V8.2 capabilities . . . . . . . . . . . . . . . . . . . . . . . . 128
8-11 SWU IBM DB2 Server 8.2 properties . . . . . . . . . . . . . . . . . . . . . . . . . . 129
8-12 SWU IBM DB2 Server 8.2 requirements definitions . . . . . . . . . . . . . . . 130
8-13 SWU IBM DB2 Server 8.2 requirements. . . . . . . . . . . . . . . . . . . . . . . . 130
8-14 SWU IBM DB2 Server V8.2 properties . . . . . . . . . . . . . . . . . . . . . . . . . 131
8-15 Creating the SWU_DB2_Server_Stack. . . . . . . . . . . . . . . . . . . . . . . . . 132
8-16 SWU_DB2_Server_Stack properties . . . . . . . . . . . . . . . . . . . . . . . . . . 133
8-17 SWU_WAS_Server_Stack software components. . . . . . . . . . . . . . . . . 134
8-18 Creating the SWU IBM WebSphere Application Server
software product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
8-19 SWU IBM WebSphere Application Server V5.1 capabilities . . . . . . . . . 137
8-20 Associating a software installable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
8-21 Defining a new requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
8-22 Adding a Configuration Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1398-23 Resource templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
8-24 The SWU WebSphere Application Server software stack . . . . . . . . . . 144
8-25 SWU_HTTP_Server_Stack software components . . . . . . . . . . . . . . . . 145
8-26 SWU IBM HTTP Server V2.0 configuration templates . . . . . . . . . . . . . 147
8-27 Using external references in a software resource template . . . . . . . . . 148
8-28 SWU_HostPlatformServer software inventory . . . . . . . . . . . . . . . . . . . 150
8-29 Initializing a software installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
8-30 Software installation: Select Software. . . . . . . . . . . . . . . . . . . . . . . . . . 151
8-31 Software installation: Select Configuration Template . . . . . . . . . . . . . . 1528-32 Software installation: Customize Template . . . . . . . . . . . . . . . . . . . . . . 152
8-33 Software installation: Select Targets. . . . . . . . . . . . . . . . . . . . . . . . . . . 153
8-34 Software installation: Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
8-35 Software installation: Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
8-36 Software installation: Task Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
8-37 Software installation: Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
8-38 Registering the software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
8-39 Software inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1578-40 SWU_HostPlatformServer infrastructure software inventory . . . . . . . . 158
8-41 Virtual servers hardware inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
9-1 Composite application components: Starting and ending environments 162
9-2 Composite application software components . . . . . . . . . . . . . . . . . . . . . 163
9-3 SWU_Composite_Database_Stack logical structure . . . . . . . . . . . . . . . 165
9-4 SWU_Composite_Database_Stack properties . . . . . . . . . . . . . . . . . . . . 172
9-5 SWU_Composite_Application_Stack structure . . . . . . . . . . . . . . . . . . . . 173
9-6 SWU Composite Database Installation SRT. . . . . . . . . . . . . . . . . . . . . . 174
9-7 SWU_Composite_Application_Stack logical layout . . . . . . . . . . . . . . . . 1759-8 The SWU_Composite_Application_Stack. . . . . . . . . . . . . . . . . . . . . . . . 177
9-9 SWU_Composite_Web_Stack logical layout . . . . . . . . . . . . . . . . . . . . . 178
9-10 SWU Composite Web Module requirements and capabilities. . . . . . . . 181
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
15/280
Figures xiii
9-11 SWU HTTP Installation with PlantsByWebSphere Instance configuration
template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
9-12 SWU Composite Web server installables . . . . . . . . . . . . . . . . . . . . . . . 183
9-13 SWU Composite Web Module Server Configuration
Installable properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
9-14 SWU Composite Web Module Server Configuration Installable device
driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
9-15 Updating interface properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
9-16 Making an interface managed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
9-17 SWU_HostPlatformServer software inventory . . . . . . . . . . . . . . . . . . . 189
9-18 Sample Web page provisioned by Tivoli Intelligent Orchestrator . . . . . 190
9-19 Removing the SWU Composite Application Module installation. . . . . . 191
10-1 Load balancer and virtual IP definition: Starting and
ending environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19410-2 Load-balanced network infrastructure. . . . . . . . . . . . . . . . . . . . . . . . . . 195
10-3 Defining a new SWU_LoadBalancer. . . . . . . . . . . . . . . . . . . . . . . . . . . 199
10-4 SWU_LoadBalancer interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
10-5 Initializing the Load Balancer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
10-6 Adding a virtual IP to RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
10-7 AddVIPtoRIP task execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
10-8 Load balancer with virtual IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
10-9 Connect to load balancer host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
10-10 Select the load balancer host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20410-11 Load balancer properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
11-1 Defining the production environments starting and ending points . . . . 208
11-2 Defining the SWU_Customer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
11-3 SWU_Composite Application properties. . . . . . . . . . . . . . . . . . . . . . . . 211
11-4 The SWU_Database_Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
11-5 Server template for the SWU_Database_Tier. . . . . . . . . . . . . . . . . . . . 213
11-6 Adding an NIC to the template VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . 214
11-7 Associating the new interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21411-8 Associating a software stack to the tier template . . . . . . . . . . . . . . . . . 214
11-9 The SWU_Composite_Database_Template. . . . . . . . . . . . . . . . . . . . . 215
11-10 Associating a server template with a tier. . . . . . . . . . . . . . . . . . . . . . . 218
11-11 Supplying an application VIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
11-12 SWU_Composite_Application properties . . . . . . . . . . . . . . . . . . . . . . 220
11-13 Application infrastructure overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
12-1 Cluster domain definition: Starting and ending environments. . . . . . . . 224
12-2 Clustering the network infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . 225
12-3 Defining the cluster domain virtual IP . . . . . . . . . . . . . . . . . . . . . . . . . . 22912-4 Adding a cluster domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
12-5 Initializing the cluster domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
12-6 Removing a server from a cluster domain . . . . . . . . . . . . . . . . . . . . . . 232
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
16/280
xiv Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
12-7 Linking a cluster domain to an application tier . . . . . . . . . . . . . . . . . . . 232
13-1 Recommendations for the SWU_Composite_Application. . . . . . . . . . . 237
13-2 Changing the operation mode of an application tier . . . . . . . . . . . . . . . 238
13-3 Server deployment in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
13-4 Successful deployment of a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
13-5 Server assigned to SWU_Composite_Database_Tier . . . . . . . . . . . . . 240
13-6 Deployed server interface properties . . . . . . . . . . . . . . . . . . . . . . . . . . 240
13-7 Deployed server software inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
13-8 Accepting the deployment recommendations . . . . . . . . . . . . . . . . . . . . 241
13-9 Tracking the semiautomated deployment . . . . . . . . . . . . . . . . . . . . . . . 242
13-10 Server deployed to the SWU_Composite_Application_Tier . . . . . . . . 242
13-11 Deploying servers manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
13-12 Manual deployment of two servers in progress. . . . . . . . . . . . . . . . . . 243
13-13 Server inventory during deployment . . . . . . . . . . . . . . . . . . . . . . . . . . 24413-14 Datacenter overview with servers deployed . . . . . . . . . . . . . . . . . . . . 245
13-15 Deployed cluster resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
13-16 Starting and stopping the cluster resources . . . . . . . . . . . . . . . . . . . . 246
13-17 SWU_Composite_Application server allocation . . . . . . . . . . . . . . . . . 247
13-18 Deprovisioning servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
17/280
Copyright IBM Corp. 2006. All rights reserved. xv
Tables
3-1 NetView discovery technology variables. . . . . . . . . . . . . . . . . . . . . . . . . . 183-2 Password credentials for the SWU environment. . . . . . . . . . . . . . . . . . . . 33
4-1 Networking properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6-1 SWU Windows 2000 SP4 OS capabilities . . . . . . . . . . . . . . . . . . . . . . . . 72
6-2 IBM JRE V1.4.1 software resource templates . . . . . . . . . . . . . . . . . . . . . 79
8-1 SWU IBM DB2 Server 8.2 capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . 128
8-2 SWU IBM WebSphere Application Server V5.1 capabilities . . . . . . . . . . 137
8-3 DB2 Client configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
8-4 HTTP Server configuration templates and their intended use . . . . . . . . 1479-1 SWU Composite Database Module software product definition . . . . . . . 167
9-2 SWU Composite Database software package definition. . . . . . . . . . . . . 168
9-3 SWU Composite Database software resource template definition . . . . . 169
10-1 SWU_LoadBalancer variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
10-2 Virtual IP variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
11-1 SWU_Database_Tier properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
11-2 SWU_Composite_Application_Template properties. . . . . . . . . . . . . . . 216
11-3 SWU_Composite_Application_Tier properties . . . . . . . . . . . . . . . . . . . 216
11-4 SWU_Composite_Web_Tier properties . . . . . . . . . . . . . . . . . . . . . . . . 21711-5 SWU_Composite_Web_Template properties . . . . . . . . . . . . . . . . . . . . 218
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
18/280
xvi Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
19/280
Copyright IBM Corp. 2006. All rights reserved. xvii
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 licenseinquiries, 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 suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, 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 cer tain 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 maymake 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 confirmthe 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 illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing applicationprograms 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.
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
20/280
xviii Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both:
DB2
DB2 Universal DatabaseeServer
IBM
ibm.com
NetViewpSeries
Redbooks
Redbooks (logo)
TivoliWebSphere
zSeries
The following terms are trademarks of other companies:
Enterprise JavaBeans, Java, JavaBeans, JDBC, JRE, and all Java-based trademarks are trademarks ofSun Microsystems, Inc. in the United States, other countries, or both.
Internet Explorer, Windows Server, Windows, and the Windows logo are trademarks of MicrosoftCorporation in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
21/280
Copyright IBM Corp. 2006. All rights reserved. xix
Preface
This IBM Redpaper reproduces the Exercise Guide that was a part of athree-hour workshop on introducing IBM Provisioning Composite Applicationsusing IBM Tivoli Provisioning Manager V3.1 delivered at the IBM 2006
Software University.
By reading through and performing these exercises, you get a quick, self-paced
introduction to the Tivoli Provisioning Manager concepts. You also gain insightinto the software model and the cluster management functions of the Tivoli
Provisioning Manager V3.1.
Throughout this tutorial, references are made to scripts and workflows that weremade available to the students during the workshop. You can download these
resources from the World Wide Web. For more details, refer to Appendix A,Additional material on page 249.
The intent of publishing this workshop material, originally intended for a "live"audience, is to demonstrate the key capabilities of Tivoli Provisioning Managerand provide examples on how to design and develop workflows and automation
packages to support the automation of particular steps in the server provisioningprocess.
The objective of this workshop
The objective of this tutorial is to transform a stand-alone system containing anembedded virtual VMware-based IBM Tivoli Intelligent Orchestrator server
system into a provisioning environment that is capable of automatically
provisioning and deprovisioning a composite application infrastructure, includingmultiple, clustered instances of the IBM Hypertext Transfer Protocol (HTTP)Server hosted on virtual servers, in order to support the varying demands for
application-hosting resources.
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
22/280
xx Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
Figure 1 shows the end result of completing this tutorial successfully.
Figure 1 An overview of the tutorial
As you complete the individual exercises in this tutorial, you gradually build all
the Tivoli Intelligent Orchestrator infrastructure components required to createthe provisioning environment.
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
23/280
Preface xxi
The model composite application, which is the target of this tutorial, is astandard, three-layered application system that is made up of a Web layer, an
application layer, and a database layer (Figure 2).
Figure 2 Sample architecture of a composite application
Because of the restrictions present in a tutorial environment, most of theresources used to implement the composite application are simulated. However,
the software implementation of a load balancer and the implementation of theWeb servers is provided in order to allow you to realize that a subset of theprovisioning operations actually performs tasks that are similar to that seen in a
production environment.
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
24/280
xxii Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
The technical environment of the workshop
The environment required to complete this workshop is depicted in Figure 3.
Figure 3 The SWU tutorial environment
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
25/280
Preface xxiii
In addition, the SWU_2006.tcdriver and the ITSO_Utilities.tcdriver files requiredto complete this tutorial have been loaded on the desktop in the Tivoli Intelligent
Orchestrator (TIO) Server system.
An outline of the exercises
When you perform the exercises in this tutorial, you will become acquainted withthe tasks that must be performed to set up the automated provisioning of acomposite application from the beginning. The exercises described in this
workshop cover the following main areas:
Introduction and setup: Exercise 1 and Exercise 2
Building the provisioning infrastructure: Exercise 3 - 7
Defining the composite application components: Exercise 8 - 10
Defining the components for on-demand provisioning: Exercise 11 and
Exercise 12
Deploying the composite application: Exercise 13
Important: If you plan to set up an environment similar to that described in
this IBM Redpaper, follow these guidelines:
Ensure that IP names are used throughout the configuration of IBM DB2,IBM Directory Server, and Tivoli Intelligent Orchestrator.
Before reinit, ensure that the IP address of the Tivoli Intelligent
Orchestrator Server corresponds to the value of the IP Address parameterin the %TIO_Home%\xml\tpmserver.xml file, and that a blocked range
statement is added to the subnetwork definition in the tpmserver.xml file.This statement must be similar to:
Ensure host name resolution in the hosts file
Set c:\cygwin\bin as the first directory of the PATH on all the systems
If Edge Server - Load Balancer is installed, add the following two lines at
the beginning of the %systemroot%\system32\dscontrol.cmd file:
set path=%SYSTEMROOT%;%SYSTEMROOT%\system32;%PATH%set IBMLBPATH="C:\ibm\edge\lb"
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
26/280
xxiv Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
Following is a brief outline of each of the exercises:
Exercise 1: Introducing the IBM Tivoli Intelligent Orchestrator V3.1
This includes starting the Tivoli Intelligent Orchestrator, verifying the
operation, logging in, and becoming acquainted with the user interface
Exercise 2: Preparing the environment on page 11
This includes importing and verifying the tutorial-specific files
Exercise 3: Discovering and configuring the data center infrastructure onpage 15 (optional)
This includes using the Tivoli Intelligent Orchestrators discovery functions to
populate the data center model
Exercise 4: Configuring the SWU networking environment on page 41
This includes defining the virtual local area networks (VLANs), subnets,
switches, and other networking objects
Exercise 5: Configuring the SWU provisioning infrastructure on page 53
This includes defining the supporting resources such as boot servers and file
repositories
Exercise 6: Preparing the software-related objects for the Pristine systems
on page 63
This includes defining the basic software objects for the operating system(OS) and the Java Runtime Environment (JRE), and creating the server
templates for the Pristine systems
Exercise 7: Creating virtual servers on page 91
This includes defining the host platform server and creating the virtual servers
Exercise 8: Defining the composite application infrastructure environment on
page 119
This includes creating software objects for the IBM HTTP Server, the IBMWebSphere Server, and the IBM DB2 Server
Exercise 9: Defining the composite application software on page 161
This includes creating and verifying the software objects for the compositeapplication modules
Exercise 10: Defining the composite application load balancer and the virtualIP on page 193
This includes defining the load balancing setup for the composite application
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
27/280
Preface xxv
Exercise 11: Defining the SWU composite application productionenvironment on page 207
This includes defining the composite application structure for Tivoli Intelligent
Orchestrator and creating the server templates for each layer
Exercise 12: Defining the cluster domain for the Web layer on page 223This includes defining and verifying the cluster domain definitions for the
application layer
Exercise 13: Deploying the composite application on page 235
This includes performing and verifying provisioning
Throughout this tutorial, shortcuts (automated procedures to accomplish the
objectives of an exercise) are provided to help you easily complete the exercises
that focus on the topics you have already mastered.
Become a published author
Join us for a two-week to six-week residency program! Help write an IBM
Redbook dealing with specific products or solutions, while getting hands-onexperience with leading-edge technologies. You will have the opportunity to teamwith IBM technical professionals, business partners, and clients.
Your efforts will help increase product acceptance and customer satisfaction. Asa bonus, you will 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 aboutthis IBM Redpaper or other IBM Redbooks in one of the following ways:
Use the online Contact us review IBM Redbook form found at:
ibm.com/redbooks
Send your comments in an e-mail to:
http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.html7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
28/280
xxvi Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
Mail your comments to:
IBM Corporation, International Technical Support OrganizationDept. HYTD Mail Station P099
2455 South RoadPoughkeepsie, NY 12601-5400
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
29/280
Copyright IBM Corp. 2006. All rights reserved. 1
Chapter 1. Exercise 1: Introducing theIBM Tivoli Intelligent
Orchestrator V3.1
This exercise helps you to become familiar with the exercises environment and
teaches you about how to start the Tivoli Intelligent Orchestrator (TIO) Server.
1
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
30/280
2 Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
1.1 The objective of this exercise
The objective of this exercise is to help you verify the operational status of the
Tivoli Intelligent Orchestrator Server, sign in, and become familiar with the user
interface.
After you complete this exercise, the Tivoli Intelligent Orchestrator Server is
started, and you can log in to the Tivoli Intelligent Orchestrator user interface,and perform basic navigation in the user interface.
1.2 Verifying the Tivoli Intelligent Orchestratoroperations
Before starting the exercises, verify whether the Tivoli Intelligent Orchestrator isrunning on your system, and whether it is configured correctly. The following
exercises are designed to help you accomplish this.
1.2.1 Verifying the Tivoli Intelligent Orchestrators operational status
To start the Tivoli Intelligent Orchestrator Server that is hosted on the
SWU2006-3759 VMware image (where SWU stands for IBM SoftwareUniversity), open the VMware image from the task bar in your tutorial system.
VMware must start automatically in the tutorial machine that is running the localWindows OS, and the SWU2006-3759 image must already be running.
1.2.2 Logging in to the Tivoli Intelligent Orchestrator Server system
To log in to the Tivoli Intelligent Orchestrator Server system hosted by theVMware SWU2006-3759 image, perform the following tasks:
1. Open the VMware application from the task bar at the bottom of your windowby double-clicking the VMware Workstation icon (Figure 1-1).
Figure 1-1 Starting VMware
If the VMware application is not displayed in the window, click it in the task
bar to maximize it.
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
31/280
Chapter 1. Exercise 1: Introducing the IBM Tivoli Intelligent Orchestrator V3.1 3
2. The VMware image for the tutorial exercises runs in the VMware application.There is only one tab, SWU2006-3759, in the VMware application window, as
shown in Figure 1-2. Click the SWU2006-3759 tab to get to the TIOServersystem.
Figure 1-2 The SWU2006-3759 VMware image
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
32/280
4 Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
3. Press Ctrl+Alt+Insert (instead of Ctrl+Alt+Delete) to log in to the TIOServer astioadmin with the password smartway, if you have not logged in already. Afteryou log in, the desktop of the TIOServer system must be visible (Figure 1-3).
Figure 1-3 The SWU2006-3759 desktop
1.2.3 Verifying the connectivity
Now that you have successfully logged in to the Tivoli Intelligent OrchestratorServer system, verify the connectivity between the tutorial system and the Tivoli
Intelligent Orchestrator Server system by performing the following tasks:
1. From the Tivoli Intelligent Orchestrator Server command line, issue thefollowing command:
ping .tivdemo.com
V if h th th b l d d h th th h t t
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
33/280
Chapter 1. Exercise 1: Introducing the IBM Tivoli Intelligent Orchestrator V3.1 5
Verify whether the name can be resolved, and whether the host systemserver responds. The address of the host system server is expected to be
192.168.1.21.
Repeat the process using the IP name of tioserver.tivdemo.com and verifywhether your Tivoli Intelligent Orchestrator Server can resolve its own name.
The address of the TIOServer is expected to be 192.168.1.1.
2. From the command line on the host system, issue the following command:
ping hostsystem.tivdemo.com
Verify whether the name can be resolved, and whether the host system
server responds. The address of the host system server is expected to be192.168.1.21.
Repeat the process using the IP name of tioserver.tivdemo.com and verify
whether the host system can resolve the name of the Tivoli IntelligentOrchestrator server. The address of the TIOServer is expected to be192.168.1.1.
3. Issue the exit command to close the command line.
1.2.4 Starting the Tivoli Intelligent Orchestrator Server
To start the Tivoli Intelligent Orchestrator server, perform the following tasks:
1. Click the SWU2006-3759 tab on the VMware application window to go to theTivoli Intelligent Orchestrator Server system.
2. Double-click the TIO_Start icon on the Tivoli Intelligent Orchestrator Serverdesktop to start the Tivoli Intelligent Orchestrator. TIO_Start is a batch file that
invokes a script to start the IBM WebSphere Application Server and the TivoliIntelligent Orchestrator services, including the Web application, the
deployment engine, and the policy engines. The TIO_Start window isdisplayed. It takes a few minutes for the Tivoli Intelligent Orchestrator to start
(Figure 1-4).
Figure 1-4 Starting the Tivoli Intelligent Orchestrator using TIO_Start
a When waiting for the TIO Start process to be completed click the Service
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
34/280
6 Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
a. When waiting for the TIO_Start process to be completed, click the Serviceicon in the task bar of the Tivoli Intelligent Orchestrator Server or select
Start ProgramsAdministrative ToolsServices to open theServices window (Figure 1-5).
Figure 1-5 Opening the Services window
b. Scroll down the list of services that are installed. Note that DB2-DB2 andIBM Tivoli Directory Server V5.2 (also known as LDAP) services are
automatically started when the system is started. These are theprerequisite software for the Tivoli Intelligent Orchestrator. Additionally,
note that IBM WebSphere Application Server V5, IBM_TIO, is not started
automatically.3. When the TIO_Start window automatically closes, it means that the Tivoli
Intelligent Orchestrator Server is started. In order to verify the status of the
services, open a command line and enter the following command:
%TIO_HOME%\tools\enginestatus all
This displays the status of the three Tivoli Intelligent Orchestrator engines.
The output is similar to that shown in Example 1-1.
Example 1-1 Status of the three Tivoli Intelligent Orchestrator engines
C:\ibm\tivoli\thinkcontrol\tools>%TIO_HOME%\tools\enginestatus all2005-12-27 12:27:12,017 INFO COPCOM421I The deployment engine isstarted.2005-12-27 12:27:15,772 INFO COPCOM423I The policy engine isstarted.2005-12-27 12:27:18,716 INFO COPCOM484I The agent shell server isstarted.
If the status indicates that none of the servers is started, use the TivoliIntelligent Orchestrator Stop icon to stop the Tivoli Intelligent OrchestratorServer, and wait for the Tivoli Intelligent Orchestrator Stop window to close.
Then, repeat step 2 to start the Tivoli Intelligent Orchestrator again. (Such asituation may occur in systems with resource constraints, such as a tutorial
system.) The second time around, the Tivoli Intelligent Orchestrator startssuccessfully.
4. Minimize the VMware application window on the local desktop.
1 2 5 Signing in to the Tivoli Intelligent Orchestrator console
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
35/280
Chapter 1. Exercise 1: Introducing the IBM Tivoli Intelligent Orchestrator V3.1 7
1.2.5 Signing in to the Tivoli Intelligent Orchestrator console
After the Tivoli Intelligent Orchestrator Server and all its engines are started, you
can begin to use the Tivoli Intelligent Orchestrator browser-based user interface.To do this, sign in to the Tivoli Intelligent Orchestrator by performing the tasks
steps described here:1. Start the Internet Explorer from the tutorial systems desktop. For
performance reasons, it is recommended that you use a local tutorial system
rather than the VMware image.
2. To access the Tivoli Intelligent Orchestrator user interface, specify thefollowing URL in the Address field of the Internet Explorer, and press Enter:
http://TIOServer.tivdemo.com:9080/tcWebUI
3. The Tivoli Intelligent Orchestrator Sign On window appears (Figure 1-6).
Enter tioappadmin as the User ID, and tioappadmin as the Password. ClickLog On.
Figure 1-6 Signing in to the Tivoli Intelligent Orchestrator
http://tioserver.tivdemo.com:9080/tcWebUIhttp://tioserver.tivdemo.com:9080/tcWebUI7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
36/280
Orchestrator or when you click the Home icon in the upper right corner of
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
37/280
Chapter 1. Exercise 1: Introducing the IBM Tivoli Intelligent Orchestrator V3.1 9
y pp gthe window. The Welcome page highlights the following:
Customer applications
This refers to the applications being managed by the Tivoli Intelligent
Orchestrator. Resource pools
This refers to the standby capacity that can be assigned toapplications.
Switch fabrics
This is the network topology underpinning all the network elementsbetween the applications and the resource pools.
Execution historyThis is a dynamic query that displays the workflow history when thebrowser is opened.
The command input field
This is used to submit the SOAP commands to the Tivoli IntelligentOrchestrator, and is located at the bottom of the window. It has theCommand field and the History options.
If you do not see this area, log out and log in again. (To log out, click LogOff.)
5. Click Help to open the Tivoli Intelligent Orchestrator Online Help. Navigate to
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
38/280
10 Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
p p g p gIntelligent OrchestratorProduct overviewArchitecture and look at
the main components on the left panel of the Help System (Figure 1-8).
Figure 1-8 The Tivoli Intelligent Orchestrator help environment
6. Close the Help window when you are done.
This concludes the verification of the Tivoli Intelligent Orchestrators operationalstatus and overview exercise. You can now import the workflows and the device
drivers for the SWU environment.
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
39/280
Copyright IBM Corp. 2006. All rights reserved. 11
Chapter 2. Exercise 2: Preparing theenvironment
In order to complete the exercises, import a set of data center model (DCM)object definitions, scripts, and installation image archive files that are preparedespecially for this environment, into your Tivoli Intelligent Orchestrator (TIO)
system in the Tivoli Intelligent Orchestrator Server.
2
2.1 The objective of this exercise
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
40/280
12 Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
2.1 The objective of this exercise
The objective of this exercise is to import the workflows, the device drivers, and
the help files in order to build the IBM Software University (SWU) provisioningenvironment. When this exercise is complete, your DCM is populated with the
device drivers and the workflows required to complete the subsequent exercises.
2.2 Importing the IBM Software University automationpackages
In this exercise, you prepare the Tivoli Intelligent Orchestrator environment byimporting the preprepared support workflows, scripts, and Extensible Markup
Language-based (XML-based) DCM definitions.
2.2.1 Importing the tcdriver
Perform the following tasks to import the objects that are to be used in theexercises:
1. Make the tcdriver files available to the Tivoli Intelligent Orchestrator system
by copying them from the desktop of the Tivoli Intelligent Orchestrator Server
system to the %TIO_HOME%\drivers directory. Overwrite the files that mayalready exist in the target directory.
2. Import the required files for the tutorial environment by opening a
command-line interface in the TIOServer system, and issue the followingcommands:
%TIO_HOME%\tools\tc-driver-manager fid ITSO_Utilities%TIO_HOME%\tools\tc-driver-manager fid SWU_2006
These commands import the objects required to complete this exercise. After
the import is complete, the following must be present in the Tivoli IntelligentOrchestrator Server system:
A set of additional SWU_....tcdriver files in the %TIO_HOME%\directory
Scripts and XML files in the %TIO_HOME%\..\SWrepository\SWU path Installation archives (.zip files) in the C:\SWUrepository directory
3. To verify whether the import is successful, use the navigation pane and selectConfiguration Device Drivers SWU This must display 11 device
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
41/280
Chapter 2. Exercise 2: Preparing the environment 13
ConfigurationDevice DriversSWU. This must display 11 device
driver objects with names starting with SWU, which were imported from thetcdriver files (Figure 2-1). All these device drivers contain links to theworkflows that provide specific implementation functionality of the logical
device operations for each type of device to be supported in the SWUenvironment.
Figure 2-1 SWU workflows
In addition, a number of XML files are placed in the%TIO_HOME%\..\SWrepository\SWY\xml directory during the import.
Optionally, you can list these on the Tivoli Intelligent Orchestrator Serversystem using the Internet Explorer.
This concludes the preparation exercise. In the exercise described in Chapter 3,Exercise 3: Discovering and configuring the data center infrastructure on
page 15, you define the network infrastructure for the SWU environment.
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
42/280
14 Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
43/280
Copyright IBM Corp. 2006. All rights reserved. 15
Chapter 3. Exercise 3: Discovering andconfiguring the data centerinfrastructure
The first activity that is to be performed to customize the Tivoli Intelligent
Orchestrator (TIO) solution is to inform the system about the existing networkinginfrastructure in the managed environment. In the Pristine IBM SoftwareUniversity (SWU) environment, this similar to that shown in Figure 3-1.
Figure 3-1 The tutorial logical networking infrastructure
3
Defining the networking infrastructure in the data center model (DCM) can beachieved as a combination of discovering the existing network components using
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
44/280
16 Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
achieved as a combination of discovering the existing network components using
the IBM Tivoli NetView discovery feature that is installed with the TivoliIntelligent Orchestrator Server, and the manual definitions for the networkcomponents that either do not exist or cannot be discovered.
NetView is capable of discovering servers, subnets, and switches. However,because there are no switches in the stand-alone SWU environment, NetView
helps you discover the existing servers and subnets only.
3.1 Setting up a NetView discovery policy
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
45/280
Chapter 3. Exercise 3: Discovering and configuring the data center infrastructure 17
To discover the components in your infrastructure, define and configure a
discovery technology that points to a particular specialized component thatknows the object types you are looking for. After defining, execute the
discovery, and optionally, review the updates that are added to the SWUenvironment.
As with other objects in the DCM, define the discovery technologies either from
the user interface or by importing a preprepared set of definitions stored in anExtensible Markup Language (XML) file.
3.1.1 Shortcut: Defining the NetView discovery technology
An Extensible Markup Language (XML) file for defining the NetView discoverytechnology is loaded into the LocalFileRepository in your TIOServer systemwhen the SWU_2006 tcdriver is installed. To import these definitions into your
DCM, perform one of the following tasks:
Execute the SWU_ImportXML workflow by providing a value for the xmlFile
parameter of netviewdiscovery, either by invoking the workflow from the userinterface or by issuing the following command from the Tivoli Intelligent
Orchestrator user interface command line:
MessageTranslatorService createDeploymentRequest 0 SWU_ImportXMLxmlFile=netviewdiscovery
Issue the following command from a command line in the Tivoli Intelligent
Orchestrator Server system:
%TIO_HOME%\..\SWrepository\SWU\bin\run_wf.cmd SWU_ImportXML"xmlFile=netviewdiscovery"
Irrespective of the method in which you invoke the workflow, select
ConfigurationDeployment Requests to check the status.
When the workflow execution is complete, continue to 3.2, Discovering the
servers and the network infrastructure on page 19.
3.1.2 Exercise: Creating the NetView discovery technology
To create the discovery technology for NetView through the user interface,perform the following tasks:
1. Navigate to InventoryInfrastructure ManagementDiscovery
Technologies EditAdd Technology. Provide the necessaryinformation, as shown in the pop-up (Figure 3-2), and click Save. To go to the
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
46/280
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
47/280
3.2.1 Shortcut: Executing a discovery technology
A script for executing a discovery technology is loaded into the
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
48/280
20 Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
A script for executing a discovery technology is loaded into the
LocalFileRepository when the SWU_2006 tcdriver is installed. To use this script,perform one of the following tasks:
Execute the SWU_DiscoverAll workflow by providing a value for thediscoveryName parameter of SWU_NetView_Discovery, either by invokingthe workflow from the user interface or by issuing the following command
from the Tivoli Intelligent Orchestrator user interface command line:
MessageTranslatorService createDeploymentRequest 0 SWU_DiscoverAlldiscoveryName=SWU NetView Discovery
Issue the following command from the TIOServer system command line:
%TIO_HOME%\..\SWrepository\SWU\bin\run_wf.cmd SWU_DiscoverAll
"discoveryName=SWU_NetView_Discovery"
When the workflow execution is complete, continue to 3.3, Defining the access
points and the credentials on page 26.
3.2.2 Exercise: Discovering the resources
To discover the resources, perform the following tasks:
1. From the Tivoli Intelligent Orchestrator user interface, navigate to TasksDiscoveryDiscover Devices and provide the necessary runtime
parameters in the New Discovery Task window (Figure 3-4). Provide a taskname, select the newly created SWU_NetView_Discovery technology, opt to
discover the entire network, and schedule the task to run immediately by
selecting Now. Click OK to continue and confirm the creation of the discoverytask.
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
49/280
Chapter 3. Exercise 3: Discovering and configuring the data center infrastructure 21
Figure 3-4 Running NetView discovery
A status message similar to the one shown in Figure 3-5 is displayed, fromwhere you can easily access the task execution details.
Figure 3-5 NetView discovery task execution confirmation
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
50/280
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
51/280
In the stand-alone SWU environment, you will not be able to discover anyswitches. However, the environment consists of two servers (the Tivoli Intelligent
Orchestrator Server and a host system) and at least one subnet. Despite all this,
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
52/280
24 Composite Application Provisioning with IBM Tivoli Provisioning Manager V3.1
y ) p ,why is only one server discovered?
Figure 3-8 Changes discovered by NetView
The explanation for this discrepancy is that the Tivoli Intelligent OrchestratorServer is already defined to the DCM, and is therefore not treated as a
discovered server. The reason for the missing information about subnets is due
to the fact that you specifically asked to control the addition of subnets to theDCM by setting the Add Device policy to Track Changes instead of the defaultAdd Device. Because of this, no subnets are added automatically. However, the
subnet information is available in the Change Records window, which can beaccessed by selecting TasksConfiguration ManagementDiscoveredChanges. This window shows that some new devices have been discovered.
3.2.4 Accepting and ignoring the changes
To view, and to optionally accept or reject changes, click the Edit icon to the rightside of the change record you want to work with. The window that opens
(Figure 3-9) shows that the NetView discovery actually found several subnets. Atthis point in the configuration of the SWU environment, you are only interested in
the 192.168.1.0 network, and you want to permanently ignore the information
pertaining to the VMware adapters that are configured in the TIOServer system.To permanently ignore the discovery information regarding the objects, select the
objects, set the value for the Action to apply on selected Attributesfield as
7/31/2019 Composite Application Provisioning With IBM Tivoli Provisioning Manager V3.1 Redp4222
53/280
Chapter 3. Exercise 3: Discovering and configuring the data center infrastructure 25
Update Permanently as shown in Figure 3-9, and click Proceed.
Figure 3-9 Discovered subnets
To accept the change for the 192.168.1.0 subnet, select the subnet and set thevalue for the Action to Apply on selected Attributes field asUpdate DCM, andclick Procee