APPLICATION-MIB Table View

The service name to service instance table uses
service name as its primary key, and service instance
identifier as its secondary key.  It facilitates the
identification and lookup of the instances of a given
service in a system.

The service instance to service name table uses
service instance identifier as its primary key, and
service name as its secondary key.  Given a service
instance identifier, it facilitates the lookup of the
name of the service being provided.

The service instance to running application element
table uses the service instance identifier as its primary
key, and the running application element index as its
secondary key.  This facilitates the identification
          
of the set of running application elements providing a
given instance of a service.

The running application element to service instance
table uses the running application element index as
its primary key and the service instance identifier as
its secondary key.  It identifies the set of services
provided by a given running application element.

The applOpenChannelTable reports information on open
channels for running application elements
and for service instances.  This table is
indexed by applElmtOrSvc, applElmtOrSvcId, and
applOpenChannelIndex. This effectively groups all
entries for a given running application element
or service instance together.  ApplChannelIndex uniquely
identifies an open channel (and, consequently, a file
or connection) within the context of a particular
running application element or service instance.
          
Some of the information in this table is available
through both sixty-four and thirty-two bit counters.
The sixty-four bit counters are not accessible in
protocols that do not support this data type.

The applOpenFileTable reports information on open files
for service instances or application elements.  This
table is indexed by applElmtOrSvc and applElmtOrSvcId,
effectively grouping all entries for a given running
service instance or application element together, and
by applOpenChannelIndex, uniquely identifying an open
channel (and, consequently, a file) within the context
of a particular service instance or application element.
          
Elements in this table correspond to elements in the
applOpenChannelTable that represent files.  For rows in
the applOpenChannelTable that do not represent files,
corresponding rows in this table will not exist.

The applOpenConnectionTable provides information about
open and listening connections from the perspective
of a running application element or service instance.
Entries in this table are indexed by applElmtOrSvc,
applElmtOrSvcID, and by applOpenChannelIndex, which
serves to uniquely identify each connection in the
context of a service instance or running application
          
element.
          
For each row in this table, a corresponding row will
exist in the applOpenChannel table.  For rows in the
applOpenChannelTable which do not represent open or
listening connections, no corresponding rows will exist
in this table.

The applTransactionStreamTable contains common
information for transaction statistic accumulation.

The applTransactFlowTable contains entries, organized by
application instance or running application element,
direction of flow, and type (request/response) for each
open transaction stream.
          
The simple model of a transaction used here looks like
this:
          
    invoker  |   Request     | performer
             | - - - - - - > |
             |               |
             |   Response    |
             | < - - - - - - |
             |               |
          
Since in some protocols it is possible for an entity
to take on both the invoker and performer roles,
information here is accumulated for transmitted and
received requests, as well as for transmitted and
received responses.  Counts are maintained for both
transactions and bytes transferred.

The applTransactKindTable provides transaction statistics
broken down by kinds of transaction.  The definition of
the kinds of transactions is specific to the application
protocol in use, and may be documented in the form of an
applicability statement.

The applPastChannelControlTable controls the
accumulation of history information about channels
from the perspective of service instances and running
application elements.  Entries in this table are indexed
by applElmtOrSvc and applElmtOrSvcId, giving control
of channel history accumulation at the level of each
service instance and running application element.

The applPastChannelTable provides history information
about channels from the perspective of running
application elements and service instances.
          
Entries in this table are indexed by applElmtOrSvc,
applElmtOrSvcId, and by applPastChannelIndex, which
serves to uniquely identify each former channel in the
context of a running application element or service
instance.
          
Note that the value of applPastChannelIndex is
independent of the value applOpenChannelIndex had when
this channel was open.
          
Entries for closed channels for a given running
application element or service instance can
be added to this table only if its entry in the
applPastChannelControlTable has the value 'enabled'
for the attribute applPastChannelControlCollect.
          
Entries for closed channels are removed under the
following circumstances:
          
    - the running application element or service
      instance no longer exists
          
    - the corresponding applPastChannelControlCollect
      attribute has been set to 'disabled'
          
    - the entry has been in the table longer that the
      time limit indicated by the corresponding
      applPastChannelControlTimeLimit and the value of
      applPastChannelControlCollect is not 'frozen'
          
    - this is the oldest entry for the running
      application element or service instance in
      question and the addition of a new element would
      otherwise cause applPastChannelControlMaxRows to
      be exceeded for this running application element
      or service instance.
          
    - a value of applPastChannelIndex has been re-used.
      Note that under normal circumstances, this is
      unlikely.
          
Removal/replacement of an entry under the
last two conditions causes the corresponding
applPastChannelControlRemItems to be incremented.

The applPastFileTable supplements the
applPastChannelTable for entries corresponding to
channels which were files.  The indexing structure is
identical to applPastChannelTable.  An entry exists in
the applPastFileTable only if there is a corresponding
(same index values) entry in the applPastChannelTable
and if the channel was a file.
          
Entries for closed files are removed when the
corresponding entries are removed from the
applPastChannelTable.

The applPastConTable supplements the applPastChannelTable
for entries corresponding to channels which were
connections.  The indexing structure is identical
to applPastChannelTable.  An entry exists in the
applPastConTable only if there is a corresponding
(same index values) entry in the applPastChannelTable
and if the channel was a connection.
          
Entries for closed connections are removed when
the corresponding entries are removed from the
applPastChannelTable.

The applPastTransStreamTable contains common
information for historical transaction statistics.

The applPastTransFlowTable contains entries, organized by
application instance or running application element,
direction of flow, and type (request/response) for each
former transaction stream.
          
The simple model of a transaction used here looks like
this:
          
    invoker  |   Request     | performer
             | - - - - - - > |
             |               |
             |   Response    |
             | < - - - - - - |
             |               |
          
Since in some protocols it is possible for an entity
to take on both the invoker and performer roles,
information here is accumulated for transmitted and
received requests, as well as for transmitted and
received responses.  Counts are maintained for both
transactions and bytes transferred.

The applPastTransKindTable provides transaction
statistics broken down by kinds of transaction.
The definition of the kinds of transactions is
specific to the application protocol in use, and may be
documented in the form of an applicability statement.

This table provides information on running application
elements, complementing information available in the
correspondingly indexed sysApplElmtRunTable [31].

This table provides the ability to control application
elements, complementing information available in the
correspondingly indexed sysApplElmtRunTable [31].