APPLICATION Configuration Syntax

The following syntax is used to group individual applications and/or groups of applications (see the Application Grouping) into a single application group for availability monitoring.

SUBSYS AVAILABILITY

APPLICATION ADDEXE (<AppName>, <ExeName>[, <NumNeeded>][, {CR|nn|DE}])
APPLICATION ADDSERVICE (<AppName>, <ServiceName>[, {CR|nn|DE}])
APPLICATION ADDPORT (<AppName>, <PortName>[, <PortRole>][, <NumActiveConx>][, {CR|nn|DE}])
APPLICATION ADDDISK (<AppName>, <DiskName>[, {CR|nn|DE}])
APPLICATION ADDTCPHOST (<AppName>, <HostName>[, {CR|nn|DE}])
APPLICATION ADDTANDEMENTITY (<AppName>, <EntityName>[, {CR|nn|DE}])
APPLICATION ADDAPP (<AppName>, <SlaveAppName>[, {CR|nn|DE}])
APPLICATION ADDTRAN (<AppName>, <Transaction Name>[, {CR|nn|DE}])
APPLICATION ADDURL (<AppName>, <URLLogicalName>[, {CR|nn|DE}])
APPLICATION ADDSMTP (<AppName>, <SMTP domain name>[, {CR|nn|DE}])
APPLICATION ADDPOP (<AppName>, <POP3 domain name>[, {CR|nn|DE}])
APPLICATION ADDEMAIL (<AppName>, <Email-ID>[, {CR|nn|DE}])
APPLICATION ADDTHRESHOLD (<AppName>, <Thresh-Entity_Name>[, {CR|nn|DE}])
APPLICATION SCHEDULE (<EntityName>, <ScheduleName>)
APPLICATION SCHEDULEWHERE (<WhereClause>, <ScheduleName>)
APPLICATION TARGET (<EntityName>, <TargetValue>)
APPLICATION TARGETWHERE (<WhereClause>, <TargetValue>)
APPLICATION OUTAGE (NO)

Syntax Elements

APPLICATION ADDEXE

Associates process entities with an application name.

<AppName>

A user defined name for a collection of entities (max 60 characters). For multi-host capability, the <AppName> can be prefixed with a hostname, e.g. \MYHOST.MYAPPL.

<ExeName>

Name of a process as defined in a PROCEXE ADDEXE statement (max 60 characters) or name of the Guardian Object file, or OSS executable, as defined in the UPDOWN Configuration.

<NumNeeded>

Optional - Number of copies or instances of this process that must be concurrently executing on this server for the application to be considered UP. For example, if a value of five is specified, the application definition will show as DOWN if only four copies of this process are running. When one more copy is started the application will be shown as UP.

{CR|nn|DE}

Optional - For details see Application Weighting.

APPLICATION ADDSERVICE

Associates an NTSERVICE with an application name.

When this statement is used on HPE NonStop or UNIX servers, only remote entities from Windows servers can be monitored.

<AppName>

A user defined name for a collection of entities (max 60 characters). For Multi-host capability, the <AppName> can be prefixed with a hostname - e.g. \MYHOST.MYAPPL.

<ServiceName>

Name of a Windows service as already defined in a SERVICE ADDSERVICE statement (max 60 characters). This too can be prefixed with a hostname.

{CR|nn|DE}

Optional - For details see Application Weighting.

APPLICATION ADDPORT

Associates a Windows PORT with an application name.

When this statement is used on HPE NonStop or UNIX servers, only remote entities from Windows servers can be monitored.

<AppName>

A user defined name for a collection of entities (max 60 characters). For Multi-host capability, the <AppName> can be prefixed with a host name - e.g. \MYHOST.MYAPPL.

<PortName>

Name of a Windows port as already defined in a PORT ADDPORT statement (max 60 characters).

<PortRole>

Optional - Can be either ACTIVE or NOLISTENER (upper case characters only).

If NOLISTENER is used, this will result in the port being flagged as UP even if there is no process actively listening to that port number.

If ACTIVE is used, the port will be flagged as DOWN if there are no active connections to the port.

If omitted, the port is considered DOWN if no process is actively listening on that port.

<NumActiveConx>

Optional - Specifies the number of active connections needed for the port to be considered UP. It must be specified as an integer.

{CR|nn|DE}

Optional - For details see Application Weighting.

APPLICATION ADDDISK

Associates DISK drive with an application name.

<AppName>

A user defined name for a collection of entities (max 60 characters). For Multi-host capability, the <AppName> can be prefixed with a host name - e.g. \MYHOST.MYAPPL.

<DiskName>

Name of a disk device as already defined in a DISK ADDDISK statement (max 60 characters).

{CR|nn|DE}

Optional - For details see Application Weighting.

APPLICATION ADDTCPHOST

Associates a TCP/IP device, usually a server, with an application name.

<AppName>

A user defined name for a collection of entities (max 60 characters). For Multi-host capability, the <AppName> can be prefixed with a host name - e.g. \MYHOST.MYAPPL.

<HostName>

Name of a TCP/IP device as already defined in a TCPIP HOST statement (max 60 characters).

{CR|nn|DE}

Optional - For details see   Application Weighting.

APPLICATION ADDTANDEMENTITY

A TANDEMENTITY is any one of a number of special entity types that are only relevant on HPE NonStop servers. This syntax is used to associate a NonStop system entity (except disks, Guardian object file name and OSS executable names). Disks are associated with an application name using the APPLICATION ADDDISK syntax. Guardian object file name and OSS executable names are associated with an application name using the APPLICATION ADDEXE syntax.

<AppName>A user defined name for a collection of entities (max 60 characters). For Multi-host capability, the <AppName> can be prefixed with a host name - e.g. \MYHOST.MYAPPL.

<EntityName>

The name of the entity as defined by the operating system:


- Named Process

- Expand Line

- BUS

- Multilan device

X25 Line

Expand Network Control Process

Magnetic Tape

CPU


Processes must be configured in the UPDOWN configuration. All other devices are automatically discovered.

{CR|nn|DE}

Optional - For details see Application Weighting.

For further details on TANDEMENTITY please refer to the UPDOWN Configuration topic in the System Functions Guide.

APPLICATION ADDAPP

<AppName>

A user defined name for a collection of entities (max 60 characters). For Multi-host capability, the <AppName> can be prefixed with a hostname, e.g. \MYHOST.MYAPPL

<SlaveAppName>

Name of the application to be added to the group (max 60 characters). This can be prefixed with a hostname.

{CR|nn|DE}

Optional - For details see Application Weighting.

APPLICATION ADDTRAN

Associates an e-commerce transaction with an application name.

When this statement is used on HPE NonStop servers, only remote entities from Windows and UNIX servers can be monitored.

<AppName>

A user defined name for a collection of entities (max 60 characters). For Multi-host capability, the <AppName> can be prefixed with a host name - e.g. \MYHOST.MYAPPL.

<Transaction Name>

Name of a recording already defined in a URL ADDTRAN statement (max 60 characters).

{CR|nn|DE}

Optional - For details see Application Weighting.

APPLICATION ADDURL

When this statement is used on HPE NonStop servers, only remote entities from Windows and UNIX servers can be monitored.

<AppName>

A user defined name for a collection of entities (max 60 characters). For Multi-host capability, the <AppName> can be prefixed with a host name - e.g. \MYHOST.MYAPPL.

<URLLogicalName>

Logical name of the URL as already defined in a URL ADDURL statement (max 60 characters).

{CR|nn|DE}

Optional - For details see Application Weighting.


APPLICATION ADDSMTP, APPLICATION ADDPOP, APPLICATION ADDEMAIL

These tokens specify an email entity to be added to an application. Either an SMTP server, a POP server or an email delivery entity, denoted by an email-id, can be added to an application either on the same node or another node.

<AppName>

A user defined name for a collection of entities (max 60 characters). For Multi-host capability, the <AppName> can be prefixed with a hostname - e.g. \MYHOST.MYAPPL.

<SMTP domain Name>
<POP domain name>
<Email-ID>

Either of these can be added to an application provided that they have already been defined by EMAIL ADDSMTP, EMAIL ADDPOP, or EMAIL ADDEMAIL (max 60 characters). For multi-host applications, SMTP/POP/Email-ID can be prefixed by the hostname e.g. \MYHOST.Email-ID, \HOST2.smtp.ir.com etc.

{CR|nn|DE}

Optional - For details see Application Weighting.

APPLICATION ADDTHRESHOLD

This entry is used in conjunction with Availability Thresholds and allows for application state to be monitored through a Threshold condition containing user-defined performance criteria.

<AppName>

A user defined name for a collection of entities (max 60 characters)

<Thresh-Entity_Name>

Statically defined Threshold entity name (max 60 characters).

{CR|nn|DE}

Optional - For details see Application Weighting.

Availability-Scheduled Outages

For detailed information about the following entries please refer to the Scheduled Availability Outages.

APPLICATION SCHEDULE

This entry is used to attach a monitoring schedule to an entity. This schedule is created through the SCHEDULE Configuration and is used to define periods when the specified entity is to be monitored. Any periods outside of the schedule are recorded as schedule outages and any outages recorded during the monitored period are treated as unscheduled outages.

<EntityName>

Name of the entity to be monitored (max 60 characters). This can be a specific entity name or wild cards '*' or '?' can be used to indicate a range of entities.

<ScheduleName>

Name of the schedule as defined in the SCHEDULE Configuration.

APPLICATION SCHEDULEWHERE

This entry is used to attach a schedule to an entity by using a specified Where Clause. Currently, only the ID field can be used in the Where Clause for this entity type. This can be useful for specifying regular expressions that are not available in the wildcard syntax.

APPLICATION TARGET

Service level targets based upon availability percentage can be specified for an entity. The target value can be specified to six decimal places. The percentage sign '%’ is not required as it is implied that the value specified is a percentage.

APPLICATION TARGETWHERE

This entry is used to specify a service level target to an entity by using a specified Where Clause. Currently, only the ID field can be used in the Where Clause for this entity type. This can be useful for specifying regular expressions that are not available in the wildcard syntax.

APPLICATION OUTAGE

By default, the Availability collector will generate detailed outage records for all entities. The generation of outage records can be stopped for a particular Availability associate by setting the APPLICATION OUTAGE entry to NO.

Provide feedback on this article