Errors starting the agent manager application, Verifying the connection to the registry, Verifying – IBM 51 User Manual
Page 96: Installation, Websphere, Application, Server, Universal, Database, Enterprise
Verifying
the
installation
of
WebSphere
Application
Server
To
verify
the
installation
of
WebSphere
Application
Server,
use
the
firststeps
tool,
located
in
the
WAS_install_dir/firststeps
directory.
Run
the
program
for
your
operating
system:
v
Windows:
firststeps.bat
v
AIX,
Linux,
or
Solaris:
firststeps.sh
Verifying
the
installation
of
DB2
Universal
Database
Enterprise
Server
Edition
(ESE)
If
the
registry
is
in
a
DB2
database
and
the
agent
manager
server
does
not
install
or
start
properly,
or
if
you
receive
errors
about
problems
accessing
the
registry,
verify
that
DB2
Universal
Database
ESE
installed
properly
and
that
the
DB2
Universal
Database
server
that
controls
the
registry
database
is
running.
To
verify
that
DB2
Universal
Database
ESE
installed
properly,
refer
to
the
DB2
Universal
Databasedocumentation
for
your
operating
system.
The
installation
documentation
contains
information
about
verifying
the
installation
using
either
the
command
line
processor
(CLP)
or
the
First
Steps
GUI.
The
general
procedure
is
the
same
for
both
methods:
1.
Create
the
SAMPLE
database.
2.
Connect
to
the
SAMPLE
database.
3.
Execute
a
query
against
the
SAMPLE
database.
4.
Drop
the
SAMPLE
database.
Errors
starting
the
agent
manager
application
server
If
you
cannot
start
the
agent
manager
application
server:
v
If
you
get
a
NoServerDefinedException
when
you
use
the
WebSphere
startServer
command
to
start
the
agent
manager
application
server,
ensure
that
you
specified
the
correct
server
name.
Although
the
default
name
of
the
agent
manager
application
server
is
AgentManager
,
the
agent
manager
might
be
installed
to
a
different
application
server,
such
as
server1
.
v
If
you
have
reconfigured
WebSphere
Application
Server
on
UNIX
or
Linux
to
run
as
a
user
other
than
root
and
get
a
FileNotFoundException
exception
or
a
“Permission
denied
”
error,
make
sure
that
the
user
ID
that
runs
the
WebSphere
processes
has
permission
to
read
the
agent
manager
files,
particularly
the
files
in
the
Agent_Manager_install_dir/certs
directory.
Errors
starting
the
agent
manager
application
If
the
logs
indicate
a
problem
starting
the
certificate
authority,
a
common
cause
is
a
problem
with
the
certificates.
To
correct
this,
you
can
replace
your
certificates.
Verifying
the
connection
to
the
registry
If
any
errors
indicate
a
problem
accessing
the
registry,
verify
that
the
registry
is
correctly
configured
and
available
by
performing
these
steps:
1.
Open
the
WebSphere
Administrative
Console,
and
then
expand
Resources
and
then
click
JDBC
Providers
.
2.
In
the
Server
field
on
the
JDBC
Providers
panel,
type
the
name
of
the
application
server
where
the
agent
manager
is
installed
or
click
Browse
to
select
it
from
a
list.
By
default,
this
is
AgentManager
.
84
Tivoli
Intelligent
Orchestrator
Problem
Determination
and
Troubleshooting
Guide