tivoli provisioning manager migration guide - ibm...
TRANSCRIPT
Tivoli® Tivoli
Provisioning
Manager
Migration
Guide
for
Linux
Version
2.1
GC32-1620-00
���
Tivoli® Tivoli
Provisioning
Manager
Migration
Guide
for
Linux
Version
2.1
GC32-1620-00
���
Note:
Before
using
this
information
and
the
product
it
supports,
be
sure
to
read
the
general
information
under
“Notices”
on
page
61.
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
Preface
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
Tivoli
Provisioning
Manager
library
.
.
.
.
. v
Prerequisite
publications
.
.
.
.
.
.
.
.
. v
Accessing
publications
online
.
.
.
.
.
.
. vi
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
.
. vi
Tivoli
technical
training
.
.
.
.
.
.
.
.
.
. vi
Contacting
Software
Support
.
.
.
.
.
.
.
.
. vi
Conventions
used
in
this
book
.
.
.
.
.
.
.
. vii
Path
variables
used
in
this
book
.
.
.
.
.
.
. vii
Knowledge
requirements
.
.
.
.
.
.
.
.
. viii
Part
1.
Before
you
begin
migration
.
. 1
Chapter
1.
About
Tivoli
Provisioning
Manager
.
.
.
.
.
.
.
.
.
.
.
.
.
. 3
Chapter
2.
Planning
for
migration
.
.
.
. 5
Migration
paths
.
.
.
.
.
.
.
.
.
.
.
.
. 5
Required
software
levels
.
.
.
.
.
.
.
.
.
. 6
New
software
in
this
release
.
.
.
.
.
.
.
.
. 7
Supported
hardware
.
.
.
.
.
.
.
.
.
.
.
. 7
Assigning
user
roles
.
.
.
.
.
.
.
.
.
.
.
. 8
Other
migration
considerations
.
.
.
.
.
.
.
. 8
Chapter
3.
Preparing
for
migration
.
.
. 9
Updating
your
system
.
.
.
.
.
.
.
.
.
.
. 9
Identifying
the
version
of
your
existing
system
.
. 9
Updating
your
system
for
migration
.
.
.
.
. 9
Backing
up
your
system
.
.
.
.
.
.
.
.
.
. 9
General
guidelines
for
backup
and
migration
.
. 10
Backing
up
servers
.
.
.
.
.
.
.
.
.
.
. 10
Backing
up
the
Tivoli
Provisioning
Manager
installation
folder
.
.
.
.
.
.
.
.
.
.
. 11
Backing
up
the
data
center
model
.
.
.
.
.
. 11
Backing
up
workflows
.
.
.
.
.
.
.
.
.
. 11
Backing
up
log
files
.
.
.
.
.
.
.
.
.
. 12
Backing
up
configuration
files
.
.
.
.
.
.
. 13
Saving
reports
.
.
.
.
.
.
.
.
.
.
.
. 13
Setting
up
customized
workflows
for
migration
.
. 13
Naming
workflows,
parameters,
and
variables
.
. 14
Creating
an
automation
package
.
.
.
.
.
. 14
Next
steps
.
.
.
.
.
.
.
.
.
.
.
.
.
. 18
Part
2.
Installing
and
upgrading
software
.
.
.
.
.
.
.
.
.
.
.
.
. 19
Chapter
4.
System
prerequisites
.
.
.
. 21
Enabling
SNMP
for
Tivoli
NetView
.
.
.
.
.
. 21
Required
packages
.
.
.
.
.
.
.
.
.
.
.
. 21
Setting
the
DB2
Universal
Database
transaction
log
size
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 21
Chapter
5.
Upgrading
the
database
server
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 23
Upgrading
DB2
Universal
Database
.
.
.
.
.
. 23
Upgrading
the
DB2
Universal
Database
server
.
. 23
Upgrading
the
DB2
Universal
Database
client
.
. 24
Loading
the
CMDB
tablespace
.
.
.
.
.
.
. 25
Chapter
6.
Upgrading
the
directory
server
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 27
IBM
Tivoli
Directory
Server
.
.
.
.
.
.
.
.
. 27
Upgrading
on
Linux
.
.
.
.
.
.
.
.
.
. 27
Upgrading
the
IBM
Directory
Server
5.1
client
.
. 30
Microsoft
Active
Directory
.
.
.
.
.
.
.
.
. 30
Chapter
7.
Upgrading
WebSphere
Application
Server
.
.
.
.
.
.
.
.
.
. 31
Uninstalling
WebSphere
Application
Server
Application
Client
.
.
.
.
.
.
.
.
.
.
.
. 31
Uninstalling
WebSphere
Application
Server
5.0.1
.
. 31
Before
you
begin
.
.
.
.
.
.
.
.
.
.
. 31
Pre-installation
steps
.
.
.
.
.
.
.
.
.
.
. 33
Creating
WebSphere
MQ
file
systems
.
.
.
.
. 33
Setting
up
the
group
IDs
and
the
user
ID
.
.
. 34
Installing
WebSphere
Application
Server
5.1
.
.
. 34
Applying
WebSphere
Application
Server
fixes
.
.
. 36
Applying
the
WebSphere
Application
Server
5.1
Cumulative
Fix
3
.
.
.
.
.
.
.
.
.
.
. 36
Applying
the
WebSphere
MQ
V5.3
fix
.
.
.
. 36
Importing
the
security
certificate
for
Microsoft
Active
Directory
.
.
.
.
.
.
.
.
.
.
.
. 37
Chapter
8.
Migrating
Tivoli
Provisioning
Manager
.
.
.
.
.
.
.
.
.
.
.
.
.
. 39
Before
you
begin
.
.
.
.
.
.
.
.
.
.
.
. 39
Installing
Tivoli
Provisioning
Manager
2.1
.
.
.
. 39
Part
3.
Migrating
data
.
.
.
.
.
.
. 43
Chapter
9.
Migrating
data
.
.
.
.
.
.
. 45
Data
that
is
migrated
automatically
.
.
.
.
.
. 45
Data
that
cannot
be
migrated
.
.
.
.
.
.
.
. 45
Installing
core
automation
packages
.
.
.
.
.
. 45
Migrating
customized
workflow
components
.
.
. 46
Workflow
dependencies
.
.
.
.
.
.
.
.
. 46
Converting
modified
workflow
components
.
. 46
Installing
the
converted
workflow
components
47
Changing
the
locale
of
workflows
.
.
.
.
.
. 48
Chapter
10.
Verifying
migration
.
.
.
. 51
Starting
the
server
and
signing
on
to
the
Web
interface
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 51
User
accounts
.
.
.
.
.
.
.
.
.
.
.
.
. 51
Data
center
model
.
.
.
.
.
.
.
.
.
.
.
. 51
©
Copyright
IBM
Corp.
2003,
2004
iii
Applications
and
provisioning
.
.
.
.
.
.
.
. 51
Customized
workflows
.
.
.
.
.
.
.
.
.
. 51
Part
4.
Post-migration
configuration
53
Chapter
11.
Additional
configuration
tasks
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 55
Setting
up
SSL
encryption
.
.
.
.
.
.
.
.
. 55
Configuration
for
new
and
updated
features
.
.
. 55
Importing
new
data
center
objects
.
.
.
.
.
. 56
Part
5.
Appendixes
.
.
.
.
.
.
.
.
. 57
Appendix.
Administrative
Tasks
.
.
.
. 59
Starting
the
server
.
.
.
.
.
.
.
.
.
.
.
. 59
Stopping
Tivoli
Provisioning
Manager
.
.
.
.
. 59
Signing
on
to
the
Web
interface
.
.
.
.
.
.
.
. 60
Signing
off
from
the
Web
interface
.
.
.
.
.
.
. 60
Notices
.
.
.
.
.
.
.
.
.
.
.
.
.
. 61
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 62
iv
Tivoli
Provisioning
Manager
Migration
Guide
Preface
This
book
describes
the
steps
to
migrate
a
previous
version
of
Tivoli®
Provisioning
Manager
It
is
intended
for
system
administrators
or
for
anyone
else
responsible
for
performing
installation
and
configuration
tasks.
Publications
Read
the
descriptions
of
the
Tivoli
Provisioning
Manager
library,
the
prerequisite
publications,
and
the
related
publications
to
determine
which
publications
you
might
find
helpful.
After
you
determine
the
publications
you
need,
refer
to
the
instructions
for
accessing
publications
online.
Tivoli
Provisioning
Manager
library
The
publications
in
the
Tivoli
Provisioning
Manager
library
include:
v
Tivoli
Provisioning
Manager
Installation
Guide
v
Tivoli
Provisioning
Manager
Migration
Guide
v
Tivoli
Provisioning
Manager
Release
Notes
v
Tivoli
Provisioning
Manager
Problem
Determination
Guide
The
remaining
product
documentation
is
available
in
the
online
help,
which
can
be
launched
from
the
Web
interface
for
the
product.
To
enable
ease
of
printing
for
help
topics,
books
have
been
created
directly
from
the
online
help
contents.
The
topics
have
been
grouped
and
the
following
PDFs
have
been
created:
v
Workflow
Developer’s
Guide:
This
document
contains
the
online
help
topics
relating
to
creating
workflows
and
automation
packages.
v
Tivoli
Provisioning
Manager
Online
Help:
This
contains
the
entire
online
help.
Prerequisite
publications
To
use
the
information
in
this
book
effectively,
you
must
have
some
prerequisite
knowledge,
which
you
can
obtain
from
the
following
publications:
v
WebSphere®
Application
Server
Information
Center
,
available
from
http://www.ibm.com/websphere.
You
can
also
download
the
WebSphere
Application
Server
documentation
plug-in
and
install
it
in
the
Tivoli
Provisioning
Manager.
This
will
allow
you
to
view
the
WebSphere
Application
Server
documentation
in
the
same
Information
Center
as
the
Tivoli
Provisioning
Manager
help.
v
DB2
Universal
Database™
Information
Center,
available
from
www.ibm.com/db2.
v
Tivoli
Directory
Server
documentation,
available
from
the
Tivoli
Software
Information
Library.
The
instructions
in
this
book
provide
information
on
installing
and
configuring
the
bundled
(packaged)
software
to
work
with
Tivoli
Provisioning
Manager.
This
book
does
not
document
how
to
install
and
configure
third-party
software
supported
by
Tivoli
Provisioning
Manager,
such
as
Oracle9i
Database
and
Microsoft®
Active
©
Copyright
IBM
Corp.
2003,
2004
v
Directory.
The
exception
to
this
are
steps
that
require
specific
settings
or
configuration
to
configure
that
software
for
Tivoli
Provisioning
Manager.
Because
every
datacenter
and
environment
is
unique,
it
is
expected
that
users
following
the
instructions
in
this
book
have
the
necessary
prerequisite
knowledge
to
install,
configure
and
administer
this
software
in
their
unique
environment.
Accessing
publications
online
The
publications
for
this
product
are
available
online
in
Portable
Document
Format
(PDF)
in
the
Tivoli
software
library:
http://www.ibm.com/software/tivoli/library
To
locate
product
publications
in
the
library,
click
the
Product
manuals
link
on
the
left
side
of
the
library
page.
Then,
locate
and
click
the
name
of
the
product
on
the
Tivoli
software
information
center
page.
Product
publications
include
release
notes,
installation
guides,
user’s
guides,
administrator’s
guides,
and
developer’s
references.
Note:
To
ensure
proper
printing
of
publications,
select
the
Fit
to
page
check
box
in
the
Adobe
Acrobat
window
(which
is
available
when
you
click
File
→
Print).
Accessibility
Accessibility
features
help
a
user
who
has
a
physical
disability,
such
as
restricted
mobility
or
limited
vision,
to
use
software
products
successfully.
With
this
product,
you
can
use
assistive
technologies
to
hear
and
navigate
the
interface.
You
also
can
use
the
keyboard
instead
of
the
mouse
to
operate
all
features
of
the
graphical
user
interface.
Tivoli
technical
training
For
Tivoli
technical
training
information,
refer
to
the
IBM
Tivoli
Education
Web
site:
http://www.ibm.com/software/tivoli/education.
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
vi
Tivoli
Provisioning
Manager
Migration
Guide
Conventions
used
in
this
book
This
book
uses
the
following
highlighting
conventions:
Boldface
type
Indicates
commands
or
graphical
user
interface
(GUI)
controls
such
as
names
of
fields,
icons,
or
menu
choices.
Monospace
type
Indicates
examples
of
text
you
enter
exactly
as
shown,
file
names,
and
directory
paths
and
names.
Italic
type
Used
to
emphasize
words.
Italics
also
indicate
names
for
which
you
must
substitute
the
appropriate
values
for
your
system.
Important
These
sections
highlight
especially
important
information.
Attention
These
sections
highlight
information
intended
to
protect
your
data.
2000Oracle
Indicates
information
specific
to
Oracle9i
Database
or
using
Oracle9i
Database
with
Tivoli
Provisioning
Manager.
Path
variables
used
in
this
book
This
guide
uses
the
following
variables
to
represent
directory
paths:
DB2_installdir
This
is
the
installation
directory
for
DB2
Universal
Database.
The
default
installation
directory
is
/opt/IBM/db2/V8.1.
IDS_installdir
This
is
the
installation
directory
for
Tivoli
Directory
Server.
The
default
installation
directory
is
/opt/IBMLDAP.
WAS_installdir
This
is
the
installation
directory
for
WebSphere
Application
Server.
The
default
installation
directories
is
/opt/WebSphere/AppServer
This
is
the
installation
directory
for
Tivoli
Provisioning
Manager.
For
migrated
systems,
the
directory
is
/home/thinkcontrol
both
before
and
after
migration.
Tivoli_commondir
This
is
the
location
of
the
Tivoli
Common
Directory.
The
Tivoli
Common
Directory
is
a
central
location
on
systems
running
Tivoli
software
for
storing
serviceability-related
files,
including
log
files.
In
Tivoli
Provisioning
Manager,
the
default
value
is
/var/ibm/tivoli/common.
This
guide
uses
the
following
variables
to
represent
directory
paths:
DB2_installdir
This
is
the
installation
directory
for
DB2
Universal
Database.
The
default
installation
directory
is
/opt/IBM/db2/V8.1.
Preface
vii
IDS_installdir
This
is
the
installation
directory
for
Tivoli
Directory
Server.
The
default
installation
directory
is
/opt/IBMLDAP.
WAS_installdir
This
is
the
installation
directory
for
WebSphere
Application
Server.
The
default
installation
directories
is
/opt/WebSphere/AppServer
TPM_installdir
This
is
the
installation
directory
for
Tivoli
Provisioning
Manager.
The
default
installation
directory
for
Tivoli
Provisioning
Manager
is
/home/thinkcontrol.
Tivoli_commondir
This
is
the
location
of
the
Tivoli
Common
Directory.
The
Tivoli
Common
Directory
is
a
central
location
on
systems
running
Tivoli
software
for
storing
serviceability-related
files,
including
log
files.
In
Tivoli
Provisioning
Manager,
the
default
value
is
/var/ibm/tivoli/common.
Knowledge
requirements
This
book
should
be
read
by
system
administrators
or
anyone
else
responsible
for
installing
and
configuring
Tivoli
Provisioning
Manager.
People
who
are
installing
and
configuring
Tivoli
Provisioning
Manager
should
have
knowledge
in
the
following
areas:
v
Linux
v
Basic
operating
system
commands
v
DB2
Universal
Database
Enterprise
Server
Edition
or
Oracle9i
Database
operation,
configuration,
and
maintenance
v
WebSphere
Application
Server
v
IBM®
HTTP
Server
operation,
configuration
and
maintenance
v
Basic
SQL
commands
v
Java™
programming
v
XML
v
The
Internet
Refer
to
the
online
help
for
more
information
on
configuring
and
administering
Tivoli
Provisioning
Manager.
viii
Tivoli
Provisioning
Manager
Migration
Guide
Part
1.
Before
you
begin
migration
The
Tivoli
Provisioning
Manager
system
consists
of
many
software
products
and
subcomponents,
each
with
its
own
underlying
technology.
It
is
therefore
important
to
understand
the
overall
migration
process
and
plan
for
the
migration
of
your
own
system.
v
Chapter
1,
“About
Tivoli
Provisioning
Manager,”
on
page
3
v
Chapter
2,
“Planning
for
migration,”
on
page
5
v
Chapter
3,
“Preparing
for
migration,”
on
page
9
©
Copyright
IBM
Corp.
2003,
2004
1
2
Tivoli
Provisioning
Manager
Migration
Guide
Chapter
1.
About
Tivoli
Provisioning
Manager
This
guide
describes
how
to
migrate
Tivoli
Provisioning
Manager
Version
1.1
for
Linux
to
Version
2.1.
It
is
intended
for
system
administrators
or
for
anyone
else
responsible
for
performing
installation
and
configuration
tasks.
Use
this
guide
to
migrate
your
existing
Tivoli
Provisioning
Manager
system
as
follows:
1.
Prepare
for
migration
using
the
information
in
Part
1,
“Before
you
begin
migration,”
on
page
1.
This
part
of
the
guide
provides
planning
and
system
backup
information.
2.
Update
your
software.
Complete
the
tasks
described
in
Part
2,
“Installing
and
upgrading
software,”
on
page
19
to
upgrade
your
system.
This
includes
prerequisite
software
as
well
as
the
Tivoli
Provisioning
Manager
software.
3.
Migrate
your
data.
The
upgrade
process
automatically
migrates
some
of
your
system
data.
Complete
the
tasks
described
in
Part
3,
“Migrating
data,”
on
page
43
to
migrate
data
that
is
not
automatically
processed
during
software
upgrades.
This
part
of
the
guide
also
provides
guidance
in
verifying
your
migration.
4.
Review
Part
4,
“Post-migration
configuration,”
on
page
53
to
learn
about
additional
Tivoli
Provisioning
Manager
features
that
you
might
want
to
set
up.
©
Copyright
IBM
Corp.
2003,
2004
3
4
Tivoli
Provisioning
Manager
Migration
Guide
Chapter
2.
Planning
for
migration
The
process
to
migrate
your
system
to
Tivoli
Provisioning
Manager
involves
the
following
high-level
tasks:
1.
Planning
the
overall
migration
at
your
site
including
the
key
decisions
on
the
migration
approach
to
adopt.
2.
Taking
inventory
of
your
current
assets,
such
as
machines,
software,
databases,
custom
code,
and
so
on.
3.
Backing
up
your
existing
system.
This
includes:
v
Tivoli
Provisioning
Manager
server
v
LDAP
server
(if
it
is
installed
on
a
separate
server)
v
Database
server4.
Upgrading
prerequisite
software
to
the
levels
required
by
Tivoli
Provisioning
Manager.
5.
Upgrading
Tivoli
Provisioning
Manager
software.
6.
Manually
migrating
data
that
is
not
migrated
during
the
software
upgrade
process.
7.
Verifying
your
migrated
system.
8.
Configuring
new
or
updated
features.
This
includes
configuring
additional
data
center
assets,
setting
up
reporting
capability,
and
setting
up
integration
with
external
products.
This
migration
guide
provides
guidance
in
these
areas.
Migration
paths
The
following
migration
paths
are
supported:
v
Tivoli
Provisioning
Manager
1.1.2
to
Tivoli
Provisioning
Manager
2.1
The
following
migration
paths
are
not
supported:
v
Tivoli
Provisioning
Manager
1.1.0
or
1.1.1
to
Tivoli
Provisioning
Manager
2.1
v
Tivoli
Intelligent
ThinkDynamic
Orchestrator
1.1.0,
1.1.1,
or
1.1.2
to
Tivoli
Provisioning
Manager
2.1
If
your
current
system
is
at
the
version
1.1.0
or
1.1.1
level,
you
must
update
your
system
to
version
1.1.2
before
you
begin
migration.
For
information
about
identifying
and
updating
your
current
product
level,
see
“Updating
your
system”
on
page
9.
This
release
supports
local
in-place
migration
only.
In
this
approach,
you
replace
your
existing
Tivoli
Provisioning
Manager
system
with
Tivoli
Provisioning
Manager
2.1.
This
release
does
not
support
remote
migration
from
a
test
system
to
your
production
system
or
coexisting
versions
of
Tivoli
Provisioning
Manager.
©
Copyright
IBM
Corp.
2003,
2004
5
Attention
Since
an
in-place
migration
requires
you
to
shut
down
your
production
system,
consider
the
time
required
to
take
your
system
down
for
the
duration
of
the
migration.
Careful
planning
is
also
required
for
recovery
back
to
the
original
configuration
in
case
you
encounter
a
problem
with
the
migration.
Required
software
levels
The
following
tables
map
the
software
versions
and
levels
required
for
Tivoli
Provisioning
Manager.
For
a
more
detailed
description
of
supported
platforms,
topologies,
and
software
prerequisites,
refer
to
the
Tivoli
Provisioning
Manager
2.1
Installation
Guide.
Note:
The
migration
process
does
not
support
switching
from
one
platform
to
another
platform.
Table
1.
Required
database
Database
Tivoli
Provisioning
Manager
1.1.2
Tivoli
Provisioning
Manager
2.1.0
DB2
Universal
Database
Enterprise
Server
Edition
DB2
Universal
Database
Workgroup
Unlimited
Edition
8.1.2
(Version
8.1
Unlimited
Edition
with
fix
pack
2)
DB2
Universal
Database
Workgroup
Unlimited
Edition
8.1.3
(Version
8.1
Unlimited
Edition
with
fix
pack
3)
Oracle9i
Database
Only
supported
in
a
Solaris
environment
2000Solaris
Oracle9i
Database
Release
2
Enterprise
Edition
with
fix
pack
1
2000Solaris
Oracle9i
Database
Release
2
Enterprise
Edition
with
fix
pack
1
Database
servers
not
listed
in
this
table
are
not
supported
—
this
includes
versions
or
editions
of
DB2
Universal
Database
not
listed
in
this
table.
Table
2.
Directory
server
Directory
server
Tivoli
Provisioning
Manager
1.1.2
Tivoli
Provisioning
Manager
2.1.0
Tivoli
Directory
Server
5.1
5.2
Microsoft
Active
Directory
Windows
2000
Service
Pack
2
Windows
2000
Service
Pack
4
Table
3.
WebSphere
Web
Application
Server
Tivoli
Provisioning
Manager
1.x
Tivoli
Provisioning
Manager
2.1
WebSphere
Application
Server
5.0.1
5.1.0.3
(Version
5.1
with
Cumulative
Fix
3)
WebSphere
Application
Client
5.0.1
Not
required
6
Tivoli
Provisioning
Manager
Migration
Guide
New
software
in
this
release
This
release
includes
the
following
software
that
was
not
available
in
previous
releases
of
Tivoli
Provisioning
Manager:
v
WebSphere
Studio
Workbench
to
provide
access
to
the
Tivoli
Provisioning
Manager
information
center.
v
Tivoli
NetView
for
discovery
features
(optional)
v
Language
Pack
(optional)
Supported
hardware
This
section
lists
the
hardware
requirements
for
Tivoli
Provisioning
Manager
2.1.
Ensure
that
you
review
the
requirements
for
this
release
and
make
the
necessary
changes
before
you
begin
migration.
Note:
This
does
not
include
the
hardware
requirements
for
other
software
components
such
as
WebSphere
Application
Server,
DB2
Universal
Database,
and
Tivoli
Directory
Server
which
may
be
different.
Ensure
each
machine
in
your
Tivoli
Provisioning
Manager
configuration
meets
the
minimum
requirements
for
each
of
the
software
packages
you
plan
on
installing
on
that
machine.
For
complete
details
about
the
prerequisites
for
each
software
application,
refer
to
the
documentation
for
that
product,
as
described
in
“Prerequisite
publications”
on
page
v
IBM
Compatible
PC
with
Microsoft
Windows
2000
or
2003
Server:
v
2.8
GHz
Intel
Pentium
4
processor
or
equivalent
v
Minimum
4GB
of
free
memory
v
Minimum
20
GB
of
free
disk
space
v
CD-ROM
drive
2000AIX
IBM
pSeries
with
AIX
5.2:
v
1
GHz
CPU
v
Minimum
4GB
of
free
memory
v
Minimum
20
GB
of
free
disk
space
v
CD-ROM
drive
2000Solaris
Sun
SPARC
or
x86
Server
with
Solaris
8
and
9:
v
1
GHz
CPU
v
Minimum
4GB
RAM
v
Minimum
20
GB
free
disk
space
v
CD-ROM
drive
IBM
Compatible
PC
with
Red
Hat
Linux
Advanced
Server
2.1:
v
2.8
GHz
Intel
Pentium
4
processor
or
equivalent
v
Minimum
4GB
of
free
memory
v
Minimum
20
GB
of
free
disk
space
v
CD-ROM
drive
iSeries
Models
that
support
LPAR
with
minimum
450CPW
in
Linux
partition:
v
Minimum
4GB
RAM
Chapter
2.
Planning
for
migration
7
v
Minimum
20
GB
free
disk
space
v
CD-ROM
drive
Assigning
user
roles
In
Tivoli
Provisioning
Manager
1.1.2,
individual
access
rights
are
assigned
to
user
accounts.
In
release
2.1,
user
accounts
are
assigned
to
specific
user
roles
that
are
associated
with
specific
access
rights.
Administrator
Provides
access
to
all
features.
Assign
this
role
to
users
who
have
the
authority
to
manage
user
accounts
and
make
changes
to
any
part
of
the
system.
The
default
user
account
(tioappadmin)
is
assigned
the
Administrator
role.
Operating
Mode
Controller
Provides
the
ability
to
change
the
global
operating
mode
and
the
operating
mode
of
applications
and
clusters.
Assign
this
role
to
users
who
have
the
authority
to
control
the
degree
of
automation
in
the
creation
and
approval
of
deployment
requests.
DCM
Operator
Provides
the
ability
to
manage
data
center
assets
in
the
data
center
model
(DCM)
and
user
accounts.
Assign
this
role
to
data
center
administrators.
Cluster
and
Pool
Manager
Provides
the
ability
to
manage
clusters
and
spare
pools.
Assign
this
role
to
users
who
are
responsible
for
adding
and
removing
servers
from
clusters
and
resource
pools.
Fault
Manager
and
Runtime
Performance
Advisor
Provides
the
ability
to
manually
manage
deployment
requests
and
the
failed
status
indicator
for
data
center
assets.
Assign
this
role
to
users
who
are
responsible
for
monitoring
the
system
and
making
manual
deployment
changes.
Review
the
users
that
you
currently
have
defined,
and
determine
what
role
is
appropriate
for
each
user.
Other
migration
considerations
Some
factors
that
can
impact
your
migration
are:
v
In-place
migration
impact
v
The
level
of
customization
at
your
data
center
v
The
size
of
your
data
center
v
The
level
of
integration
with
third-party
systems
v
How
well
your
system
complies
with
recommended
practices
and
standards
8
Tivoli
Provisioning
Manager
Migration
Guide
Chapter
3.
Preparing
for
migration
This
chapter
describes
the
steps
you
need
to
perform
with
your
existing
system
before
you
can
upgrade
the
system
software.
v
“Updating
your
system”
v
“Backing
up
your
system”
v
“Setting
up
customized
workflows
for
migration”
on
page
13
Updating
your
system
If
your
current
system
is
at
the
version
1.1.0
or
1.1.1
level,
you
must
update
your
system
to
version
1.1.2
before
you
begin
migration.
Identifying
the
version
of
your
existing
system
Tivoli
Provisioning
Manager
1.1.2
is
required
for
migration,
and
some
product
features
and
procedures
described
in
this
guide
are
also
specific
to
a
particular
product
level.
If
you
do
not
know
the
current
product
level
of
your
existing
system,
you
can
verify
it
on
the
Welcome
page
in
the
Tivoli
Provisioning
Manager
Web
interface.
If
you
are
currently
logged
onto
the
Web
interface,
click
Home
to
view
the
Welcome
page.
Note:
On
the
Welcome
page,
Version
1.1
represents
product
level
1.1.1
(Version
1.1
with
Fix
Pack
1).
Version
1.2
represents
product
level
1.1.2
(Version
1.1
with
Fix
Pack
2).
Updating
your
system
for
migration
To
update
your
system,
apply
Tivoli
Provisioning
Manager
Fix
Pack
2.
You
can
obtain
the
fix
pack
from
the
Tivoli
Software
Support
site.
On
the
IBM
Software
Support
page
at
http://www.ibm.com/software/support/,
search
for
reference
number
4006668.
Refer
to
the
Fix
Pack
2
Readme
for
details
about
applying
the
fix
pack.
After
you
have
applied
the
fix
pack,
verify
that
your
updated
Tivoli
Provisioning
Manager
system
is
working.
1.
Start
the
Tivoli
Provisioning
Manager
server.
2.
Verify
that
you
can
log
on
to
the
Web
interface
successfully.
For
details
about
how
to
start
the
server
and
access
the
Web
interface,
see
“Administrative
Tasks,”
on
page
59.
Backing
up
your
system
Currently
Tivoli
Provisioning
Manager
only
supports
in-place
migration,
which
requires
you
to
completely
replace
your
existing
system.
It
is
therefore
important
to
back
up
your
existing
system
before
you
begin
the
migration
process.
This
ensures
that
you
can
recover
the
system
if
a
migration
problem
occurs,
and
that
your
configuration
and
system
data
are
stored
for
any
required
manual
data
migration
processes.
©
Copyright
IBM
Corp.
2003,
2004
9
Tivoli
Provisioning
Manager
does
not
include
tools
for
backing
up
or
restoring
your
system.
You
must
follow
the
standard
procedures
for
backup
and
recovery
that
are
used
by
your
company.
Ensure
that
your
system
backup
includes
the
following
software
and
data:
v
A
full
backup
of
the
main
Tivoli
Provisioning
Manager
server.
Backing
up
the
entire
server
ensures
that
you
have
a
working
copy
of
all
the
software
components
installed
on
Tivoli
Provisioning
Manager
directory
server.
v
A
full
backup
of
other
system
servers
with
supporting
software,
including
the
database
server
and
directory
server.
v
A
backup
of
data
that
you
want
to
archive
or
migrate
after
your
system
is
upgraded.
This
includes
reports,
automation
packages,
workflows,
commands,
and
log
files.
General
guidelines
for
backup
and
migration
Ensure
that
you
follow
the
guidelines
in
this
section
as
you
perform
backup
and
migration
tasks.
v
Review
the
backup
procedures
in
this
chapter
before
you
begin
the
backup
process.
v
For
some
procedures,
you
must
extract
or
obtain
information
from
your
existing
system,
and
then
save
the
data
that
you
extract
or
collect.
Most
of
the
data
required
for
these
procedures
is
available
from
the
Web
interface.
v
For
most
backup
procedures,
you
must
stop
the
Tivoli
Provisioning
Manager
server.
You
should
also
ensure
that
workflows
are
not
running
before
you
perform
system
backup
or
migration
tasks.
For
instructions
on
starting
and
stopping
the
server
and
accessing
the
Web
interface,
see
“Administrative
Tasks,”
on
page
59.
To
search
for
workflows
that
are
currently
running,
perform
the
following
steps:
1.
Log
on
to
the
Web
interface.
2.
If
you
have
applications
running
in
automatic
mode,
put
the
applications
in
maintenance
to
prevent
further
deployments.
3.
Click
System
configuration
and
workflow
management—>Workflow
Executions.
4.
On
the
Workflow
Executions
page,
search
for
workflows
with
a
status
of
In
progress.
Any
workflows
that
appear
are
currently
running.
You
should
wait
until
the
workflows
have
completed
before
starting
system
backups
and
migration
tasks.
Backing
up
servers
Back
up
your
current
Tivoli
Provisioning
Manager
system
so
that
you
can
recover
it
if
necessary.
Perform
your
system
backup
in
accordance
with
the
documentation
that
is
provided
with
your
operating
system
or
with
any
specialized
backup
and
restore
software
that
you
use.
Typically,
you
can
back
up
your
system
to
a
tape
drive,
a
ZIP
drive,
or
some
other
file
system.
Back
up
the
following
servers:
v
The
Tivoli
Provisioning
Manager
server.
v
The
database
server,
if
it
is
on
a
separate
machine.
v
The
directory
server,
if
it
is
on
separate
machine.
10
Tivoli
Provisioning
Manager
Migration
Guide
Backing
up
the
Tivoli
Provisioning
Manager
installation
folder
Back
up
the
Tivoli
Provisioning
Manager
installation
directory
separately
from
your
full
system
backup.
This
enables
you
to
compare
files
in
your
current
system
with
files
in
your
upgraded
system
after
migration,
and
can
help
you
to
diagnose
any
migration
issues.
In
release
1.1.2,
Tivoli
Provisioning
Manager
is
installed
in
the
/home/thinkcontrol
subdirectory
for
the
tioadmin
user.
Backing
up
the
data
center
model
Tivoli
Provisioning
Manager
1.1.x
releases
do
not
support
exporting
of
the
data
center
model.
Since
the
Tivoli
Provisioning
Manager
2.1
installation
program
automatically
migrates
the
data
center
model,
you
do
not
need
to
have
a
copy
of
your
existing
data
center
model
for
migration
purposes.
However,
if
you
want
to
store
a
backup
copy
of
your
existing
data
center
model,
consider
one
of
the
following
options:
v
If
you
used
an
XML
file
to
create
your
data
center
model,
you
can
create
a
backup
copy
of
this
file.
You
can
update
this
file
to
reflect
your
current
data
center
configuration
before
you
store
the
file.
v
If
you
do
not
have
an
XML
file
that
defines
your
data
center
model,
generate
reports
of
your
customers,
applications,
and
data
center
inventory
in
Tivoli
Provisioning
Manager,
and
then
save
or
the
reports.
You
can
then
use
the
information
in
the
reports
to
rebuild
your
data
center
model,
if
necessary.
Reports
are
available
from
the
Reports
navigation
tree
in
the
Web
interface.
Backing
up
workflows
Any
workflows
that
you
have
created
or
modified
must
be
exported
and
saved
for
migration.
Tivoli
Provisioning
Manager
2.1
includes
a
tool
to
back
up
these
files.
The
backup
tool:
v
Extracts
and
saves
all
workflow
components
in
your
existing
system
to
a
backup
folder.
v
Generates
log
files
of
conversion
activity
and
reports
of
all
workflow
changes.
Keep
a
copy
of
the
backed
up
files.
During
the
software
upgrade
process,
the
Tivoli
Provisioning
Manager
installation
program
replaces
all
existing
workflows
with
updated
workflows.
If
you
do
not
back
up
and
migrate
workflow
components
that
you
created
or
modified,
they
will
be
inaccessible
after
the
software
is
upgraded.
If
you
made
changes
to
workflow
components,
you
must
manually
migrate
the
changed
components.
After
the
backup
is
complete,
you
must
create
automation
packages
that
contains
the
customized
components
so
that
you
can
convert
them
to
the
proper
format
for
Tivoli
Provisioning
Manager
2.1
and
install
them
on
your
migrated
system.
Notes:
1.
The
workflow
backup
tool
is
specific
to
release
1.1.x
systems.
You
cannot
use
this
tool
to
back
up
workflows
after
migration.
2.
The
backup
process
can
take
some
time,
depending
on
the
number
of
workflows
in
your
system
and
the
amount
of
customization
that
you
have
performed.
Chapter
3.
Preparing
for
migration
11
Before
you
back
up
workflow
components
Before
you
run
the
workflow
backup
tool,
verify
the
following:
v
If
you
plan
to
migrate
your
customized
workflows,
ensure
that
the
workflows
have
unique
names.
If
you
modified
core
workflows
provided
with
Tivoli
Provisioning
Manager
1.1.x
but
did
not
change
the
workflow
names,
name
conflicts
with
Tivoli
Provisioning
Manager
2.1
workflows
will
prevent
you
from
installing
your
customized
workflows
during
the
workflow
migration
process.
You
should
also
ensure
that
all
names
are
valid.
For
information
about
requirements
for
workflow,
parameter,
and
variable
names,
see
“Naming
workflows,
parameters,
and
variables”
on
page
14.
If
you
need
to
rename
workflows,
perform
the
following
steps:
1.
To
identify
workflows
that
have
been
modified,
run
the
backup
tool
as
described
in
“Backing
up
workflow
components.”
2.
Review
the
log
files
that
the
tool
creates
to
identify
modified
workflows.
3.
In
Tivoli
Provisioning
Manager,
rename
modified
workflows
that
still
have
their
original
names.
4.
Remove
the
backup
files,
and
then
run
the
workflow
backup
tool
again
to
save
your
renamed
workflows
and
other
workflow
components.v
The
JAVA_HOME
environment
variable
is
set
to
the
directory
where
IBM
Java
JDK
1.4.1
is
installed.
Backing
up
workflow
components
To
back
up
workflow
components:
1.
Log
on
to
the
Tivoli
Provisioning
Manager
server
as
tioadmin.
2.
On
Tivoli
Provisioning
Manager,
Version
2.1
CD,
copy
the
/tools/wfbackup
folder
to
the
TIO_installdir/tools
directory.
The
backup
script
is
called
wfbackup.sh.
3.
Run
the
following
command
./wfbackup.sh
The
script
backs
up
workflows
that
have
been
added
or
changed,
and
displays
a
list
of
workflows
that
have
been
modified,
added,
or
removed.
You
should
save
the
full
set
of
backed
up
files
and
reports
with
the
other
system
data
that
you
are
backing
up.
By
default,
backup
files
and
report
files
are
stored
in
the
following
directories:
v
Back
up
files
are
stored
in
the
./backup
directory.
v
Report
files
that
describe
changes
to
workflow
components
are
stored
in
the
./reports
directory.
The
.diff
files
show
the
details
of
your
workflow
changes.
The
following
log
files
list
the
backup
activity:
Table
4.
Workflow
backup
log
files
File
name
Contents
workflow.log
Changes
to
workflows
command.log
Changes
to
commands
requesttype.log
Changes
to
request
types
Backing
up
log
files
Back
up
your
log
files
so
that
you
have
a
record
of
past
system
activity
and
errors.
This
includes
log
files
created
for
Tivoli
Provisioning
Manager
and
WebSphere
Application
Server.
12
Tivoli
Provisioning
Manager
Migration
Guide
v
Log
files
for
Tivoli
Provisioning
Manager
1.1.x
are
stored
in
the
TIO_installdir/logs
directory.
v
Log
files
for
WebSphere
Application
Server
are
stored
in
the
WAS_installdir/logs/server1
directory.
Note:
After
you
migrate
your
system,
log
files
for
Tivoli
Provisioning
Manager
2.1
will
be
stored
in
the
Tivoli_commondir/COP/logs
directory.
Your
old
log
files
will
not
be
removed.
Backing
up
configuration
files
If
your
current
system
is
currently
integrated
with
external
software
systems,
such
as
Tivoli
Configuration
Manager,
consider
backing
up
configuration
files
on
the
Tivoli
Provisioning
Manager
server.
For
additional
information
about
relevant
configuration
files,
refer
to
the
documentation
for
the
automation
package
that
you
used
to
integrate
the
external
product.
Saving
reports
Tivoli
Provisioning
Manager
2.1
uses
new
reporting
tools
to
collect
report
data
and
generate
reports.
In
this
release,
Tivoli
Data
Warehouse
collects
and
stores
data
for
reports,
and
Crystal
Reports
generates
reports.
The
types
of
available
reports
have
also
changed.
In
previous
releases,
reports
were
based
on
the
current
configuration
of
your
system.
In
Tivoli
Provisioning
Manager,
reports
are
historical.
You
can
generate
reports
based
on
a
specified
period
in
the
past.
If
there
are
specific
reports
for
your
existing
system
that
you
want
to
keep,
you
must
generate
the
reports,
and
then
or
save
them.
To
generate
a
report,
log
on
to
the
Web
interface,
and
then
click
the
report
that
you
want
to
view
in
the
Reports
navigation
tree.
Setting
up
customized
workflows
for
migration
If
you
made
changes
to
workflows
in
your
existing
system,
you
need
to
prepare
your
customized
workflow
files
for
migration.
Perform
the
following
steps:
1.
Review
the
.diff
files
that
were
created
by
the
workflow
backup
tool
to
identify
changes
to
workflows.
You
can
then
determine
which
workflow
components
you
want
to
migrate.
The
workflow
backup
tool
is
described
in
“Backing
up
workflows”
on
page
11.
2.
Create
directory
for
each
automation
package
(.tcdriver
file)
that
you
want
to
migrate
in
a
temporary
location.
The
files
for
each
automation
package
will
be
placed
in
a
contents
subdirectory.
Examples:
TIO_installdir/custom_workflows/old/my_router/contents
TIO_installdir/custom_workflows/old/my_switch/contents
Note:
The
contents
subdirectory
is
new
in
Tivoli
Provisioning
Manager
2.1.
3.
Create
target
directories
where
you
want
to
store
your
converted
workflow
components.
Examples:
TIO_installdir/custom_workflows/new/my_router
TIO_installdir/custom_workflows/new/my_switch
Chapter
3.
Preparing
for
migration
13
Note:
Ensure
that
both
your
source
and
target
directories
have
full
file
access
permissions
so
that
the
all
workflows
can
be
accessed
by
the
conversion
tool
during
the
workflow
conversion
process.
4.
Organize
your
automation
packages.
v
If
you
already
have
.tcdriver
files
for
the
workflow
components
you
want
to
convert,
extract
the
file
structure
for
each
automation
package
to
its
own
directory.
For
example,
if
you
have
an
automation
package
called
my_router.tcdriver,
extract
the
files
to
the
TIO_installdir/custom_workflows/old/my_router/contents
directory.
After
extracting
the
files,
the
file
structure
includes
the
following
directories:
TIO_installdir/custom_workflows/old/my_router/contents
TIO_installdir/custom_workflows/old/my_router/contents/workflow
TIO_installdir/custom_workflows/old/my_router/contents/doc
TIO_installdir/custom_workflows/old/my_router/contents/bin
TIO_installdir/custom_workflows/old/my_router/contents/lib
TIO_installdir/custom_workflows/old/my_router/contents/TC-INF
v
If
you
did
not
create
automation
packages
with
your
customized
workflows,
create
the
file
structure
required
for
each
automation
package
using
the
files
in
the
./backup
directory.
For
information
about
the
required
file
structure
for
an
automation
package,
see
“Creating
an
automation
package.”
Copy
each
automation
package
file
structure
to
the
appropriate
directory
created
in
step
2.
Naming
workflows,
parameters,
and
variables
To
ensure
that
your
workflows
can
be
installed
properly,
ensure
that
you
use
valid
names
for
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.
Creating
an
automation
package
Automation
packages
are
device
drivers
that
support
one
particular
type
of
software
or
physical
device.
It
contains
all
of
the
workflows,
database
table
entries,
JAR
files,
and
external
scripts
that
are
necessary
to
operate
that
physical
device,
for
example
a
Cisco™
CSS11000
switch.
For
the
purposes
of
migration,
you
must
create
an
automation
package
that
contains
all
the
workflow
components
that
you
added
or
modified
and
want
to
migrate.
14
Tivoli
Provisioning
Manager
Migration
Guide
Existing
automation
packages
are
located
in
the
TIO_installdir/drivers
directory
on
the
Tivoli
Provisioning
Manager
server.
When
you
use
the
workflow
backup
tool,
the
files
are
stored
in
a
backup
directory
as
described
in
“Backing
up
workflow
components”
on
page
12.
Contents
of
automation
packages
Automation
packages
have
a
specific
internal
structure.
The
workflow
components
must
be
organized
in
this
structure
when
you
want
to
create
a
new
automation
package.
v
When
you
use
the
convertTCDriver
tool
to
convert
your
workflows,
all
individual
files
must
be
available
in
the
required
file
structure.
v
When
you
need
to
install
an
automation
package,
the
file
structure
must
be
zipped
into
a
single
file
with
a
.tcdriver
file
extension.
The
structure
of
an
automation
package
includes
the
following
directories:
command
This
directory
contains
all
of
the
commands
that
are
available
for
that
specific
physical
device.
doc
This
directory
contains
the
documentation
for
implementation
of
the
automation
package
in
a
readme.txt
file.
java-plugin
This
directory
contains
all
of
the
Java
plug-ins
that
are
installed
and
used
on
that
specific
physical
device.
TC-INF
This
directory
contains
the
manifest
file
for
the
automation
package.
For
details
on
the
content
of
the
manifest
file,
refer
to
“Manifest
file
contents.”
workflow
This
directory
contains
a
collection
of
workflows
that
have
been
developed
to
operate
that
specific
physical
device.
lib
This
directory
contains
any
Java
JAR
files
that
need
to
be
copied
to
the
TIO_installdir/drivers/lib
directory
and
made
available
to
the
deployment
engine
class
path.
bin
This
directory
contains
any
script
files
to
be
copied
to
a
repository,
for
example
TIO_installdir/bin
files,
which
are
then
used
by
workflows.
Manifest
file
contents
The
manifest
file
for
automation
packages
are
an
.xml
file,
tc-driver.xml,
that
contains
the
name
and
the
version
number
of
the
automation
packages,
the
version
number
of
the
automation
package
template,
and
describes
all
of
the
automation
package
dependencies
on
other
automation
packages.
The
manifest
file
includes
the
following
main
sections:
<dependencies>
This
section
lists
all
of
the
other
drivers
that
the
current
automation
package
depends
on.
<actions>
This
section
lists
all
of
the
separate
classes
that
are
necessary
to
install
separate
items
like
Java
drivers,
commands,
and
so
on.
<items>
This
section
lists
all
the
items
to
be
installed
on
the
automation
package.
Each
item
identifies
a
certain
operation
that
will
be
performed
on
that
automation
package.
Chapter
3.
Preparing
for
migration
15
<device-models>
This
section
lists
all
the
items
to
be
installed
on
the
automation
package.
Each
item
identifies
a
certain
operation
that
will
be
performed
on
that
automation
package.
<post-install-workflows>
This
optional
section
names
a
workflow
along
with
its
parameters
to
be
executed
after
all
the
items
are
installed.
This
workflow
may
be
one
installed
by
the
current
Automation
Package,
or
one
previously
installed.
<property>
This
optional
section
defines
a
macro
substitution
that
can
be
used
for
any
subsequent
quoted
strings
in
the
manifest
file,
using
an
″Ant
like″
syntax.
For
example,
if
we
have
the
following
entry:
<property
name="tc.pkg"
location="com.thinkdynamics.kanaha.tcdrivermanager
.action"
/>
then,
wherever
${tc.pkg}
occurs
in
an
attribute
string
inside
tc-driver.xml,
a
substitution
is
made.
<software=products>
This
section
defines
any
software
product
entries
to
be
installed
in
the
Data
Center
Model
database.
The
syntax
is
identical
to
the
<software>
element
in
the
XML
format
used
by
the
xmlimport
utility,
but
has
been
extended
to
allow
using
the
${xxx}
properties
substitutions
within
attribute
values.
<driver-name>
Name
of
the
driver
<driver-version>
Optional
version
number
<description>
Short,
one
sentence
description
of
the
purpose
of
this
Automation
Package.
<documentation>
Specifies
the
name
of
a
text
file
in
the
Automation
Package
contents
that
provides
an
in-depth
description
and
any
special
instructions.
Here
is
an
example
of
the
syntax:
<documentation
location="doc/readme.txt"/>
The
following
is
an
example
of
an
XML
manifest
file
for
the
AIX-Operating-System:
Note:
Some
lines
may
be
split
in
two,
with
the
second
line
indented,
for
presentation
purposes
only.
All
lines,
in
particular
those
beginning
with
<item
name=
should
be
written
on
a
single
line
with
no
line
breaks.<?xml
version="1.0"
encoding="UTF-8"?>
<!--
/*****************************************************************
*
Licensed
Materials
-
Property
of
IBM
*
5724-F75
*
(C)
Copyright
IBM
Corp.
2003
*
All
Rights
Reserved
*
US
Government
Users
Restricted
Rights
-Use,
duplication
or
*
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corp.
*
****************************************************************
*/
-->
<tc-driver>
<tc-driver-format>1.0</tc-driver-format>
<driver-name>AIX-Operating-System</driver-name>
<version>1.0</version>
16
Tivoli
Provisioning
Manager
Migration
Guide
<description>This
Automation
Package
contains
workflows
for
controlling
AIX
servers</description>
<documentation
location="doc/AIX-Operating-System.txt"
/>
<dependencies>
<dependency
name="core"/>
</dependencies>
<property
name="tc.pkg"
location="com.thinkdynamics.kanaha.
tcdrivermanager.action"/>
<actions>
<action
name="command"
class="${tc.pkg}.SimpleCommandActions"/>
<action
name="copy-file"
class="${tc.pkg}.CopyFileActions"/>
<action
name="workflow"
class="${tc.pkg}.WorkflowActions"/>
<action
name="java-plugin"
class="${tc.pkg}.JavaPluginActions"/>
</actions>
<items>
<item
name="repository/configIP.sh"
action="copy-file">
<param
name="dest.path"
value="${tc.home}/repository/
AIX-Operating-System/configIP.sh"/>
<param
name="chmod"
value="755"
/>
</item>
<item
name="repository/configRoute.sh"
action="copy-file">
<param
name="dest.path"
value="${tc.home}/repository/
AIX-Operating-System/configRoute.sh"/>
<param
name="chmod"
value="755"
/>
</item>
<item
name="doc/AIX-Operating-System.txt"
action="copy-file">
<param
name="dest.path"
value="${tc.home}/drivers/
AIX-Operating-System.txt"/>
</item>
<!--
<item
name="lib/AIX-Operating-System.jar"
action="copy-file">
<param
name="dest.path"
value="${tc.javaplugin.dir}/
AIX-Operating-System.jar"/>
</item>
-->
<item
name="java-plugin/com.ibm.thinkdynamics.javaplugin.software.AIX.
GetRoutingTableInfo.xml"
action="java-plugin"/>
<item
name="workflow/AIX
Software
Reboot
Async.xml"
action="workflow"/>
<item
name="workflow/AIX
Software
Reboot
Sync.xml"
action="workflow"/>
<item
name="workflow/AIX
Copy
File
from
Local.xml"
action="workflow"/>
<item
name="workflow/AIX
Remote
Remove
File.xml"
action="workflow"/>
<item
name="workflow/AIX
chdev
an
Interface.xml"
action="workflow"/>
<item
name="workflow/AIX
Add
IP
Address.xml"
action="workflow"/>
<item
name="workflow/AIX
Remove
IP
Address.xml"
action="workflow"/>
<item
name="workflow/AIX
Check
OS
Install.xml"
action="workflow"/>
<item
name="workflow/AIX
Apply
Routing
Table.xml"
action="workflow"/>
</items>
<device-models>
<device-model
name="AIX
Operating
System"
category="Software
Products">
<workflow
name="AIX
Software
Reboot
Async"/>
<workflow
name="AIX
Software
Reboot
Sync"/>
<workflow
name="AIX
Add
IP
Address"/>
<workflow
name="AIX
Remove
IP
Address"/>
<workflow
name="AIX
Check
OS
Install"/>
<workflow
name="AIX
Apply
Routing
Table"/>
</device-model>
</device-models>
<!--
Chapter
3.
Preparing
for
migration
17
<software-products>
<software
name="AIX"
is-device-model="AIX
Operating
System"
version="5.0"
package_path="_"
install_path="_"
type="OPERATING_SYSTEM">
</software>
</software-products>
-->
</tc-driver>
Next
steps
To
complete
migration
of
workflow
components,
several
additional
steps
are
required:
1.
When
you
have
completed
the
backup
tasks
described
in
this
chapter,
upgrade
your
software
as
described
in
Part
2,
“Installing
and
upgrading
software,”
on
page
19.
2.
Install
the
core
automation
packages
provided
with
Tivoli
Provisioning
Manager
by
following
the
steps
in
“Installing
core
automation
packages”
on
page
45.
3.
Migrate
your
customized
workflows
by
following
the
steps
in
“Migrating
customized
workflow
components”
on
page
46:
18
Tivoli
Provisioning
Manager
Migration
Guide
Part
2.
Installing
and
upgrading
software
This
part
describes
how
to:
v
Upgrade
your
prerequisite
software
to
the
levels
required
by
Tivoli
Provisioning
Manager.
v
Upgrade
Tivoli
Provisioning
Manager
software.
Prior
to
upgrading
your
software,
ensure
that
you
back
up
your
system
as
described
in
Chapter
3,
“Preparing
for
migration,”
on
page
9.
If
you
need
to
stop
any
of
your
software
components,
see
the
appropriate
installation
guide
for
your
product
and
platform.
v
Chapter
4,
“System
prerequisites,”
on
page
21
v
Chapter
5,
“Upgrading
the
database
server,”
on
page
23
v
Chapter
6,
“Upgrading
the
directory
server,”
on
page
27
v
Chapter
7,
“Upgrading
WebSphere
Application
Server,”
on
page
31
v
Chapter
8,
“Migrating
Tivoli
Provisioning
Manager,”
on
page
39
©
Copyright
IBM
Corp.
2003,
2004
19
20
Tivoli
Provisioning
Manager
Migration
Guide
Chapter
4.
System
prerequisites
This
chapter
describes
configuration
steps
you
must
perform
before
you
begin
upgrading
software.
Enabling
SNMP
for
Tivoli
NetView
If
you
want
to
use
Tivoli
NetView
for
discovery
capabilities
in
Tivoli
Provisioning
Manager,
you
SNMP
must
be
installed
and
enabled
on
the
Tivoli
Provisioning
Manager.
For
information
about
configuring
SNMP,
refer
to
your
operating
system
documentation.
Required
packages
In
addition
to
the
packages
that
are
currently
installed
on
your
Tivoli
Provisioning
Manager
1.1.2
system,
you
must
install
the
following
packages
for
Tivoli
Provisioning
Manager
2.1:
v
rpm-build:
This
is
required
by
the
WebSphere
Application
Server.
and
is
provided
on
the
RedHat
AS
2.1
CDs.
v
rpm-build-4.0.4-7x.20.i386.rpm
:
This
is
required
by
WebSphere
Application
Server
installation
for
the
prerequisite
software
installer
and
is
provided
on
the
RedHat
AS
2.1
CDs.
Setting
the
DB2
Universal
Database
transaction
log
size
Some
installation
and
migration
tasks
require
a
larger
DB2
Universal
Database
transaction
log
size
due
to
higher
transaction
volumes
and
commands
than
run
for
a
longer
time.
This
includes
tasks
such
as
installation
of
automation
packages.
The
required
minimum
settings
for
migration
are
a
log
size
of
8000,
and
six
primary
logs.
The
default
log
file
size
is
1000..
To
change
the
database
log
file
settings,
run
the
following
command:
db2
update
database
configuration
for
db_name
using
LOGFILSIZ
8000
LOGPRIMARY
6
where
v
db_name
is
the
name
of
your
database.
v
LOGFILSIZ
is
the
log
file
size
used
by
the
primary
and
secondary
logs.
v
LOGPRIMARY
is
the
number
of
primary
log
files.
©
Copyright
IBM
Corp.
2003,
2004
21
22
Tivoli
Provisioning
Manager
Migration
Guide
Chapter
5.
Upgrading
the
database
server
You
must
ensure
that
your
database
server
and
client
are
at
the
product
level
supported
by
Tivoli
Provisioning
Manager
2.1.
v
If
you
are
currently
using
DB2
Universal
Database,
Workgroup
Unlimited
Edition
8.1.2
as
your
database,
you
must
update
it
to
version
8.1.3
with
fix
pack
3.
If
the
database
is
installed
on
a
separate
server,
you
should
also
update
the
client
on
the
Tivoli
Provisioning
Manager
server.
You
can
identify
your
current
DB2
Universal
Database
product
level
by
running
the
db2level
command.
Note:
Migration
from
one
type
of
database
to
another
is
not
supported.
If
you
want
to
switch
the
type
of
the
database
that
you
are
using,
you
must
successfully
complete
the
installation
and
configuration
steps
described
in
your
Tivoli
Provisioning
Manager
1.1
documentation.
Upgrading
DB2
Universal
Database
You
must
upgrade
your
DB2
Universal
Database
server
and
client
software.
Upgrading
the
DB2
Universal
Database
server
To
update
your
database
software:
1.
Ensure
that
the
DB2
Universal
Database
client
is
not
running.
2.
Log
on
as
root.
3.
Ensure
that
DB2
processes
are
stopped.
a.
Log
on
as
root.
b.
Run
the
following
commands
for
each
instance:
su
-
iname
.
$HOME/sqllib/db2profile
db2
force
applications
all
db2
terminate
db2stop
db2licd
-end
#
run
at
each
physical
node
exit
where
iname
is
the
instance
owner
name.
If
you
are
a
High
Availability
Cluster
Multi-Processing
(hacmp)
user,
you
must
use
the
ha_db2stop
command
instead
of
the
db2stop
command.
Otherwise
the
db2stop
command
will
trigger
a
failure
event.
c.
Stop
all
instances
that
are
using
DB2
Version
8,
including
the
Fault
Monitor
if
it
exists
and
is
using
DB2
Version
8.
Post-installation
steps
Applying
the
DB2
Fix
Pack:
You
must
apply
the
DB2
Version
8.1
Fix
Pack
3
after
installing
DB2
Universal
Database.
To
install
the
fix
pack:
1.
Insert
the
DB2
Universal
Database,
Workgroup
Server
Unlimited
Edition,
Version
8.1
Fix
Pack
3
CD
for
your
platform
into
the
CD
drive.
Mount
the
CD
©
Copyright
IBM
Corp.
2003,
2004
23
drive,
but
do
not
change
directory
to
the
mount
point.
Changing
directories
to
the
mount
point
will
lock
the
CD
drive
and
prevent
you
from
being
able
to
swap
CDs.
2.
Perform
the
following
steps:
a.
Copy
the
compressed
tar
file
from
the
CD
into
a
temporary
directory
on
your
system.
This
directory
must
have
2
GB
of
free
space.
b.
Uncompress
the
fix
pack
file.
c.
Change
to
the
directory
where
you
uncompressed
the
file,
and
run
the
command
./installFixPak
3.
Follow
the
instructions
in
the
fix
pack
installer.
4.
Reboot
the
machine.
Updating
database
instances:
Perform
the
following
post-installation
steps
to
complete
the
DB2
update:
1.
Log
on
as
root.
2.
Run
the
following
command
to
obtain
a
list
of
all
instances:
DB2_installdir/instance/db2ilist
3.
Update
each
instance
identified
in
step
2
to
use
the
new
level
of
DB2
Run
the
command:
DB2_installdir/instance/db2iupdt
iname
where
iname
is
the
instance
name.
For
more
information
on
the
db2iupdt
command,
run
the
command
with
the
-h
option
4.
For
each
instance,
log
in
as
the
instance
owner
and
run
the
db2start
command.
5.
For
each
database
in
the
instance,
bind
your
DB2
utilities
against
your
database.
This
step
is
necessary
for
the
fixes
to
take
effect,
and
only
needs
to
be
performed
once
per
database.
Run
the
following
commands:
db2
terminate
db2
CONNECT
TO
dbname
db2
"BIND
DB2_installdir/bnd/@db2ubind.lst
BLOCKING
ALL
GRANT
PUBLIC"
where
dbname
is
the
name
of
a
database
to
which
the
utilities
should
be
bound.
The
files
db2ubind.lst
and
db2cli.lst
contain
the
names
of
the
required
bind
files
for
DB2
CLI
to
connect
to
DB2
Version
8
servers.
6.
Reboot
the
machine.
Upgrading
the
DB2
Universal
Database
client
You
must
remove
the
existing
DB2
Universal
Database
Run-Time
Client
before
you
can
install
the
DB2
Universal
Database
Administration
Client
required
for
use
with
DB2
Universal
Database
Workgroup
Server
Edition
8.1.3.
To
install
the
Administration
Client:
1.
Log
on
to
the
Tivoli
Provisioning
Manager
server
as
root.
2.
Run
the
following
commands
for
each
instance:
su
-
iname
.
$HOME/sqllib/db2profile
db2
force
applications
all
db2
terminate
db2stop
where
iname
is
the
instance
owner
name.
24
Tivoli
Provisioning
Manager
Migration
Guide
If
you
are
a
High
Availability
Cluster
Multi-Processing
(hacmp)
user,
you
must
use
the
ha_db2stop
command
instead
of
the
db2stop
command.
Otherwise
the
db2stop
command
will
trigger
a
failure
event.
3.
Use
the
operating
system
tools
to
remove
the
Administration
Client:
v
2000Linux
Use
rpm
to
remove
the
Administration
Client
package.4.
Install
DB2
Universal
Database
Run-Time
Client:
a.
Ensure
that
you
have
the
Tivoli
Provisioning
Manager,
Version
2.1
Prerequisite
Software
Installer
CD
and
the
DB2
Administration
Client
Component,
Version
8.1
CD.
b.
Insert
the
Tivoli
Provisioning
Manager,
Version
2.1
Prerequisite
Software
Installer
CD
into
the
CD
drive.
Mount
the
CD
drive,
but
do
not
change
directory
to
the
mount
point.
Changing
directories
to
the
mount
point
will
lock
the
CD
drive
and
prevent
you
from
being
able
to
swap
CDs.
c.
Run
the
command
for
your
platform:
v
2000Linux
mount_point/setuplinux.bin.
v
2000iSeries
mount_point/setuplinuxppc.bin.d.
When
you
are
prompted
to
select
a
product
to
install,
select
DB2
Universal
Database,
and
then
click
Next.
On
the
next
configuration
panel,
select
DB2
Administrator
Client
with
Fixpack
3:
This
will
install
the
DB2
Administrator
client
and
the
fixpack.
Select
this
option
if
you
will
be
creating,
or
have
already
created,
a
remote
database
server
and
you
are
running
the
installer
on
your
Tivoli
Provisioning
Manager
machine.
The
DB2
client
instance
will
be
created
for
you.
Loading
the
CMDB
tablespace
Before
you
can
install
Tivoli
Provisioning
Manager,
you
must
load
the
Configuration
Management
Database
(CMDB)
tablespace.
This
tablespace
provides
integration
with
the
Tivoli
CMDB
Relationship
Registry
and
enables
Tivoli
Provisioning
Manager
to
insert
information
about
items
that
are
managed
in
the
data
center.
To
load
the
CMDB
tablespace:
1.
Connect
to
the
database
as
the
database
administrator
(a
user
with
privileges
to
create
tablespaces).
db2
connect
to
db_name
user
admin_user
using
password
where
db_name
is
the
database
name,
admin_user
is
the
administrator
user
name,
and
password
is
the
administrator
password.
2.
Copy
CDBTableSpace.sql
from
the
Tivoli
Provisioning
Manager,
Version
2.1
CD
in
the
/tools/db/db2
directory
to
the
database
server.
3.
In
the
directory
where
you
copied
the
CDBTableSpace.sql
file,
run
the
following
command:
db2
-tvf
CDBTableSpace.sql
Chapter
5.
Upgrading
the
database
server
25
26
Tivoli
Provisioning
Manager
Migration
Guide
Chapter
6.
Upgrading
the
directory
server
You
must
ensure
that
your
directory
server
and
client
are
at
the
product
level
supported
by
Tivoli
Provisioning
Manager
2.1.
v
If
you
are
currently
using
Tivoli
Directory
Server,
you
must
update
it
to
version
5.2.
If
Tivoli
Directory
Server
is
installed
on
a
separate
server
you
should
also
update
the
client
on
the
Tivoli
Provisioning
Manager
server.
v
If
you
are
currently
using
Microsoft
Active
Directory
as
your
directory
server,
you
do
not
need
to
make
changes
to
the
software.
Note:
Tivoli
Directory
Server
can
be
on
the
same
server
as
Tivoli
Provisioning
Manager
or
on
a
separate
server.
If
it
is
installed
on
a
separate
server,
the
server
can
be
running
a
different
operating
system
than
the
Tivoli
Provisioning
Manager
server.
For
more
information
about
supported
topologies,
refer
to
the
Tivoli
Provisioning
Manager
2.1
Installation
Guide.
For
additional
information
about
migrating
Tivoli
Directory
Server,
refer
to
the
Tivoli
Directory
Server
5.2
documentation
in
the
Tivoli
Information
Center:
http://publib.boulder.ibm.com/infocenter/tivihelp/index.jsp.
IBM
Tivoli
Directory
Server
Tivoli
Provisioning
Manager
2.1
requires
Tivoli
Directory
Server
5.2.
This
section
provides
procedures
for
upgrading
IBM
Directory
Server
to
Tivoli
Directory
Server
5.2.
Note:
In
previous
releases,
this
product
was
called
IBM
Directory
Server.
As
of
Version
5.2,
the
product
is
called
IBM
Tivoli
Directory
Server.
Upgrading
on
Linux
Tivoli
Directory
Server
5.2
is
not
supported
on
Red
Hat
Enterprise
Linux
AS
2.1.
If
Tivoli
Directory
Server
5.1
are
currently
installed
on
a
Red
Hat
Enterprise
Linux
AS
2.1
server,
you
must
install
and
configure
Tivoli
Directory
Server
Version
5.2
on
a
separate
server
that
is
running
a
supported
platform
instead
of
updating
your
existing
server.
In
addition
to
Red
Hat
Enterprise
Linux
AS
2.1,
the
following
operating
environments
are
supported:
v
AIX
5.2
v
Solaris
8
v
Solaris
9
v
Windows
2000
v
Windows
Server
2003
Standard
Edition
v
SLES
8
for
iSeries
Power
PC
Pre-installation
steps
Perform
the
following
pre-installation
steps:
1.
Create
directories
for
the
data
you
will
migrate.
Type
the
following
commands:
mkdir
IDS_installdir/etc/userV52
mkdir
IDS_installdir/etc/userV52/ldapV51
2.
Export
your
data:
©
Copyright
IBM
Corp.
2003,
2004
27
a.
In
the
Configuration
Tool,
click
Export
LDIF
data
in
the
task
list.
b.
In
the
Export
LDIF
data
window,
specify
the
path
and
file
name
of
the
LDIF
file
in
the
Path
and
LDIF
file
name
field.
c.
Click
Export.
Save
the
file
to
the
IDS_installdir/etc
directory.
3.
Stop
IBM
Directory
Server.
4.
Back
up
the
previous
versions
of
the
slapd32.conf
or
ibmslapd.conf
and
any
schema
files
from
the
IDS_installdir/etc
directory
to
the
IDS_installdir/etc/userV52
directory.
The
backup
should
include
files
with
the
following
file
extensions.
v
.oc
v
.at
v
.conf
and
the
following
files:
v
V3.ldapsyntaxes
v
V3.matchingrules
v
V3.modifiedschema
From
the
IDS_installdir/etc
directory,
type
the
following
commands:
cp
*.ldif
userV52
cp
*.conf
userV52
cp
ldapV51/*
userV52/ldapV51
5.
Copy
all
the
backup
files
in
IDS_installdir/etc/userV52
to
a
location
where
you
can
obtain
it
for
migration
to
the
new
Tivoli
Directory
Server
machine.
6.
Uninstall
IBM
Directory
Server:
v
2000Linux
Uninstall
with
InstallShield.
Switch
to
the
/usr/ldap/_uninst
directory.
Run
the
command
./uninstall.
Remove
all
IBM
Directory
Server
components.
v
2000iSeries
Run
the
following
commands
to
remove
IBM
Directory
Server
packages:
rpm
-ev
ldap-server-5.2-1
rpm
-ev
ldap-webadmin-5.2-1
rpm
-ev
ldap-client-5.2-1
rpm
-ev
ldap-msg-xxx-5.2-1.i386.rpm
(Where
xxx
is
language
dependent.)
rpm
-ev
ldap-html-xxx-5.2-1.i386.rpm
7.
8.
Verify
that
all
IBM
Directory
Server
packages
have
been
removed.
Run
the
following
command:
pkginfo
-l
|
grep
-i
ldap
9.
If
any
IBM
Directory
Server
packages
are
found,
remove
them.
Type
rpm
-e
package_name,
where
package_name
is
the
package
name.
10.
Restart
the
computer.
Installing
Tivoli
Directory
Server
5.2
Install
Tivoli
Directory
Server
5.2
on
a
server
that
is
running
a
supported
platform
other
than
Red
Hat
Enterprise
Linux
AS
2.1.
To
Install
Tivoli
Directory
Server
5.2:
28
Tivoli
Provisioning
Manager
Migration
Guide
1.
Insert
the
appropriate
Tivoli
Directory
Server
5.2
CD
into
the
CD
drive.
Mount
the
CD
drive,
but
do
not
change
directory
to
the
mount
point.
Changing
directories
to
the
mount
point
will
lock
the
CD
drive
and
prevent
you
from
being
able
to
swap
CDs.
2.
From
the
root
directory
on
the
CD
run
./setup
(UNIX
or
Linux
on
iSeries)
or
setup.exe
(Windows).
3.
Follow
the
instructions
in
the
installer
to
install
the
software.
Note:
The
installer
identifies
preinstalled
components
and
corresponding
version
levels.
Ensure
that
you
selectServer
5.2
and
Client
SDK
5.2
for
installation.
The
Web
Administration
Tool
is
not
compatible
with
WebSphere
Application
Server
5.1
and
should
not
be
used
after
you
upgrade
WebSphere
Application
Server
to
Version
5.1.
Applying
the
Tivoli
Directory
Server
fix
After
you
install
Tivoli
Directory
Server
on
the
new
directory
server,
perform
the
following
steps:
1.
Apply
the
Tivoli
Directory
Server
fix.
Copy
the
V3.ibm.at
fix
from
the
ITDS
directory
on
the
Tivoli
Provisioning
Manager,
Version
2.1
Generic
Fixes
CD
to
the
IDS_installdir/etc
directory.
Importing
directory
server
data
Since
you
had
to
uninstall
IBM
Directory
Server
5.1
in
order
to
install
Tivoli
Directory
Server
5.2,
you
must
import
the
Tivoli
Provisioning
Manager
2.1
schema
and
import
your
IBM
Directory
Server
5.1
data.
To
import
data:1.
Copy
the
file
schema.ldif
from
the
Tivoli
Provisioning
Manager
Version
2.1
CD
located
in
the
tools\ldap
to
the
IDS_installdir
directory.
2.
Start
the
Tivoli
Directory
Server
Configuration
Manager.
3.
Click
Add,
and
then
click
OK.
4.
Click
Manage
Schema
files
and
then:
a.
Browse
to
the
IBM
Tivoli
Directory
Server
5.2
home
directory
and
select
the
schema.ldif.
b.
Click
Add
and
then
click
OK.5.
Create
directories
for
migrating
data:
mkdir
IDS_installdir/etc/userV52
mkdir
IDS_installdir/etc/userV52/ldapV51
6.
Copy
the
files
that
you
backed
up
on
the
original
server
to
the
IDS_installdir/etc/userV52
directory
on
this
server.
7.
Migrate
the
configuration
files
that
you
backed
up
by
running
the
migrate52
script.
Type
the
following
commands
at
a
command
prompt:
cd
IDS_installdir/etc
../sbin/migrate52
Note:
You
must
run
the
migrate52
script
even
if
you
did
not
modify
the
previous
schema.
There
are
new
schema
files
and
entries
in
the
ibmslapd.conf
file
that
are
not
compatible
with
previous
versions.
’
8.
Import
the
data
that
you
exported
from
the
original
Tivoli
Directory
Server
machine.
a.
In
Configuration
Manager,
click
Import
LDIF
data
in
the
task
list.
b.
In
the
Export
LDIF
data
window,
specify
the
path
and
file
name
of
the
LDIF
file
that
you
exported
in
the
Path
and
LDIF
file
name
field.
Chapter
6.
Upgrading
the
directory
server
29
c.
Select
the
Standard
Import,
and
then
click
Import.
Upgrading
the
IBM
Directory
Server
5.1
client
If
Tivoli
Directory
Server
is
installed
on
a
separate
server,
you
should
update
the
Tivoli
Directory
Server
client
on
the
Tivoli
Provisioning
Manager
server.
To
upgrade
the
client:
1.
Log
on
as
root.
2.
Uninstall
the
IBM
Directory
Server
5.1
client:
a.
Type
rpm
-qa
|
grep
-i
ldap-client-5.1
to
find
the
client
packages.
Type
rpm
-e
package_name
to
remove
each
client
package,
where
package_name
is
the
package
name.3.
Insert
the
Tivoli
Directory
Server
Version
5.2
CD
into
the
CD
drive.
Mount
the
CD
drive,
but
do
not
change
directory
to
the
mount
point.
Changing
directories
to
the
mount
point
will
lock
the
CD
drive
and
prevent
you
from
being
able
to
swap
CDs.
4.
To
start
the
installer,
run
./setup,
and
the
follow
the
instructions
in
the
installer.
When
you
are
prompted
to
select
products
to
install,
select
Client
SDK
5.2
only.
Microsoft
Active
Directory
A
Windows
2000
Server
with
Microsoft
Active
Directory
installed
can
be
used
as
a
directory
server
for
Tivoli
Provisioning
Manager.
To
migrate
to
Tivoli
Provisioning
Manager
2.1
v
Microsoft
Active
Directory
must
be
set
up
with
your
existing
Tivoli
Provisioning
Manager
1.1.2
system.
v
Update
the
Windows
2000
Server
to
Service
Pack
4.
You
can
obtain
the
Service
Pack
from
the
Microsoft
web
site
at
http://www.microsoft.com.
v
After
you
upgrade
WebSphere
Application
Server
to
Version
5.1,
you
must
re-import
the
security
certificate
for
SSL
communication.
For
more
information,
refer
to
the
chapter
“Installing
and
configuring
Microsoft
Active
Directory”
in
the
Tivoli
Provisioning
Manager
Installation
Guide.
30
Tivoli
Provisioning
Manager
Migration
Guide
Chapter
7.
Upgrading
WebSphere
Application
Server
Previous
releases
of
Tivoli
Provisioning
Manager
required
both
WebSphere
Application
Server
and
WebSphere
Application
Server
Application
Client.
5.0.1
This
release
requires
WebSphere
Application
Server
5.1
only.
To
prepare
for
migration,
you
must
perform
the
following
procedures:
1.
Uninstall
WebSphere
Application
Server
5.0.1
and
WebSphere
Application
Server
Application
Client
5.0.1.
2.
Ensure
that
prerequisites
for
WebSphere
Application
Server
5.1
are
properly
installed
and
configured.
WebSphere
Application
Server
Application
Client
is
not
required
for
Tivoli
Provisioning
Manager
2.1.
3.
Install
WebSphere
Application
Server
5.1.
4.
Apply
WebSphere
Application
Server
5.1
fixes.
Uninstalling
WebSphere
Application
Server
Application
Client
WebSphere
Application
Server
Application
Client
is
not
required
for
Tivoli
Provisioning
Manager
2.1
and
should
be
removed.
To
uninstall
the
client:
1.
Switch
to
the
uninstallation
directory
for
WebSphere
Application
Server
Application
Client
installation.
The
default
location
is
/opt/WebSphere/AppClient/_uninst.
2.
Run
the
uninstall
program.
Uninstalling
WebSphere
Application
Server
5.0.1
Before
you
begin
If
you
downloaded
and
installed
interim
fixes
and
fix
packs,
you
must
uninstall
all
interim
fixes
and
fix
packs
before
uninstalling
the
base
WebSphere
Application
Server
product.
For
details
about
removing
an
interim
fix
or
fix
pack,
refer
to
the
associated
fix
pack
documentation.
If
WebSphere
Application
Server
is
not
uninstalled
properly,
reinstalling
into
the
same
directory
can
result
in
invalid
XML
configurations.
The
following
uninstall
procedure
describes
the
manual
uninstall
process
required
to
establish
a
clean
environment
for
reinstallation.
Note:
Since
IBM
HTTP
Server
was
installed
with
WebSphere
Application
Server
5.0.1,
uninstalling
WebSphere
Application
Server
also
uninstalls
IBM
HTTP
Server.
Uninstalling
the
WebSphere
Application
Server
To
uninstall
WebSphere
Application
Server
5.0.1:
1.
Log
on
as
root.
2.
Stop
WebSphere
Application
Server
processes.
a.
Type
the
ps
-ef
|
grep
java
to
list
all
Java
processes.
©
Copyright
IBM
Corp.
2003,
2004
31
b.
To
stop
WebSphere
Application
Server
processes
run
the
following
command:
kill
-9
pid
where
pid
are
the
IDs
of
the
processes
to
stop.3.
Stop
any
running
WebSphere
MQ
queue
managers.
a.
Type
dspmq
to
show
the
state
of
any
queue
managers.
b.
Type
endmqm
-i
for
each
running
queue
manager.4.
Check
for
and
remove
interprocess
communication:
a.
Use
the
ipcs
command
to
check
for
interprocess
communication.
v
Type
ipcs
-aq
|
grep
mqm
to
check
for
message
queues
owned
by
WebSphere
MQ.
v
Type
ipcs
-am
|
grep
mqm
to
check
for
shared
memory
owned
by
WebSphere
MQ.
v
Type
ipcs
-as
|
grep
mqm
to
check
for
semaphores
owned
by
WebSphere
MQ.b.
Remove
each
identified
interprocess
communication,
with
the
ipcrm
command.
v
Type
ipcrm
-q
id
to
check
for
message
queues
owned
by
WebSphere
MQ.
v
Type
ipcrm
-m
id
to
check
for
shared
memory
owned
by
WebSphere
MQ.
v
Type
ipcrm
-s
id
to
check
for
semaphores
owned
by
WebSphere
MQ.
where
id
is
the
identifier
for
the
entry.
The
identifier
is
similar
to
a
file
descriptor
and
is
used
by
the
operations
function
calls
to
access
the
resource
after
a
get
is
performed
on
it.
For
more
information
about
interprocess
communication,
refer
to
the
Interprocess
Communication
(IPC)
Overview.
On
the
IBM
Software
Support
page
at
http://www.ibm.com/software/support/,
search
for
reference
number
pTechnote0716.5.
Stop
all
WebSphere
MQ
processes:
a.
Type
the
ps
-ef
|
grep
mqm
to
list
WebSphere
MQ
processes.
b.
Type
kill
-9
amq_ids
to
stop
the
message
queues
where
amq_ids
are
the
application
message
queue
IDs
to
stop.
6.
Run
the
WAS_installdir\_uninst\uninstall
program.
7.
Search
for
related
packages
with
the
following
commands:
v
Type
rpm
-qa
|
grep
-i
wsb
to
show
packages
for
the
base
WebSphere
Application
Server
product
and
the
IBM
HTTP
Server
product.
v
Type
rpm
-qa
|
grep
-i
mq
to
show
packages
for
the
embedded
messaging
feature,
which
is
based
on
WebSphere
MQ
technology.
v
Type
rpm
-qa
|
grep
-i
series
to
show
MQ
series
packages.
v
Type
rpm
-qa
|
grep
-i
wemps
to
show
more
packages
for
the
embedded
messaging
feature.
v
Type
rpm
-qa
|
grep
-i
tivguid
to
show
the
Tivoli
GUID
package.8.
Type
rpm
-e
package_name
to
remove
all
packages,
where
package_name
is
the
package
name.
Note:
If
you
cannot
remove
package
because
of
package
dependencies,
use
the
following
command
to
ignore
the
dependencies.
rpm
-e
package_name
--nodeps
--justdb
32
Tivoli
Provisioning
Manager
Migration
Guide
9.
Remove
the
product
directories
with
the
following
commands:
rm
-rf
/opt/WebSphere/AppServer
rm
-rf
/opt/WebSphere/AppClient
rm
-rf
/opt/IBMHttpServer
rm
-fr
/var/wemps
/opt/wemps
rm
-fr
/var/mqm
/opt/mqm
10.
Remove
the
existing
version
of
Tivoli
GUID
with
the
following
command:
rm
-rf
/opt/tivoli/guid
11.
Edit
the
vpd.properties
file.
a.
Locate
the
vpd.properties
file
in
the
/root
directory.
b.
Remove
any
lines
related
to
WebSphere
Application
Server:
v
WSB
for
the
base
WebSphere
Application
Server,
V5.0.x
product
v
WSC
for
the
WebSphere
Application
Server
Application
Clients
v
WSM
for
the
WebSphere
MQ
productc.
Save
the
file
and
close
it.
Note:
Do
not
delete
or
rename
the
vpd.properties
file
because
the
InstallShield
for
MultiPlatforms
(ISMP)
program
uses
it
for
other
products
that
it
installs.
Pre-installation
steps
Before
you
install
WebSphere
Application
Server
5.1,
perform
the
following
steps:
1.
Verify
that
the
file
structure
required
for
WebSphere
MQ
exists.
2.
Verify
that
the
group
IDs
and
user
IDs
required
for
WebSphere
MQ
exist.
Creating
WebSphere
MQ
file
systems
Before
you
install
WebSphere
embedded
messaging,
you
must:
1.
Recreate
the
file
systems
for
WebSphere
MQ
and
its
data.
2.
Verify
the
group
IDs
and
user
ID
for
WebSphere
MQ.
Creating
a
file
system
for
working
data
You
must
recreate
the
file
system
that
you
removed
when
you
uninstalled
WebSphere
Application
Server.
1.
Create
and
mount
a
journalized
file
system
called
/var/mqm.
Use
a
partition
strategy
with
a
separate
volume
for
the
WebSphere
MQ
data.
This
ensures
that
other
system
activity
will
not
be
affected
if
/var/mqm
accumulates
a
large
amount
of
WebSphere
MQ
data.
2.
Ensure
that
the
/var
directory
is
large
enough
to
handle
the
workload.
The
/var
file
system
is
used
to
store
all
the
security
logging
information
for
the
system,
and
is
used
to
store
the
temporary
files
for
and
printing.
Therefore,
it
is
critical
that
you
maintain
free
space
in
/var
for
these
operations.
If
you
do
not
create
a
separate
file
system
for
messaging
data,
and
/var
fills
up,
all
security
logging
will
be
stopped
on
the
system
until
free
space
becomes
available
in
/var,
and
you
will
not
be
able
to
or
print.
To
determine
the
size
of
the
/var/mqm
file
system
for
a
server
installation,
consider
the
following
criteria:
v
The
maximum
number
of
messages
in
the
system
at
one
time
v
Contingency
for
message
buildups,
if
there
is
a
system
problem
v
The
average
size
of
the
message
data,
plus
500
bytes
for
the
message
header
v
The
number
of
queues
Chapter
7.
Upgrading
WebSphere
Application
Server
33
v
The
size
of
log
files
and
error
messages
v
The
amount
of
SSL
trace
that
is
written
to
the
/var/mqm/trace
directory
v
Allow
50
MB
as
a
minimum
for
a
WebSphere
MQ
server.
You
need
less
space
in
/var/mqmfor
a
WebSphere
MQ
client.
Typically
this
is
15
MB.
Creating
separate
file
systems
for
working
data
1.
Create
a
file
system
/var/mqm/log
for
your
log
data.
If
possible,
store
log
files
on
a
different
physical
volume
from
the
WebSphere
MQ
queues
(/var/mqm).
This
ensures
data
integrity
in
the
case
of
a
hardware
failure.
2.
Create
a
file
system
/var/mqm/errors
for
your
error
files.
Note:
The
size
of
the
log
file
depends
on
the
log
settings
that
you
use.
The
recommended
size
is
set
to
support
circular
logging
using
the
default
settings.
For
further
information
on
log
sizes
refer
to
the
WebSphere
MQ
System
Administration
Guide.
Setting
up
the
group
IDs
and
the
user
ID
You
can
use
the
System
Administration
Manager
(SAM)
to
manage
user
IDs.
Verify
the
following
group
and
user
ID
information:
1.
The
mqm
group
and
mqbrkrs
group
exist.
Type
the
following
command:
cat
/etc/group
|
grep
mq
Sample
output:
mqm::103:root,mqbrks,tioadmin,mqm
mqbrkrs::104:root,mqbrks,tioadmin,mqm
2.
The
user
mqm
exists
and
mqm
is
set
as
the
primary
group.
The
mqm
user
ID
owns
the
directories
and
files
that
contain
the
resources
associated
with
WebSphere
MQ.
Type
the
following
command:
cat
/etc/passwd
|
grep
mqm
Sample
output:
mqm:x:1003:103::/home/mqm:/bin/ksh
3.
The
user
root
exists
in
the
mqm
group
and
mqbrkrs
group.
This
can
be
verified
with
the
command
in
step
1.
Note:
If
you
make
any
changes,
log
out
and
then
log
back
in
to
implement
the
changes.
Installing
WebSphere
Application
Server
5.1
The
prerequisite
software
installer
provides
a
method
for
installing
IBM
middleware
and
its
related
components.
It
is
based
on
ISMP
and
will
install
the
applications
with
minimal
user
input.
For
new
installations,
the
Tivoli
Provisioning
Manager
this
installer
can
be
used
to
install
WebSphere
Application
Server,
DB2
Universal
Database
and
Tivoli
Directory
Server.
For
system
migration,
the
installer
can
only
be
used
for
software
installation
in
specific
situations.
WebSphere
Application
Server
5.1
requires
you
to
remove
WebSphere
Application
Server
5.0.1
and
then
install
WebSphere
Application
Server
5.1.
The
prerequisite
software
installer
can
be
used
for
WebSphere
Application
Server
5.1
installation.
To
install
WebSphere
Application
Server
5.1:
34
Tivoli
Provisioning
Manager
Migration
Guide
Limitation:
WebSphere
Application
Server
cannot
be
installed
using
the
PICS
installer
through
remote
desktop
connections
or
network
mapping.
1.
Log
on
as
user
root.
2.
Insert
the
Pre-requisite
Software
Installer
CD
into
the
CD
drive.
Mount
the
CD
drive,
but
do
not
change
directory
to
the
mount
point.
Changing
directories
to
the
mount
point
will
lock
the
CD
drive
and
prevent
you
from
being
able
to
swap
CDs.
3.
Run
the
command
for
your
platform:
v
2000Linux
mount_point/setuplinux.bin.
v
2000iSeries
mount_point/setuplinuxppc.bin.
4.
A
language
pack
panel
appears.
Select
whether
you
wish
to
install
support
for
languages
other
than
English.
Click
Next.
5.
Review
the
information
on
the
Tivoli
Software
screen
and
click
Next.
6.
On
the
Prerequisite
software
installer
panel,
click
Next.
The
installer
program
verifies
that
the
prerequisites
have
been
met.
During
this
time,
the
installer
screen
may
not
be
visible.
7.
On
the
next
panel,
specify
a
directory
into
which
you
will
copy
the
Pre-requisite
Software
Installer
application.
v
Choose
a
directory
in
usr/ibm/pics.
v
Choose
a
directory
in
opt/ibm/pics.
The
Pre-requisite
Software
Installer
copies
itself
to
the
local
hard
drive
to
free
up
the
CD
drive.
Note:
It
is
recommended
that
you
do
not
use
a
directory
path
with
a
space
in
the
path
name.
8.
Click
Next.
While
the
Pre-requisite
Software
Installer
copies
code
to
the
hard
drive,
the
installer
screen
may
not
be
visible.
9.
On
the
next
panel,
select
which
products
to
install
on
this
machine.
Ensure
that
the
only
selected
option
is
WebSphere
Application
Server
5.1,
and
then
click
Next.
10.
The
next
screen
confirms
the
installation
options
you
have
selected,
including
installation
directories,
port
numbers,
user
names,
and
so
on.
Record
this
information;
some
of
the
information
will
be
needed
during
the
Tivoli
Provisioning
Manager
installation.
Click
Next.
11.
You
are
prompted
to
enter,
or
browse
to
the
paths
where
the
installation
code
for
the
software
you
have
selected.
If
you
will
be
installing
the
software
selections
from
the
local
CD
drive,
insert
the
first
CD
and
specify
the
appropriate
drive
location.
If
you
have
copied
the
software
CD
images
to
a
local
or
network
drive,
enter
the
path
to
the
location
of
the
images.
Click
Next.
Note:
The
installation
process
can
take
some
time.
12.
Verify
the
location
of
your
Java
directory
and
then
check
the
value
of
the
$JAVA_HOME
environment
variable.
It
might
be
different
from
the
path
that
was
configured
for
your
WebSphere
Application
Server
5.01
installation.
This
variable
must
be
configured
correctly
to
apply
the
mandatory
WebSphere
Application
Server
fixes.
Chapter
7.
Upgrading
WebSphere
Application
Server
35
Applying
WebSphere
Application
Server
fixes
After
installing
the
prerequisite
software,
you
must
apply
the
mandatory
patches
to
the
Tivoli
Directory
Server
and
the
WebSphere
Application
Server.
The
fixes
are
located
on
the
Tivoli
Provisioning
Manager
Version
2.1
Generic
Fixes
CD.
The
fixes
that
need
to
be
applied
are:
v
WebSphere
Application
Server
5.1
cumulative
fix
3
v
WebSphere
MQ
V5.3
fix
Applying
the
WebSphere
Application
Server
5.1
Cumulative
Fix
3
Follow
these
steps
to
apply
WebSphere
Application
Server
5.1
Cumulative
Fix
3.
To
apply
the
WebSphere
Application
Server
5.1
Cumulative
Fix
31.
Log
on
as
root.
2.
Stop
the
WebSphere
Application
Server.
3.
Create
a
directory
called
WAS_installdir/update/was510_cf3.
4.
Copy
the
Cumulative
Fix
3
for
WebSphere
Application
Server
5.1
from
the
WAS/CF3
directory
on
the
CD
to
the
WAS_installdir/update/was510_cf3
directory.
v
2000Linux
was510_cf3_linux.zip
v
2000iSeries
was510_cf3_linuxppc.zip5.
Unzip
the
Cumulative
Fix
3
package.
6.
Run
the
UpdateWizard
with
the
command
updateWizard.sh.
During
installation
ensure
that
the
Install
fix
packs
option
is
selected.
Note:
On
some
platforms,
the
UpdateWizard
interface
to
the
update
installer
program
does
not
recognize
the
existing
WebSphere
Application
Server
product.
This
problem
is
caused
by
a
limitation
in
the
InstallShield
for
MultiPlatforms
(ISMP)
program
that
the
update
installer
program
uses.
To
work
around
the
problem,
click
Specify
product
information
and
type
the
fully
qualified
installation
root
directory
for
the
existing
product
in
the
Installation
directory
field
of
the
UpdateWizard
panel.
7.
After
installing
the
fix,
restart
WebSphere
Application
Server.
Applying
the
WebSphere
MQ
V5.3
fix
To
apply
the
WebSphere
MQ
fix:
1.
Log
on
as
root.
2.
Copy
the
file
IC38409.unix.tar.Z
file
into
a
temporary
directory
on
your
hard
drive.
3.
Uncompress
the
file
using
the
command:
uncompress
IC38409.unix.tar.Z
4.
Untar
the
file
using
the
command:
tar
-xvf
IC38409.unix.tar
5.
Stop
any
running
WebSphere
MQ
queue
managers.
a.
Type
dspmq
to
show
the
state
of
any
queue
managers.
b.
Type
endmqm
-i
for
each
running
queue
manager.6.
Write
down
the
properties
of
the
existing
com.ibm.mqjms.jar
and
com.ibm.mq.jar
files
(permissions,
ownership).
By
default
they
are
stored
in
the
/opt/mqm/java/lib
directory.
36
Tivoli
Provisioning
Manager
Migration
Guide
7.
Make
a
backup
copy
of
the
existing
files.
8.
Replace
the
existing
com.ibm.mqjms.jar
and
com.ibm.mq.jar
files
with
the
new
versions.
Verify
that
the
new
versions
of
files
have
retained
the
same
properties
as
the
old
versions.
If
required,
correct
any
modified
properties.
Importing
the
security
certificate
for
Microsoft
Active
Directory
If
you
are
using
Microsoft
Active
Directory
as
your
directory
server,
you
must
re-import
the
security
certificate
for
SSL
communication
into
WebSphere
Application
Server.
For
details
about
importing
the
security
certificate,
refer
to
the
chapter
“Installing
and
configuring
Microsoft
Active
Directory”
in
the
Tivoli
Provisioning
Manager
Installation
Guide.
Chapter
7.
Upgrading
WebSphere
Application
Server
37
38
Tivoli
Provisioning
Manager
Migration
Guide
Chapter
8.
Migrating
Tivoli
Provisioning
Manager
After
you
have
installed
the
software
prerequisites,
you
are
ready
to
upgrade
Tivoli
Provisioning
Manager.
Before
you
begin
Before
you
begin
Tivoli
Provisioning
Manager
installation,
ensure
that
you
have
the
following
CDs:
v
Tivoli
Provisioning
Manager
2.1.0
CDs
v
Tivoli
NetView
CDs
(if
you
selected
the
Tivoli
NetView
installation
option).
Ensure
that
there
are
no
users
currently
logged
on
as
tioadmin.
Tivoli
Provisioning
Manager
2.1
cannot
be
installed
properly
if
a
user
is
logged
on
as
tioadmin
during
the
installation
process.
Notes:
1.
If
you
want
to
use
Tivoli
NetView
for
discovery
capabilities
in
Tivoli
Provisioning
Manager,
you
must
install
SNMP
on
the
Tivoli
Provisioning
Manager.
Ensure
that
SNMP
is
enabled
on
the
server.
2.
2000iSeries
Tivoli
NetView
is
not
supported
on
iSeries
Linux.
Installing
Tivoli
Provisioning
Manager
2.1
To
install
Tivoli
Provisioning
Manager:
1.
Log
on
to
the
system
as
the
root.
2.
Ensure
that
your
directory
server
and
the
database
server
are
started.
3.
Insert
the
Tivoli
Provisioning
Manager
CD
into
the
CD
drive.
Mount
the
CD
drive,
but
do
not
change
directory
to
the
mount
point.
Changing
directories
to
the
mount
point
will
lock
the
CD
drive
and
prevent
you
from
being
able
to
swap
CDs.
4.
Run
the
installer
with
the
appropriate
command:
v
2000Linux
mount_point/setuplinux.bin
v
2000iSeries
mount_point/setup.bin
5.
On
the
Tivoli
Provisioning
Manager
box,
select
the
language
you
want
the
graphical
installer
to
use,
and
then
click
OK.
6.
Read
the
information
on
the
Welcome
panel,
and
then
click
Next.
7.
The
Software
License
Agreement
panel
displays.
Review
the
terms
of
the
license
agreement
and
select
one
of
the
options.
v
If
you
accept
the
terms
of
license
agreement,
select
I
accept
the
terms
in
the
license
agreement
and
click
Next.
v
If
you
decline
the
terms
of
the
license
agreement,
select
I
do
not
accept
the
terms
in
the
license
agreement
and
click
Next.
A
confirmation
window
is
shown
with
the
message:
Do
you
really
wish
to
decline
the
license
agreement?
Click
Yes
to
exit
the
installation
program
or
click
No
to
be
returned
back
to
the
Software
License
Agreement
panel.
©
Copyright
IBM
Corp.
2003,
2004
39
8.
The
installer
indicates
that
it
has
detected
your
existing
Tivoli
Provisioning
Manager
software.
The
panel
describes
actions
you
must
take
before
migrating.
Click
Next
to
continue.
9.
The
installer
must
verify
that
your
system
meets
the
software
prerequisites
for
installation.
Click
Next
to
initiate
the
prerequisite
check.
This
may
take
a
few
minutes,
during
which
time
the
install
panel
may
disappear.
It
will
reappear
when
the
prerequisite
check
is
complete.
If
an
error
occurs
during
the
prerequisite
check,
or
if
your
system
does
not
meet
the
prerequisite
criteria,
a
panel
will
appear
with
an
explanation.
10.
The
Language
Package
Selection
panel
defines
the
language
that
will
be
used
on
the
Tivoli
Provisioning
Manager
graphical
user
interface.
The
default
language
used
by
the
graphical
installer
is
English.
If
you
need
other
supported
international
languages,
select
the
check
box
and
then
click
Next.
11.
The
DB2
Configuration
panel
prompts
you
for
your
database
information.
The
fields
contain
the
values
from
your
current
installation.
The
user
IDs
and
directory
paths
you
enter
on
this
panel
must
match
those
entered
during
your
original
DB2
Universal
Database
installation.
Verify
the
information
in
the
fields.
The
following
fields
appear
for
DB2
Universal
Database:
Database
Name
for
the
IBM
Tivoli
Provisioning
Manager
database
Enter
the
name
of
the
database
to
be
used
with
Tivoli
Provisioning
Manager
Database
User
Name
This
can
be
the
local
administrative
user
ID
or
any
other
user
name
that
already
exists
on
the
system.
The
user
name
entered
here
does
not
need
to
match
the
database
server
instance
owner
ID.
Database
User
Password
Enter
the
password
for
the
database
user
ID.
Local
DB2
instance
SQLLIB
directory
Verify
that
the
correct
path
is
entered
in
this
field.
If
multiple
instances
exist
on
this
server,
or
if
you
installed
to
a
directory
other
than
the
default,
the
installer
cannot
detect
which
instance
directory
is
to
be
used
with
Tivoli
Provisioning
ManagerEnter
the
directory
path
to
the
local
database
client.
If
you
have
installed
your
database
server
on
a
remote
server,
enter
the
path
to
the
local
database
client
directory.The
following
fields
are
displayed
for
Oracle9i
Database:For
more
information
on
these
database
user
IDs
and
how
they
are
used,
refer
to
your
database
product
documentation.
12.
Click
Next.
The
installer
will
validate
the
database
connection,
which
may
take
a
moment
before
the
next
panel
is
displayed.
13.
On
the
IBM
Directory
Server
panel,
enter
the
properties
of
the
existing
directory
server.
Base
DN
This
field
is
displayed
for
Microsoft
Active
Directory
only.
The
default
value
is
dc=ibm,
dc=com.
Change
this
to
reflect
your
domain
information.
LDAP
Administrator
User
Name
LDAP
Administrator
User
Password
Enter
the
password
for
the
LDAP
Administrator
user.
40
Tivoli
Provisioning
Manager
Migration
Guide
Fully
Qualified
Host
Name
or
IP
Address
Enter
the
fully
qualified
host
name.
For
example,
myhost.domain.com.
Host
Port
The
port
that
is
used
to
communicate
with
the
directory
server.
The
default
value
is
389.
Accept
the
default
value.
If
the
default
port
value
is
already
in
use
in
your
system,
select
another
port
value.
Enable
SSL
for
Runtime
Transactions
Select
this
check
box
to
enable
SSL
encryption.
If
you
enable
SSL:
v
You
must
change
the
Host
Port
number
to
the
secure
port
used
by
your
directory
server.
For
Tivoli
Directory
Server,
the
secure
port
is
636.
v
You
must
complete
the
configuration
instructions
for
enabling
SSL
communication
provided
in
the
Tivoli
Provisioning
Manager
2.1
Installation
Guide
when
Tivoli
Provisioning
Manager
installation
completes
successfully.14.
Click
Next.
15.
On
the
WebSphere
Application
Server
configuration
panel,
verify
the
information
in
the
fields:
DNS
Suffix
Name
This
must
be
the
DNS
domain
or
sub-domain.
For
example,
subdomain.domain.com.
This
information
is
used
for
the
single
signon
functionality
in
WebSphere
Application
Server.
Installation
Directory
Verify
that
the
location
of
the
WebSphere
Application
Server
directory
is
correct.16.
Click
Next.
17.
On
the
next
panel,
click
Next
to
verify
that
WebSphere
Application
Server
is
operating
properly
before
you
install
Tivoli
Provisioning
Manager.
The
system
runs
an
automated
server
stop
and
start.
While
the
system
starts
the
server,
the
panel
displays
the
message:
“Starting
the
WebSphere
Application
Server”,
and
a
blue
process
bar
indicates
that
the
system
is
processing.
When
the
server
is
stopped,
the
system
starts
it
again,
and
the
panel
displays
the
message:
“Stopping
the
WebSphere
Application
Server”.
When
the
server
is
stopped
a
second
time,
the
verification
cycle
is
complete.
Click
Next.
18.
The
Installation
Preview
panel
summarizes
the
information
you
have
entered
during
the
Tivoli
Provisioning
Manager
installation.
Review
the
information
to
ensure
that
it
is
accurate.
If
the
information
is
correct,
click
Next
to
continue.
If
the
information
is
not
correct,
click
Back
to
return
to
the
previous
panels,
and
then
enter
the
correct
information
in
the
appropriate
fields.
19.
As
Tivoli
Provisioning
Manager
is
being
installed,
a
panel
displays
showing
the
progress
of
the
installation.
The
installation
is
complete
when
the
summary
panel
displays.
Note:
The
movement
of
the
progress
bar
is
based
on
installation
for
an
average
system.
Actual
installation
time
depends
on
the
performance
of
your
Tivoli
Provisioning
Manager
server,
and
might
vary
a
little
from
the
reported
installation
progress.
Chapter
8.
Migrating
Tivoli
Provisioning
Manager
41
20.
If
you
would
like
to
start
the
Tivoli
Provisioning
Manager
services
immediately,
select
the
check
box.
Click
Finish
to
exit
the
installation
wizard.
21.
Log
out
and
then
log
back
in
as
tioadmin
so
that
all
defined
environment
variables
take
effect.
22.
Verify
that
required
environment
variables
are
properly
defined
for
the
tioadmin
user.
v
$WAS_HOME:
The
installation
directory
for
WebSphere
Application
Server.
v
$TIO_HOME:
The
installation
directory
for
Tivoli
Provisioning
Manager.
Note:
This
variable
replaces
the
$TC_HOME
variable
that
was
used
in
Tivoli
Provisioning
Manager
previous
releases.
v
$JAVA_HOME:
The
directory
where
Java
is
installed.
This
variable
is
required
for
some
tools
and
features,
such
as
the
workflow
backup
utility
and
running
SOAP
commands.
If
Java
is
not
currently
installed
on
the
Tivoli
Provisioning
Manager,
you
can
obtain
the
IBM
Java
Developer
Kit
(JDK)
from
http://www-106.ibm.com/developerworks/java/jdk/
v
$TIO_LOGS%:
The
directory
where
Tivoli
Provisioning
Manager
stores
log
files.
The
default
value
is
/var/ibm/tivoli/common
Notes:
1.
By
default
DB2
8.1.2
has
LOCKTIMEOUT=-1
(no
timeout).
The
Tivoli
Provisioning
Manager
installation
runs
a
script
to
change
the
LOCKTIMEOUT
value
to
120.
2.
The
installer
does
not
change
the
default
DB2
locklist
value
of
50.
The
recommended
value
is
2000
for
Tivoli
Provisioning
Manager.
For
information
about
the
locklist
value,
refer
to
locklist
topic
in
the
DB2
Universal
Database
Information
Center
at
http://www-3.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/v8document.d2w/
report?fn=r0000267.htm.
3.
If
Java
error
messages
appear
at
the
end
of
the
installation
indicating
that
images
in
the
com.sun.java.swing.plaf.motif.MotifLookAndFeel/icons/
directory
are
missing,
the
messages
can
be
ignored.
They
are
not
used
by
the
Tivoli
Provisioning
Manager
installer.
42
Tivoli
Provisioning
Manager
Migration
Guide
Part
3.
Migrating
data
This
part
describes:
v
The
types
of
data
that
are
automatically
migrated
during
the
software
upgrade
process
v
The
types
of
data
that
cannot
be
migrated
v
Data
that
you
must
migrate
manually
v
Verifying
your
migration
After
data
migration
is
complete,
you
should
verify
that
your
system
is
working
properly.
This
part
also
provides
procedures
for
verifying
that
your
migration
was
successful
v
Chapter
9,
“Migrating
data,”
on
page
45
v
Chapter
10,
“Verifying
migration,”
on
page
51
©
Copyright
IBM
Corp.
2003,
2004
43
44
Tivoli
Provisioning
Manager
Migration
Guide
Chapter
9.
Migrating
data
The
software
upgrade
process
automatically
migrates
or
updates
some
of
your
data.
Data
that
is
not
automatically
migrated
is
either
deprecated
in
Tivoli
Provisioning
Manager
2.1
or
must
be
migrated
manually.
Data
that
is
migrated
automatically
The
following
data
is
automatically
migrated
or
updated
when
you
upgrade
Tivoli
Provisioning
Manager:
Data
center
model
The
data
center
model
is
automatically
migrated
User
accounts
User
accounts
are
automatically
migrated
Workflow
associations
The
installer
automatically
migrates
associations
between
data
center
objects
and
their
assigned
device
models
and
workflows.
After
you
have
upgraded
software,
you
must
run
a
script
to
install
the
core
Tivoli
Provisioning
Manager
automation
packages
as
described
in
“Installing
core
automation
packages”
on
page
45.
Data
that
cannot
be
migrated
When
you
upgrade
your
Tivoli
Provisioning
Manager
software,
the
installation
program
does
not
remove
obsolete
files.
The
following
data
is
cannot
be
migrated.
Log
files
Log
files
should
be
backed
up
as
described
in
“Backing
up
your
system”
on
page
9.
Reports
Reports
cannot
be
migrated
since
Tivoli
Provisioning
Manager
uses
new
reporting
tools
and
new
types
of
reports.
If
you
want
to
keep
a
copy
of
reports
for
your
existing
system,
generate
the
reports
and
then
or
save
them
as
described
in
“Backing
up
your
system”
on
page
9.
Deployment
history
The
format
of
the
deployment
history
has
changed.
If
you
need
to
access
past
deployment
history
after
upgrading
your
software,
you
can
also
perform
a
database
query
on
the
WORKFLOW_EXECUTION
and
TRANSITION_EXECUTION
database
tables.
Installing
core
automation
packages
After
you
install
Tivoli
Provisioning
Manager,
you
must
run
a
script
to
update
the
automation
packages
provided
with
the
product.
When
the
core
automation
packages
are
installed,
you
can
then
install
any
customized
workflows
that
you
are
migrating.
The
automation
package
installation
script
tries
to
install
all
automation
packages
in
TIO_installdir/drivers
directory,
you
should
delete.
If
you
added
any
automation
packages
to
this
directory,
they
will
not
be
installed
when
you
run
the
script.
©
Copyright
IBM
Corp.
2003,
2004
45
Note:
Consider
removing
any
automation
packages
that
you
added
to
the
TIO_installdir/drivers
directory
to
prevent
“not
installed”
error
messages
form
appearing
when
you
run
the
automation
package
installation
script.
To
install
core
automation
packages:
1.
Log
on
as
tioadmin.
2.
In
the
TIO_instaldir\tools\log4j-util.prop
file,
check
the
value
of
log4j.appender.file.append.
If
the
value
is
set
to
false,
change
it
to
true.
3.
Switch
to
the
TIO_installdir/tools
directory.
4.
Run
the
command
post-install.sh
start.
5.
If
you
changed
the
value
of
log4j.appender.file.append
in
step
1,
reset
the
value
to
false.
Migrating
customized
workflow
components
If
you
created
or
modified
workflows
for
your
Tivoli
Provisioning
Manager
1.1.x
system,
you
created
an
automation
package
with
the
customized
workflow
components
during
the
system
backup
process
described
in
Chapter
3,
“Preparing
for
migration,”
on
page
9.
After
you
upgrade
your
system
software,
you
must
convert
and
install
the
automation
package
to
migrate
your
workflow
components.
The
migration
process
involves
the
following
steps:
1.
Convert
your
modified
workflow
components
as
described
in
“Converting
modified
workflow
components.”
2.
Install
your
converted
workflow
components
as
described
in
“Installing
the
converted
workflow
components”
on
page
47.
3.
For
workflows
that
contain
logical
device
operations,
change
the
local
of
the
workflows
to
en_US
(English).
See
“Changing
the
locale
of
workflows”
on
page
48.
Workflow
dependencies
If
a
workflow
in
an
automation
package
references
a
workflow
in
another
automation
package,
you
must
convert
and
install
the
automation
package
with
the
referenced
workflow
first.
If
you
do
not
install
the
workflows
required
by
an
automation
package
that
you
are
converting,
a
compile
error
message
is
displayed
and
includes
the
name
of
the
missing
workflow.
Example:
The
automation
package
mypkgA.tcdriver
contains
the
workflow
My.Add.Server.
This
workflow
calls
a
workflow
in
mypkgB.tcdriver
called
My.Configure.Monitoring.
Before
you
can
convert
mypkgA.tcdriver,
you
must
convert
and
install
mypkgB.tcdriver.
Converting
modified
workflow
components
Before
a
workflow
can
be
converted,
it
must
be
both
installed
and
available
in
its
unzipped
format
as
individual
files
as
described
in
“Setting
up
customized
workflows
for
migration”
on
page
13.
If
your
.tcdriver
files
contain
workflow
components
that
were
not
installed
in
your
Tivoli
Provisioning
Manager
1.1.x
system
before
upgrading
to
Version
2.1,
you
must
install
these
automation
packages
before
you
use
the
conversion
tool.
To
install
an
automation
package:
46
Tivoli
Provisioning
Manager
Migration
Guide
1.
Log
on
as
tioadmin.
2.
Open
a
command
window.
3.
Switch
to
the
TIO_installdir/tools
directory.
4.
Run
the
following
command:
tc-driver-manager.sh
installDriver
drivername
where
drivername
is
the
name
of
the
automation
package
that
you
created
with
your
customized
workflow
components.
Running
the
conversion
tool
To
convert
the
automation
package
with
customized
workflows:
1.
Log
on
as
tioadmin.
2.
Switch
to
the
TIO_installdir/.tools/migration
directory.
3.
At
the
command
prompt,
run
the
command
convertTCDriver.sh
source_dir
target_dir
driver_name
where
v
source_dir
is
the
directory
that
contains
the
automation
package
to
convert.
v
target_dir
is
the
output
directory
for
the
converted
automation
package.
v
driver_name
is
the
name
of
the
automation
package
file
that
you
want
the
conversion
tool
to
convert
(for
example,
custom-extreme-48i).
Omit
the
.tcdriver
extension
from
the
name.
Example:
./convertTCDriver.sh
TIO_installdir/custom_workflows/old
TIO_installdir/custom_workflows/new
my_router
The
conversion
script
converts
the
workflows
in
the
source
automation
package,
and
creates:
v
A
file
structure
with
the
new
automation
package
contents
in
the
specified
output
directory.
v
A
converted
automation
package
with
the
.tcdriver
extension.
You
can
install
the
converted
.tcdriver
file.
If
you
want
to
make
any
changes
to
the
converted
workflows
in
the
output
file
structure,
you
must
package
them
into
a
.tcdriver
file
after
you
make
your
changes.
Note:
If
a
workflow
compilation
error
occurs
during
conversion,
the
conversion
tool
still
creates
a
new
workflow
in
the
target
directory.
If
compilation
error
messages
appear
during
conversion,
ensure
that
you
check
the
converted
workflows
associated
with
the
error.
Installing
the
converted
workflow
components
After
the
conversion
process
is
complete,
the
new
converted
workflows
must
be
installed.
1.
Log
on
as
tioadmin.
2.
Open
a
command
window.
3.
Copy
the
converted
automation
package
(.tcdriver
file)
into
TIO_installdir/drivers
4.
Switch
to
the
TIO_installdir/tools
directory.
5.
Run
the
following
command:
tc-driver-manager.sh
installDriver
forceInstallDriver
driver_name
-overwrite=true
Chapter
9.
Migrating
data
47
where
driver_name
is
the
name
of
the
automation
package
that
you
created
with
your
customized
workflow
components.
Notes:
1.
The
-overwrite
parameter
is
required
with
the
tc-driver-manager
command
because
your
customized
Tivoli
Provisioning
Manager
1.1.x
workflows
already
exist
in
the
system
with
the
same
names
as
your
converted
files.
The
converted
workflows
must
to
be
installed
to
replace
them.
2.
Some
customization
changes
might
not
be
fully
converted
by
the
conversion
script.
Check
your
customized
workflows
after
you
install
them
to
ensure
that
they
work
correctly.
Changing
the
locale
of
workflows
Tivoli
Provisioning
Manager
2.1
workflows
enable
you
to
specify
a
locale
(language)
for
a
target
device,
or
indicate
that
a
workflow
applies
to
any
locale
(language).
If
your
customized
workflows
include
logical
device
operations,
you
must
specify
the
en_US
(English)
locale
for
the
target
device
of
the
logical
device
operations.
When
a
locale
is
specified,
a
workflow
fails
if
the
target
device
for
the
workflow
does
not
match
the
locale.
To
specify
a
locale
using
the
Web
interface:
1.
Log
on
to
the
Web
interface.
For
logon
instructions,
refer
to
“Administrative
Tasks,”
on
page
59.
2.
Click
System
configuration
and
workflow
management
—>
Workflows,
and
then
click
the
workflow
to
edit.
3.
Drag-and-drop
Check
Device
Locale
into
the
workflow.
4.
Click
the
Check
Device
Locale
command
and
then
specify
the
target
device
ID
and
locale.
For
more
information
about
using
Workflow
Composer,
click
Help
to
view
the
Tivoli
Provisioning
Manager
Information
Center.
To
specify
a
locale
using
a
text
editor:
1.
Export
the
workflow.
a.
Log
on
to
the
Web
interface.
b.
Click
System
configuration
and
workflow
management
—>
Workflows,
and
then
click
the
workflow
to
edit.
The
workflow
appears
in
Workflow
Composer.
c.
Click
Edit
—>
Export
to
save
your
workflow.
2.
Open
the
exported
workflow
in
a
text
editor.
3.
Use
the
CheckDeviceLocale
command
to
specify
a
locale
for
a
device.
Refer
to
the
following
example:
workflow
test
var
v
=
Jython("en_US")
var
deviceId
=
Jython(5)
CheckDeviceLocale
deviceId
v
CheckDeviceLocale
deviceId
"fr_FR"
4.
Save
the
workflow
with
a
.wkf
extension.
5.
Click
the
Check
Device
Locale
command
and
then
specify
the
target
device
ID
and
locale.
For
more
information
about
using
Workflow
Composer,
refer
to
the
online
help.
6.
In
the
Web
interface,
return
to
Workflow
Composer.
7.
Click
Edit
—>Open.
8.
Click
Browse
and
navigate
to
the
workflow
that
you
created.
48
Tivoli
Provisioning
Manager
Migration
Guide
9.
Click
OK.
10.
Click
Compile
—>Compile
to
save
the
workflow
to
the
database.
Chapter
9.
Migrating
data
49
50
Tivoli
Provisioning
Manager
Migration
Guide
Chapter
10.
Verifying
migration
After
migration
perform
the
tasks
described
in
this
chapter
to
verify
the
migration
of
your
Tivoli
Provisioning
Manager
system.
Your
verification
should
include
the
following
tasks:
Starting
the
server
and
signing
on
to
the
Web
interface
Verify
that
you
can
start
the
Tivoli
Provisioning
Manager
server
and
log
on
to
the
Web
interface.
For
details,
refer
to
the
instructions
in
“Administrative
Tasks,”
on
page
59.
User
accounts
In
Tivoli
Provisioning
Manager
2.1,
users
are
assigned
to
specific
user
roles
that
are
associated
with
individual
access
rights.
During
the
software
upgrade
process,
user
roles
are
automatically
assigned
to
user
accounts.
Check
the
user
role
assignments
to
ensure
that
they
are
appropriate.
1.
Log
on
to
the
Web
interface.
2.
Click
System
configuration
and
workflow
management
—>Users.
The
Users
page
displays
all
defined
users.
3.
In
the
row
for
the
user
you
want
to
view,
click
More
—>Properties.
4.
Verify
that
the
user
is
assigned
to
the
correct
role.
For
more
information
about
access
rights
associated
with
each
role,
refer
to
the
online
help..
Data
center
model
In
the
Web
interface,
review
the
configuration
of
your
assets
and
resource
pool
in
the
Data
center
assets
and
resources
navigation
tree.
Applications
and
provisioning
Verify
that
your
customers
and
applications
in
the
Customer
applications
navigation
tree
have
been
migrated.
After
you
have
verified
the
application
migration,
manually
provision
a
server
from
the
Web
interface
to
confirm
that
your
data
center
model
has
been
migrated
properly,
and
that
workflows
for
provisioning
work
correctly.
For
details
about
the
following
steps,
refer
to
the
online
help.
1.
Change
the
mode
of
the
operating
mode
of
application
to
manual.
2.
Add
a
server
to
an
application.
3.
After
the
server
is
added,
check
the
deployment
history
for
a
record
of
the
change.
Click
System
configuration
and
workflow
management
—>Workflow
Executions.
Customized
workflows
Verify
that
your
customized
workflows
appear
in
the
System
configuration
and
workflow
management
navigation
tree.
Run
one
of
your
customized
workflows
to
verify
that
it
works
correctly.
©
Copyright
IBM
Corp.
2003,
2004
51
52
Tivoli
Provisioning
Manager
Migration
Guide
Part
4.
Post-migration
configuration
This
part
contains
information
about
additional
installation
and
configuration
steps
that
you
might
want
to
perform
after
migration
to
take
advantage
of
new
Tivoli
Provisioning
Manager
2.1
features.
v
Chapter
11,
“Additional
configuration
tasks,”
on
page
55
©
Copyright
IBM
Corp.
2003,
2004
53
54
Tivoli
Provisioning
Manager
Migration
Guide
Chapter
11.
Additional
configuration
tasks
This
chapter
describes
installation
and
configuration
tasks
that
you
might
want
to
implement
after
migration.
Setting
up
SSL
encryption
To
secure
communication
between
the
Tivoli
Provisioning
Manager,
WebSphere
Application
Server,
directory
server
(Tivoli
Directory
Server
or
Microsoft
Active
Directory),
and
web
clients,
you
can
install
and
configure
SSL
certificates
on
the
servers.
For
details
about
installing
and
configuring
SSL,
refer
to
the
Tivoli
Provisioning
Manager
Installation
Guide.
Configuration
for
new
and
updated
features
This
section
describes
some
of
the
new
and
changed
features
in
Tivoli
Provisioning
Manager
2.1
that
you
might
want
to
set
up
after
migration.
For
details
about
these
features,
refer
to
the
online
help.
Reports
Reporting
capabilities
are
optional.
If
you
want
to
access
and
view
reports,
you
must
install
Tivoli
Data
Warehouse
and
the
associated
Web
Enablement
Pack.
For
more
information
about
setting
up
Tivoli
Provisioning
Manager
for
reports,
see
the
Tivoli
Provisioning
Manager
Installation
Guide
and
the
Tivoli
Provisioning
Manager
Warehouse
Enablement
Pack
Implementation
Guide.
New
monitoring
capabilities
Tivoli
Provisioning
Manager
enables
you
to
manage
monitoring
of
resources
by
external
systems
such
as
IBM
Tivoli
Monitoring.
From
the
Web
interface,
you
can
apply
monitoring
to
specific
servers,
and
then
start
and
stop
monitoring
as
required.
New
event
management
capabilities
If
you
are
using
IBM
Tivoli
Enterprise
Console
to
manage
event
collection,
performance
monitoring,
and
recovery
from
events,
you
can
set
up
your
system
to:
v
Send
workflow
failure
events
to
Tivoli
Enterprise
Console.
v
Run
SOAP
commands
remotely
from
Tivoli
Enterprise
Console
when
the
condition
of
an
event
is
met.
Discovery
Tivoli
Provisioning
Manager
2.1
helps
you
to
manage
changes
to
your
data
center
by
automatically
detecting
changes
in
the
configuration
of
defined
devices
(configuration
drift)
and
identifying
devices
that
are
added
to
the
system
and
that
have
not
been
added
to
the
data
center
model.
Virtual
servers
and
storage
There
are
two
new
types
of
data
center
assets.
Virtual
servers
Virtualization
allows
multiple
operating
systems
to
run
©
Copyright
IBM
Corp.
2003,
2004
55
concurrently
on
a
single
processor.
You
can
define
and
manage
virtual
servers
in
your
data
center.
Storage
Tivoli
Provisioning
Manager
2.1
supports
two
types
of
storage
architecture:
Direct
access
storage
(DAS)
and
Storage
area
networks
(SAN).
Importing
new
data
center
objects
Since
Tivoli
Provisioning
Manager
supports
additional
types
of
data
center
assets,
you
might
want
to
add
data
center
assets
to
the
data
center
model.Tivoli
Provisioning
Manager
2.1
enables
you
to
add
specific
assets
by
importing
an
XML
file
that
defines
the
assets
that
you
want
to
add.
For
more
information
about
this
capability,
refer
to
the
Tivoli
Provisioning
Manager2.1
Information
Center.
Some
new
features
for
integration
with
external
systems
also
require
new
data
center
objects.
For
example,
if
you
want
to
use
Tivoli
Monitoring
to
collect
utilization
data
from
servers,
you
must
import
the
objective-analyzer-type
and
data-acquisition
objects
required
for
this
feature.
You
can
look
at
the
sample
data
center
model
XML
file
to
see
the
format
of
a
data
center
model
in
Tivoli
Provisioning
Manager
2.1
and
become
familiar
with
new
data
center
objects.
TIO_installdir/xml/venice.xml
56
Tivoli
Provisioning
Manager
Migration
Guide
Part
5.
Appendixes
©
Copyright
IBM
Corp.
2003,
2004
57
58
Tivoli
Provisioning
Manager
Migration
Guide
Appendix.
Administrative
Tasks
This
chapter
provides
details
on
how
to
start
and
stop
the
Tivoli
Provisioning
Manager
server,
along
with
the
instructions
on
accessing
the
main
administrative
console.
For
further
information
on
using
Tivoli
Provisioning
Manager,
refer
to
the
Tivoli
Provisioning
Manager
Information
Center
available
from
the
Web
interface.
Starting
the
server
Before
you
start
Tivoli
Provisioning
Manager,
verify
the
following
requirements:
v
WebSphere
Application
Server
service
is
stopped.
v
Tivoli
Directory
Server
service
is
started.
v
You
are
logged
in
as
tioadmin.
Follow
the
steps
below
to
start
the
Tivoli
Provisioning
Manager
server.
Note:
The
user
tioadmin
uses
the
bash
shell
as
the
login
shell.
A
line-mode
login
(for
example,
via
telnet)
will
work
without
additional
configuration.
If
you
use
a
window
manager
such
as
a
Common
Desktop
Environment,
you
might
not
be
able
to
create
a
complete
login
environment,
which
is
required
for
Tivoli
Provisioning
Manager
to
function
properly.
This
can
be
resolved
by
doing
the
following:
1.
Create
the
.bashrc
file
in
tioadmin’s
home
directory,
and
insert
the
following
single
line:
.
$HOME/.profile
2.
Save
the
file.
3.
Edit
the
.dtprofile
in
tioadmin’s
home
directory
and
uncomment
the
following
line:
DTSOURCEPROFILE=true.
This
file
is
automatically
created
when
user
tioadmin
logs
in
to
CDE
for
the
first
time.
4.
Login
as
user
tioadmin
again
to
the
Common
Desktop
Environment
.
To
start
the
server:
1.
Switch
to
the
$TIO_HOME\tools
directory.
2.
Run
the
command
./tio.sh
start.
A
command
window
will
open.
3.
To
access
the
Tivoli
Provisioning
Manager
console,
refer
to
“Signing
on
to
the
Web
interface”
on
page
60.
Stopping
Tivoli
Provisioning
Manager
To
stop
Tivoli
Provisioning
Manager:
1.
Log
in
as
user
tioadmin.
2.
Switch
to
the
TIO_installdir/tools
directory.
3.
Run
the
command
./tio.sh
stop.
You
will
be
prompted
to
enter
the
WebSphere
Application
Server
admin
user
name,
which
is
the
default
wasadmin
and
the
password.
If
you
have
not
changed
the
password
yet,
the
default
password
is
wasadmin.
4.
Check
the
log
file
TIO_installdir/logs/tio_stop.log
for
errors.
5.
After
a
few
moments,
both
windows
will
close.
©
Copyright
IBM
Corp.
2003,
2004
59
Signing
on
to
the
Web
interface
Before
you
log
on,
verify
the
following
requirements:
v
You
have
an
appropriate
Web
browser
v
You
have
the
fully
qualified
domain
name
(for
example,
hostname.domain.com)
and
port
number
for
the
Tivoli
Provisioning
Manager
server.
The
default
port
number
is
9080.
Contact
your
installation
team
to
obtain
the
correct
server
information.
v
You
have
your
Tivoli
Provisioning
Manager
user
name
and
password.
v
Tivoli
Provisioning
Manager
is
running.
To
access
the
main
Tivoli
Provisioning
Manager
console:
1.
Open
a
Web
browser
and
enter
the
following
URL:
http://host_name:9080/tcWebUI
where
host_name
is
the
fully-qualified
domain
name
of
the
server.The
Sign
On
window
opens.
2.
Enter
your
user
name
and
password.
The
default
user
name
is
tioappadmin
and
if
you
have
not
already
changed
the
password,
the
default
password
is
tioappadmin.
Signing
off
from
the
Web
interface
To
sign
off
from
the
system,
click
Logoff.
The
Sign
Off
window
opens.
You
will
automatically
be
logged
off
the
system
after
thirty
minutes
of
session
inactivity.
60
Tivoli
Provisioning
Manager
Migration
Guide
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
61
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
registered
trademarks
of
Intel
Corporation
in
the
United
States,
other
countries,
or
both.
Java
and
all
Java-based
trademarks
and
logos
are
trademarks
or
registered
trademarks
of
Sun
Microsystems,
Inc.
in
the
United
States,
other
countries,
or
both.
Microsoft
and
Windows®
are
trademarks
or
registered
trademarks
of
Microsoft
Corporation
in
the
United
States,
other
countries,
or
both.
Other
company,
product
and
service
names
may
be
trademarks
or
service
marks
of
others.
62
Tivoli
Provisioning
Manager
Migration
Guide
����
Printed
in
USA
GC32-1620-00