ASAP Migration Guide for NSX and OMF Users

ASAP 2.0 Overview
ASAP Migration Guide for NSX and OMF Users—520627-001
1-3
Domains
Domains
In ASAP 2.0, a domain is a logical concept representing an object or group of objects to
monitor. It applies to all entities. A domain can be a CPU number, disk volume, spooler
supervisor name, subvolume name, and so on; for example: 03, $data, $spls,
$db1.logfiles, respectively. In NSX and OMF, a domain is called an object name.
Various entities require different approaches for monitoring and display of domain
information. In general, entities monitor domains and report on them following this
hierarchical model:
\Node\Entity\Domain
For example:
\Asap\Disk\$Data
Some entities require additional levels below the domain. These entities have a
subdomain, that identifies one or more levels below the domain. For example, for files
in a subvolume: only the subvolume domain is configured, but information about each
file in that subvolume is available for display if needed. The APP and Spooler entities
also use subdomains. Because of this, the domains used for configuration and the
displayed domains might vary.
Table 1-2
shows examples of domain names used for configuration, and the ones that
can be displayed for each entity.
Table 1-2. Domain Names (page 1 of 2)
Entity
Domain Names—
Configuration Domain Name—Display Comments
APP n.a. Atm\Chicago\Deposit\$Atm1 User-defined name
via ASAPX API,
up to five levels
CPU 01 01 CPU number
Disk $Data $Data Disk volume name
Expand $Lhchi $Lhchi Expand line name
File $System.system.userid
$Data.db
$System.system.userid
$Data.db
$Data.db.file1
Selected files or
subvolumes;
subdomain display
available
Node n.a. Node names on the network
Process $Lsn1 $Lsn1 Selected process
name
ProcessBusy n.a. 01/top n processes Process busy per
CPU number
For clarity, the node and entity levels were omitted from the table. Assume both \Node\Entity\ levels to the left
of all domain names.