IBM Tivoli Java Collector: Installation Guide
50
IBM Tivoli Java Collector Installation Guide Version 1.0 — November 2003 SC32-1488-00
Transcript of IBM Tivoli Java Collector: Installation Guide
IBM
Tivoli
Java
Collector
Installation
Guide
Version
1.0
—
November
2003
SC32-1488-00
���
IBM
Tivoli
Java
Collector
Installation
Guide
Version
1.0
—
November
2003
SC32-1488-00
���
Note
Before
using
this
information
and
the
product
it
supports,
read
the
information
in
“Notices,”
on
page
33.
Limited
Edition
(November
2003)
©
Copyright
International
Business
Machines
Corporation
2003.
All
rights
reserved.
US
Government
Users
Restricted
Rights
–
Use,
duplication
or
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corp.
Contents
Preface
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
Who
should
read
this
book
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
What
this
book
contains
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vi
IBM
Tivoli
Java
Collector
library
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vi
Related
publications
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vi
Accessing
publications
online
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vi
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Contacting
software
support
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Conventions
used
in
this
book
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Typeface
conventions
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Operating
system
differences
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Chapter
1.
Installation
overview
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 1
Supported
operating
systems
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 1
Software
prerequisites
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 2
Processor
and
memory
requirements
for
Server
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 2
Disk
and
Memory
Requirements
for
Client
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 3
Disk
and
Memory
Requirements
for
Administration
GUI
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 3
Chapter
2.
Installing
the
Tivoli
Java
Collector
server
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 5
Before
you
begin
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 5
Using
the
command
line
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 5
Before
you
begin
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 5
Installing
without
a
.toc
file
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 5
Installing
with
a
.toc
file
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 6
Installing
using
SMIT
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 6
Configuring
the
JAC
Server
(JAC
Server
setup)
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7
Chapter
3.
Installing
the
Tivoli
Java
Collector
client
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 11
Before
you
begin
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 11
Installing
the
JAC
Client
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 11
Chapter
4.
Installing
the
Tivoli
Java
Collector
JAC
Administration
GUI
.
.
.
.
.
.
.
. 19
Before
you
begin
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19
Installing
the
Administration
GUI
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19
Chapter
5.
Removing
the
JAC
Server,
JAC
Client,
or
Administration
GUI
.
.
.
.
.
.
. 25
Removing
the
JAC
Server
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 25
Removal
using
the
command
line
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 25
Removal
using
SMIT
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 25
Removing
the
JAC
Client
from
a
Windows
machine
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 26
Removing
the
JAC
Client
from
a
UNIX
machine
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 26
Removing
the
Administration
GUI
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 26
Chapter
6.
After
the
installation
has
completed
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 27
Chapter
7.
Troubleshooting
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 29
Installing
in
console
mode
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 29
Installing
with
an
alternate
temporary
directory
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 29
Files
left
in
temporary
directory
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 30
Chapter
8.
Silent
install
for
the
client
and
GUI
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 31
©
Copyright
IBM
Corp.
2003
iii
Appendix.
Notices
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 33
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 34
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 37
iv
IBM
Tivoli
Java
Collector:
Installation
Guide
Preface
The
IBM®
Tivoli®
Java
Collector
Installation
Guide
explains
how
to
install
and
configure
the
IBM
Tivoli
Java
Collector
software.
Tivoli
Java
Collector
is
a
data
collection
service
that
gathers
and
stores
a
wide
variety
of
information
from
multiple
participating
systems.
Information
types
can
include
any
data
on
a
system,
such
as
operating
system
versions,
software
patch
levels,
and
security-related
data.
System
and
security
administrators
can
use
the
Tivoli
Java
Collector
service
to
monitor
specific
data
checkpoints
on
any
given
machine
(or
group
of
machines).
This
limited
internal
implementation
of
Tivoli
Java
Collector
is
used
exclusively
as
a
security
audit
service
that
collects
only
security-related
data
and
produces
reports
that
reveal
adherence
to
or
violation
of
specific
system
security
policies.
Who
should
read
this
book
The
target
audience
for
this
installation
guide
includes:
v
Security
administrators
v
System
administrators
Readers
should
be
familiar
with:
v
TCP/IP
v
Relational
databases
v
Security
management,
including
authentication
and
authorization
v
If
you
are
enabling
CWA
authentication,
you
should
be
familiar
with
IBM
Bluepages
and
LDAP.
What
this
book
contains
This
document
contains
the
following
chapters:
v
Chapter
1,
“Installation
overview,”
on
page
1
describes
the
prerequisites
for
Tivoli
Java
Collector.
v
Chapter
2,
“Installing
the
Tivoli
Java
Collector
server,”
on
page
5
describes
how
to
install
and
configure
the
JAC
Server.
v
Chapter
3,
“Installing
the
Tivoli
Java
Collector
client,”
on
page
11
describes
how
to
install
the
client
software.
v
Chapter
4,
“Installing
the
Tivoli
Java
Collector
JAC
Administration
GUI,”
on
page
19
describes
how
to
install
the
JAC
Administration
GUI.
v
Chapter
5,
“Removing
the
JAC
Server,
JAC
Client,
or
Administration
GUI,”
on
page
25
describes
how
to
remove
the
JAC
Server,
the
JAC
Client,
and
the
JAC
Administration
GUI.
v
Chapter
6,
“After
the
installation
has
completed,”
on
page
27
describes
what
to
do
immediately
after
you
have
completed
the
installation.
v
Chapter
7,
“Troubleshooting,”
on
page
29
describes
solutions
for
problems
that
you
might
encounter
during
the
installation
or
configuration
of
Tivoli
Java
Collector.
©
Copyright
IBM
Corp.
2003
v
v
Chapter
8,
“Silent
install
for
the
client
and
GUI,”
on
page
31
describes
how
to
install
the
JAC
Client
and
the
JAC
Administration
GUI
in
silent
mode
using
a
response
file
to
provide
input.
Publications
Read
the
descriptions
of
the
IBM
Tivoli
Java
Collector
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.
IBM
Tivoli
Java
Collector
library
The
publications
in
the
IBM
Tivoli
Java
Collector
library
are:
v
IBM
Tivoli
Java
Collector
Installation
Guide
(SC32-1488-00)
Explains
how
to
install
and
configure
Tivoli
Java
Collector
software.
v
IBM
Tivoli
Java
Collector
User’s
Guide
(SC32-1487-00)
Explains
how
to
manage
and
configure
Tivoli
Java
Collector
services
using
the
JAC
Administration
GUI.
v
IBM
Tivoli
Java
Collector
Release
Notes
(GI11-4163-00)
Provides
late-breaking
information,
such
as
software
limitations,
workarounds,
and
documentation
updates.
Related
publications
This
section
lists
publications
related
to
the
Tivoli
Java
Collector
library.
The
Tivoli
Software
Library
provides
a
variety
of
Tivoli
publications
such
as
white
papers,
datasheets,
demonstrations,
redbooks,
and
announcement
letters.
The
Tivoli
Software
Library
is
available
on
the
Web
at:
http://www.ibm.com/software/tivoli/library/
The
Tivoli
Software
Glossary
includes
definitions
for
many
of
the
technical
terms
related
to
Tivoli
software.
The
Tivoli
Software
Glossary
is
available,
in
English
only,
from
the
Glossary
link
on
the
left
side
of
the
Tivoli
Software
Library
Web
page
http://www.ibm.com/software/tivoli/library/
IBM
DB2
Universal
Database
IBM
DB2®
Universal
Database™
is
required
when
using
Tivoli
Java
Collector.
Additional
information
about
DB2
can
be
found
at:
http://www.ibm.com/software/data/db2/
Accessing
publications
online
The
publications
for
this
product
are
available
online
in
Portable
Document
Format
(PDF)
or
Hypertext
Markup
Language
(HTML)
format,
or
both
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.
vi
IBM
Tivoli
Java
Collector:
Installation
Guide
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.
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
customer
support
Conventions
used
in
this
book
This
reference
uses
several
conventions
for
special
terms
and
actions
and
for
operating
system-dependent
commands
and
paths.
Typeface
conventions
The
following
typeface
conventions
are
used
in
this
reference:
Bold
Lowercase
commands
or
mixed
case
commands
that
are
difficult
to
distinguish
from
surrounding
text,
keywords,
parameters,
options,
names
of
Java
classes,
and
objects
are
in
bold.
Italic
Variables,
titles
of
publications,
and
special
words
or
phrases
that
are
emphasized
are
in
italic.
Monospace
Code
examples,
command
lines,
screen
output,
file
and
directory
names
that
are
difficult
to
distinguish
from
surrounding
text,
system
messages,
text
that
the
user
must
type,
and
values
for
arguments
or
command
options
are
in
monospace.
Operating
system
differences
This
book
uses
the
UNIX
convention
for
specifying
environment
variables
and
for
directory
notation.
When
using
the
Windows
command
line,
replace
$variable
with
%variable%
for
environment
variables
and
replace
each
forward
slash
(/)
with
a
backslash
(\)
in
directory
paths.
If
you
are
using
the
bash
shell
on
a
Windows
system,
you
can
use
the
UNIX
conventions.
Preface
vii
viii
IBM
Tivoli
Java
Collector:
Installation
Guide
Chapter
1.
Installation
overview
This
chapter
lists
the
supported
operating
systems,
prerequisites,
and
disk
and
memory
requirements
for
IBM
Tivoli
Java
Collector.
It
also
suggests
important
things
you
should
consider
before
you
begin
the
product
installation.
Supported
operating
systems
The
following
tables
list
the
supported
operating
systems
for
the
Tivoli
Java
Collector
Server
(JAC
Server),
Tivoli
Java
Collector
Client
(JAC
Client),
collectors
(JAC
collectors)
and
JAC
Administration
GUI.
Table
1.
Server
operating
systems
Operating
system
Level
Patch/maintenance
level
AIX
®
4.3.3
Fix
pack
10
or
higher
AIX
5.2
No
fix
pack
required
Table
2.
Clients
and
Collectors
Operating
system
Level
Patch/maintenance
level
AIX
4.3.3
Fix
pack
10
or
higher
AIX
5.2
Latest
cumulative
patches
HP-UX
11.0
Latest
cumulative
patches
Red
Hat
Linux
6.2
Latest
cumulative
patches
Red
Hat
Linux
7.3
Latest
cumulative
patches
Red
Hat
Linux
8.0
Latest
cumulative
patches
Sun
2.6
Latest
cumulative
patches
Sun
2.7
Latest
cumulative
patches
Sun
2.8
Latest
cumulative
patches
Windows
NT®
4.0
Server
Service
Pack
6
and
Security
Rollup
Package
Windows
NT
4.0
Workstation
Service
Pack
6
and
Security
Rollup
Package
Windows®
2000
Server
Service
Pack
3
and
Security
Rollup
Package
Windows
2000
Advanced
Server
Service
Pack
3
and
Security
Rollup
Package
Windows
2000
Server
with
Citrix
Metaframe
1.8
or
higher
Service
Pack
3
and
Security
Rollup
Package
Table
3.
JAC
Administration
GUI
operating
systems
Operating
system
Level
Patch/maintenance
level
Windows
NT
4.0
Server
Service
Pack
6
and
Security
Rollup
Package
Windows
NT
4.0
Workstation
Service
Pack
6
and
Security
Rollup
Package
©
Copyright
IBM
Corp.
2003
1
Table
3.
JAC
Administration
GUI
operating
systems
(continued)
Operating
system
Level
Patch/maintenance
level
Windows
2000
Server
Service
Pack
3
and
Security
Rollup
Package
Windows
2000
Professional
Service
Pack
3
and
Security
Rollup
Package
Windows
2000
Advanced
Server
Service
Pack
3
and
Security
Rollup
Package
Windows
XP
Professional
Service
Pack
1
Software
prerequisites
The
following
table
lists
the
software
prerequisites
for
the
JAC
Server.
Table
4.
Server
software
prerequisites
Operating
system
Requirements
Additional
Requirements
AIX
4.3.3
with
fix
pack
level
4.3.3.10
v
IBM
Java
Runtime
Environment
(JRE)
1.3.1.7
v
DB2
7.2
If
using
JRE:
xll.adt.lib
(4.3.3.10).
If
using
Java
Developer’s
Kit
(JDK):
v
xll.adt.lib
(4.3.3.10)
v
OpenGL.OpenGL_X.rte.base
(4.3.3.76
or
higher)
v
OpenGL.OpenGL_X.rte.soft
(4.3.3.75
or
higher)
AIX
5.2
v
IBM
Java
Runtime
Environment
(JRE)
1.3.1.7
v
DB2
7.2
none
The
following
table
lists
the
software
prerequisites
for
the
HP-UX
JAC
Client.
Table
5.
Client
software
prerequisites
Operating
system
Requirements
HP-UX
11.0
Java
Runtime
Environment
(JRE)
1.3.1
Processor
and
memory
requirements
for
Server
The
following
table
lists
the
processor
and
memory
requirements
for
the
JAC
Server.
Table
6.
Server
Processor
and
Memory
Requirements
Type
of
Tivoli
Java
Collector
Deployment
Processor
Memory
Requirements
Small
(1–500
clients)
1
256
MB
RAM
Medium
(501–2500
clients)
2
512
MB
RAM
Large
(2501–10,000
clients)
2–4
2–4
GB
RAM
You
need
5
MG
of
disk
space
to
install
the
JAC
Server
package.
2
IBM
Tivoli
Java
Collector:
Installation
Guide
Disk
and
Memory
Requirements
for
Client
The
following
table
lists
the
disk
and
memory
requirements
for
the
Tivoli
Java
Collector
Client.
Table
7.
Disk
and
Memory
Requirements
for
Tivoli
Java
Collector
Client
Client
Platform
Disk
Requirements
for
Installation
Directory
Disk
Requirements
for
Temporary
Directory
Memory
Requirements
AIX
35
MB
45
MB
35
MB
RAM
HP-UX
1
MB
6
MB
35
MB
RAM
Linux
36
MB
46
MB
35
MB
RAM
Solaris
55
MB
65
MB
35
MB
RAM
Windows
32
MB
44
MB
35
MB
RAM
Note:
The
HP-UX
platform
values
in
the
table
are
much
smaller
than
the
other
platform
values
because
the
Java
Runtime
Environment
is
not
packaged
with
the
HP-UX
Client.
Disk
and
Memory
Requirements
for
Administration
GUI
The
following
table
lists
the
disk
and
memory
requirements
for
the
JAC
Administration
GUI.
Table
8.
Disk
and
Memory
Requirements
for
JAC
Administration
GUI
Administration
GUI
Platform
Disk
Requirements
for
Installation
Directory
Disk
Requirements
for
Temporary
Directory
Memory
Requirements
Windows
32
MB
62
MB
35
MB
RAM
Chapter
1.
Installation
overview
3
4
IBM
Tivoli
Java
Collector:
Installation
Guide
Chapter
2.
Installing
the
Tivoli
Java
Collector
server
You
can
install
the
Tivoli
Java
Collector
Server
(JAC
Server)
on
the
AIX
operating
system
only.
You
can
use
the
command
line
or
you
can
use
the
System
Management
Interface
Tool
(SMIT).
Before
you
begin
Before
you
install
the
JAC
Server:
v
If
you
are
reinstalling
the
JAC
Server,
please
stop
the
JAC
Server
and
uninstall
it
before
you
attempt
to
reinstall
it.
See
Chapter
5,
“Removing
the
JAC
Server,
JAC
Client,
or
Administration
GUI,”
on
page
25
for
more
information.
v
The
JAC
Server
installs
in
/opt/IBM/JACserver.
This
must
not
be
on
the
root
file
system.
If
the
/opt
directory
is
located
in
the
root
file
system,
consider
one
of
the
following
options:
–
Create
a
separate
file
system
for
/opt
(the
optimum
solution).
–
Create
a
separate
file
system
for
/opt/IBM
or
/opt/IBM/JACserver
–
Create
a
symbolic
link
from
/opt
to
/usr/opt
–
Create
a
symbolic
link
from
/opt/IBM
or
/opt/IBM/JACserver
to
some
other
file
system
(perhaps
/usr/opt/IBM
or
/usr/opt/IBM/JACserver).
The
/opt
directory
is
often
a
part
of
the
root
file
system.
Causing
the
root
file
system
to
fill
up
may
impact
other
applications,
including
the
operating
system
itself.
Changing
the
mount
point
does
not
remove
the
possibility
of
filling
up
a
file
system
but
it
does
reduce
the
impact
to
other
applications
that
are
running
on
the
system.
It
localizes
a
file
system
problem
to
Tivoli
Java
Collector.
v
DB2
must
be
installed.
Consider
making
a
separate
file
system
for
the
DB2
database
that
is
to
be
used
by
the
JAC
Server.
This
may
be
necessary
if
the
JAC
Server
encounters
DB2
errors
indicating
that
there
is
not
enough
space
to
store
Tivoli
Java
Collector
data.
This
does
not
remove
the
possibility
of
filling
up
a
file
system
but
it
does
reduce
the
impact
to
other
applications
that
are
using
DB2
and
using
the
file
system
that
DB2
uses
by
default.
If
the
file
system
has
an
error,
it
will
be
easier
to
isolate
the
problem
to
Tivoli
Java
Collector.
v
You
need
to
know
the
DB2
instance
ID
and
password
v
You
must
be
logged
on
as
AIX
User
ID
root
Using
the
command
line
This
section
contains
instructions
on
how
to
install
the
JAC
Server
using
the
installp
command.
Before
you
begin
Because
you
will
be
installing
only
one
product
package,
you
can
use
installp
without
a
.toc
(table
of
contents)
file.
See
“Installing
without
a
.toc
file.”
Installing
without
a
.toc
file
To
install
the
JAC
Server
without
a
.toc
file,
run
the
following
command:
installp
-acXd
install_image_filename
jacsrv
©
Copyright
IBM
Corp.
2003
5
where:
v
-a
means
apply
v
-c
means
commit
v
-X
means
automatically
expand
file
systems
v
-d
is
the
installation
device
or
directory
v
install_image_filename
is
the
file
name
of
the
installation
image
file
rather
than
the
directory
containing
the
image.
v
jacsrv
is
the
name
of
the
product.
Installing
with
a
.toc
file
If
you
need
to
create
a
.toc
file,
after
copying
an
AIX
installation
image
to
a
directory,
use
the
following
command:
inutoc
directory
where
directory
is
the
directory
containing
the
installation
images.
To
install
the
JAC
Server
with
a
.toc
file,
run
the
following
command:
installp
-acXd
directory
jacsrv
where:
v
-a
means
apply
v
-c
means
commit
v
-X
means
automatically
expand
file
systems
v
-d
is
the
installation
device
or
directory
v
directory
is
the
directory
containing
the
installation
image
and
where
there
is
a
.toc
file
in
the
directory
v
jacsrv
is
the
name
of
the
product
Installing
using
SMIT
To
install
the
JAC
Server
using
SMIT:
1.
On
the
command
line,
type
smit.
The
System
Management
panel
opens
and
presents
you
with
a
list
of
selections.
2.
Select
Software
Installation
and
Maintenance.
The
Software
Installation
and
Maintenance
panel
opens
and
asks
you
to
make
a
selection.
3.
Select
Install
and
Update
Software.
The
Install
and
Update
Software
panel
opens
and
asks
you
to
make
a
selection.
4.
Select
Install
Software.
A
panel
opens
and
prompts
you
for
the
directory
where
you
downloaded
the
server
code.
5.
Provide
a
directory
name
and
press
OK.
The
Install
Software
panel
opens.
6.
Press
List
next
to
the
SOFTWARE
to
install
item.
A
Multi-select
list
opens.
6
IBM
Tivoli
Java
Collector:
Installation
Guide
7.
Select
jacsrv
from
the
multi-select
list
by
highlighting
it.
Press
OK.
The
Install
Software
panel
reopens.
8.
Review
all
of
the
other
options
on
the
panel
before
you
press
OK.
An
Are
You
Sure?
panel
opens
and
you
are
asked
to
confirm
the
installation.
9.
Press
OK
to
install
the
server
code.
A
panel
opens
with
output.
10.
Review
the
output
to
ensure
the
installation
ran
correctly.
If
the
installation
did
not
run
correctly,
you
will
see
an
error
message.
Contact
IBM
Customer
Support.
11.
Press
Done.
The
Software
Install
panel
reopens.
12.
Press
Cancel.
13.
You
may
now
exit
SMIT.
Configuring
the
JAC
Server
(JAC
Server
setup)
During
the
configuration
or
setup
of
the
JAC
Server,
many
of
the
steps
present
you
with
a
default
choice
in
brackets.
If
you
want
to
accept
the
default,
press
Enter
at
each
step.
To
configure
or
setup
the
JAC
Server
from
the
command
line:
1.
cd
/opt/IBM/JACserver
and
press
Enter.
2.
Type
./jacsetup
and
press
Enter.
3.
The
JAC
server
connection
port
[1955]:
prompt
displays.
Press
Enter
for
the
default
port
or
type
the
desired
port
number.
4.
The
JAC
client
connection
port
[1950]:
prompt
displays.
Press
Enter
for
the
default
port
or
type
the
desired
port
number.
5.
The
sendmail
host
[localhost]:
prompt
displays.
The
localhost
is
the
host
you
are
running
on
and
is
the
default.
Press
Enter
for
the
default
or
type
the
IP
address
of
the
sendmail
(SMTP)
server.
6.
The
address
of
JAC
server
[default
address]:
prompt
displays.
Press
Enter
for
the
default
or
type
the
address
desired
for
the
JAC
Server.
(This
is
the
From
field
that
will
be
filled
in
when
someone
receives
from
the
JAC
Server).
7.
The
User
authenticator
IBM
Intranet
password?
(y/n)
prompt
displays.
You
are
asked
if
you
want
to
use
the
IBM
Intranet
password,
also
know
as
the
Common
Web
Access
(CWA)
password,
for
user
authentication.
If
yes,
go
to
step
7a.
If
not,
go
to
step
7b.
a.
Type
y
if
you
would
like
users
to
log
in
to
the
JAC
Server
from
the
JAC
Administration
GUI
using
their
intranet
ID
and
password.
Now
go
to
step
9
on
page
8.
b.
Type
n
if
you
want
the
JAC
Server
to
manage
its
own
authentication.
Continue
with
the
next
step.
8.
You
are
asked
for
the
default
JAC
Administrator
ID.
This
is
the
initial
administrator
for
the
Tivoli
Java
Collector
environment,
for
example:
admin.
a.
Type
the
default
JAC
Administrator
ID.
You
are
asked
for
the
default
JAC
Administrator
password.
b.
Type
the
default
JAC
Administrator
password.
(There
is
no
default).
Chapter
2.
Installing
the
Tivoli
Java
Collector
server
7
c.
You
are
asked
to
confirm
the
password
by
retyping
it.
Go
to
step
10.
9.
You
are
asked
for
the
host
for
the
Intranet
server.
Press
Enter
to
accept
the
default
or
type
the
host.
a.
You
are
asked
for
the
Intranet
domain.
Press
Enter
to
accept
the
default
or
type
the
Intranet
domain.
b.
You
are
asked
for
the
default
JAC
administrator
ID.
This
is
the
initial
administrator
for
the
Tivoli
Java
Collector
environment.
Because
you
are
using
CWA,
it
must
be
in
the
form
of
an
address,
for
example:
Type
the
default
JAC
Administrator
ID.10.
You
are
asked
for
the
DB2
instance
ID.
Press
Enter
to
accept
the
default
or
type
the
DB2
instance
ID.
11.
You
are
asked
for
the
DB2
instance
ID
password.
Type
the
DB2
instance
ID
password.
There
is
no
default.
12.
You
are
asked
to
confirm
the
DB2
ID
password
by
retyping
it.
13.
You
are
asked
to
provide
the
database
location.
Press
Enter
to
accept
the
default
or
provide
a
fully-qualified
path
to
the
desired
location.
14.
You
are
asked
for
the
system
name
for
certificates.
Every
digital
certificate
has
an
attribute
called
the
distinguished
name,
(DN).
The
DN
identifies
who
the
certificate
was
issued
to.
The
system
name
is
used
to
provide
a
command
identifier
which
is
used
to
create
the
DN’s
for
all
the
generated
certificates
and
keys.
Press
Enter
to
accept
the
default
or
type
the
system
name.
15.
You
are
asked
for
a
master
keystore
password.
The
authorization
key
is
signed
by
the
master
key.
The
server
is
configured
to
require
the
authorization
key
be
signed
by
the
master
key.
Type
a
master
keystore
password
of
your
choice.
There
is
no
default.
16.
You
are
asked
to
confirm
the
master
keystore
password
by
retyping
it.
17.
You
are
asked
for
an
authorization
keystore
password.
Both
of
the
server’s
keys
are
signed
by
the
authorization
key.
The
authorization
key’s
signature
is
used
to
prevent
the
server
administrator
from
creating
a
new
set
of
keys
without
the
permission
of
whoever
holds
the
authorization
keystore
password.
Additionally,
the
authorization
key
is
used
to
sign
collectors
before
they
are
registered.
JAC
Server’s
are
configured
to
allow
only
those
collectors,
which
have
been
signed
by
a
valid
authorization
key,
to
be
registered.
Administrators
are
thus
able
to
run
only
those
collectors
approved
by
the
holder
of
the
authorization
keystore
password.
The
holder
of
the
authorization
keystore
password
can
authorize
collectors
by
using
the
authorization
tool.
See
the
IBM
Tivoli
Java
Collector
User’s
Guide
for
more
information
about
the
authorization
tool.
Type
an
authorization
keystore
password
of
your
choice.
There
is
no
default.
Note:
Remember
this
authorization
keystore
password.
You
will
need
it
when
working
with
the
authorization
tool.
See
the
IBM
Tivoli
Java
Collector
User’s
Guide
for
more
information
about
the
authorization
tool.
18.
You
are
asked
to
confirm
the
authorization
keystore
password
by
retyping
it.
8
IBM
Tivoli
Java
Collector:
Installation
Guide
19.
You
are
asked
for
the
server
keystore
password.
The
server
keystore
password
is
used
to
protect
the
JAC
Server’s
keys.
The
server
has
two
keys:
an
SSL
key
and
a
loading
key.
The
SSL
key
is
used
to
enable
the
SSL
connections
that
the
server
offers.
The
loading
key
is
used
to
sign
each
collector
as
it
is
loaded.
This
signature
is
performed
so
that
a
client
can
verify
that
the
collector
it
received
was
actually
sent
by
the
server
and
not
simply
extracted
from
the
hard
drive.
Type
the
server
keystore
password.
There
is
no
default.
20.
You
are
asked
to
confirm
the
server
keystore
password
by
retyping
it.
Your
current
settings
are
displayed.
21.
A
summary
screen
opens.
You
are
asked
whether
you
want
to
accept
these
settings
and
erase
any
existing
JAC
database?
Type
y
to
accept
the
settings
or
n
if
you
do
not
want
to
accept
the
settings.
22.
The
Start
the
JAC
server
now?
(y/n):
prompt
displays.
Type
y
to
start
the
JAC
Server
or
n
to
exit.
Note:
The
installation
will
update
the
init
tab
file
so
that
the
server
starts
if
you
reboot
the
machine.
23.
To
start
the
server
manually,
type
/opt/IBM/JACserver/jacserver
start.
Chapter
2.
Installing
the
Tivoli
Java
Collector
server
9
10
IBM
Tivoli
Java
Collector:
Installation
Guide
Chapter
3.
Installing
the
Tivoli
Java
Collector
client
This
chapter
describes
how
to
install
the
Tivoli
Java
Collector
Client
(JAC
Client).
Before
you
begin
If
you
are
reinstalling
the
JAC
Client,
please
stop
the
JAC
Client
and
uninstall
it
before
you
attempt
to
reinstall
it.
See
Chapter
5,
“Removing
the
JAC
Server,
JAC
Client,
or
Administration
GUI,”
on
page
25
for
more
information.
There
are
two
files
used
in
the
installation
of
the
JAC
Client:
1.
Jar
file
-jacclient.jar
2.
Launcher
executable
file
(platform-specific)
v
jacclient_aix.bin
v
jacclient_hpux.bin
v
jacclient_linux.bin
v
jacclient_solaris.bin
v
jacclient_win32.exe
Before
you
perform
the
installation,
ensure
that
the
launcher
executable
file
and
the
jar
file
are
in
the
same
directory.
Notes:
1.
On
Windows
operating
systems
using
NTFS,
access
controls
for
files
and
directories
are
inherited
from
the
parent
directory.
It
may
be
desirable
to
create
the
installation
directory
and
explicitly
set
its
folder
permissions
prior
to
installing
the
JAC
Client.
2.
On
UNIX/Linux
operating
systems,
the
JAC
Client
installation
attempts
to
set
the
default
installation
directory
to
a
non-root
file
system.
If
it
does
not
find
a
non-root
file
system
among
the
set
of
directories
that
it
searches,
a
warning
message
will
be
displayed.
Installing
the
JAC
Client
To
install
the
JAC
Client:
1.
Type
jacclient_platform,
where
platform
is
replaced
by
one
of
the
following:
aix.bin,
hpux.bin,
linux.bin,
solaris.bin,
win32.
©
Copyright
IBM
Corp.
2003
11
The
Welcome
to
the
InstallShield®Wizard
for
JAC
Client
screen
opens.
2.
To
continue
the
installation,
click
Next.
A
license
screen
opens.
You
are
asked
to
accept
the
terms
of
the
license
agreement.
Figure
1.
Welcome
to
the
InstallShield
Wizard
for
JAC
Client
screen
12
IBM
Tivoli
Java
Collector:
Installation
Guide
Accept
the
terms
if
you
want
to
continue
with
the
installation.
3.
Click
Next.
A
screen
opens
that
allows
you
to
choose
the
directory
for
the
client
installation.
Figure
2.
License
Agreement
screen
Chapter
3.
Installing
the
Tivoli
Java
Collector
client
13
4.
Click
Next
to
accept
the
directory
given
or
click
Browse
to
install
the
JAC
Client
in
a
different
directory.
A
screen
opens,
which
asks
you
JAC
Client
configuration
questions.
Figure
3.
Choose
directory
for
Client
installation
14
IBM
Tivoli
Java
Collector:
Installation
Guide
Select
the
type
of
client:
v
Push
v
Pull
Note:
The
pull
client
is
useful
when
the
JAC
Server
is
behind
a
firewall
and
the
client
is
in
front
of
the
firewall.
Otherwise,
the
push
client
is
a
more
efficient
choice.
If
you
chose
the
pull
option,
go
to
step
6
on
page
16.
5.
If
you
chose
the
push
option,
click
Next.
A
screen
opens,
which
asks
you
further
configuration
questions.
Figure
4.
Configure
the
JAC
Client
screen
Chapter
3.
Installing
the
Tivoli
Java
Collector
client
15
Enter
the
JAC
Server
host
name
and
the
JAC
Server
connection
port.
6.
Click
Next.
A
summary
screen
opens
with
your
chosen
installation
location
and
the
size
of
the
client.
Figure
5.
Configure
the
JAC
Client
screen,
continued
16
IBM
Tivoli
Java
Collector:
Installation
Guide
7.
Click
Next.
A
status
screen
opens
showing
the
progress
of
the
installation.
A
final
screen
appears
indicating
successful
installation
of
the
JAC
Client.
Figure
6.
Installation
location
screen
Chapter
3.
Installing
the
Tivoli
Java
Collector
client
17
8.
Click
Finish
to
exit
the
wizard.
Figure
7.
Installation
success
screen
18
IBM
Tivoli
Java
Collector:
Installation
Guide
Chapter
4.
Installing
the
Tivoli
Java
Collector
JAC
Administration
GUI
This
chapter
provides
instructions
on
how
to
install
the
Tivoli
Java
Collector
JAC
Administration
GUI.
Before
you
begin
If
you
are
reinstalling
the
JAC
Administration
GUI,
please
stop
the
JAC
Administration
GUI
and
uninstall
it
before
you
attempt
to
reinstall
it.
See
Chapter
5,
“Removing
the
JAC
Server,
JAC
Client,
or
Administration
GUI,”
on
page
25
for
more
information.
There
are
two
files
used
in
the
installation
of
the
JAC
Administration
GUI:
1.
Jar
file
-
jacadmin.jar
2.
Launcher
executable
file
-
jacadmin_win32.exe
Before
you
perform
the
installation,
ensure
that
the
launcher
executable
file
and
the
jar
file
are
in
the
same
directory.
Installing
the
Administration
GUI
To
install
the
JAC
Administration
GUI:
1.
Double-click
jacadmin_win32.
The
JACGUI
-
InstallShield
Wizard
opens.
The
InstallShield
Wizard
will
extract
the
files
needed
to
install
the
JAC
Administration
GUI
on
your
computer.
2.
The
Welcome
to
the
InstallShield
Wizard
for
JAC
Administration
GUI
screen
opens.
Figure
8.
Extracting
Files
screen
©
Copyright
IBM
Corp.
2003
19
3.
Click
Next
to
continue.
A
License
Agreement
screen
opens.
Figure
9.
Welcome
to
the
InstallShield
Wizard
for
JAC
Administration
GUI
screen
20
IBM
Tivoli
Java
Collector:
Installation
Guide
You
are
asked
to
accept
the
license
agreement.
If
you
choose
not
to
accept
the
license
agreement,
you
will
not
be
able
to
install
the
JAC
Administration
GUI.
4.
Click
Next
to
accept
the
license
agreement.
A
screen
opens
that
allows
you
to
choose
your
destination
directory
for
the
files
to
be
installed.
Figure
10.
License
Agreement
screen
Chapter
4.
Installing
the
Tivoli
Java
Collector
JAC
Administration
GUI
21
You
are
asked
to
either
accept
the
destination
directory
indicated
or
click
Browse
to
choose
another
directory.
5.
After
you
choose
a
destination
directory,
click
Next.
Note:
The
InstallShield
program
performs
some
checks
before
displaying
the
directory
confirmation
screen.
On
some
of
the
older
systems,
this
might
take
a
minute
or
more.
You
will
not
get
any
feedback
while
this
is
happening
so
remain
patient.
If
you
click
the
Next
button
a
second
time,
an
hourglass
is
displayed
while
the
checks
are
taking
place.
This
will
not
harm
the
installation.
A
directory
confirmation
screen
opens.
Figure
11.
Choose
Destination
Directory
screen
22
IBM
Tivoli
Java
Collector:
Installation
Guide
6.
Click
Next.
The
Setup
Status
screen
opens
for
a
few
seconds
7.
The
Setup
Status
screen
closes.
A
screen
opens
indicating
the
installation
was
successful.
Figure
12.
Directory
Confirmation
screen
Chapter
4.
Installing
the
Tivoli
Java
Collector
JAC
Administration
GUI
23
Click
Finish
to
exit
InstallShield.
8.
After
installation,
start
the
GUI
using
the
icon
on
your
Start
menu.
Figure
13.
Installation
Successful
screen
24
IBM
Tivoli
Java
Collector:
Installation
Guide
Chapter
5.
Removing
the
JAC
Server,
JAC
Client,
or
Administration
GUI
This
chapter
describes
how
to
remove
the
JAC
Server,
JAC
Client,
or
Administration
GUI.
Removing
the
JAC
Server
You
can
remove
the
JAC
Server
by
using
either
the
command
line
or
SMIT.
You
must
be
logged
on
as
root.
Removal
using
the
command
line
From
the
command
line,
run:
installp
-u
jacsrv
The
JAC
Server,
directories,
and
files
are
removed.
Removal
using
SMIT
To
remove
the
JAC
Server
using
SMIT:
1.
On
the
command
line,
type
smit.
The
System
Management
panel
opens
and
presents
you
with
a
list
of
selections.
2.
Select
Software
Installation
and
Maintenance.
The
Software
Installation
and
Maintenance
panel
opens
and
asks
you
to
make
a
selection.
3.
Select
Software
Maintenance
and
Utilities.
4.
Select
Remove
Installed
Software.
5.
From
the
Remove
Installed
Software
panel,
select
[list]
for
the
SOFTWARE
name
item.
A
Multi-select
list
opens.
6.
From
the
Multi-select
list,
find
and
select
jacsrv.rte.
Press
OK.
You
return
to
the
Remove
Install
Software
panel.
7.
Make
sure
that
the
PREVIEW
item
is
set
to
no
and
press
OK.
8.
A
pop-up
panel
asking
″ARE
YOU
SURE″?
opens.
9.
Press
OK
to
remove
the
jacsrv.rte
fileset.
A
panel
opens
with
output.
10.
Review
the
output
to
ensure
the
installation
was
removed.
If
the
installation
was
not
removed,
contact
IBM
Customer
Support.
11.
Press
Done.
The
Software
Install
panel
reopens.
12.
Press
Cancel.
13.
You
may
now
exit
SMIT.
The
JAC
Server,
directories,
and
files
are
removed.
©
Copyright
IBM
Corp.
2003
25
Removing
the
JAC
Client
from
a
Windows
machine
To
remove
the
JAC
Client
from
the
Start
menu:
1.
Click
Settings.
2.
Click
Control
Panel.
3.
Click
Add/Remove
Programs
and
click
the,
Install/Uninstall
tab.
Scroll
down
until
you
find
JAC
Client.
4.
Click
JAC
Client
and
then
click
Add/Remove.
The
InstallShield
wizard
opens.
5.
Follow
the
directions
to
uninstall
the
JAC
Client.
Removing
the
JAC
Client
from
a
UNIX
machine
To
remove
the
JAC
Client
from
a
UNIX
machine,
type:
InstallDir/_uninst/uninstaller.bin
where
InstallDir
is
the
fully-qualified
path
of
where
the
client
is
installed.
For
example,
/opt/IBM/JACclient/_uninst/uninstaller.bin
Removing
the
Administration
GUI
To
remove
the
Tivoli
Java
Collector
JAC
Administration
GUI,
from
the
Start
menu:
1.
Click
Settings.
2.
Click
Control
Panel.
3.
Click
Add/Remove
Programs
and
click
the
Install/Uninstall
tab.
Scroll
down
until
you
find
Tivoli
Java
Collector
Administration
GUI.
4.
Click
Tivoli
Java
Collector
Administration
GUI
then
click
Add/Remove.
You
are
asked
to
either
modify,
repair,
or
remove
the
installation.
5.
Click
Remove.
You
are
asked
to
confirm
the
uninstall.
6.
Click
OK.
7.
Click
Finish.
Note:
When
you
uninstall
the
JAC
Administration
GUI,
some
of
the
Tivoli
Java
Collector
configuration
files
stored
in
user
directories
are
not
removed
by
the
uninstall
process.
You
need
to
manually
remove
these
files
after
you
uninstall
theJAC
Administration
GUI.
If
you
access
the
JAC
Administration
GUI
as
a
Windows
administrator,
these
files
can
generally
be
found
in
%SystemRoot%\Profiles\Administrator\JAC
for
Windows
NT
systems
or
in
%SystemDrive%\Documents
and
Settings\Administrator\JAC
for
Windows
2000
or
Windows
XP
systems.
26
IBM
Tivoli
Java
Collector:
Installation
Guide
Chapter
6.
After
the
installation
has
completed
After
you
have
installed
the
JAC
Server,
the
JAC
Client,
and
the
JAC
Administration
GUI,
be
sure
to
install
the
Tivoli
Java
collectors
from
the
product
CD
into
a
directory
that
is
readable
and
writable
by
the
JAC
Server.
You
will
need
to
run
the
authorization
tool
against
these
collectors
before
you
register
them.
See
the
IBM
Tivoli
Java
Collector
User’s
Guide
for
more
information
about
this
procedure.
After
you
have
installed
Tivoli
Java
Collector,
it
is
important
to
review
log
space
in
DB2
to
determine
if
you
have
adequate
space
for
Tivoli
Java
Collector
logging
requirements.
You
must
have
administrator
authority
for
DB2
to
issue
the
following
commands,
which
will
enable
you
to
review
the
logging
requirements
and
make
changes,
if
necessary.
The
values
in
the
following
commands
are
a
recommended
minimum
for
a
reasonably
loaded
system.
If
you
are
using
a
more
heavily
loaded
system,
you
may
need
to
increase
the
log
file
size
and
or
the
number
of
log
files.
1.
To
see
the
current
DB2
settings,
issue
the
command:
db2
get
db
cfg
for
JAC
2.
To
set
the
log
file
to
1000
4K
pages,
issue
the
command:
db2
update
db
config
for
JAC
using
LOGFILSIZ
1000
3.
To
set
DB2
to
use
10
circular
log
files,
issue
the
command:
db2
update
db
config
for
JAC
using
LOGPRIMARY
10
4.
After
you
make
these
changes,
please
stop
and
then
restart
the
JAC
Server.
©
Copyright
IBM
Corp.
2003
27
28
IBM
Tivoli
Java
Collector:
Installation
Guide
Chapter
7.
Troubleshooting
This
chapter
contains
several
problems
that
you
might
encounter
as
you
install
and
configure
Tivoli
Java
Collector
and
it
provides
some
solutions
to
these
problems.
Installing
in
console
mode
The
JAC
Client
and
the
JAC
Administration
GUI
are
packaged
into
InstallShield
MultiPlatform
installation
packages.
Occasionally,
there
can
be
problems
when
installing
these
packages
in
graphical
mode.
For
example,
on
UNIX/Linux
systems,
problems
might
occur
with
some
Window
managers
or
when
installing
from
a
remote
system.
The
InstallShield
MultiPlatform
tool
provides
support
for
installing
in
an
ASCII
text-based
mode
that
is
called
console
mode.
To
install
the
JAC
Client
or
the
JAC
Administration
GUI
in
console
mode,
use
the
command
form:
launcher_name
-is:javaconsole
-console
where
launcher_name
is
the
name
of
the
installation
launcher
program
for
the
JAC
Client
or
JAC
Administration
GUI.
Note:
After
obtaining
user
input,
the
InstallShield
program
performs
some
checks
before
displaying
the
summary
screen.
On
some
older
systems,
this
might
take
a
minute
or
more.
You
will
not
get
any
feedback
while
this
is
happening
so
please
remain
patient.
Installing
with
an
alternate
temporary
directory
The
installation
of
the
JAC
Client
and
the
installation
of
the
JAC
Administration
GUI
require
a
significant
amount
of
temporary
free
space
that
is
used
to
unpack
and
contain
the
bundled
Java
runtime
environment
and
other
installation
files.
Specific
space
requirements
are
documented
in
Chapter
1,
“Installation
overview,”
on
page
1.
If
the
temporary
directory
on
your
system
does
not
contain
sufficient
free
space
to
perform
the
installation,
you
must
change
the
directory
that
is
used
for
temporary
space
to
one
that
does
contain
sufficient
space.
Note:
Before
you
install,
the
temporary
directory
must
already
exist,
otherwise
the
option
is
ignored.
To
install
the
JAC
Client
or
the
JAC
Administration
GUI
and
use
an
alternate
directory
for
temporary
installation
space,
use
the
command
form:
launcher_name
-is:tempdir
temp_dir
where
launcher_name
is
the
name
of
the
installation
launcher
program
for
the
JAC
Client
or
JAC
Administration
GUI
and
temp_dir
is
the
name
of
the
directory
that
will
be
used
to
store
temporary
files.
©
Copyright
IBM
Corp.
2003
29
Files
left
in
temporary
directory
Occasionally,
InstallShield
files
are
left
in
the
temporary
directory.
This
problem
can
occur
if
you
use
Ctrl-C
to
cancel
out
of
an
installation
or
if
the
installation
abnormally
terminates.
30
IBM
Tivoli
Java
Collector:
Installation
Guide
Chapter
8.
Silent
install
for
the
client
and
GUI
You
can
install
the
JAC
Client
and
the
JAC
Administration
GUI
in
silent
mode
using
a
response
file
to
provide
input.
Note:
Before
you
begin
be
aware
that
ISMP
does
not
report
any
errors
in
silent
mode.
Therefore,
if
you
mistype
any
of
the
options,
the
installation
will
silently
fail
or
do
unexpected
things.
For
example,
if
you
are
installing
in
/syslocal/tools/JAC
and
you
were
to
mistype:
-P
installLocation="syslocal/tools/JAC
as
-P
nstallLocation="syslocal/tools/JAC
the
JAC
Client
would
be
installed
in
/usr/opt/IBM/JACclient
not
/syslocal/tools/JAC,
and
there
would
be
no
error
message.
The
InstallShield
MultiPlatform
tool
provides
the
capability
to
create
a
template
file
that
contains
all
possible
responses.
The
tool
also
provides
a
record
option
that
allows
you
to
record
the
responses
given
when
installing
a
particular
system.
Response
files
created
using
these
techniques
can
be
used
to
perform
silent
installations.
In
the
example
commands
given
in
this
section
for
the
variable
platform,
substitute
one
of
the
following:
aix.bin,
hpux.bin,
linux.bin,
solaris.bin,
win32.
To
record
a
response
file
during
an
installation
of
the
JAC
Client,
run:
jacclient_platform
-options-record
filename
where
filename
is
the
path
name
of
the
file
to
which
the
recorded
response
data
will
be
written.
To
generate
a
template
file
for
the
JAC
client,
run:
jacclient_platform
-options-template
filename
where
filename
is
the
path
name
of
the
file
to
which
the
template
response
data
will
be
written.
When
the
template
generation
successfully
completes,
you
will
receive
the
following
message:
Options
file
filename
was
successfully
created
The
template
file
that
is
created
must
be
edited
using
a
text
editor
as
follows:
v
For
options
you
wish
to
set,
remove
the
three
comment
characters
(###)
at
the
start
of
the
option
line.
v
Replace
value
with
the
appropriate
value
for
each
uncommented
option.
To
record
a
response
file
during
an
installation
of
the
JAC
administration
GUI,
run:
jacadmin_win32
-options-record
filename
©
Copyright
IBM
Corp.
2003
31
where
filename
is
the
path
name
of
the
file
to
which
the
recorded
response
data
will
be
written.
To
generate
a
template
file
for
the
JAC
administration
GUI,
run:
jacadmin_win32
-options-template
filename
where
filename
is
the
path
name
of
the
file
to
which
the
template
response
data
will
be
written.
When
you
first
perform
silent
installation,
use
the
-options-record
option
to
generate
a
response
file
from
an
actual
installation.
This
allows
you
to
familiarize
yourself
with
the
data
variables
that
can
be
set
and
the
valid
responses.
Once
you
are
familiar
with
the
data
that
must
be
provided
in
the
response
file,
you
might
find
the
-options-template
option,
which
provides
a
template
file
of
all
possible
responses,
to
be
useful.
Once
you
have
created
a
response
file
with
the
desired
data
input,
you
can
use
that
file
in
a
subsequent
silent
installation.
For
example,
to
perform
a
silent
installation
of
the
client,
run:
jacclient_platform
-silent
-options
filename
where
filename
is
the
path
name
of
the
file
that
contains
the
response
data
to
be
used.
32
IBM
Tivoli
Java
Collector:
Installation
Guide
Appendix.
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
give
you
any
license
to
these
patents.
You
can
send
license
inquiries,
in
writing,
to:
IBM
Director
of
Licensing
IBM
Corporation
500
Columbus
Avenue
Thornwood,
NY
10594
U.S.A
For
license
inquiries
regarding
double-byte
(DBCS)
information,
contact
the
IBM
Intellectual
Property
Department
in
your
country
or
send
inquiries,
in
writing,
to:
IBM
World
Trade
Asia
Corporation
Licensing
2-31
Roppongi
3-chome,
Minato-ku
Tokyo
106,
Japan
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.
©
Copyright
IBM
Corp.
2003
33
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:
IBM
Corporation
2Z4A/101
11400
Burnet
Road
Austin,
TX
78758
USA
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
information
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.
Any
performance
data
contained
herein
was
determined
in
a
controlled
environment.
Therefore,
the
results
obtained
in
other
operating
environments
may
vary
significantly.
Some
measurements
may
have
been
made
on
development-level
systems
and
there
is
no
guarantee
that
these
measurements
will
be
the
same
on
generally
available
systems.
Furthermore,
some
measurement
may
have
been
estimated
through
extrapolation.
Actual
results
may
vary.
Users
of
this
document
should
verify
the
applicable
data
for
their
specific
environment.
Information
concerning
non-IBM
products
was
obtained
from
the
suppliers
of
those
products,
their
published
announcements
or
other
publicly
available
sources.
IBM
has
not
tested
those
products
and
cannot
confirm
the
accuracy
of
performance,
compatibility
or
any
other
claims
related
to
non-IBM
products.
Questions
on
the
capabilities
of
non-IBM
products
should
be
addressed
to
the
suppliers
of
those
products.
All
statements
regarding
IBM’s
future
direction
or
intent
are
subject
to
change
or
withdrawal
without
notice,
and
represent
goals
and
objectives
only.
This
information
contains
examples
of
data
and
reports
used
in
daily
business
operations.
To
illustrate
them
as
completely
as
possible,
the
examples
include
the
names
of
individuals,
companies,
brands,
and
products.
All
of
these
names
are
fictitious
and
any
similarity
to
the
names
and
addresses
used
by
an
actual
business
enterprise
is
entirely
coincidental.
If
you
are
viewing
this
information
softcopy,
the
photographs
and
color
illustrations
may
not
appear.
Trademarks
The
following
terms
are
trademarks
or
registered
trademarks
of
International
Business
Machines
Corporation
in
the
United
States,
other
countries,
or
both:
AIX
DB2
IBM
34
IBM
Tivoli
Java
Collector:
Installation
Guide
IBM
logo
Tivoli
Tivoli
logo
Microsoft,
Windows,
Windows
NT,
and
the
Windows
logo
are
trademarks
of
Microsoft
Corporation
in
the
United
States,
other
countries,
or
both.
Java
and
all
Java-based
trademarks
and
logos
are
trademarks
or
registered
trademarks
of
Sun
Microsystems,
Inc.
in
the
United
States
and
other
countries.
UNIX
is
a
registered
trademark
of
The
Open
Group
in
the
United
States
and
other
countries.
Other
company,
product,
and
service
names
may
be
trademarks
or
service
marks
of
others.
Appendix.
Notices
35
36
IBM
Tivoli
Java
Collector:
Installation
Guide
Index
AAdministration
GUI
removal
26
Administration
GUI,
installing
19
CClient
installation
11
Client
removal
26
configuration,
JAC
Server
7
Iinstallation
prerequisites
1
installingAdministration
GUI
19
Client
11
Server
5
JJAC
Server
configuration
7
Pproduct
removal
25
Rreinstalling
Administration
GUI
19
Client
11
Server
5
related
publications
vi
removalAdministration
GUI
26
JAC
Client
26
JAC
Server
25
SServer
installation
5
using
command
line
5
using
SMIT
6
Server
removal
25
silent
installAdministration
GUI
31
JAC
Client
31
SMIT
5
software
prerequisites
1
System
Management
Interface
Tool
5
Uuninstalling
25
©
Copyright
IBM
Corp.
2003
37
38
IBM
Tivoli
Java
Collector:
Installation
Guide
����
Printed
in
USA
SC32-1488-00
