![](https://pdfstore-manualsonline.prod.a.ki/pdfasset/1/cf/1cff7c4d-621c-4eb6-bc3e-9de70e5199ff/1cff7c4d-621c-4eb6-bc3e-9de70e5199ff-bg98.png)
BMC Software, Inc., Confidential and Proprietary Information
8-2 PATROL
®
Database Administration Installation Guide
Configuring the Client
The first task after installing the server and the client is to start and
configure the client. You must configure the client before you can use the
product. To configure the client, double-click the Database
Administration Products icon from the PATROL
®
DB-Admin Client 3.0
program group.
Configuration involves the following tasks:
• define hosts or servers
A host or server is the Unix, Windows NT, or OS/390 system that
performs the Database Administration server operations. Each host
or server has both a Database Administration server and at least one
relational database management system (RDBMS) installed on it.
Identifying an available host or server to the client is called defining
a host or server.
You must define at least one host or server in order to use the
Database Administration products. You should define a separate host
or server for each workstation or system that you want to use as a
server for the Database Administration products.
Note
(PATROL Agent
™
monitoring only) You must follow certain naming
conventions for hosts in order to monitor jobs using a PATROL Agent.
When specifying a host, do not use spaces as part of the host name.
Instead, use a special character, such as an underscore or a plus sign (for
example, foxport_600).
• create connection profiles
When you start a connection, you use a connection profile to specify
the details for that connection. For Unix and Windows NT, the
connection profile specifies which Database Administration host,
database server, and database login or user ID to use during that
connection. For DB2 for OS/390 connections, the connection profile
specifies which Database Administration product, host, DB2
Subsystem, and TSO user ID to use during that connection.