Tivoli® Tivoli

Provisioning

Manager

Release

Notes

Version

2.1

GI11-4698-00

���

Tivoli® Tivoli

Provisioning

Manager

Release

Notes

Version

2.1

GI11-4698-00

���

Note:

Before

using

this

information

and

the

product

it

supports,

be

sure

to

read

the

general

information

under

“Notices”

on

page

33.

First

Edition,

June

2004

This

edition

applies

to

Version

2.1

of

Tivoli

Provisioning

Manager

(product

number

5724-I14)

and

to

all

subsequent

releases

and

modifications

until

otherwise

indicated

in

new

editions.

©

Copyright

IBM®

Corporation

2003,

2004.

All

rights

reserved.

May

only

be

used

pursuant

to

a

Tivoli®

Systems

Software

License

Agreement,

an

IBM

Software

License

Agreement,

or

Addendum

for

Tivoli

Products

to

IBM

Customer

or

License

Agreement.

No

part

of

this

publication

may

be

reproduced,

transmitted,

transcribed,

stored

in

a

retrieval

system,

or

translated

into

any

computer

language,

in

any

form

or

by

any

means,

electronic,

mechanical,

magnetic,

optical,

chemical,

manual,

or

otherwise,

without

prior

written

permission

of

IBM

Corporation.

IBM

Corporation

grants

you

limited

permission

to

make

hardcopy

or

other

reproductions

of

any

machine-readable

documentation

for

your

own

use,

provided

that

each

such

reproduction

shall

carry

the

IBM

Corporation

copyright

notice.

No

other

rights

under

copyright

are

granted

without

prior

written

permission

of

IBM

Corporation.

©

Copyright

International

Business

Machines

Corporation

2003,

2004.

All

rights

reserved.

US

Government

Users

Restricted

Rights

—Use,

duplication

or

disclosure

restricted

by

GSA

ADP

Schedule

Contract

with

IBM

Corp.

©

Copyright

International

Business

Machines

Corporation

2003,

2004.

All

rights

reserved.

US

Government

Users

Restricted

Rights

–

Use,

duplication

or

disclosure

restricted

by

GSA

ADP

Schedule

Contract

with

IBM

Corp.

Contents

About

this

release

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 1

New

in

this

release

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 1

Downloads

and

Updates

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 2

Product

compatibility

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 2

Installation,

migration,

upgrade

and

configuration

information

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 2

Uninstallation

information

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 2

Known

limitations,

problems

and

workarounds

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 3

Limitations

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 3

Running

scripts

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 3

Server

must

be

stopped

before

using

XMLImport

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 3

Deleting

applications

and

clusters

created

using

a

deployment

plan

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 3

Naming

logical

device

operations

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 3

The

SetAttribute

logical

device

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 4

Known

problems

and

workarounds

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 4

APAR

IY57410

patch

for

DB2

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 4

Websphere

MQ

error

MQJMS2002

fix

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 5

Error

installing

WebSphere

Application

Server

version

5.0

fixpack

2

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 5

Need

to

remove

^M

characters

on

Solaris

when

using

XMLExport/XMLImport

.

.

.

.

.

.

.

.

.

.

.

. 6

Changes

to

Tivoli

Provisioning

Manager

installation

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 6

InstallShield

MultiPlatform

(ISMP)

display

may

truncate

translated

text

.

.

.

.

.

.

.

.

.

.

.

.

.

. 6

Icon

view

is

obscured

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 7

Cygwin

on

Japanese,

Traditional

Chinese

and

Simplified

Chinese

Windows

.

.

.

.

.

.

.

.

.

.

.

.

. 7

When

using

XMLImport

or

XMLExport,

Java

exceptions

can

be

ignored

.

.

.

.

.

.

.

.

.

.

.

.

.

. 7

The

TEC

server

needs

3.9

fixpack

1

installed

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 7

Data

center

model

export

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 7

Credentials

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 8

Changing

object

identifiers

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 8

Workflows

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 8

New

Virtual

Server

doesn’t

get

added

to

correct

Resource

Pool

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 10

Package

repository

attribute

required

for

cluster

during

XMLImport

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 10

-unsafe

command

line

parameter

for

XMLImport

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 11

Transaction

log

full

error

when

running

post-install.cmd

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 11

Automount

needs

to

be

disabled

on

Solaris

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 12

Install

the

new

Warehouse

Enablement

Pack

(WEP)

from

the

IBM

Tivoli

Software

Support

site

.

.

.

.

.

. 12

Documentation

additions

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 13

Data

center

fragment

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 13

Configuring

a

data

center

fragment

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 13

Viewing

the

software

registry

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 14

Registering

software

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 14

Deregistering

software

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 14

Editing

the

properties

of

a

software

module

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 14

Creating

a

deployment

plan

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 16

Selecting

a

logical

application

structure

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 16

Selecting

software

stacks

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 17

Selecting

an

application

deployment

template

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 17

Specifying

additional

deployment

parameters

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 18

Selecting

a

data

center

fragment

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 18

Reviewing

the

deployment

plan

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 18

Finalizing

the

deployment

plan

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 19

Documentation

updates

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 19

Installation

Guide

correction

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 19

Creating

a

new

workflow

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 20

Running

a

workflow

using

a

defined

service

access

point

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 20

©

Copyright

IBM

Corp.

2003,

2004

iii

||||

||

||

Viewing

workflow

run

history

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 20

Stopping

a

workflow

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 20

Displaying

workflow

run

history

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 21

Using

the

TC_HOME

variable

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 21

Workflow

variables,

parameters,

and

transitions

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 21

Setting

up

Tivoli

Provisioning

Manager

to

collect

utilization

data

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 21

Required

data

center

objects

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 21

Sample

XML

file

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 22

NAT

support

added

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 24

SOAP

commands

for

obtaining

server

IDs

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 24

Deploying

a

monitoring

configuration

to

a

server

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 25

SOAP

command

syntax

reference:

getApplicationMode

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 25

Viewing

the

discovery

ID

of

Discovery

Objects

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 25

Updates

to

running

SOAP

commands

from

a

remote

computer

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 25

Java

requirements

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 25

Procedure

for

running

commands

remotely

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 26

Log

files

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 27

Log

file

location

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 27

Trace

and

message

log

file

names

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 27

Capacity

on

demand

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 27

Creating

resource

reservations

for

an

application

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 28

Working

with

power

units

and

outlets

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 28

Migration

Guide

updates

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 29

Database

upgrade

changes

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 29

Changes

to

data

migration

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 29

Contacting

Software

Support

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 31

Notices

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 33

Trademarks

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 34

iv

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

||||||

About

this

release

These

release

notes

describe

product

changes

and

enhancements

in

the

Tivoli®

Provisioning

Manager

product

release.

New

in

this

release

Tivoli

Provisioning

Manager

version

2.1

includes

the

following

new

features

and

enhancements:

Monitoring

enhancements

You

can

control

monitoring

of

your

data

center

by

using

external

monitoring

applications.

This

release

includes

support

for

monitoring

of

operating

systems

using

IBM

Tivoli

Monitoring.

Fault

management

enhancements

You

can

configure

Tivoli

Provisioning

Manager

to

send

an

event

to

IBM

Tivoli

Enterprise

Console

when

a

workflow

fails.

You

can

also

set

up

Tivoli

Enterprise

Console

so

that

it

can

run

SOAP

commands

when

a

specified

event

occurs.

Reporting

integration

with

Tivoli

Data

Warehouse

Tivoli

Provisioning

Manager

now

integrates

with

IBM

Tivoli

Data

Warehouse,

which

provides

centralized

data

storage

and

reporting

capabilities

for

multiple

management

systems.

You

can

review

historical

reports

of

demand

and

performance,

and

print

or

export

reports

for

your

records.

Workflow

development

enhancements

This

release

includes

several

workflow

development

enhancements.

The

Web-based

interface

includes

an

editor

that

you

can

use

to

create

or

modify

workflows.

There

are

also

several

enhancements

to

workflows

themselves,

including

conditional

branching

and

loops.

Managing

new

devices

and

external

configuration

changes

Tivoli

Provisioning

Manager

can

use

discovery

technologies

to

identify

external

configuration

changes

to

devices

and

new

devices

that

are

not

currently

managed.

Discovery

capability

helps

you

control

external

changes

to

your

data

center,

and

ensures

that

the

data

center

model

in

Tivoli

Provisioning

Manager

accurately

reflects

the

actual

data

center

infrastructure

that

you

are

managing.

Virtual

server

support

Virtual

server

capability

enables

you

to

run

multiple

servers

concurrently

on

a

single

computer.

In

Tivoli

Provisioning

Manager,

you

can

manage

virtual

servers

and

the

associated

host

platforms.

Globalized

product

This

product

is

globalized

to

maximize

interoperability

and

multilingual

capability,

and

to

support

locale

preferences

such

as

date,

time,

and

number

formats.

The

current

release

is

available

in

ten

different

languages.

©

Copyright

IBM

Corp.

2003,

2004

1

Downloads

and

Updates

The

IBM

Orchestration

and

Provisioning

Automation

Library

is

available

online

at:

http://www.developer.ibm.com/tivoli/workflow.html.

The

IBM

Orchestration

and

Provisioning

Automation

Library

delivers

the

tools

and

community

you

need

to

build

your

business

around

on

demand

automation.

New

workflows

and

automation

packages

and

updated

readme

files

for

automation

packages

shipped

with

Tivoli

Provisioning

Manager

will

be

posted

to

the

IBM

Orchestration

and

Provisioning

Automation

Library.

This

site

will

also

contain

the

most

up-to-date

information

about

the

full

list

of

available

workflows.

Note:

Many

workflows

cannot

be

categorized

by

platform,

for

example

the

network

devices

and

storage

workflows.

However,

the

workflow

for

each

readme

will

document

any

platform-specific

information.

Product

compatibility

See

the

Tivoli

Provisioning

Manager

Installation

Guide

for

product

compatibility

information.

Installation,

migration,

upgrade

and

configuration

information

See

the

Tivoli

Provisioning

Manager

Installation

Guide

for

installation

and

configuration

information,

and

for

information

on

upgrading

Tivoli

Provisioning

Manager

2.1

to

Tivoli

Intelligent

ThinkDynamic

Orchestrator

2.1.

See

the

Tivoli

Provisioning

Manager

Migration

Guide

for

information

on

migrating

from

Tivoli

Intelligent

ThinkDynamic

Orchestrator

1.1

to

Tivoli

Intelligent

ThinkDynamic

Orchestrator

2.1,

or

from

Tivoli

Provisioning

Manager

1.1

to

Tivoli

Provisioning

Manager

2.1.

Note:

Migration

from

Tivoli

Provisioning

Manager

1.1

to

Tivoli

Intelligent

ThinkDynamic

Orchestrator

2.1

is

not

supported.

Uninstallation

information

See

the

Tivoli

Provisioning

Manager

Installation

Guide

for

uninstallation

information.

2

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

Known

limitations,

problems

and

workarounds

This

section

describes

the

limitations

that

are

associated

with

Tivoli

Provisioning

Manager

and

provides

workarounds

for

known

problems,

when

workarounds

are

available.

Limitations

Running

scripts

If

you

are

installing

Tivoli

Provisioning

Manager

on

Windows,

any

scripts

you

run

must

be

run

in

a

Windows

command

window

and

not

in

a

Cygwin

bash

shell.

Always

run

the

.cmd

version

of

the

script

and

not

the

.sh

version

which

might

also

be

installed.

Server

must

be

stopped

before

using

XMLImport

Tivoli

Provisioning

Manager

processes

cache

some

information

and

they

depend

on

JMS

messages

for

notification

when

events

occur

(for

example,

when

the

system

runs

logical

device

operations

and

workflows).

However,

an

XML

import

does

not

send

any

notifications

to

the

Tivoli

Provisioning

Manager

processes,

when

it

loads

the

database.

If

you

perform

an

XML

import

while

the

server

is

running,

unexpected

behavior

can

result.

To

avoid

unexpected

behavior,

shut

down

Tivoli

Provisioning

Manager

before

you

run

an

XML

import

and

then

restart

it

when

the

XML

import

is

complete.

Deleting

applications

and

clusters

created

using

a

deployment

plan

Objects

deployed

through

application

topology

using

a

deployment

plan

are

not

meant

to

be

deleted

manually,

as

they

are

created

as

part

of

a

deployment

process.

During

the

deployment

process,

changes

are

made

to

the

data

center

model

to

accommodate

the

deployment

of

the

application.

These

objects,

including

clusters,

are

meant

to

be

removed

through

an

undeployment

process,

so

that

not

only

the

objects

are

removed,

but

any

data

center

configurations

made

to

accommodate

the

objects

are

also

reversed.

While

a

complete

undeployment

workflow

is

not

currently

available,

you

can

download

a

workflow

from

our

support

library

at

“Downloads

and

Updates”

on

page

2.

This

workflow

performs

a

minimal

clean-up

of

the

structures

created

during

the

deployment

process.

This

workflow

has

to

be

invoked

manually,

passing

the

ID

of

the

application

to

the

undeployment

process.

Before

attempting

to

delete

such

an

application,

use

this

workflow

to

undeploy

it

first.

Naming

logical

device

operations

When

naming

a

logical

device

operation,

it

must

be

in

the

form:

XXXX.YYYY,

where

XXXX

is

the

logical

device

name

and

YYYY

is

the

operation

name.

©

Copyright

IBM

Corp.

2003,

2004

3

The

SetAttribute

logical

device

If

you

use

the

SetAttribute

logical

device,

you

must

set

the

AttributeType

variable

as

an

integer.

You

cannot

set

the

attribute

as

a

string.

Known

problems

and

workarounds

APAR

IY57410

patch

for

DB2

If

DB2

has

been

upgraded

to

at

least

fixpak

3,

you

must

apply

APAR

IY57410

from

the

Tivoli

Provisioning

Manager,

Version

2.1

Generic

Fixes

CD.

The

following

describes

the

process

for

each

platform:

AIX

1.

Stop

Tivoli

Provisioning

Manager.

2.

Logon

as

root.

3.

Copy

special_10829.tar.Z

from

the

Generic

Fixes

CD.

4.

Stop

DB2

and

ensure

all

db2

processes

are

stopped.

5.

Extract

the

contents

fo

the

file

to

a

temporary

directory.

6.

Make

a

backup

copy

of

the

originally

installed

DB2

files

of

the

same

names.

7.

Copy

the

extracted

files

to

the

appropriate

directory.

8.

Be

careful

to

ensure

ownership

and

permissions

are

the

same

as

those

of

the

original

files.

9.

Restart

DB2.

Solaris

1.

Stop

Tivoli

Provisioning

Manager.

2.

Logon

as

root.

3.

Copy

special_10830.tar.Z

from

the

Generic

Fixes

CD.

4.

Stop

DB2

and

ensure

all

db2

processes

are

stopped.

5.

Extract

the

contents

fo

the

file

to

a

temporary

directory.

6.

Make

a

backup

copy

of

the

originally

installed

DB2

files

of

the

same

names.

7.

Copy

the

extracted

files

to

the

appropriate

directory.

8.

Be

careful

to

ensure

ownership

and

permissions

are

the

same

as

those

of

the

original

files.

9.

Restart

DB2.

Linux®

intel

1.

Stop

Tivoli

Provisioning

Manager.

2.

Logon

as

root.

3.

Copy

special_10833.tar.Z

from

the

Generic

Fixes

CD.

4.

Stop

DB2

and

ensure

all

db2

processes

are

stopped.

5.

Extract

the

contents

fo

the

file

to

a

temporary

directory.

6.

Make

a

backup

copy

of

the

originally

installed

DB2

files

of

the

same

names.

7.

Copy

the

extracted

files

to

the

appropriate

directory.

8.

Be

careful

to

ensure

ownership

and

permissions

are

the

same

as

those

of

the

original

files.

9.

Restart

DB2.

4

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

|

|||

|

|

|

|

|

|

||

|

||

|

|

|

|

|

|

|

||

|

||

|

|

|

|

|

|

|

||

|

||

|

Linux

i-series

1.

Stop

Tivoli

Provisioning

Manager.

2.

Logon

as

root.

3.

Copy

special_10841.tar.Z

from

the

Generic

Fixes

CD.

4.

Stop

DB2

and

ensure

all

db2

processes

are

stopped.

5.

Extract

the

contents

fo

the

file

to

a

temporary

directory.

6.

Make

a

backup

copy

of

the

originally

installed

DB2

files

of

the

same

names.

7.

Copy

the

extracted

files

to

the

appropriate

directory.

8.

Be

careful

to

ensure

ownership

and

permissions

are

the

same

as

those

of

the

original

files.

9.

Restart

DB2.

Windows

1.

Copy

hotfixpkg_10831.exe

to

your

local

directory.

2.

Please

stop

all

DB2

processes

before

you

apply

hotfixpkg_10831.exe.

Stop

all

DB2

processes

using

services,

just

running

db2stop

is

not

enough.

3.

Run:

hotfixpkg_10831

-a

-f.

This

will

stop

all

DB2

processes.

4.

Under

..\sqllib\

run

hotfix

-l

and

db2level.

They

should

display

the

special

build.

5.

To

uninstall

the

hotfix,

run

either

hotfix

-u

HotFixID

to

uninstall

the

most

recent

hotfix;

or

hotfix

-u

all

to

uninstall

all

the

hotfixes.

Note:

You

may

also

use

winzip

to

extract

the

hotfixpkg_10831.exe

to

a

directory

and

run

hotfix

-f

to

automatically

terminate

all

DB2

processes

and

install

the

hotfix.

Websphere

MQ

error

MQJMS2002

fix

If

you

are

running

Tivoli

Provisioning

Manager

server

for

a

long

period

of

time,

for

instance

over

an

hour,

and

workflow

deployment

stops

working,

check

the

console.log

file

in

the

deploymentEngine

directory.

If

you

see

error

MQJMS2002,

then

you

need

to

install

WebSphere

MQ

v5.3

CSD05

to

resolve

the

problem.

This

patch

can

be

downloaded

from

https://www6.software.ibm.com/dl/wsmqcsd/wsmqcsd-p.

Error

installing

WebSphere

Application

Server

version

5.0

fixpack

2

When

installing

WebSphere

Application

Server

version

5.0

fixpack

2

on

Windows

2000

or

Windows

2003,

the

embedded

messaging

installation

fails

and

a

dialog

box

is

displayed

containing

the

following

message:

Error

installing

CSD

04.

Examine

log

file

’<WAS_HOME>\logs\MQCSDLog.txt’.

(AMQ4760)

The

file

MQCSDLog.txt

contains

the

following

entries:

Installing

’<WMQ

HOME>\bin\amqxms0n.dll’

copying

from

’<CSD

HOME>\CSD\CSD00001\amqxms0n.dll’

to

’<WMQ

HOME>\bin\amqxms0n.dll’

source

version:

’5.300.400.3168’

target:

’5.300.100.2283’

source

file

time

’Sep

29

2003

at

15:25’

(127093227302812500)

target

file

time

’Oct

11

2002

at

08:00’

(126787968000000000)

***Copy

failed

1224

Known

limitations,

problems

and

workarounds

5

|

|

|

|

|

|

||

|

||

|

|

|

|||

|

||

||

|||

|

||||||

Finished

file

installation

MessageBox:

’Error

installing

CSD

04.

Examine

log

file

’<WAS

HOME>\logs\MQCSDLog.txt’.

(AMQ4760)’

Ending

with

RC

1603

(0x00000643)

This

problem

occurs

because

the

Windows

Managment

Instrumentation

system

service

uses

the

file

amqxms0n.dll.

If

you

attempt

to

install

fixpack

2

while

this

service

is

running,

the

fixpack

is

unable

to

update

the

file,

as

it

is

currently

in

use.

Before

installing

fixpack

2,

ensure

that

the

Windows

Management

Instrumentation

system

service

is

stopped.

To

stop

this

service:

1.

Click

Settings→Control

Panel

from

the

Windows

Start

menu.

The

Control

Panel

is

displayed.

2.

Click

Administrative

Tools.

3.

Click

Services.

The

Services

applet

is

displayed.

4.

Identify

the

entry

for

the

Windows

Management

Instrumentation

service

in

the

list

of

services,

right

click

it

and

then

click

Stop

in

the

displayed

menu.

You

can

now

install

WebSphere

Application

Server

version

5.0

fixpack

2.

Need

to

remove

^M

characters

on

Solaris

when

using

XMLExport/XMLImport

When

you

use

XMLExport

to

create

a

file

you

want

to

subsequently

use

with

XMLImport,

carriage

return

characters

are

included

throughout

the

file.

On

Solaris

systems,

these

appear

as

a

^M

periodically

and

can

cause

problems

with

an

import.

To

avoid

problems,

use

the

UNIX

tr

command

to

remove

the

^M

characters

prior

to

performing

an

XMLImport.

To

do

this:

1.

Backup

the

original

file

to

<filename.bak>,

where

<filename.bak>

is

the

name

of

the

file

you

want

to

backup

with

a

.bak

extension.

For

example:

cp

filename

filename.bak

2.

Run

the

command

to

truncate

the

characters:

tr

-d

’\r’

>

filename

Changes

to

Tivoli

Provisioning

Manager

installation

The

following

change

applies

to

the

“Migrating

Tivoli

Provisioning

Manager”

chapter:

One

of

the

notes

at

the

end

of

the

installation

procedure

recommends

a

DB2

Universal

Database™

locklist

value

of

2000.

If

you

do

not

increase

the

locklist

value

from

the

default

value

of

50,

you

might

experience

timeout

or

deadlock

errors.

To

prevent

these

errors,

ensure

that

the

locklist

value

is

set

to

2000

or

greater

for

Tivoli

Provisioning

Manager.

InstallShield

MultiPlatform

(ISMP)

display

may

truncate

translated

text

There

is

a

known

issue

with

the

translated

versions

of

the

InstallShield

MultiPlatform

(ISMP)

installation

wizard.

In

some

languages,

text

on

the

translated

version

of

the

Database

Configuration

Panel

may

appear

truncated.

Specifically,

the

sentence:

Do

not

perform

database

configuration

steps.

(For

advanced

users

only)

appears

truncated.

To

view

the

entire

sentence,

resize

the

window.

6

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

Icon

view

is

obscured

When

using

the

Icon

View,

menu

items

or

popup

windows

might

be

obscured.

If

this

occurs,

return

to

the

Details

View

and

try

again.

Cygwin

on

Japanese,

Traditional

Chinese

and

Simplified

Chinese

Windows

In

Japanese,

Traditional

Chinese

and

Simplified

Chinese

Windows

environments,

it

is

recommended

that

you

use

only

English

characters

for

the

object

names

which

the

user

defines,

and

for

the

external

object

names

to

which

the

workflow

refers.

Some

double-byte

character

set

(DBCS)

languages

use

encoding

schemes

with

characters

that

have

the

hexadecimal

value

0x5C

as

the

second

byte.

This

is

the

ASCII

hexidecimal

code

for

a

backslash

(\).

Some

commands

in

the

Cygwin

bash

shell

interpret

double-byte

characters

without

understanding

that

the

bytes

should

be

processed

in

pairs.

When

these

languages

see

the

0x5C

value

they

interpret

it

is

a

backslash.

This

causes

an

error

since

it

is

really

just

the

second

byte

of

a

single

DBCS

character.

The

bash

shell

is

used

by

Tivoli

Provisioning

Manager

for

executing

commands

from

within

workflows.

For

Japanese,

Traditional

Chinese

or

Simplified

Chinese

on

Windows

systems,

if

these

commands

or

their

results

are

DBCS

characters,

and

one

of

those

characters

happens

to

contain

0x5C,

the

command

fails.

Limiting

the

characters

to

English

is

the

easiest

way

to

avoid

this

problem.

(The

workflows

that

ship

with

Tivoli

Provisioning

Manager

are

designed

to

operate

in

English

using

English

data.)

Note:

This

problem

does

not

occur

in

Korean

language

workflows.

When

using

XMLImport

or

XMLExport,

Java

exceptions

can

be

ignored

When

errors

occur

while

using

XMLImport

or

XMLExport,

there

might

be

some

Java

exceptions

displayed

along

with

the

Tivoli

Provisioning

Manager

error

message,

in

the

form

COPxxxyyy

ID.

The

exceptions

are

extraneous

and

they

should

be

ignored.

Use

only

the

valid

Tivoli

Provisioning

Manager

error

message

to

troubleshoot

the

problem.

The

TEC

server

needs

3.9

fixpack

1

installed

The

TEC

Server

crashes

when

it

receives

events

with

locale

specific

decimal

characters

[.]

in

the

event

string.

Installing

the

TEC

3.9

Fixpack

1

solves

the

problem.

Data

center

model

export

Out

of

memory

error

on

a

data

center

model

export

You

may

experience

a

JVM

out-of-memory

error

during

a

data

center

model

export

with

a

large

number

of

entities.

The

possibility

of

failure

depends

on

the

number

of

data

center

model

entities

and

the

physical

memory

installed

on

the

Tivoli

Provisioning

Manager

server.

To

avoid

the

problem,

do

one

of

the

following:

v

Shut

down

the

Tivoli

Provisioning

Manager

server

and

try

again.

v

Increase

the

physical

memory

installed

on

the

Tivoli

Provisioning

Manager

server.

v

Increase

the

virtual

memory

setting.

Known

limitations,

problems

and

workarounds

7

|

||

|||

|||||||

|||||||

|

|||||

Running

dcmExport.cmd

on

a

CYGWIN

console

This

problem

only

applies

to

Windows

platforms.

When

running

the

dcmExport.cmd

on

a

CYGWIN

console,

the

optional

output

file

pathname

cannot

be

correctly

passed

to

the

dcmExport.cmd

script.

You

must

run

the

dcmExport.cmd

on

a

Windows

DOS

console.

Credentials

Creating

credentials

for

host

and

client

communication

If

your

environment

contains

two

server

objects

that

are

located

on

one

machine,

you

must

still

create

two

sets

of

credentials

for

both

host

and

client

communication.

Credentials

deleted

from

a

software

stack

If

an

entire

system

image

is

replaced,

all

old

credentials

that

are

associated

with

a

software

stack

are

deleted

from

the

database

after

a

new

image

is

installed.

All

new

credentials

that

are

configured

with

the

image

software

stack

will

be

installed

automatically

after

the

old

ones

are

deleted.

Changing

object

identifiers

Currently,

data

acquisition

engine

SNMP

drivers

for

UNIX

and

Windows

rely

on

fixed

object

identifiers

(OIDs)

to

retrieve

their

information.

You

can

change

the

object

identifiers

for

a

Windows

data

acquisition

engine

driver

using

a

DCM

import

file.

For

example:

<dae-driver

device=’server’

classname=’com.thinkdynamics.kanaha.dataacquisitionengine.snmp.WindowsDriver’>

<property

name=’snmp.oid’

value=’1.2.3.4.5.6.7.8.9’/>

</dae-driver>

There

is

no

similar

capability

for

UNIX.

Workflows

Deleting

workflows

You

cannot

delete

a

workflow

that

is

referenced

by

another

workflow

or

Java

plug-in,

and

you

cannot

uninstall

an

automation

package

that

includes

workflows

or

Java

plug-ins

that

are

referenced

by

other

workflows

or

Java

plug-ins.

You

must

remove

these

references

first

before

you

can

delete

the

workflow

or

Java

plug-in.

Alternatively,

you

can

use

forceUninstallDriver,

as

shown

on

“Uninstalling

automation

packages”

on

page

9.

Creating

a

workflow

with

a

different

locale

Tivoli

Provisioning

Manager

workflows

that

are

shipped

with

the

product

are

locale

sensitive

and

are

designed

to

work

in

only

the

en_US

locale.

To

use

the

functionality

of

a

workflow

in

a

locale

other

than

en_US,

the

workflow

must

be

copied

and

modified

for

use

in

that

locale.

If

the

workflow

uses

an

external

shell

script

which

has

a

locale

dependency,

the

script

file

must

be

modified

accordingly.

For

example,

if

the

script

expects

messages

from

a

target

application,

it

should

be

modified

to

accept

messages

for

the

target

locale.

To

identify

referenced

script

files,

please

see

the

device

driver

document

corresponding

to

the

workflow.

The

packaged

files

section

of

the

document

includes

a

list

of

referenced

scripts.

The

example

below

describes

how

to

copy

and

modify

the

Telnet_Execute_Command

workflow

to

work

with

the

Japanese

ja_JP

locale.

The

expect

script

file

telnet_execute.exp

is

referenced

from

the

Telnet_Execute_Command

workflow.

In

this

example,

the

script

file

should

be

modified

as

well.

8

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

||||||

|||||||||||||

Changing

the

workflow

using

Web-based

interface

1.

Open

the

Telnet_Password_Execute_Command

workflow.

2.

Change

the

name

of

the

workflow

to

Telnet_Password_Execute_Command_ja_JP.

3.

Change

the

en_US

argument

of

the

CheckDeviceLocale

transition

to

ja_JP.

4.

Compile

the

workflow.

5.

Refresh

the

tree

and

expand

Device

Drives

→

Service

Access

Point,

and

open

Telnet

Service

Access

Point.

6.

Remove

the

Telnet_Password_Execute_Command

workflow

and

add

the

Telnet_Password_Execute_Command_ja_JP

workflow.

Note:

For

limitations

on

non-en_US

workflows,

see

“Cygwin

on

Japanese,

Traditional

Chinese

and

Simplified

Chinese

Windows”

on

page

7.

Modifying

the

script

(prerequisite:

requires

Expect

knowledge)

1.

Change

to

the

thinkcontrol/bin

directory.

2.

Add

the

line:

exp_internal

1

to

the

top

of

the

telnet_execute.exp

file.

3.

Add

parity

0

before

the

expect

{}

block

and

parity

1

after

the

block.

4.

Do

not

close

the

file.

5.

Run

the

script

and

the

matching

information

will

be

displayed

on

the

screen.

expect:

does

"\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n\rAIX

Version

5\r\n\r(C)

Copyrights

by

IBM

and

by

others

1982,

2002.

\r\n\rlogin:

tioadmin\r\ntioadmin

$N%Q%9%o!<%I:

"

(spawn_id

4)

match

regular

expression

"assword:

[

\r\t\n\x0c]*$"?

no

"passwd:

$"?

no

6.

Find

the

input

received

from

the

telnet

server

($N%Q%9%o!<%I:),

copy

the

text,

and

paste

it

into

the

expect

script

as

shown

below.

You

may

need

to

add

backslashes

(\)

before

any

special

characters

such

as

$.

parity

0

expect

{

-re

"\\\$N%Q%9%o!<%I:

$"

{

send

"$pass\r"

exp_continue

}

7.

Run

and

modify

the

script

until

you

find

the

matching

patterns

for

all

expected

patterns.

expect:

does

"tioadmin\r\ntioadmin

$N%Q%9%o!<%I:

"

(spawn_id

4)

match

regular

expression

"\$N%Q%9%o!<%I:

$"?

yes

expect:

set

expect_out(0,string)

"$N%Q%9%o!<%I:

"

expect:

set

expect_out(spawn_id)

"4"

expect:

set

expect_out(buffer)

"tioadmin\r\ntioadmin

$N%Q%9%o!<%I:

"

8.

Remove

the

exp_internal

1

line

when

you

are

finished.

Uninstalling

automation

packages

On

a

Windows

platform,

the

Tivoli

Provisioning

Manager

deployment

engine

must

be

shut

down

before

an

automation

package

can

be

uninstalled.

If

the

deployment

engine

is

not

shut

down,

the

automation

package

jar

file

is

locked

and

the

automation

package

cannot

be

uninstalled.

To

uninstall

an

automation

package

that

is

already

associated

with

a

device

model:

1.

Change

the

directory

to

%TIO_HOME%/tools

2.

Run

tcdriver-manager

forceUninstallDriver

<automation

package

name>

Known

limitations,

problems

and

workarounds

9

Workflow

variable

value

limits

Workflow

variable

values

are

limited

to

4000

bytes.

If

a

scriptlet

or

Java

plug-in

returns

a

value

longer

than

4000

bytes,

DB2

will

throw

an

exception

error.

Naming

workflows,

parameters,

and

variables

Only

the

following

characters

can

be

used

in

workflow

names:

a-z,

A-Z,

0-9,

underscore

(_),

and

period

(.).

v

The

first

character

can

be

any

of:

a-z,

A-Z,

or

underscore

(_).

It

cannot

be

0-9

or

a

period

(.)

v

The

last

character

in

the

name

cannot

be

a

period

(.)

v

Intervening

characters

between

the

first

character

and

the

last

character

in

the

workflow

can

be:

a-z,

A-Z,

0-9,

underscore

(_),

or

period

(.)

v

Workflow

descriptions

can

be

255

characters

in

length.

Only

the

following

characters

can

be

used

for

workflow

parameter

and

variable

names:

a-z,

A-Z,

0-9,

and

underscore

(_).

v

The

first

character

can

only

be:

a-z,

A-Z,

or

underscore

(_).

It

cannot

be

0-9.

v

The

remaining

characters

can

be:

a-z,

A-Z,

0-9,

or

underscore

(_).

Note:

Any

Unicode

character

can

be

used

to

enter

comments

in

workflow

scripts.

New

Virtual

Server

doesn’t

get

added

to

correct

Resource

Pool

When

trying

to

allocate

a

virtual

server

on

a

Tivoli

Provisioning

Manager

AIX

managed

server

and

specifying

the

resource

pool,

it

successfully

calls

and

runs

the

workflow

pSeries

Create

Virtual

Server

,

but

it

doesn’t

put

the

new

virtual

server

in

the

resource

Pool

specified.

Instead,

the

virtual

server

ends

up

in

the

″no-owner″

server

list.

To

rectify

this,

set

that

property

manually.

Package

repository

attribute

required

for

cluster

during

XMLImport

A

cluster

import

throws

an

exception

because

it

could

not

find

a

property.

The

error

is:

COPCOM062E

The

system

cannot

find

the

deployment

engine

property

PackageRepositoryDir.

10:41:40,219

ERROR

[main]

xmlimport.XmlImport:

COPCOM062E

The

system

cannot

find

the

deployment

engine

property

PackageRepositoryDir.

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ObjectNotFoundException:

COPCOM062E

The

system

cannot

find

the

deployment

engine

property

PackageRepositoryDir.

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ImportCluster.

getRepositoryDir(ImportCluster.java:137)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ImportCluster.

importElement(ImportCluster.java:308)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ImportApplication.

importElement(ImportApplication.java:128)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ImportCustomer.

importElement(ImportCustomer.java:101)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.XmlImport.

importData(XmlImport.java:335)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.XmlImport.main(XmlImport.java:114)

10:41:40,594

MSG_ERROR

[main]

xmlimport.XmlImport:

COPCOM062E

The

system

cannot

find

the

deployment

engine

property

PackageRepositoryDir.

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ObjectNotFoundException:

COPCOM062E

The

system

cannot

find

the

deployment

engine

property

PackageRepositoryDir.

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ImportCluster.

getRepositoryDir(ImportCluster.java:137)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ImportCluster.

10

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

|||||

importElement(ImportCluster.java:308)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ImportApplication.

importElement(ImportApplication.java:128)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ImportCustomer.

importElement(ImportCustomer.java:101)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.XmlImport.

importData(XmlImport.java:335)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.XmlImport.

main(XmlImport.java:114)

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ObjectNotFoundException:

COPCOM062E

The

system

cannot

find

the

deployment

engine

property

PackageRepositoryDir.

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ImportCluster.

getRepositoryDir(ImportCluster.java:137)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ImportCluster.

importElement(ImportCluster.java:308)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ImportApplication.

importElement(ImportApplication.java:128)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.ImportCustomer.

importElement(ImportCustomer.java:101)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.XmlImport.

importData(XmlImport.java:335)

at

com.thinkdynamics.kanaha.datacentermodel.xmlimport.XmlImport.

main(XmlImport.java:114)

It

should

not

be

mandatory

for

this

property

to

be

present,

but

for

now

you

have

to

enter

a

value

for

the

PackageRepositoryDir

for

the

import

to

succeed..

-unsafe

command

line

parameter

for

XMLImport

If

XMLImport

fails

with

SQL

exception

SQL0964C,

use

the

–unsafe

command

line

parameter.

This

error

typically

occurs

when

you

are

importing

huge

data

center

model

(DCM)

files.

It

is

not

possible

to

use

this

parameter

within

the

reinit

script.

A

workaround

is

to

import

an

empty

file

during

reinit

and

then

use

XMLImport

with

the

–unsafe

parameter

to

import

your

DCM

file.

Note:

Using

the

–unsafe

parameter

will

damage

the

database

if

your

DCM

file

contains

any

errors.

If

this

happens,

the

database

must

be

recreated

using

the

reinit

script.

If

you

are

unsure

about

the

validity

of

your

DCM

file,

export

your

database

first

using

the

XMLExport

utility.

This

way,

should

the

database

become

corrupt,

you

can

recover

quickly.

Transaction

log

full

error

when

running

post-install.cmd

If

you

are

getting

this

error,

you

need

to

increase

the

allotted

size

of

the

database

parameter

LOGFILSIZ

to

8000.

The

default

size

on

UNIX

is

1000,

and

on

Windows

the

default

size

is

250.

To

change

the

database

log

file

size

to

8000,

run

the

following

command:

db2

update

database

configuration

for

db_name

using

LOGFILSIZ

8000

LOGPRIMARY

6

where

db_name

is

the

name

of

your

database.

The

large

log

file

size

is

needed

to

accommodate

all

possible

transactions,

which

in

some

cases

can

be

considerable.

The

LOGFILSIZ

parameter

is

used

by

the

primary

log

and

the

secondary

log.

The

number

of

primary

log

files

set

with

the

LOGPRIMARY

parameter

works

in

combination

with

the

LOGFILSIZ

parameter

to

provide

enough

space

for

all

possibilities.

Known

limitations,

problems

and

workarounds

11

|||

|||||

|

Automount

needs

to

be

disabled

on

Solaris

Tivoli

Provisioning

Manager

fails

to

create

user

account

on

Solaris

due

to

Automount

daemon

keeping

/home

as

the

mount

point.

The

user

needs

to:

1.

Login

as

root.

2.

Edit

the

file

/etc/auto_master.

For

example,

vi

/etc/auto_master.

3.

Comment

out

the

entry

for

/home.

To

do

this,

put

an

octothorpe

(#)

in

front

of

the

auto_home

line:

Change

this:

/home

auto_home

to

this:

#/home

auto_home

4.

Save

the

edited

auto_master

file.

5.

Run

Automount

to

read

in

the

changes.

Note:

If

this

change

is

only

required

temporarily,

remember

to

uncomment

the

/home

line

and

rerun

Automount

to

apply

the

change.

Install

the

new

Warehouse

Enablement

Pack

(WEP)

from

the

IBM

Tivoli

Software

Support

site

An

updated

Warehouse

Enablement

Pack

(WEP)

is

available

from

the

IBM

Tivoli

Software

Support

site

at

http://www.ibm.com/software/support/.

Before

following

the

instructions

to

install

Tivoli

Data

Warehouse

and

the

Warehouse

Enablement

Pack,

download

the

latest

version

of

the

Warehouse

Enablement

Pack

from

the

Support

Web

site.

The

update

contains

key

fixes

to

enable

Oracle

support

and

schema

changes

to

support

rollup

and

pruning.

To

get

the

update:

1.

Go

to

http://www.ibm.com/software/support/.

2.

Search

on

Tivoli

Provisioning

Manager

in

Downloads

only.

3.

When

the

search

results

are

displayed,

change

the

sort

order

to

Date-newest

first

so

the

most

recently

available

downloads

are

listed

first.

4.

Download

and

install

the

update.

12

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

|

Documentation

additions

This

section

contains

help

topics

which,

due

to

time

constraints,

are

not

available

in

the

online

help.

Data

center

fragment

A

data

center

fragment

(DCF)

is

a

subset

of

the

data

center

model

(DCM).

The

DCF

is

a

collection

of

DCM

objects

that

are

required

to

support

the

application

deployment

template

(ADT).

You

can

edit

the

deployment

plan

to

remove

any

elements

chosen

by

using

the

DCF

after

creating

the

deployment

plan.

Data

center

fragments

include:

switches

A

DCF

can

only

contain

one

switch

fabric,

so

all

switches

in

a

data

center

fragment

must

belong

to

the

same

switch

fabric.

routers

These

appear

as

detached

resources

in

the

DCF,

even

though

routers

are

a

subset

of

switches

in

the

data

center

model

(DCM).

pools

Pools

that

are

not

in

the

DCF

can

still

be

used

for

the

clusters

in

a

deployment

plan,

but

you

must

manually

add

them

when

you

create

or

edit

the

deployment

plan.

servers

Any

server

in

the

DCM

can

be

added

to

the

DCF.

Some

are

used

to

create

new

pools

if

there

are

no

pools

available

in

the

DCF.

Only

no-owner

(not

already

in

a

cluster

or

pool)

servers

are

used

to

assemble

new

pools.

If

there

are

none

available

to

be

selected,

the

user

must

manually

select

which

servers

to

use.

load

balancers

At

deployment

time,

if

there

are

any

Logical

Deployment

Templates

containing

clusters

using

load

balancers,

the

system

chooses

which

load

balancers

to

use

from

the

list

defined

in

the

Data

Centre

Fragment.

However,

the

user

can

override

this

behavior

and

use

any

other

load

balancers

defined

in

the

entire

Data

Centre

Model

by

editing

the

Deployment

Plan.

Configuring

a

data

center

fragment

As

soon

as

a

DCF

has

been

created

from

the

individual

devices,

you

can

configure

it

as

a

whole.

To

configure

a

data

center

fragment:

1.

Click

Data

center

assets

and

resources

→

Inventory

→

Data

Center

Fragments.

The

Data

Center

Fragments

Inventory

page

is

displayed.

2.

Click

the

name

of

the

DCF

you

want

to

configure.

The

Data

Center

Fragment

General

page

is

displayed.

Note:

To

rename

the

DCF,

click

Edit

→

Properties,

make

your

changes

and

then

click

Save

when

you

are

done.

You

can

also

fine-tune

your

DCF

by

©

Copyright

IBM

Corp.

2003,

2004

13

removing

previously

added

devices.

Identify

the

device

you

want

to

remove

and

then

click

More

→

Remove.

Viewing

the

software

registry

The

software

registry

is

a

repository

of

software

modules

used

when

creating

a

deployment

plan.

To

view

the

software

registry:

Click

Data

center

assets

and

resources

→

Inventory

→

Software

Registry.

The

Software

Registry

page

is

displayed.

Registering

software

The

registry

is

configured

by

adding

capabilities,

requirements

and

supported

requirement

types

to

software

products

and

stacks

already

existing

in

the

data

center

model

(DCM).

To

register

software:

1.

Click

Data

center

assets

and

resources

→

Inventory

→

Software

Registry.

The

Software

Registry

page

is

displayed.

2.

Click

Edit

→

Register.

The

Register

Software

dialog

is

displayed.

3.

Click

the

type

of

software

you

would

like

to

register

in

the

Software

Type

list.

Depending

on

your

selection

and

what

software

products

currently

exist

in

the

DCM,

the

Software

list

is

populated

with

options.

4.

Click

the

software

to

register

in

the

Software

list.

5.

Click

Save.

The

selected

software

is

displayed

in

the

Software

Registry

list.

Deregistering

software

To

deregister

software

previously

registered:

1.

Click

Data

center

assets

and

resources

→

Inventory

→

Software

Registry.

The

Software

Registry

page

is

displayed.

2.

Identify

the

software

in

the

list

you

would

like

to

deregister.

3.

Click

More

→

Deregister.

4.

Click

OK

when

prompted.

The

page

refreshes

and

the

selected

software

is

removed

from

the

list.

Editing

the

properties

of

a

software

module

If

a

software

module

has

capabilities

(the

ability

to

host

or

satisfy

the

requirements

of

other

software

modules),

it

is

referred

to

as

an

infrastructure

software

module.

To

edit

the

properties

of

a

software

module:

1.

Click

Data

center

assets

and

resources

→

Inventory

→

Software

Registry.

The

Software

Registry

page

is

displayed.

2.

Identify

the

module

in

the

list

you

want

to

edit.

3.

Click

More

→

Edit.

The

Software

Module

page

is

displayed,

showing

all

existing

requirements

and

capabilities.

14

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

To

add

requirements

1.

Click

Edit

→

Add

Requirement.

The

New

Requirement

dialog

box

is

displayed.

2.

Click

the

name

of

the

new

requirement

in

the

Name

list.

3.

Click

the

type

of

the

new

requirement

in

the

Type

list.

4.

Depending

on

the

item

selected

in

the

Name

list,

there

could

also

be

Available

Values

in

this

dialog.

If

there

are,

select

all

the

check

boxes

which

apply

to

the

requirement

you

are

adding.

5.

If

the

requirement

being

added

is

of

hosting

type,

select

the

Hosting

check

box.

6.

Click

Save.

The

new

requirement

is

added

to

the

existing

list

of

requirements

for

this

software

module.

Note:

If

more

than

one

Available

Values

check

box

was

selected,

the

list

under

Requirement

Values

has

all

the

selected

values

and

you

can

choose

which

one

should

be

current

by

clicking

it

in

the

Requirement

Value

list.

To

edit

a

requirement

1.

Identify

the

requirement

you

want

to

delete

in

the

Requirement

Name

list.

2.

Click

More

→

Edit.

The

Edit

Requirement

dialog

box

is

displayed.

3.

Make

changes

as

required.

4.

Click

Save.

The

requirement

is

updated

in

the

existing

list

of

requirements

for

this

software

module.

Note:

If

more

than

one

Available

Values

check

box

was

selected,

the

list

under

Requirement

Values

has

all

the

selected

values

and

you

can

choose

which

one

should

be

current

by

clicking

it

in

the

Requirement

Value

list.

To

delete

a

requirement

1.

Identify

the

requirement

you

want

to

delete

in

the

Requirement

Name

list.

2.

Click

More

→

Delete.

3.

Click

OK

when

prompted.

The

requirement

is

updated

in

the

existing

list

of

requirements

for

this

software

module.

To

add

a

supported

requirement

1.

Click

Edit

→

Add

Supported

Requirement.

The

Supported

Requirement

Type

dialog

box

is

displayed.

2.

Click

the

supported

type

in

the

Available

Requirement

Types

list.

3.

Click

Save.

The

new

Supported

Requirement

Type

Name

is

added

to

the

existing

list

of

supported

requirement

type

names

for

this

software

module.

To

delete

a

supported

requirement

1.

Identify

the

supported

requirement

you

want

to

delete

in

the

Supported

Requirement

Type

Name

list.

2.

Click

More

→

Delete.

3.

Click

OK

when

prompted.

To

add

a

capability

1.

Click

Edit

→

Add

Capability.

The

New

Capability

dialog

box

is

displayed.

2.

Click

the

name

of

the

capability

you

want

to

add

in

the

Name

list.

3.

If

the

capability

has

a

value,

enter

it

in

the

Value

field.

Documentation

additions

15

4.

Click

Save.

The

new

Capability

is

added

to

the

existing

list

of

capabilities

for

this

software

module.

To

edit

a

capability

1.

Identify

the

capability

you

want

to

edit

in

the

Capability

Name

list.

2.

Click

More

→

Edit.

The

Edit

Capability

dialog

box

is

displayed.

3.

Click

the

name

of

the

capability

you

want

to

add

in

the

Name

list.

4.

Edit

the

value

as

required.

5.

Click

Save.

Creating

a

deployment

plan

A

deployment

plan

is

a

list

of

resources,

configurations

and

implementations

required

to

realize

the

deployment

of

a

business

application.

A

business

application,

unlike

a

standalone

software

application,

can

span

across

multiple

tiers,

servers

or

systems.

The

actual

implementation

is

achieved

through

the

use

of

workflows.

You

must

follow

seven

steps

to

create

a

deployment

plan.

Each

step

must

be

completed

before

the

next

can

be

started.

The

seven

steps

are:

Step

1.

Select

a

logical

application

structure.

Step

2.

For

each

module

in

the

logical

application

structure,

select

a

software

stack

which

satisfies

the

hosting

requirements

of

the

application.

Step

3.

Select

an

application

deployment

template.

Step

4.

Specify

the

deployment

parameters.

Step

5.

Select

a

data

center

fragment.

Step

6.

Edit

the

deployment

plan.

Step

7.

Finalize

the

deployment

plan.

To

create

a

deployment

plan:

1.

If

the

application

for

the

deployment

plan

doesn’t

exist,

create

it.

2.

Click

Customer

applications

and

then

click

a

customer_name.

Then

click

an

application_name.

The

Application

Overview

Clusters

page

is

displayed.

Note:

If

there

are

currently

no

applications

in

the

data

center

model,

the

actual

first

step

will

be

creating

one.

3.

Click

the

Deployment

Topology

tab.

The

Application

Deployment

Topology

page

is

displayed.

4.

Click

Deployment

→

Create

New

Deployment

Plan

and

click

OK

when

prompted.

Selecting

a

logical

application

structure

Before

performing

this

action,

you

need

to

complete

“Creating

a

deployment

plan.”

A

logical

application

structure

(LAS)

consists

of

a

collection

of

business

modules.

The

LAS

is

selected

from

a

list

of

LAS

templates

in

the

database,

or

a

new

LAS

template

can

be

uploaded

to

the

database.

The

system

identifies

these

by

their

name.

16

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

Note:

Make

sure

the

names

defined

in

the

LAS,

ADT,

LDT

and

NTT

templates

are

unique.

To

select

a

logical

application

structure:

1.

Click

a

name

in

the

logical

application

structure

list

to

select

a

template

already

in

the

database.

If

the

template

you

want

to

select

is

not

yet

in

the

database,

click

Upload

Template

File,

browse

for

your

template

on

your

local

system

and

click

Update

to

add

the

template

to

the

database,

and

then

click

the

name

in

the

logical

application

structure

list

to

select

the

just

added

template.

2.

Click

Next.

Selecting

software

stacks

Before

performing

this

action,

you

need

to

complete

“Selecting

a

logical

application

structure”

on

page

16.

Tivoli

Provisioning

Manager

builds

the

software

stack

for

each

module

in

the

logical

application

structure

(LAS)

based

on

the

information

in

the

software

registry.

If

more

than

one

possible

solution

exists,

all

solutions

are

added

to

the

Hosting

options

list

so

the

user

can

select

the

most

appropriate

one.

This

happens

for

each

module

in

the

LAS.

To

select

software

stacks:

1.

For

each

module

in

the

list,

click

a

software

stack

name

in

the

Hosting

options

list.

Note:

The

number

of

modules

which

appear

in

the

list

is

determined

by

the

number

of

modules

in

the

LAS

template

selected

in

the

previous

step.

2.

Click

Next.

Note:

If

you

want

to

make

any

changes

to

the

previous

step,

click

Back.

Proceed

to

Selecting

an

application

deployment

template.

Selecting

an

application

deployment

template

Before

performing

this

action,

you

need

to

complete

“Selecting

software

stacks.”

The

application

deployment

template

(ADT)

is

a

combination

of

the

logical

deployment

template

(LDT)

and

the

network

topology

template

(NTT).

If

the

ADT

doesn’t

already

exist

in

your

database,

you

can

upload

one,

or

create

one

from

an

existing

LDT

in

combination

with

an

existing

NTT.

To

select

an

application

deployment

template:

Click

a

name

in

the

application

deployment

template

list

to

select

a

template

already

in

the

database.

If

the

template

you

want

to

select

is

not

yet

in

the

database,

click

Upload

Template

File,

browse

for

your

template

on

your

local

system

and

click

Update

to

add

the

template

to

the

database.

Then

click

the

the

template

name

in

the

application

deployment

template

list.

Note:

If

you

want

to

make

any

changes

to

the

previous

step,

click

Back.

Documentation

additions

17

Specifying

additional

deployment

parameters

Before

performing

this

action,

you

need

to

complete

“Selecting

an

application

deployment

template”

on

page

17.

Some

clusters

can

be

parameterized

during

deployment.

This

means

that

their

minimum

and

maximum

value

is

not

hardcoded.

For

each

module,

you

can

enter

the

minimum

and

maximum

size

of

the

cluster

at

this

point

in

the

wizard.

To

specify

additional

deployment

parameters

for

each

module

in

the

list:

1.

Type

the

initial,

or

minimum,

value

of

the

module

you

want

in

the

min-size

field.

2.

Repeat

for

each

listed

module.

3.

Type

the

maximum

value

of

the

module

you

want

in

the

max-size

field.

4.

Click

Next.

Note:

If

you

want

to

make

any

changes

to

the

previous

step,

click

Back.

Selecting

a

data

center

fragment

Before

performing

this

action,

you

need

to

complete

“Specifying

additional

deployment

parameters.”

Selecting

a

data

center

fragment

(DCF)

tells

the

deployment

plan

what

resources

it

has

access

to.

If

no

DCF

is

selected,

the

entire

data

center

model

(DCM)

is

assumed.

Note:

Be

aware

that

selecting

a

DCF

does

not

reserve

the

objects

in

the

DCF

for

the

deployment

plan,

it

simply

restricts

the

selection

possibilities.

To

select

a

data

center

fragment:

1.

Click

a

name

in

the

data

center

fragment

list

to

select

a

DCF

already

in

the

database.

2.

Click

Next

to

generate

the

deployment

plan.

Note:

If

you

want

to

make

any

changes

to

the

previous

step,

click

Back.

Reviewing

the

deployment

plan

Before

performing

this

action,

you

need

to

complete

“Selecting

a

data

center

fragment.”

Reviewing

the

deployment

plan

produced

by

the

wizard,

allows

you

to

fine-tune

the

plan

before

finalizing

it.

You

can

rename

elements

either

by

clicking

on

their

name

or

by

clicking

properties,

if

the

element

has

a

properties

icon

menu

associated

with

it.

Note:

In

the

plan,

you

will

see

several

elements

called

<server

template>.

Based

on

your

input

in

the

previous

wizard

steps,

the

clusters

and

servers

created

in

your

plan

need

basic,

structural

information.

For

instance,

you

will

need

to

know

how

many

NICs

should

be

configured

for

this

server

and

what

all

their

vlan/subnet/port

details

are.

This

information

can

be

changed

later,

but

it

needs

to

be

created

at

this

stage.

18

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

To

review

the

deployment

plan:

1.

Review

and

rename

elements,

as

desired.

2.

Click

Next

to

finalize

the

deployment

plan.

Note:

If

you

want

to

make

any

changes

to

the

previous

step,

click

Back.

Finalizing

the

deployment

plan

Before

performing

this

action,

you

need

to

complete

“Reviewing

the

deployment

plan”

on

page

18.

When

you

finalize

the

deployment

plan,

you

are

saving

it.

If

you

return

to

this

application

later,

the

plan

you

generated

will

still

be

there.

Note:

Finalizing

or

saving

a

deployment

plan

does

not

reserve

the

objects

in

the

plan,

it

simply

provides

a

configuration

snapshot

at

the

time

the

plan

was

generated.

You

can

also

make

the

same

changes

here

that

you

can

during

the

review

step.

To

finalize

the

deployment

plan:

1.

Select

the

Realize

the

Plan

Immediately

check

box

if

you

want

to

implement

this

plan

right

away.

2.

Click

Finish

to

finalize

or

save

the

deployment

plan.

Note:

If

you

want

to

make

any

changes

to

the

previous

step,

click

Back.

To

deploy

a

saved

plan

at

a

later

date,

without

changes,

simply

come

back

to

this

application

and

on

the

Deployment

Topology

page,

click

Deployment

→

Deploy.

Documentation

updates

The

following

sections

contain

errata

which

complements

or

corrects

existing

help

information.

Installation

Guide

correction

In

the

Installation

Guide

section

titled

″Post-Installation

steps″

there

are

instructions

to

edit

the

file

datacenter.xml

after

you

have

installed

Tivoli

Provisioning

Manager.

This

file

is

found

either

in

%TIO_HOME%\xml,

for

Windows

environments,

or

in

$TIO_HOME/xml,

for

UNIX

environments.

You

should

not

perform

these

steps

at

that

point

of

the

installation

process,

as

required

information

has

not

yet

been

defined.

The

datacentermodel.xml

file

requires

that

you

declare

some

variables

for

your

data

center

before

importing

it,

such

as

vlan,

subnet

or

software

product.

You

must

first

enter

the

VLAN,

subnet

and

software

product

for

your

Tivoli

Provisioning

Manager

system

before

you

can

import

the

xml

file

which

references

(or

uses)

it.

To

enter

the

values

in

the

application,

after

completing

the

installation:

1.

Logon

to

Tivoli

Provisioning

Manager.

For

more

information,

refer

to

the

Installation

Guide.

2.

Enter

the

information

required

for

the

subnet,

VLAN

and

software

product

in

your

data

center.

Information

on

completing

this

task

can

be

found

in

the

online

help.

3.

Logoff

from

Tivoli

Provisioning

Manager.

Documentation

additions

19

4.

Now,

follow

the

instructions

provided

in

the

″Post-installation

steps″

of

the

Installation

Guide

to

edit

the

file

datacentermodel.xml.

Creating

a

new

workflow

The

Tutorial:

Creating

a

new

workflow

topic

references

a

menu

item

named:

Add

Workflow.

This

has

been

changed

to

New.

Running

a

workflow

using

a

defined

service

access

point

To

run

a

workflow

using

a

defined

service

access

point:

1.

Click

Data

center

assets

and

resources

→

Inventory→

Servers

→

Server

name.

2.

Click

the

Credentials

tab.

3.

In

the

list,

click

the

name

of

the

service

access

point

to

assign

to

your

workflows.

If

one

does

not

exist,

click

Edit

→

Add

Access

Point.

4.

Click

the

new

service

access

point.

5.

Click

the

Workflows

tab.

6.

In

the

Logical

Operations

list,

select

the

logical

operation

for

the

workflow.

7.

In

the

Workflow

list,

click

the

workflow

to

assign

to

the

service

access

point.

8.

Click

Add

Selected

Workflow.

The

workflow

is

added

to

the

list

of

all

workflows

that

are

currently

assigned

to

that

service

access

point.

If

necessary,

repeat

steps

6

through

8

to

assign

other

workflows

to

this

service

access

point.

Note:

Some

device

drivers

are

predefined

for

service

access

points

that

are

running

certain

application

protocols.

For

example,

SNMP

v1

and

SSH

both

have

predefined

drivers.

Viewing

workflow

run

history

The

steps

for

viewing

run

history

are

incorrect

in

the

Troubleshooting

workflows

topic.

The

correct

steps

are:

1.

After

you

run

a

workflow,

the

Deployment

Requests

page

is

displayed.

On

that

page,

click

the

Request

ID

of

that

same

workflow.

The

Execution

Logs

page

is

displayed.

2.

Select

Click

for

more

workflow

actions.

3.

Click

Error.

The

Error

page

is

displayed.

Note:

You

can

access

the

Execution

Logs

page

by

clicking

System

configuration

and

workflow

management

→

Deployment

Requests.

Repeat

the

steps

above

to

view

the

run

details

of

a

workflow.

Stopping

a

workflow

The

steps

in

the

Stopping

a

workflow

that

is

running

topic

are

incorrect.

The

correct

steps

are:

1.

After

you

run

a

workflow,

the

Deployment

Requests

page

is

displayed.

On

that

page,

click

the

Request

ID

of

that

same

workflow.

The

Execution

Logs

page

is

displayed.

2.

Select

Click

for

more

workflow

actions.

3.

Click

Stop

Execution.

20

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

Displaying

workflow

run

history

The

first

step

of

the

topic,

Displaying

workflow

run

history

is

incorrect.

It

should

read:

1.

Click

System

configuration

and

workflow

management

→

Deployment

Requests.

Using

the

TC_HOME

variable

Any

instance

of

TC_HOME

in

the

documentation

should

be

replaced

with

TIO_HOME.

Workflow

variables,

parameters,

and

transitions

The

Adding

and

managing

workflow

variables

and

parameters

and

Adding

and

managing

workflow

transitions

topics

in

the

online

help

are

obsolete.

Setting

up

Tivoli

Provisioning

Manager

to

collect

utilization

data

This

section

describes

changes

to

the

configuration

steps

required

to

set

up

Tivoli

Monitoring

to

collect

utilization

data

from

managed

servers.

This

procedure

is

described

in

the

information

center

topic

“Setting

up

Tivoli

Intelligent

ThinkDynamic

Orchestrator

to

collect

utilization

data”.

Required

data

center

objects

Before

you

start

configuration

steps

in

the

Web-based

interface

described

in

the

documentation,

you

must

ensure

that

the

data

center

objects

required

for

CPU

data

collection

by

Tivoli

Monitoring

are

defined

in

your

data

center

model.

v

objective-analyzer-type

object

for

capacity

on

demand

v

data-acquisition

object

These

data

center

objects

cannot

be

defined

in

the

Web-based

interface.

If

you

initialized

your

data

center

model

with

the

sample

data

center

contained

in

the

venice.xml

file,

the

required

data

center

objects

will

already

be

loaded.

If

you

performed

initialization

with

an

empty

data

center

model,

imported

an

existing

data

center

model

XML

file

that

does

not

contain

the

required

objects,

or

migrated

from

a

previous

release

of

Tivoli

Provisioning

Manager,

you

must

create

and

import

an

XML

file

that

contains

the

required

data

center

objects:

Set

up

these

objects

as

follows:

objective-analyzer-type

CPU

utilization

data

is

only

collected

for

servers

that

are

dedicated

or

allocated

to

an

application

cluster.

Within

the

XML

file

you

must

associate

the

objective

analyzer

for

capacity

on

demand

with

the

parent

application

of

the

servers

Tivoli

Monitoring

is

monitoring

for

CPU

utilization.

data-acquisition

You

must

define

a

data

acquisition

object

that

is

used

for

the

CPU

utilization

data

collection.

The

sample

XML

file

in

this

section

shows

how

these

objects

are

defined,

as

well

as

the

other

properties

associated

with

CPU

utilization

collection

by

Tivoli

Monitoring.

These

additional

properties

can

also

be

configured

in

the

Web-based

interface.

Documentation

additions

21

Once

you

have

defined

the

required

objects

and

associated

the

objective-analyzer-type

object

with

the

applications

that

you

want

to

monitor

for

CPU

utilization,

you

must

import

the

XML

file

with

the

xmlImport

command.

v

Windows:

%TIO_HOME%\tools\xmlimport.cmd

file:%TIO_HOME%\xml\import_file

v

UNIX:

$TIO_HOME/tools/xmlimport.sh

file:$TIO_HOME/xml/import_file

Where

import_file

is

the

XML

file

to

import.

For

details

about

importing

XML

files,

refer

to

the

Tivoli

Provisioning

Manager

information

center.

Changes

to

the

component

for

Tivoli

Monitoring

variables

In

the

current

information

center,

the

topic

“Setting

up

Tivoli

Intelligent

ThinkDynamic

Orchestrator

to

collect

utilization

data”

indicates

that

the

variables

are

associated

with

the

data

acquisition

engine

component.

These

variables

associations

have

been

changed

to

so

that

configuration

of

Tivoli

Monitoring

for

both

CPU

data

collection

and

server

monitoring

(using

Tivoli

Monitoring

as

a

monitoring

application)

use

the

same

component

associations.

For

the

configuration

of

both

features,

these

variables

are

associated

with

the

deployment

engine

component.

Sample

XML

file

The

following

XML

file

shows

the

data

center

object

definitions

required

to

set

up

Tivoli

Monitoring

to

collect

CPU

utilization

data.

<?xml

version="1.0"

encoding="UTF-8"?>

<!DOCTYPE

datacenter

SYSTEM

"../xml/xmlimport.dtd">

<datacenter>

<!--

add

SUBNETWORK

-

need

subnet

for

each

real

server

IP

address

-->

<subnetwork

name="192.168.138.0/24"

ipaddress="192.168.138.0"

netmask="255.255.255.0">

<vlan

vlan-number="801"

fabric="Default

Fabric"/>

</subnetwork>

<!--

The

TIO

Server

and

the

TMR

Servers

as

in

a

SPARE

POOL

-->

<spare-pool

name="A142"

os-type="windows"

fabric="Default

Fabric"

vlan="801"

>

<!--

TIO

SERVER

-->

<server

name="tgs41"

is-device-model="Windows

Operating

System"

locale="en_US">

<!--

REMEMBER

THIS

IS

THE

ADDRESS

OF

THE

VMWARE

HOST,

NOT

THE

VMWARE

IMAGE

HOST

api.myhost.domain.com

=>

192.168.138.169

HOST

solo.myhost.domain.com

=>

192.168.138.227

-->

<network-interface

name="tgs41.myhost.domain.com"

ipaddress="192.168.138.227"

netmask="255.255.255.0"/>

</server>

<!--

TMR

1

-

SunOS

5.8

-->

<server

name="robinson"

is-device-model="Solaris

Operating

System"

locale="en_US">

<network-interface

name="robinson.myhost.domain.com"

ipaddress="192.168.138.78"

netmask="255.255.255.0"/>

<!--

NOTE:

These

properties

apply

to

two

ITM

integration

features:

-

Using

ITM

as

a

monitoring

application

-

Using

ITM

to

collect

CPU

utilization

data

-->

<property

component="DEPLOYMENT_ENGINE"

name="TMA.Label_propkey"

value="TMR1.TMA_Label"/>

<property

component="DEPLOYMENT_ENGINE"

name="TMR1.TMA_Label"

value="robinson-tmr1"/>

<property

component="DEPLOYMENT_ENGINE"

name="TMR2.TMA_Label"

value="robinson-tmr2"/>

<!--

These

properties

apply

if

you

are

configuring

ITM

to

collect

CPU

utilization

data

-->

22

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

<property

component="DATA_ACQUISITION_ENGINE"

name="TIO.TMETaskLibraryName"

value="TIOTaskLib"/>

<property

component="DATA_ACQUISITION_ENGINE"

name="TIO.TMETaskName"

value="TIOGetCPUTask"/>

<property

component="DATA_ACQUISITION_ENGINE"

name="TIO.TMEBunchFactor"

value="30"/>

<property

component="DATA_ACQUISITION_ENGINE"

name="TIO.TMETaskTimeout"

value="150000"/>

<sap

name="TMRLogin"

port="0"

host="true"

protocol-type="unknown"

app-protocol="UNKNOWN"

locale="en_US">

<credentials

search-key="tme"

is-default="true">

<password-credentials

username="root"

password="inn0v8"/>

</credentials>

</sap>

</server>

<!--

TMR

2

-

AIX

5.2

-->

<server

name="kilauea"

is-device-model="AIX

Operating

System"

locale="en_US">

<network-interface

name="kilauea.myhost.domain.com"

ipaddress="192.168.138.171"

netmask="255.255.255.0"/>

<!--

NOTE:

These

properties

apply

to

two

ITM

integration

features:

-

Using

ITM

as

a

monitoring

application

-

Using

ITM

to

collect

CPU

utilization

data

-->

<property

component="DEPLOYMENT_ENGINE"

name="TMA.Label_propkey"

value="TMR2.TMA_Label"/>

<property

component="DEPLOYMENT_ENGINE"

name="TMR1.TMA_Label"

value="kilauea-tmr1"/>

<property

component="DEPLOYMENT_ENGINE"

name="TMR2.TMA_Label"

value="kilauea-tmr2"/>

<!--

These

properties

apply

if

you

are

configuring

ITM

to

collect

CPU

utilization

data

-->

<property

component="DEPLOYMENT_ENGINE"

name="TIO.TMETaskLibraryName"

value="TIOTaskLib"/>

<property

component="DEPLOYMENT_ENGINE"

name="TIO.TMETaskName"

value="TIOGetCPUTask"/>

<property

component="DEPLOYMENT_ENGINE"

name="TIO.TMEBunchFactor"

value="30"/>

<property

component="DEPLOYMENT_ENGINE"

name="TIO.TMETaskTimeout"

value="150000"/>

<sap

name="TMRLogin"

port="0"

host="true"

protocol-type="unknown"

app-protocol="UNKNOWN"

locale="en_US">

<credentials

search-key="tme"

is-default="true">

<password-credentials

username="root"

password="inn0v8"/>

</credentials>

</sap>

</server>

</spare-pool>

<!--

NOT

NEEDED

if

you

imported

"venice.xml"

<objective-analyzer-type

name="TIO

capacity-on-demand"

classname="com.ibm.tivoli.orchestrator.

objectiveAnalyzer.tio.TIOPerfmObjectiveAnalyzer"

description="Capacity

on

demand"

id="7">

<objective-analyzer-parameter

name="weighting"

default-value="1"

description="weighting"/>

<objective-analyzer-parameter

name="display-server-utilization"

default-value="true"/>

</objective-analyzer-type>

-->

<customer

name="BIG

Tivoli

Customer">

<application

name="BIG

Tivoli

Customer

Application"

priority="1">

<service-level-objective

internal="false"

type="min-availability"

value="0.99"/>

<service-level-objective

internal="false"

type="max-response-time"

value="0.167"/>

<cluster

name="ITM

Cluster"

min-servers="0"

max-servers="4"

pool="IIS-Win2K"

vlan="801"

fabric="Default

Fabric">

<with-load-balancer

name="Alteon

184-01"/>

<server

name="bear-tma"

is-device-model="Windows

Operating

System"

locale="en_US">

<network-interface

name="bear.myhost.domain.com"

ipaddress="192.168.138.21"

Documentation

additions

23

netmask="255.255.255.0"/>

<!--

NOTE:

These

properties

apply

to

two

ITM

integration

features:

-

Using

ITM

as

a

monitoring

application

-

Using

ITM

to

collect

CPU

utilization

data

-->

<property

component="DEPLOYMENT_ENGINE"

name="TMR1.TMA_Label"

value="bear-tmr1"/>

<property

component="DEPLOYMENT_ENGINE"

name="TMR2.TMA_Label"

value="bear-tmr2"/>

</server>

<property

component="DEPLOYMENT_ENGINE"

name="itmserver"

value="kilauea"/>

<property

component="DEPLOYMENT_ENGINE"

name="server.driver"

value="com.thinkdynamics.kanaha.dataacquisitionengine.itm.ITMDriver"/>

<data-acquisition>

<!--

This

"dae-driver"

and

the

next

two

"dae-signal"

elements

configure

a

"null"

load

balancer

-->

<dae-driver

device="load-balancer"

classname="com.thinkdynamics.kanaha.

dataacquisitionengine.ZeroValueDriver"/>

<dae-signal

name="arrival-rate"

device="load-balancer"

metric="arrival-rate"

aggregation="any"

filter="low-pass-filter"/>

<dae-signal

name="raw-arrival-rate"

device="load-balancer"

metric="arrival-rate"

aggregation="any"

filter="low-pass-filter"/>

<!--

This

"dae-driver"

and

the

"dae-signal"

elements

configure

our

CPU

utilization

-->

<dae-driver

device="server"

classname="com.thinkdynamics.kanaha.

dataacquisitionengine.itm.ITMDriver"/>

<dae-signal

name="cpu-utilization"

device="server"

metric="cpu-utilization"

aggregation="average"

filter="low-pass-filter"/>

</data-acquisition>

</cluster>

<objective-analyzer

type-name="TIO

capacity-on-demand"/>

</application>

</customer>

</datacenter>

NAT

support

added

Ability

to

define

multiple

identical

subnetworks

with

the

same

IP

in

various

address

spaces

has

been

added.

SOAP

commands

for

obtaining

server

IDs

There

is

a

typographical

error

in

the

getDCMObjectIdFromIPAddress

documentation.

Be

sure

that

anywhere

the

term

getDCMObjectIdFromIPAddress

is

used,

it

is

spelled

exactly

as

shown

here.

The

Note

under

getDCMObjectIdFromServerName

should

say

Currently,

this

method

works

the

same

way

as

the

getDCMObjectIdFromHostName

method.

Also,

the

server_name

definition

should

say

The

host

name

of

the

server

(for

example,

hp-server6).

Under

getDCMObjectIdFromHostName,

the

host_name

definition

should

say

The

host

name

of

the

server

(for

example,

hp-server6).

24

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

Deploying

a

monitoring

configuration

to

a

server

If

you

are

using

Tivoli

Monitoring

with

Tivoli

Provisioning

Manager

to

manage

monitoring

of

servers,

a

server

that

you

want

to

monitor

must

meet

the

following

requirements

before

you

can

configure

monitoring,

as

described

in

the

Information

Center

online

help

topic

“Applying

monitoring

to

servers”.

v

The

Tivoli

Monitoring

Agent

(TMA)

must

be

added

to

the

endpoint

v

The

Java

Runtime

Environment

(JRE)

must

be

installed,

as

specified

in

the

Tivoli

Monitoring

User

Guide

The

Tivoli

Monitoring

software

package

includes

a

JRE

image

for

most

platforms.

You

can

also

use

the

following

command

to

push

JRE

to

an

endpoint.

wdmdistrib

-J

java_image_root_dir

endpoint

where

java_image_root_dir

is

the

location

of

the

JRE

image

and

endpoint

is

the

endpoint

label.

For

more

information,

refer

to

the

Tivoli

Monitoring

documentation.

SOAP

command

syntax

reference:

getApplicationMode

The

example

given

should

say

soapcli

tc

pwd

http://hostname:port/tcSoap/wsdl/com/ibm/tc/soap/OperationsModeSer

vice.wsdl

getApplicationMode

1208.

Viewing

the

discovery

ID

of

Discovery

Objects

There

are

times

when

the

user

is

prompted

for

the

Discovery

ID

of

discovery

objects.

To

determine

what

this

ID

is,

click

Data

center

assets

and

resources

→

Inventory

→

Discovery.

Hold

the

cursor

over

the

object

you

want

to

know

the

ID

of,

and

in

a

moment,

the

ID

appears

in

a

popup

tip.

Updates

to

running

SOAP

commands

from

a

remote

computer

Java

requirements

To

run

SOAP

commands

from

a

remote

computer,

a

Java

Development

Kit

(JDK)

that

supports

Java

Technology

version

1.4

or

later

must

be

installed

on

the

remote

server.

Before

you

copy

the

SOAP

commands

to

the

remote

server

and

modify

the

soapcli

scripts,

ensure

that

the

SDK

is

installed

and

properly

configured.

1.

Install

a

JDK

if

one

is

not

currently

installed.

You

can

obtain

a

JDK

from

IBM,

Sun

Microsystems,

and

various

open

source

groups.

v

The

IBM

developer

kits

are

available

from

http://www-106.ibm.com/developerworks/java/jdk/

v

The

Sun

Microsystems

developer

kits

are

available

from

http://java.sun.com

Note:

The

JDK

installation

directory

should

not

include

spaces.

2.

Ensure

that

the

JAVA_HOME

environment

variable

is

set

to

the

SDK

installation

directory.

3.

If

you

are

using

a

remote

Windows

server,

add

the

\java\bin

directory

to

the

system

path.

For

example,

if

the

directory

path

is

d:\java\bin,

type

the

following

command

at

the

command

line:

PATH=d:\java\bin;%PATH%.

Documentation

additions

25

Procedure

for

running

commands

remotely

Several

changes

apply

to

the

procedures

for

running

SOAP

commands

from

a

remote

computer

as

described

in

the

online

help

topic

“Running

SOAP

commands

from

the

command

line”.

Setting

up

the

remote

computer

The

following

changes

apply

to

setting

up

a

remote

computer

to

run

SOAP

commands:

v

A

SOAP

script

is

available

for

running

SOAP

commands

from

a

bash

environment

on

a

Windows

server.

This

script

is

useful

when

an

application

runs

remote

commands

from

a

bash

environment

on

a

Windows

server.

Examples

include:

–

Using

Tivoli

Enterprise

Console

on

a

Windows

server

to

run

SOAP

commands

when

a

workflow

fails.

Tivoli

Enterprise

Console

runs

the

remote

commands

in

a

bash

environment.

–

Running

SOAP

commands

from

a

Cygwin

window

on

a

Windows

server.v

Updates

to

environment

variables

that

need

to

be

set

for

running

commands.

The

variable

%TC_HOME%

has

changed

to

%TIO_HOME%.

The

updated

procedure

for

setting

up

the

remote

server

is

as

follows:

1.

Copy

the

contents

of

the

%TIO_HOME%\tools\soap

directory

to

the

remote

computer.

2.

On

the

remote

computer,

open

the

appropriate

SOAP

command-line

interface

script

in

a

text

editor.

Windows

soapcli.cmd

Windows

running

commands

in

a

bash

environment

soapcli_bash4win.sh

Unix

soapcli.sh

3.

Make

the

appropriate

changes

to

the

configuration.

soapcli.cmd

a.

In

the

line

set

MY_LIB=%TIO_HOME%\tools\soap\lib,

change

%TIO_HOME%\tools\soap

to

the

directory

that

contains

the

files

that

you

copied

to

the

remote

server.

For

example,

if

you

copied

the

files

to

d:\soapcmd,

change

the

value

to:

MY_LIB=d:\soapcmd\lib

b.

Change

the

variable

%JAVA_HOME%

to

the

installation

directory

for

the

JDK

on

this

server,

if

it

does

not

match

the

directory

defined

by

the

JAVA_HOME

environment

variable.

soapcli.sh

or

soapcli_bash4win.sh

In

the

line

set

MY_LIB=$TIO_HOME/tools/soap/lib,

change

$TIO_HOME/tools/soap

to

the

directory

that

contains

the

files

that

you

copied

to

the

remote

server.

For

example,

if

you

copied

the

files

to

/usr/soapcmd,

change

the

value

to:

MY_LIB=/usr/soapcmd/lib

Change

the

variable

$JAVA_HOME

to

the

installation

directory

for

the

JDK

on

this

server,

if

it

does

not

match

the

directory

defined

by

the

JAVA_HOME

environment

variable.4.

Save

the

file.

26

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

Running

SOAP

commands

remotely

from

a

bash

environment

on

a

Windows

server

The

SOAP

command

syntax

information

in

the

online

help

refers

to

the

soapcli.cmd

and

soapcli.sh

scripts

only.

If

you

need

to

run

SOAP

commands

from

a

bash

environment

on

a

Windows

server,

replace

references

to

soapcli

with

soapcli_bash4win.

The

following

example

shows

a

command

for

moving

a

port

to

a

new

VLAN:

soapcli_bash4win

tc

pwd

"http://tio.myhost.com:9080/tcSoap/wsdlservice?wsdl=

wsdl/com/ibm/tc/soap/SwitchComponentService.wsdl"

movePortToVLAN

1039

1032

1034

null

11

Note:

The

above

command

should

be

typed

all

on

one

line.

Due

to

space

constraints,

it

is

shown

wrapped

on

two

lines

here.

Log

files

Log

file

location

In

previous

releases

of

Tivoli

Intelligent

ThinkDynamic

Orchestrator,

log

files

for

the

product

were

stored

in

the

$TC_HOME/logs

directory.

In

Tivoli

Intelligent

ThinkDynamic

Orchestrator

2.1,

log

files

are

stored

in

the

Tivoli

Common

Directory,

a

central

location

on

the

system

that

stores

serviceability-related

files

for

all

Tivoli

products.

Log

files

for

Tivoli

Intelligent

ThinkDynamic

Orchestrator

are

stored

in

Tivoli_commondir/COP/logs,

where

Tivoli_commondir

is

the

default

location

of

the

Tivoli

Common

Directory.

Windows

The

default

value

is

ProgramFilesDir\ibm\tivoli\common\,

where

ProgramFilesDir

represents

the

value

of

the

Windows

registry

entry

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProgramFilesDir

Unix

The

default

value

is

/var/ibm/tivoli/common.

Trace

and

message

log

file

names

The

names

of

the

trace

and

message

logs

are

incorrect

in

the

online

help.

Table

1.

Log

file

names

Log

file

File

name

in

online

help

Correct

file

name

Trace

log

console.log

trace.log

Message

log

message.log

msg.log

Capacity

on

demand

In

Tivoli

Intelligent

ThinkDynamic

Orchestrator

1.1,

automatic

server

provisioning

occurs

when

the

application

clusters

are

in

automatic

mode,

based

on

demand

and

application

priority.

In

release

2.1,

you

can

enable

or

disable

automatic

server

provisioning,

or

capacity

on

demand,

at

the

application

level.

By

default,

capacity

on

demand

is

disabled.

When

capacity

on

demand

is

disabled,

servers

are

not

automatically

provisioned

when

application

demand

increases

or

released

when

demand

decreases.

You

should

disable

capacity

on

demand

for

an

application

when:

Documentation

additions

27

v

You

want

to

deploy

the

application

with

a

fixed

number

of

servers

that

does

not

change

based

on

demand.

For

example,

this

behavior

can

be

useful

in

test

environments

where

resources

are

shared.

You

can

set

up

an

application

reservation

for

a

specific

number

of

servers

that

are

only

required

for

the

reservation

period.

v

You

want

to

closely

manage

server

allocation

for

the

application

in

manual

mode.

When

capacity

on

demand

is

enabled,

servers

are

automatically

allocated

to

clusters

when

demand

increases,

and

removed

when

demand

decreases.

You

should

enable

capacity

on

demand

for

an

application

when:

v

You

want

the

system

to

automatically

manage

server

provisioning

for

the

application

in

automatic

mode.

v

You

want

to

review

and

implement

server

allocation

recommendations

for

the

application

in

semi-automatic

mode.

You

can

enable

or

disable

capacity

on

demand

when

you

add

or

modify

an

application.

1.

In

the

Customer

applications

navigation

tree,

click

the

application

that

you

want

to

change.

2.

If

the

application

is

not

in

maintenance,

click

Management>To

Maintenance.

3.

Click

Edit>Properties.

4.

Change

the

Capacity

On

Demand

setting

as

required.

Creating

resource

reservations

for

an

application

This

section

applies

to

resource

reservations

for

an

application.

In

the

Tivoli

Provisioning

Manager

information

center,

the

topic

“Requesting

resources

for

a

specific

period”

describes

the

required

conditions

for

resource

reservations.

One

additional

requirement

applies

to

application

reservations.

The

application

that

you

want

to

reserve

cannot

contain

dedicated

servers.

The

workflows

that

deallocate

servers

after

the

application

reservation

period

will

fail

if

a

cluster

in

the

application

contains

dedicated

servers.

Working

with

power

units

and

outlets

Both

power

units

and

power

outlets

are

controlled

from

the

Power

Units

General

Tab.

To

turn

a

Power

Unit

on,

off

or

to

initialize

it

Click

Data

center

assets

and

resources

→

Inventory

→

Power

Units

and

then

click

the

name

of

the

power

unit

you

would

like

to

work

with.

To

control

the

power

unit,

on

the

General

tab

click

Management

and

select

the

desired

action

from

the

menu.

To

turn

an

Outlet

on,

off

or

to

cycle

its

power

Click

Data

center

assets

and

resources

→

Inventory

→

Power

Units

and

then

click

the

name

of

the

power

unit

you

would

like

to

work

with.

To

control

the

outlet,

locate

the

outlet

you

would

like

to

control

on

the

General

tab

and

then

click

More

and

select

the

desired

action

from

the

menu.

28

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

Migration

Guide

updates

Several

changes

apply

to

the

Tivoli

Provisioning

Manager

Version

2.1

Migration

Guide.

Database

upgrade

changes

The

following

changes

apply

to

the

“Upgrading

the

database

server”

chapter:

v

In

the

section

titled

“Upgrading

the

DB2

Universal

Database

client”,

step

4

should

state

that

the

Run-Time

Client

must

be

removed,

and

step

5

should

state

that

the

Administration

Client

must

be

installed.

v

The

APAR

IY57410

patch

for

DB2

Universal

Database

must

be

applied

after

applying

Fix

Pack

3,

as

described

on

“APAR

IY57410

patch

for

DB2”

on

page

4.

v

For

migrations

in

an

AIX

environment,

one

possible

migration

path

is

a

two-node

topology

with

DB2

Universal

Database

installed

on

the

same

machine

as

Tivoli

Provisioning

Manager.

If

you

are

following

this

migration

path,

you

must

catalog

a

TCP/IP

loopback

connection

to

enable

a

single

machine

to

simulate

a

two-machine

configuration

for

DB2

Universal

Database.

To

implement

the

loopback:

1.

Catalog

the

TCP/IP

node

with

the

following

command:

db2

catalog

tcpip

node

tcpip_nodename

remote

serverName

server

50000

where

serverName

is

the

host

name

of

the

machine

and

tcpip_nodename

is

a

name

for

the

node.

2.

Implement

the

loopback

using

the

following

commands:

db2

uncatalog

database

database_name

db2

catalog

database

database_name

at

node

tcpip_nodename

db2

catalog

database

database_name

as

database_alias

db2

catalog

database

database_alias

as

database_name

at

node

tcpip_nodename

where

database_name

is

the

host

name

of

your

database

server,

database_alias

is

the

alias

name

of

the

database

server,

and

tcpip_nodename

is

the

node

name.

3.

Verify

that

you

are

able

to

connect

to

the

database

using

the

command:

db2

connect

to

database_name

user

database_name

using

database_password

4.

Terminate

the

connection

using

the

command:

db2

connect

reset

Changes

to

data

migration

The

following

change

applies

to

the

“Migrating

data”

chapter:

In

the

section

titled

“Installing

core

automation

packages”,

the

location

of

the

log4j-util.prop

file

should

be:

For

Windows

TIO_instaldir\config

For

UNIX

TIO_instaldir/config

Changing

this

value

is

only

required

if

you

want

to

increase

the

logging

level

during

the

automation

package

installation

process.

Documentation

additions

29

|

||

|

|

|||

||

|||||

|

|

|

||

|

||||

||

|

|

|

|

|

||

||

||

||

30

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

Contacting

Software

Support

Before

contacting

IBM

Tivoli

Software

Support

with

a

problem,

refer

to

the

IBM

Tivoli

Software

Support

site

by

clicking

the

Tivoli

support

link

at

the

following

Web

site:

http://www.ibm.com/software/support/

If

you

need

additional

help,

contact

Software

Support

by

using

the

methods

described

in

the

IBM

Software

Support

Guide

at

the

following

Web

site:

http://techsupport.services.ibm.com/guides/handbook.html

The

guide

provides

the

following

information:

v

Registration

and

eligibility

requirements

for

receiving

support

v

Telephone

numbers,

depending

on

the

country

in

which

you

are

located

v

A

list

of

information

you

should

gather

before

contacting

Software

Support

©

Copyright

IBM

Corp.

2003,

2004

31

32

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

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.

Consult

your

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

IBM

product,

program,

or

service

may

be

used.

Any

functionally

equivalent

product,

program,

or

service

that

does

not

infringe

any

IBM

intellectual

property

right

may

be

used

instead.

However,

it

is

the

user’s

responsibility

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

grant

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

provisions

are

inconsistent

with

local

law:

INTERNATIONAL

BUSINESS

MACHINES

CORPORATION

PROVIDES

THIS

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

disclaimer

of

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

made

to

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

at

any

time

without

notice.

Any

references

in

this

information

to

non-IBM

Web

sites

are

provided

for

convenience

only

and

do

not

in

any

manner

serve

as

an

endorsement

of

those

Web

sites.

The

materials

at

those

Web

sites

are

not

part

of

the

materials

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

without

incurring

any

obligation

to

you.

Licensees

of

this

program

who

wish

to

have

information

about

it

for

the

purpose

of

enabling:

(i)

the

exchange

of

information

between

independently

created

programs

and

other

programs

(including

this

one)

and

(ii)

the

mutual

use

of

the

information

which

has

been

exchanged,

should

contact:

©

Copyright

IBM

Corp.

2003,

2004

33

IBM

Canada

Ltd.

Office

of

the

Lab

Director

8200

Warden

Avenue

Markham,

Ontario

L6G

1C7

Canada

Such

information

may

be

available,

subject

to

appropriate

terms

and

conditions,

including

in

some

cases,

payment

of

a

fee.

The

licensed

program

described

in

this

document

and

all

licensed

material

available

for

it

are

provided

by

IBM

under

terms

of

the

IBM

Customer

Agreement,

IBM

International

Program

License

Agreement

or

any

equivalent

agreement

between

us.

Trademarks

The

IBM

logo

and

the

following

terms

are

trademarks

or

registered

trademarks

of

International

Business

Machines

Corporation

in

the

United

States

or

other

countries

or

both:

DB2®

DB2

Universal

Database

IBM

WebSphere

Tivoli

UNIX®

is

a

registered

trademark

of

The

Open

Group

in

the

United

States,

other

countries,

or

both.

Pentium®

and

Intel®

are

trademarks

of

Intel

Corporation

in

the

United

States,

other

countries,

or

both.

Java™

and

all

Java-based

trademarks

are

trademarks

of

Sun

Microsystems,

Inc.

in

the

United

States,

other

countries,

or

both.

Microsoft®

and

Windows®

are

trademarks

of

Microsoft

Corporation

in

the

United

States,

other

countries,

or

both.

Linux

is

a

trademark

of

Linus

Torvalds

in

the

United

States,

other

countries,

or

both.

Other

company,

product

or

service

names

may

be

trademarks

or

service

marks

of

others.

34

Tivoli

Intelligent

ThinkDynamic

Orchestrator

Version

2.1.0

Release

Notes

����

Printed

in

USA

GI11-4698-00