IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual page 294

IIOP, a part of the CORBA standard, is
based on the client/server computing
model, in which a client program makes
requests of a server program that waits to
respond to client requests. With IIOP, you
can write client programs that
communicate with your site's existing
server programs wherever they are
located without having to understand
anything about the server other than the
service it performs and its address (called
the Interoperable Object Reference, IOR,
which comprises the server's port number
and IP address).
Interoperable Object Reference
Connects clients to the Tivoli Enterprise
Portal Server. The IOR identifies a remote
object, including such information as
name, capabilities, and how to contact it.
The URL may include an IOR because it
goes through the web server; the portal
server uses it to tell the client which IOR
to fetch. After it does that, the portal
server extracts the host and port
information and tells the client where to
route the request.
interval
The number of seconds that have elapsed
between one sample and the next.
IOR See Interoperable Object Reference.
Java Database Connectivity
A standard API that enables application
developers to access and update relational
databases (RDBMSes) from within Java
programs. The JDBC standard is based on
the X/Open SQL Call Level Interface
(CLI) and complies with the SQL-92 Entry
Level standard; it provides a
DBMS-independent interface that enables
SQL-compliant database access for Java
programmers.
Java Management Extensions
A set of Java classes for application and
network management in J2EE
environments. JMX provides Java
programmers a set of native Java tools
called MBeans (managed beans) that
facilitate network, device, and application
management. JMX provides a Java-based
alternative to the Simple Network
Management Protocol.
JDBC See Java Database Connectivity.
276
IBM Tivoli Monitoring: Troubleshooting Guide
JMX See Java Management Extensions.
LDAP See Lightweight Directory Access
Protocol.
Lightweight Directory Access Protocol
A protocol that conforms to the
International Standards Organization's
X.500 directory standard that uses TCP/IP
to access directory databases where
applications can store and retrieve
common naming and location data. For
example, applications can use LDAP to
access such directory information as email
addresses, service configuration
parameters, and public keys.
location broker
The component of the Tivoli Enterprise
Monitoring Server that manages
connections for the hub monitoring
server, enabling it to find all other Tivoli
Monitoring components, including remote
monitoring servers, the Tivoli Enterprise
Portal Server, and Tivoli Enterprise
Monitoring Agents.
managed object
An icon created in the Tivoli Enterprise
Portal from a managed object template
that represents resources you monitor
using situations. Managed objects are
converted to items in the Navigator
Logical view.
managed system
A particular operating system, subsystem,
or application in your enterprise where a
monitoring agent is installed and running.
This is any system that the Tivoli
Enterprise Monitoring Server is
monitoring.
managed system list
A named list of managed systems of the
same type that is maintained by a user.
Example: a list of Linux managed systems
for a geographic region named
LINUX_LONDON. You can see and select
a managed system list when you
distribute a situation or policy, edit a
query specification, or assign managed
systems to Navigator items in custom
Navigator views.
If a managed system list is updated
(usually when a constituent managed
system is added or deleted), then all the