Mass deployment of DB2 Universal Database Version 8.2 on ... db2/11134.pdf · DB2 UDB Personal...
70
Mass deployment of DB2 Universal Database Version 8.2 on Microsoft Windows operating systems
Transcript of Mass deployment of DB2 Universal Database Version 8.2 on ... db2/11134.pdf · DB2 UDB Personal...
-
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
���
-
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
���
-
ii
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
Contents
Authors
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
Chapter
1.
Introduction
.
.
.
.
.
.
.
. 1
Chapter
2.
DB2
UDB
Version
8.2
product
overview
.
.
.
.
.
.
.
.
.
.
.
.
.
. 3
DB2
clients
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 3
DB2
UDB
servers
and
database
engines
.
.
.
.
. 4
DB2
UDB
developer’s
editions
.
.
.
.
.
.
.
. 4
DB2
UDB
features
.
.
.
.
.
.
.
.
.
.
.
. 5
Chapter
3.
DB2
UDB
product
unattended
installation
capabilities
.
.
.
.
.
.
.
. 7
DB2
UDB
product
response
files
.
.
.
.
.
.
.
. 7
Creating
a
response
file
.
.
.
.
.
.
.
.
.
. 7
Creating
a
DB2
configuration
profile
.
.
.
.
. 9
Chapter
4.
Reducing
the
size
of
the
DB2
UDB
product
installation
image
.
. 11
How
the
db2iprune
utility
works
.
.
.
.
.
.
. 11
Pruning
a
DB2
UDB
product
installation
image
.
. 12
Chapter
5.
Deployment
of
DB2
UDB
products
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19
Deploying
DB2
UDB
products
by
performing
the
unattended
silent
installation
.
.
.
.
.
.
.
. 19
Deploying
DB2
UDB
products
using
Microsoft
Systems
Management
Server
(SMS)
2003
.
.
.
. 20
Packaging
DB2
UDB
using
SMS
.
.
.
.
.
. 20
Distributing
DB2
UDB
using
SMS
.
.
.
.
.
. 25
Deploying
DB2
UDB
products
using
Tivoli
Software
Distribution
4.2
.
.
.
.
.
.
.
.
.
.
.
.
. 32
DB2
UDB
software
package
creation
options
.
. 32
Creating
software
packages
for
installation
using
the
Software
Package
Editor
.
.
.
.
.
.
.
. 33
Creating
a
DB2
UDB
software
package
using
the
Package
Definition
File
Importer
tool
.
.
.
.
. 47
Deploying
DB2
UDB
product
FixPaks
.
.
.
.
. 48
Chapter
6.
Diagnosing
problems
with
distributed
installations
.
.
.
.
.
.
. 51
Troubleshooting
silent
installations
.
.
.
.
.
. 51
Locating
the
installation
log
files
.
.
.
.
.
. 51
Recording
tracing
information
.
.
.
.
.
.
. 51
Reading
the
log
files
.
.
.
.
.
.
.
.
.
. 51
Determining
installation
success
or
failure
.
.
. 53
Response
file
errors
.
.
.
.
.
.
.
.
.
.
. 54
The
WiLogUtl.exe
file
tool
.
.
.
.
.
.
.
. 55
Chapter
7.
Notices
.
.
.
.
.
.
.
.
.
. 57
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 59
iii
-
iv
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
Authors
v
Rory
A.A.
Hinton,
DB2
Up
and
Running
Solutions,
IBM
Toronto
Software
Lab
v
Andrew
Hilden,
DB2
Installation,
IBM
Toronto
Software
Lab
v
Louisa
Ford,
DB2
Installation,
IBM
Toronto
Software
Lab
v
-
vi
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
Chapter
1.
Introduction
The
distribution
and
installation
of
any
database
software
across
large
numbers
of
clients
and
servers
can
be
a
daunting
task.
However,
DB2®
Universal
Database
(UDB)
Version
8.2
has
features
and
tools
that
allow
both
servers
and
clients
to
be
deployed
quickly
and
seamlessly
across
your
enterprise
using
a
variety
of
deployment
methods.
DB2
UDB
Version
8.2
can
be
deployed
using
deployment
technologies
such
as
Microsoft®
SMS
and
Tivoli
Software
Distribution,
and
it
also
supports
an
easy
and
effective
manual
deployment
method.
The
type
of
deployment
method
best
suited
for
your
organization
depends
on
your
distribution
and
maintenance
requirements,
as
well
as
on
the
hardware,
software,
and
overall
infrastructure
of
your
existing
computer
environment.
If
you
are
a
database
or
systems
administrator,
use
the
information
in
this
paper
to
prepare
and
deploy
a
DB2
UDB
software
package
across
your
existing
computer
environment.
This
paper
includes
information
on
using
Microsoft
SMS
2003
and
Tivoli
Software
Distribution
4.2
for
DB2
UDB
deployment.
If
your
preferred
method
of
distribution
is
not
covered
explicitly
in
this
paper,
the
concepts
discussed
can
be
applied
to
other
distribution
methods.
Before
you
start
a
mass
deployment
of
DB2
UDB,
you
might
need
to
migrate
your
present
version
of
DB2
UDB
to
DB2
UDB
Version
8.2.
For
more
information,
consult
the
following
resources:
v
The
DB2
UDB
support
site
should
be
your
first
stop
for
DB2
UDB
information
that
includes
news
alerts,
DB2
UDB
FixPaks,
DB2
client
downloads,
FAQs,
Redbooks,
white
papers,
presentations,
and
hints
and
tips:
http://www.ibm.com/software/data/db2/udb/support.html
v
The
DB2
Information
Center
contains
documentation
for
DB2
UDB
and
related
DB2
products.
It
covers
every
aspect
of
DB2
products,
from
getting
started,
to
database
connectivity,
database
administration,
query
management,
business
intelligence,
and
application
development.
The
DB2
Information
Center
is
available
at:
http://publib.boulder.ibm.com/infocenter/db2help/index.jsp
v
The
DB2
Migrate
Now!
web
site
provides
resources
for
migration
from
Oracle,
Sybase,
and
Microsoft
SQL
server.
You
can
find
a
variety
of
tools
and
information
to
help
you
migrate
applications,
database
designs,
and
data
to
DB2
UDB
at:
http://www.ibm.com/software/data/db2/migration/
v
DB2
UDB
conferences
also
provide
valuable
DB2
UDB
information
on
new
product
features
and
techniques
for
problem
solving
1
-
2
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
Chapter
2.
DB2
UDB
Version
8.2
product
overview
Before
you
start,
you
should
understand
which
DB2
UDB
products
and
features
to
install
on
which
computers.
The
DB2
UDB
product
line
for
Version
8.2
on
Windows
operating
systems
has
over
15
products.
Choosing
the
right
product
to
install
for
your
existing
computer
environment
can
be
challenging
if
you
are
not
familiar
with
the
DB2
UDB
product
line.
To
help
you
determine
which
DB2
UDB
products
to
install
on
the
computers
in
your
computer
environment,
we
have
provided
the
following
product
overview.
This
overview
is
not
intended
to
detail
the
licensing
terms
of
each
product,
but
to
summarize
the
features
and
usage
scenarios
for
each
product.
Furthermore,
this
overview
focuses
on
the
products
that
seem
to
have
caused
some
confusion
over
their
roles
(as
indicated
through
PMRs,
newsgroup
postings,
and
other
communications
with
IBM
customers);
it
does
not
cover
all
DB2
UDB
products.
DB2
clients
There
are
four
DB2
client
products.
Each
product
provides
a
different
level
of
functionality.
The
DB2
Run-time
Client
is
designed
for
computers
that
need
the
DB2
client
to
enable
communications
with
remote
DB2
UDB
servers,
but
do
not
need
to
administer
any
servers.
No
graphical
tools
are
provided.
However,
any
application
which
uses
DB2
UDB
should
be
able
to
run
with
just
this
product.
There
is
also
a
smaller
version
of
the
run-time
client
called
the
DB2
Run-time
Client
Lite.
This
client
is
available
for
Windows
operating
systems
only.
It
provides
most
of
the
features
in
the
DB2
Run-time
Client
except
NetBIOS,
APPC
and
MDAC
are
not
bundled
with
the
installation
image.
Please
note
that
the
command
line
parameters
for
the
setup.exe
file
of
the
DB2
Run-time
Client
Lite
are
different
than
the
other
client
products.
Therefore,
some
of
the
discussions
in
this
paper
must
be
adapted
for
the
DB2
Run-time
Client
Lite.
The
DB2
Administration
Client
is
designed
for
DB2
UDB
administrators.
It
has
all
the
abilities
of
the
DB2
Run-time
Client,
plus
all
of
the
graphical
tools.
A
compact
installation
of
the
DB2
Administration
Client
is
functionally
equivalent
to
a
compact
installation
of
the
DB2
Run-time
Client.
The
DB2
Application
Development
Client
is
designed
for
software
developers
who
are
writing
software
to
use
with
DB2
UDB,
or
compiling
software
against
both
DB2
UDB
and
DB2
Connect.
It
has
all
the
functionality
of
the
DB2
Administration
Client,
with
additional
tools
for
application
development.
DB2
Connect
Personal
Edition
is
a
licensed
client
that
has
all
of
the
functionality
of
the
DB2
Application
Development
Client,
plus
the
ability
to
connect
to
host
or
iSeries
databases,
such
as
DB2
UDB
for
MVS.
Because
each
client
includes
all
of
the
functionality
of
the
clients
preceding
it,
you
rarely
need
more
than
one
client
installed
on
a
single
computer.
Multiple
clients
are
usually
installed
when
a
computer
role
is
being
changed.
For
example,
this
scenario
would
occur
when
a
user
is
promoted
to
a
DBA
role,
and
thus
may
need
to
move
from
a
DB2
Run-time
Client
to
a
DB2
Administration
Client.
Another
scenario
could
involve
a
user
who
has
a
new
requirement
to
access
host
or
iSeries
3
-
databases
and
thus
needs
to
move
to
DB2
Connect
Personal
Edition.
In
these
cases,
on
Windows
operating
systems,
you
can
upgrade
by
simply
installing
the
new
client
at
the
same
FixPak
level
over
top
of
the
existing
one.
You
can
later
remove
the
client
that
you
no
longer
require
from
the
system
without
affecting
the
newly
installed
product.
DB2
UDB
servers
and
database
engines
DB2
UDB
servers
scale
in
much
the
same
way
as
the
clients.
All
DB2
UDB
servers
are
licensed.
DB2
UDB
Personal
Edition
is
a
local
database
engine.
It
does
not
permit
connections
from
remote
clients,
however,
local
clients
can
work
directly
with
local
databases.
It
also
contains
all
of
the
functionality
of
the
DB2
UDB
Application
Development
Client.
DB2
UDB
Express
Editions
are
designed
for
small
and
medium
businesses
with
a
smaller
number
of
clients.
They
have
all
of
the
functionality
of
DB2
UDB
Personal
Edition,
but
also
allow
connections
from
remote
clients.
DB2
UDB
Workgroup
Server
Editions
are
designed
for
larger
scale
servers.
They
have
all
of
the
functionality
of
DB2
UDB
Express
Edition,
but
provide
more
extensive
licensing
options.
DB2
Connect
Enterprise
Editions
are
designed
for
three-tier
gating
of
clients
to
host
databases
such
as
DB2
UDB
for
MVS.
They
have
all
the
functionality
of
DB2
Connect
Personal
Edition,
plus
gateway
functionality.
DB2
UDB
Enterprise
Server
Edition
is
designed
for
large
and
very
large
databases.
As
such
this
product
includes
features
like
High
Availability
Disaster
Recover,
as
well
as
the
Data
Partitioning
Feature
(DPF).
It
also
contains
the
functionality
of
both
DB2
UDB
Workgroup
Edition
and
DB2
Connect
Enterprise
Edition.
Because
each
server
has
the
full
functionality
of
all
clients,
including
the
graphical
tools
and
application
development
tools,
there
is
no
reason
to
install
a
client
on
a
computer
that
already
has
a
server.
This
situation
greatly
simplifies
a
mass
deployment
of
DB2
UDB.
DB2
UDB
developer’s
editions
DB2
UDB
Personal
Developer’s
Edition
is
a
limited-license
version
of
DB2
UDB
Personal
Edition,
targeted
towards
small
development
groups.
It
contains
the
limited-license
DB2
UDB
Personal
Edition
and
the
DB2
Application
Development
Client,
allowing
individual
developers
to
write,
compile,
and
test
code
against
local
databases.
While
it
also
allows
for
the
use
of
remote
databases
for
development,
the
remote
database
server
products
are
not
included
in
this
package.
Since
DB2
UDB
hides
details,
such
as
where
the
database
is
physically
located
behind
the
DB2
API,
developing
under
DB2
UDB
Personal
Edition
is
the
same
as
developing
under
a
DB2
UDB
server
such
as
DB2
UDB
Enterprise
Server
Edition.
DB2
UDB
Universal
Developer’s
Edition
is
a
full-featured
one-stop
development
offering
that
is
targeted
towards
large
development
groups.
It
contains
a
bundle
of
nearly
all
DB2
UDB
for
Linux,
Unix,
and
Windows
operating
system
products,
including
products
not
mentioned
in
this
paper.
Since
it
includes
all
server
4
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
products
for
all
platforms,
it
is
used
by
those
who
are
developing
for
multiple
platforms,
or
platforms
not
supported
by
DB2
UDB
Personal
Developer’s
Edition.
Since
these
products
are
identical
to
previous
products,
except
for
their
licensing
terms,
there
is
no
need
to
install
these
over
top
of
existing
products.
DB2
UDB
features
Each
DB2
UDB
product
comes
with
a
set
of
features
that
determine
the
amount
of
functionality
and
disk
space
used
by
the
installed
product.
If
you
perform
a
Custom
installation,
you
can
select
which
features
to
install.
For
descriptions
of
DB2
UDB
features,
refer
to
the
db2_features
file
in
the
\db2\windows\samples
directory
of
the
DB2
UDB
installation
image.
Prerequisite
features
that
are
required
by
other
features
are
automatically
installed
by
the
DB2
installer
so
the
selected
features
will
function
properly.
If
you
require
your
DB2
UDB
installation
image
to
have
a
smaller
footprint,
you
can
use
the
db2iprune
utility
to
prune
your
image
prior
to
installing
it.
Refer
to
the
section
″Reducing
the
size
of
the
DB2
UDB
product
installation
image″
in
this
paper
for
more
information.
Chapter
2.
DB2
UDB
Version
8.2
product
overview
5
-
6
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
Chapter
3.
DB2
UDB
product
unattended
installation
capabilities
The
DB2
installer
can
run
either
as
a
graphical
installer
which
provides
for
an
interactive
type
of
installation,
or
in
a
mode
where
input
is
passed
to
the
installer
through
a
response
file.
The
latter
method,
which
is
referred
to
as
an
unattended
installation,
does
not
display
a
GUI
nor
does
it
require
any
user
input.
An
unattended
installation
is
used
to
deploy
software
to
a
large
number
of
users,
embed
DB2
UDB
software
within
applications,
or
to
repeat
an
installation
with
the
same
settings
as
a
previous
installation.
An
unattended
installation
also
provides
much
more
functionality
and
flexibility
than
a
GUI
installation.
You
can
create
more
than
one
instance,
catalog
and
create
databases,
set
database
manager
configuration
parameters
and
profile
registry
variables
during
installation,
and
import
instance
profiles
generated
from
the
db2cfexp
command
(the
connectivity
configuration
export
tool).
Considering
the
advantages
of
the
DB2
UDB
product
unattended
installation,
the
best
way
to
deploy
your
DB2
UDB
product
across
your
organization
is
to
perform
multiple
unattended
installations
using
the
DB2
installer
with
a
response
file.
The
unattended
installation
eliminates
the
need
for
user
input
at
the
target
computers,
and
by
using
the
same
response
file,
you
can
roll
out
identical
copies
of
your
DB2
UDB
product
across
multiple
computers
that
contain
the
same
components,
registry
variable
settings,
and
instance
configuration
settings.
All
DB2
UDB
products
can
be
installed
in
unattended
mode.
In
subsequent
sections,
we
explain
how
to
create
a
response
file
and
launch
an
unattended
installation.
DB2
UDB
product
response
files
In
order
to
perform
an
unattended
installation,
you
must
first
create
a
DB2
UDB
product
response
file.
A
response
file
is
a
text
file
that
is
used
to
specify
which
DB2
UDB
product
features
and
settings
to
install.
For
most
DB2
UDB
products,
this
specification
includes
components,
languages,
registry
variable
settings,
and
instance
configuration
settings.
You
can
also
use
the
response
file
to
import
a
client
configuration
profile,
which
allows
you
to
deploy
node
and
database
catalog
information
to
clients.
The
response
file
is
used
as
input
for
the
unattended
installation.
Creating
a
response
file
On
DB2
UDB
products
for
Windows
operating
systems,
there
are
three
different
methods
through
which
you
can
create
a
response
file:
v
Using
the
DB2
Setup
wizard
v
Using
the
DB2
response
file
generator
(db2rspgn)
v
Manually
editing
the
sample
response
file
Read
the
following
descriptions
to
find
out
which
method
is
best
for
you.
Using
the
DB2
Setup
wizard
The
DB2
Setup
wizard
is
the
graphical
DB2
product
installer
that
is
used
to
perform
interactive
installations.
This
tool
is
recommended
for
a
single
installation
7
-
because
the
wizard
provides
help
and
guidance
about
which
features
and
settings
to
install.
It
can
also
create
a
response
file
that
contains
the
features
and
settings
that
were
selected
in
the
wizard.
Procedure:
To
create
a
response
file
using
the
DB2
Setup
wizard:
1.
Select
the
Custom
installation
option,
and
then
select
the
Create
a
response
file
check
box
on
the
next
panel.
The
installer
saves
all
of
the
chosen
features
and
settings
to
a
text
file.
2.
The
default
target
destination
of
the
response
file
is
displayed
on
the
last
panel
of
the
DB2
Setup
wizard.
On
this
panel,
you
may
change
the
location
of
the
response
file
by
typing
a
new
path
name
in
the
response
file
field.
3.
The
response
file
gets
generated
during
the
DB2
UDB
product
installation.
The
DB2
Setup-generated
response
file
uses
default
values
for
DB2
registry
variables
and
instance
configuration
settings.
If
you
want
to
deploy
configuration
settings
that
are
different
from
the
defaults,
then
you
can
manually
add
these
settings
to
the
generated
response
file.
Refer
to
the
sample
response
file
in
the
\db2\windows\samples
directory
of
the
DB2
UDB
installation
image
for
a
list
of
valid
keywords
and
values
for
your
particular
DB2
UDB
product.
Using
the
DB2
response
file
generator
(db2rspgn)
You
can
create
a
response
file
after
your
DB2
UDB
product
has
been
installed
by
using
the
DB2
UDB
product
response
file
generator
utility,
called
db2rspgn.
The
db2rspgn
utility
takes
a
snapshot
of
your
DB2
UDB
product
installation
and
configuration
settings
and
saves
this
information
to
a
response
file
and
configuration
profile.
This
method
is
recommended
if
you
plan
to
perform
any
configuration
of
your
DB2
UDB
product
after
installation,
such
as
setting
configuration
parameters
or
cataloging
remote
nodes
and
databases.
All
of
this
information
gets
saved
to
the
response
file,
thus
eliminating
the
need
to
manually
add
it
yourself.
The
db2rspgn
utility
automatically
creates
an
instance
configuration
profile
so
you
do
not
need
to
run
the
db2cfexp
command.
The
resulting
configuration
profile
gets
saved
to
the
same
directory
as
the
generated
response
file.
Procedure:
To
use
the
db2rspgn
utility,
to
create
a
response
file:
1.
Open
the
DB2
CLP
and
issue
the
db2rspgn
command
using
the
following
syntax:
db2rspgn
–d
[-i]
where:
v
-d
is
used
to
pass
the
destination
directory
for
the
generated
response
file
and
any
instance
configuration
files.
v
-i
is
an
optional
parameter
used
to
input
the
instances
for
which
you
want
to
create
a
profile.
This
parameter
can
be
specified
multiple
times
to
input
more
than
1
instance.
For
example,
to
create
a
response
file
and
profile
in
the
C:\myfiles
directory
for
the
default
DB2
instance,
use
the
following
command:
db2rspgn
–d
C:\myfiles
–i
DB2
8
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
The
C:\myfiles
directory
contains
two
files:
a
response
file
(db2ese.rsp)
and
the
DB2.INS
file.
DB2.INS
is
the
configuration
profile
file
(also
known
as
the
Internet
Communication
Settings
file)
that
contains
configuration
and
connectivity
settings.
By
default,
the
generated
response
file
is
configured
to
import
DB2.INS
at
installation
time
by
setting
the
DB2.CLIENT_IMPORT_PROFILE
keyword
to
DB2.INS.
Manually
editing
the
sample
response
file
A
sample
response
file
is
a
pre-made
response
file
that
contains
all
possible
features
and
settings
to
install.
The
sample
response
file
is
located
in
the
\db2\windows\samples\*.rsp
directory
on
the
DB2
UDB
installation
CD
(they
are
the
files
with
the
″.rsp″
extension).
You
can
create
a
response
file
by
manually
editing
this
text
file.
Procedure:
To
specify
features
and
settings
to
install
through
the
sample
response
file:
1.
Uncomment
the
corresponding
keywords
by
deleting
the
comment
symbol
denoted
by
an
asterisk
(*).
Some
keywords
are
mandatory,
which
means
that
they
must
be
specified
in
order
for
the
installation
to
continue.
These
keywords
are
not
commented
out
(not
preceded
by
*).
The
remaining
keywords
are
optional,
which
means
that
the
installation
will
continue
using
default
values
if
they
are
not
uncommented
and
specified.
All
optional
keywords
are
preceded
by
an
asterisk.
The
sample
response
file
has
a
DB2.CLIENT_IMPORT_PROFILE
parameter
that
allows
you
to
import
a
configuration
profile
to
the
target
computers.
If
you
want
to
use
this
feature,
you
will
first
need
to
install
DB2
UDB
on
a
test
computer
and
take
a
snapshot
of
the
configuration
information
using
the
db2cfexp
utility.
Refer
to
the
section
called
″Creating
a
DB2
configuration
profile″
in
this
paper
for
more
information
on
how
to
create
a
configuration
profile.
This
method
is
the
most
complicated
of
the
three
methods
and
should
only
be
used
if
you
are
familiar
with
DB2
UDB
features
and
settings.
It
is
also
the
most
feature-rich
option
because
it
allows
you
to
deploy
a
sizable
number
of
DB2
configuration
settings
that
cannot
be
generated
using
the
DB2
Setup
wizard
or
the
db2rspgn
utility.
Creating
a
DB2
configuration
profile
The
DB2
configuration
profile
specifies
instance
configuration
settings,
as
well
as
node
and
database
catalog
information
found
in
the
system
node
and
database
directories
of
your
installed
DB2
UDB
product.
Use
the
db2cfexp
utility
to
create
a
configuration
profile.
This
utility
takes
a
snapshot
of
the
DB2
instance
profile
and
connectivity
information
and
generates
an
export
file
that
allows
you
to
distribute
DB2
UDB
with
identical
configuration
information
across
multiple
computers.
The
settings
that
get
recorded
are
database
information
(including
DCS
and
ODBC
information),
node
information,
protocol
information,
database
manager
configuration
settings,
UDB
registry
settings,
and
common
ODBC/CLI
settings.
If
you
created
a
response
file
using
the
DB2
response
file
generator
(db2rspgn),
you
do
not
need
to
perform
this
step
because
the
db2rspgn
utility
automatically
creates
a
configuration
profile
for
you.
If
you
used
the
DB2
Setup
wizard
or
a
sample
response
file
to
generate
your
response
file,
you
might
want
to
consider
creating
a
configuration
profile
by
using
the
db2cfexp
utility.
Chapter
3.
DB2
UDB
product
unattended
installation
capabilities
9
-
Procedure:
To
use
the
db2cfexp
command
to
create
a
configuration
profile:
1.
Open
up
the
DB2
CLP
and
enter
the
db2cfexp
command
using
the
following
syntax:
db2cfexp
filename
[
template
|
backup
|
maintain
]
where:
v
filename
represents
the
path/filename
of
the
configuration
profile
v
template
creates
a
configuration
profile
that
will
be
used
as
a
template
for
other
instances
of
the
same
instance
type
v
backup
creates
a
configuration
profile
for
backup
purposes
v
maintain
creates
a
configuration
profile
that
only
contains
database
and
node
information
for
maintaining
other
instances.
For
example,
the
following
command
creates
a
configuration
profile
called
db2ese_config
in
the
C:\myfiles
directory:
db2cfexp
C:\myfiles\db2ese_config
After
you
have
created
the
configuration
profile,
specify
its
path
name
in
the
DB2
response
file
by
setting
the
DB2.CLIENT_IMPORT_PROFILE
keyword.
10
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
Chapter
4.
Reducing
the
size
of
the
DB2
UDB
product
installation
image
DB2
UDB
products
give
full
flexibility
to
customers
by
including
the
maximum
number
of
installable
features
in
their
installation
images.
However,
this
can
put
customers
at
a
slight
disadvantage
due
to
the
large
footprint
size
of
the
installation
images.
This
issue
of
footprint
size
is
particularly
important
for
Independent
Software
Vendors
(ISVs)
who
often
embed
a
DB2
UDB
product
image
into
other
applications,
and
who
therefore
require
a
very
small
installation
image
footprint.
To
manually
reduce
the
size
of
the
installation
image
requires
someone
to
investigate
which
parts
of
the
installation
image
belong
to
which
feature
(usually
the
cabinet
files),
which
features
are
not
needed,
and
then
to
delete
the
unwanted
features.
This
process
is
time
consuming,
error-prone,
and
requires
an
advanced
knowledge
of
DB2
UDB
products.
For
example,
since
some
removed
features
may
be
required
for
other
features
to
work,
removing
them
without
this
knowledge
would
prevent
DB2
UDB
products
from
functioning
properly.
You
can
avoid
these
potential
problems
by
using
the
new
db2iprune
command
line
utility
to
reduce
the
size
of
your
DB2
UDB
product
installation
image
for
Windows
operating
systems.
This
tool
is
especially
useful
for
mass
deployments
of
DB2
UDB
products,
as
well
as
for
embedding
DB2
UDB
products
within
other
applications.
It
is
located
in
the
\db2\windows\utilities\db2iprune
directory
and
consists
of
an
input
file
and
a
db2iprune
executable
file.
The
input
file,
or
.prn
file,
contains
a
full
list
of
removable
features
and
is
used
to
indicate
which
features
and
languages
you
want
to
remove
from
the
installation
image.
The
db2iprune
executable
file
(db2iprune.exe)
removes
the
cabinet
(.cab)
files
associated
with
those
features
and
languages
(cabinet
files
are
a
number
of
related
files
that
are
packaged
together
for
deployment
purposes),
and
makes
it
impossible
to
remove
a
component
from
the
installation
image
if
a
different
feature
in
the
image
requires
that
component
to
be
present.
Only
the
unspecified
features,
and
any
components
that
the
unspecified
features
require,
are
included
in
the
pruned
installation
image.
When
the
pruned
image
is
installed,
features
that
were
removed
do
not
appear
in
the
installation
GUI
panels.
After
a
pruned
image
is
installed,
the
result
is
the
same
as
if
the
user
had
selected
only
that
subset
of
features
during
an
installation
from
a
full
image.
The
end
result
of
using
the
db2iprune
utility
is
a
new,
smaller
DB2
UDB
installation
image
that
can
be
installed
using
the
regular
DB2
UDB
product
installation
methods.
How
the
db2iprune
utility
works
v
When
the
db2iprune
utility
is
correctly
invoked
from
the
command
line,
the
first
thing
it
does
is
read
the
value
of
the
PROD
keyword
from
the
db2iprune
input
file
and
confirm
that
a
valid
DB2
UDB
product
installation
image
for
that
product
exists
in
the
path
that
is
specified
with
the
-p
parameter.
v
In
a
first
pass
through
the
input
file,
the
db2iprune
utility
reads
each
COMP
or
LANG
keyword,
it
queries
the
condition
table
in
the
.msi
database
to
get
the
corresponding
feature
name,
and
then
it
builds
a
list
of
features
that
the
customer
wants
to
remove
(called
the
removable
features
collection).
v
It
then
reads
each
COMP
or
LANG
keyword
again.
It
uses
the
value
of
this
keyword
to
look
up
which
feature
it
needs
to
remove
by
querying
the
condition
table
in
the
.msi
database.
It
also
verifies
that
this
feature
is
selectable
by
validating
that
11
-
it
exists
in
the
condition
table.
Only
the
features
that
are
selectable
based
on
the
customer’s
input
exist
in
the
condition
table.
v
It
then
finds
out
which
components
belong
to
this
feature
by
querying
the
FeatureComponents
table.
This
table
associates
features
with
the
components
that
belong
to
them.
It
verifies
that
none
of
the
components
belonging
to
this
feature
belong
to
another
feature
that
does
not
exist
in
the
condition
table.
It
also
verifies
that
none
of
these
components
belong
to
a
feature
that
is
not
to
be
removed.
It
does
so
by
verifying
that
any
feature
that
this
component
belongs
to
is
already
in
the
removable
features
collection.
This
check
is
not
required
for
language
features
since
their
components
are
not
shared
with
other
features.
v
The
db2iprune
utility
queries
the
file
table
and
retrieves
the
highest
sequence
in
that
table
for
a
file
in
that
component.
Using
this
number,
it
looks
up
the
media
table
to
determine
the
.cabfile
containing
the
files
for
that
component
and
ensures
that
the
.cabfiles
to
be
deleted
are
writable,
and
it
then
deletes
them.
v
In
the
final
step,
the
db2iprune
utility
ensures
that
the
features
that
have
been
pruned
are
invisible
to
the
user
and
are
not
installable.
It
completes
this
function
by
making
the
installation
level
for
the
features
equal
to
zero
in
the
condition
table
(features
with
an
install
level
of
zero
are
invisible).
This
is
not
done
for
language
features
because
they
are
always
invisible.
The
db2iprune
utility
then
invalidates
any
existing
installation
level
in
the
condition
table
for
this
feature
by
making
its
condition
false,
thereby
making
the
feature
uninstallable.
Pruning
a
DB2
UDB
product
installation
image
Procedure:
To
prune
a
DB2
UDB
product
installation
image
using
the
db2iprune
utility:
1.
Open
the
input
file,
or
.prn
file,
that
is
located
in
the
\db2\windows\utilities\db2iprune
directory,
and
uncomment
all
features
and
languages
that
you
want
removed
from
the
DB2
UDB
product
installation
image.
Comments
are
denoted
by
an
asterisk
(*).
The
db2iprune
input
file
contains
3
keywords:
PROD,
LANG,
and
COMP.
v
The
PROD
keyword
identifies
the
DB2
UDB
product
installation
image
to
be
pruned.
This
keyword
is
required
and
should
not
be
modified.
v
The
LANG
keyword
is
used
to
specify
which
languages
to
remove
from
the
DB2
UDB
product
installation
image.
To
remove
the
.cab
files
for
a
language,
as
well
as
the
doc
files
in
the
installation
image
for
this
language,
uncomment
the
equivalent
LANG
keyword.
v
The
COMP
keyword
represents
which
features
to
remove
from
the
DB2
UDB
product
installation
image.
To
remove
the
.cab
files
for
a
feature,
simply
uncomment
the
equivalent
COMP
keyword.
You
can
uncomment
several
COMP
or
LANG
keywords
in
the
same
input
file
to
remove
several
features
or
languages.
The
db2iprune
input
file
behaves
differently
from
the
DB2
UDB
product
response
files
(used
for
unattended
installations).
The
DB2
UDB
product
response
file
is
used
to
specify
components
that
you
want
to
install,
while
the
db2iprune
input
file
is
used
to
specify
components
that
you
want
removed
from
the
image
and
hence
cannot
be
installed.
2.
From
the
command
line,
execute
the
db2iprune.exe
file
using
the
following
syntax:
db2iprune.exe
-r
-p
-o
where:
12
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
v
the
parameter
following
the
-r
switch
determines
the
full
path
to
the
db2iprune
input
file.
v
the
parameter
following
the
-p
switch
determines
the
full
path
to
the
root
directory
of
the
source
installation
image.
This
directory
contains
the
setup.exe
file,
and
is
also
the
root
directory
of
the
DB2
UDB
product
installation
CD.
v
the
parameter
following
the
-o
switch
determines
the
full
path
to
the
location
where
the
new
DB2
UDB
pruned
product
image
is
copied.
Make
sure
that
you
have
write
access
to
this
directory.
For
example,
consider
the
following
features
selection
panel
from
an
unpruned
DB2
UDB
Run-time
Client
Version
8.2
installation
image
using
the
Custom
installation
option:
Next,
consider
the
following
changes
made
to
the
db2rtcl.prn
input
file
for
this
installation
image.
In
this
input
file
the
following
LANG
features
are
commented
out
and
will
be
installed,
whereas
the
COMP
features
are
uncommented
and
will
not
be
installed:
v
Languages
commented:
–
CN
(Chinese)
–
FR
(French)
–
ES
(Spanish)
–
JP
(Japanese)v
Components
uncommented:
–
SYSTEM_BIND_FILES
(System
Bind
Files
are
used
by
DB2
UDB
for
such
things
as
database
creation
and
accessing
remote
host
databases)
–
LDAP_EXPLOITATION
(Lightweight
Directory
Access
Protocol
(LDAP)
Exploitation
allows
DB2
UDB
to
use
an
LDAP
directory
to
store
database
directory
and
configuration
information)
Chapter
4.
Reducing
the
size
of
the
DB2
UDB
product
installation
image
13
-
–
NETBIOS_DB2_CLIENT_SUPPORT
(NetBIOS
allows
you
to
use
the
NetBIOS
communication
protocol
to
transfer
data
in
a
computer
environment
that
contains
clients
and
servers)
–
NPIPE_DB2_CLIENT_SUPPORT
(Named
Pipes
allows
you
to
use
the
Named
Pipes
communication
protocol
to
transfer
data
in
a
computer
environment
that
contains
clients
and
servers)
–
APPC_DB2_CLIENT_SUPPORT
(APPC
allows
you
to
use
the
APPC
communication
protocol
to
transfer
data
in
a
computer
environment
that
contains
clients
and
servers)*
Sample
input
file
for
use
with
the
db2iprune.exe
utility
*
------------------------------------------------------------
*
*
Comments
are
made
by
placing
either
a
*
or
a
#
at
the
start
of
a
line,
or
by
*
placing
**
or
##
after
the
start
of
a
line
to
comment
out
the
rest
of
that
*
line.
*
*
To
remove
the
.cab
files
for
a
feature,
uncomment
the
equivalent
COMP
keyword,
*
to
remove
the
.cab
files
for
a
language,
as
well
as
the
doc
files
in
the
image
*
for
this
language,
uncomment
the
equivalent
LANG
keyword.
*
The
PROD
keyword
is
required
to
identify
the
product
and
does
not
change
*===============================================================
PROD
=
RUNTIME_CLIENT
LANG
=
AR
LANG
=
BG
LANG
=
BR
*LANG
=
CN
LANG
=
CZ
LANG
=
DE
LANG
=
DK
LANG
=
FI
*LANG
=
FR
LANG
=
EL
*LANG
=
ES
LANG
=
HR
LANG
=
HU
LANG
=
IW
LANG
=
IT
*LANG
=
JP
LANG
=
KR
LANG
=
NL
LANG
=
NO
LANG
=
PL
LANG
=
PT
LANG
=
RO
LANG
=
RU
LANG
=
SE
LANG
=
SL
LANG
=
SK
LANG
=
TR
LANG
=
TW
COMP
=
SYSTEM_BIND_FILES
*COMP
=
MDAC
*COMP
=
ODBC_SUPPORT
*COMP
=
OLE_DB_SUPPORT
*COMP
=
JDBC_SUPPORT
*COMP
=
SQLJ_SUPPORT
COMP
=
LDAP_EXPLOITATION
*COMP
=
CLIENT_TOOLS
*COMP
=
TCPIP_DB2_CLIENT_SUPPORT
COMP
=
NETBIOS_DB2_CLIENT_SUPPORT
COMP
=
NPIPE_DB2_CLIENT_SUPPORT
COMP
=
APPC_DB2_CLIENT_SUPPORT
*COMP
=
COMMAND_CENTER
14
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
To
prune
the
DB2
UDB
Run-time
Client
installation
image
based
on
these
changes
to
the
db2rtcl.prn
input
file,
enter
the
following
command
at
the
command
prompt:
db2iprune.exe
-r
c:\db2rtcl.prn
-p
d:\RTCL\image
-o
d:\compact_rtcl
where:
v
the
db2iprune.exe
file
is
located
in
the
C:\
directory
v
the
input
file
(db2rtcl.prn)
is
located
in
the
C:\
directory
v
the
DB2
UDB
product
setup.exe
file
is
located
in
the
d:\RTCL\image\
directory
v
the
DB2
UDB
Run-time
Client
image
will
be
copied
to
the
d:\compact_rtcl
directory
You
should
receive
the
following
output
in
your
command
window:
Based
upon
these
changes,
when
you
install
the
new
pruned
installation
image
using
the
Custom
installation
option,
you
should
see
the
following
changes
to
the
features
selection
panel
for
the
DB2
UDB
Run-Time
Client
(notice
the
Chapter
4.
Reducing
the
size
of
the
DB2
UDB
product
installation
image
15
-
footprint
change
from
6121
KB
to
5057
KB):
3.
Use
any
of
the
regular
installation
methods
to
install
and
maintain
the
pruned
DB2
UDB
product
installation
image:
v
DB2
Setup
wizard
installation:
–
For
a
TYPICAL
installation,
the
regular
TYPICAL
components
for
that
product
are
installed
(minus
the
components
removed
by
the
db2iprune
utility).
–
For
a
COMPACT
installation,
the
regular
COMPACT
components
for
that
product
are
installed
(minus
the
components
removed
by
the
db2iprune
utility).
–
For
a
CUSTOM
installation,
only
the
remaining
components
are
displayed
in
the
feature
selection
panel.
The
components
removed
by
the
db2iprune
utility
are
not
displayed
as
options
to
install.
However,
the
removed
languages
will
still
be
displayed
in
the
language
selection
panel.
Therefore,
ensure
that
you
do
not
select
a
language
that
you
have
removed
from
the
image
using
the
db2iprune
utility.
If
you
select
a
language
that
you
have
removed,
you
will
receive
an
error
message.v
Response
file
installation:
–
If
you
specify
INSTALL_TYPE=TYPICAL
in
the
response
file,
all
the
typical
components
that
are
included
in
the
pruned
installation
image
are
installed.
–
If
you
specify
INSTALL_TYPE=COMPACT
in
the
response
file,
the
result
is
the
same
as
if
you
had
installed
from
a
compact
installation
image,
minus
the
pruned
features.
–
If
you
specify
INSTALL_TYPE=CUSTOM
in
the
response
file,
only
the
components
that
are
both
in
the
pruned
installation
image
and
specified
in
the
response
file
will
be
installed.
If
the
response
file
specifies
components
that
are
not
included
in
the
pruned
installation
image,
those
components
will
be
ignored.
16
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
–
If
you
plan
to
use
a
response
file
for
an
unattended
installation,
ensure
that
you
specify
only
the
languages
and
features
available
in
the
DB2
UDB
pruned
product
installation
image.v
FixPak
installation:
–
Since
DB2
UDB
product
FixPaks
for
Windows
operating
systems
are
full
installation
images,
the
db2iprune
utility
can
be
used
with
FixPak
images
as
well.
The
FixPak
application
process
is
the
same
for
full
and
pruned
images.
When
the
DB2
UDB
product
FixPak
is
installed
it
detects
and
updates
only
the
components
that
were
installed
using
the
db2iprune
utility
and
ignores
any
components
that
are
not
installed.
Note:
If
the
db2iprune
utility
is
used
with
a
DB2
UDB
product
FixPak
image,
ensure
that
the
FixPak
image
contains
all
of
the
components
that
were
initially
installed.
If
the
FixPak
image
does
not
contain
all
the
installed
components,
you
will
receive
an
error
about
missing
.cab
files
when
the
FixPak
application
is
attempted.
Chapter
4.
Reducing
the
size
of
the
DB2
UDB
product
installation
image
17
-
18
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
Chapter
5.
Deployment
of
DB2
UDB
products
You
can
use
the
following
three
methods
to
deploy
DB2
UDB
on
Windows
operating
systems:
v
Deploying
DB2
UDB
products
by
running
the
unattended
silent
installation
v
Deploying
DB2
UDB
products
using
Microsoft
Systems
Management
Server
(SMS)
2003
v
Deploying
DB2
UDB
products
using
Tivoli
Software
Distribution
4.2
Deploying
DB2
UDB
products
by
performing
the
unattended
silent
installation
Although
the
DB2
Setup
wizard
is
a
Windows
Installer
based
installation,
a
launcher
executable
(setup.exe)
file
is
provided
to
make
the
command
line
parameters
easier
to
use.
During
an
unattended
silent
installation
this
executable
file
calls
the
Windows
Installer
with
the
proper
command
line
parameters
and
properties
that
the
Windows
Installer
needs
to
perform
the
installation.
Procedure:
To
perform
an
unattended
silent
installation
of
DB2
UDB
using
the
setup.exe
file:
1.
Enter
the
following
command
at
the
command
prompt:
setup.exe
—u
Here
is
a
complete
list
of
the
valid
command
line
syntax
and
parameters
for
the
setup
command:
Command
syntax:
��
setup
-f
-i
language
-l
log_file
-t
trace_file
�
�
-u
response_file
-w
-?
-h
��
Command
parameters:
-f
Forces
any
DB2
processes
to
stop
before
installing.
-i
language
Two-letter
language
code
of
the
language
in
which
to
perform
the
installation.
-l
log_file
Full
path
and
file
name
of
the
log
file
to
use.
-t
trace_file
Generates
a
file
with
install
trace
information.
-u
response_file
Full
path
and
file
name
of
the
response
file
to
use.
-w
Keeps
the
parent
process
alive
until
the
installation
finishes.
19
-
-?,
-h
Generates
usage
information.
For
example
The
following
command
will
run
a
silent
unattended
installation
with
the
log
being
written
to
the
C:\db2logs
directory:
setup.exe
–u
\\server\share\db2ese.rsp
-l
c:\db2logs\db2.log
As
mentioned
previously,
for
an
unattended
silent
installation
the
important
parameter
is
–u
[response_file].
This
parameter
is
used
to
run
the
installation
in
unattended
mode.
Along
with
the
–u
option,
you
must
provide
the
full
path
to
the
response
file
that
the
DB2
Setup
wizard
will
use
to
install
and
configure
the
computer.
For
more
information
on
the
response
file
please
see
the
section
called
″DB2
UDB
product
response
files″
in
this
paper.
DB2
UDB
Version
8.2
products
do
not
require
the
–w
parameter.
However
if
you
have
an
earlier
version
of
the
product
installed
you
must
provide
the
–w
parameter
to
keep
setup.exe
from
exiting
before
the
installation
has
finished.
If
you
do
not
do
this,
the
exit
code
that
is
returned
by
setup.exe
will
not
tell
you
whether
the
installation
has
completed
successfully
or
not
because
the
value
is
returned
before
the
installation
has
finished.
You
can
choose
to
write
the
installation
logs
to
an
alternative
location.
You
can
do
this
by
specifying
the
–l
parameter
to
setup.exe
with
the
full
path
to
the
file
where
logging
information
will
be
written
to.
Depending
on
your
requirements
for
total
installation
time,
you
may
also
want
to
specify
the
–t
parameter.
This
option
creates
a
trace
file,
and
also
causes
more
details
to
appear
in
the
log
file.
These
files
allow
you
to
diagnose
almost
any
problem
without
having
to
go
through
the
effort
of
reproducing
the
problem.
For
more
information
on
diagnosing
installation
problems
refer
to
the
scetion
on
Diagnosing
problems
with
distributed
installations
in
this
paper.
Deploying
DB2
UDB
products
using
Microsoft
Systems
Management
Server
(SMS)
2003
With
Microsoft
Systems
Management
Server
(SMS),
you
can
set
up
the
installation
of
DB2
UDB
from
a
central
location,
and
install
it
in
an
efficient
and
reliable
manner
across
a
computer
network.
SMS
provides
tools
that
automate
deployment
tasks,
thereby
reducing
the
amount
of
work
that
users
have
to
perform.
This
installation
method
is
suitable
for
a
mass
deployment
of
DB2
UDB
on
a
large
number
of
client
computers
that
are
all
based
on
the
same
setup.
Use
the
following
instructions
to
package
and
distribute
DB2
UDB
across
your
computer
network
using
SMS:
v
Packaging
DB2
UDB
using
SMS
v
Distributing
DB2
UDB
using
SMS
Once
DB2
UDB
has
been
distributed
using
SMS,
it
will
automatically
be
installed
on
the
clients
on
your
computer
network.
Packaging
DB2
UDB
using
SMS
Prerequisites:
v
You
must
have
Microsoft
SQL
Server
2000
installed
on
the
server
that
functions
as
the
SMS
primary
site.
20
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
v
You
must
have
SMS
2003
installed
and
configured
on
your
network
for
both
your
SMS
2003
server
and
your
SMS
2003
client
workstations.
Refer
to
Microsoft’s
Systems
Management
Server
Concepts,
Planning,
and
Deployment
Guide
and
Microsoft’s
Systems
Management
Server
Operations
Guide
at
http://www.microsoft.com/technet/downloads/sms.mspx
for
details
on:
–
SMS
2003
platform
and
prerequisite
information
–
Setting
up
SMS
(including
setting
up
the
primary
and
the
secondary
sites)
–
Adding
clients
to
the
SMS
2003
system
Procedure:
To
package
DB2
UDB
using
SMS:
1.
Copy
the
DB2
UDB
Version
8.2
product
installation
image
to
a
location
where
its
contents
can
be
edited.
2.
Create
a
DB2
response
file.
Refer
to
the
section
″DB2
UDB
product
response
files″
in
this
paper
for
instructions
on
how
to
create
one.
3.
On
an
SMS
2003
distribution
point
server
in
your
SMS
2003
environment,
open
the
SMS
Administrator
Console
by
selecting
Programs—>Systems
Management
Server—>SMS
Administrator
Console
from
the
Start
menu.
4.
On
the
SMS
Administrator
Console,
open
the
Site
Database
object
tree
and
right-click
Packages.
Select
New—>Package
From
Definition:
Chapter
5.
Deployment
of
DB2
UDB
products
21
-
5.
When
the
Welcome
to
the
Create
Package
from
Definition
Wizard
opens,
click
Next:
6.
When
the
Package
Definition
page
opens,
click
Browse
to
search
for
the
DB2
package
definition
file:
7.
Select
the
desired
db2*.pdf
file
from
the
list
shown
in
the
Browse
window.
By
default
this
file
is
located
in
the
db2\Windows\samples\
directory
of
the
DB2
22
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
UDB
installation
image.
Click
Open:
8.
The
Package
Definition
page
reopens,
continuing
the
package
definition
of
the
DB2
UDB
product
you
want
to
distribute.
Click
Next
to
continue
the
distribution:
Chapter
5.
Deployment
of
DB2
UDB
products
23
-
9.
In
the
Source
Files
window,
select
the
Create
a
compressed
version
of
the
source
radio
button.
Click
Next:
10.
In
the
Source
Directory
window,
select
the
Source
directory
location
and
the
Source
directory
of
the
DB2
package.
Select
the
appropriate
Source
directory
location
radio
button
to
specify
whether
the
source
files
are
accessed
from
a
local
drive
or
from
a
remote
network
drive.
In
the
Source
directory
field,
type
the
directory
name
where
the
DB2
UDB
product
installation
image
resides.
This
is
the
directory
containing
the
setup.exe
file.
Click
Next:
24
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
11.
To
finish
the
creation
of
your
SMS
package,
click
Finish
on
the
Completing
the
Create
Package
from
Definition
Wizard
page:
Distributing
DB2
UDB
using
SMS
Prerequisites:
v
You
must
have
Microsoft
SQL
Server
2000
installed
on
the
server
that
functions
as
the
SMS
primary
site.
v
You
must
have
SMS
2003
installed
and
configured
on
your
network
for
both
your
SMS
2003
server
and
your
SMS
2003
client
workstations.
Refer
to
Microsoft’s
Systems
Management
Server
Concepts,
Planning,
and
Deployment
Guide
and
Microsoft’s
Systems
Management
Server
Operations
Guide
at
http://www.microsoft.com/technet/downloads/sms.mspx
for
details
on:
–
SMS
2003
platform
and
prerequisite
information
–
Setting
up
SMS
(including
setting
up
the
primary
and
the
secondary
sites)
–
Adding
clients
to
the
SMS
2003
system
Procedure:
To
distribute
DB2
UDB
using
SMS:
1.
After
the
package
creation
has
finished,
on
the
SMS
Administrator
Console,
open
the
Site
Database
object
tree
and
right-click
Packages.
Select
All
Chapter
5.
Deployment
of
DB2
UDB
products
25
-
Tasks—>Distribute
Software.
2.
When
the
Welcome
to
the
Distribute
Software
Wizard
page
opens,
click
Next:
26
Mass
deployment
of
DB2
Universal
Database
Version
8.2
on
Microsoft
Windows
operating
systems
-
3.
In
the
Package
page,
select
the
Select
an
existing
package
radio
button
and
select
the
package
you
want
to
distribute.
Click
Next:
4.
When
the
Distribution
Points
page
opens,
select
the
distribution
points
for
the
package.
Click
Next:
Chapter
5.
Deployment
of
DB2
UDB
products
27
-
5.
In
the
Advertise
a
Program
page,
select
the
radio
button
indicating
that
you
want
to
adver
