HP ACMS for OpenVMS, Version 5.1B (SPD 82.40.04)

HP ACMS for OpenVMS, SPD 82.40.04
Version 5.1B
• Application Authorization Utility (AAU) — Authorizes
applications to be installed.
• User Definition Utility (UDU) — Authorizes users to
log in to ACMS and assigns login displays, including
default menus, to ACMS users.
• Device Definition Utility (DDU) — Authorizes ACMS
terminals and, optionally, defines captive terminals to
log in directly to ACMS.
• Queue Manager (QUEMGR) — Creates and man-
ages ACMS task queues and queued task elements.
• Software Event Log Utility Program (SWLUP) — Cre-
ates reports of selected events recorded by the Soft-
ware Event Logger.
• Audit Trail Report Utility (ATR) — Returns records of
application and user activity.
In addition to the utilities, ACMS also provides users
with the following support for application management
and control:
• ACMS operator commands — Performs standard op-
erator functions such as starting and stopping the
ACMS system, the TSC process, the QTI process,
and ACMS applications.
• Command procedures — Evaluates and modifies the
values of OpenVMS and ACMS system parameters
and of ACMS run-time process quotas.
Remote System Management
The ACMS Remote Manager provides the capability
to monitor and manage the ACMS application environ-
ment. ACMS system managers can access the Remote
Manager using one of the supported interfaces over a
TCP/IP network.
The Remote Manager must be running on the same
node as the ACMS run-time system it is monitoring or
accessing. Communication between the Remote Man-
ager and the ACMS run-time system is transparent.
Three interfaces allow access to the Remote Manager:
• RPC Interface—Provides local or remote access to
ACMS management information using the Open Net-
work Computing Remote Procedure Call (ONC RPC)
protocol. This interface can be used by user-written
programs to implement customized ACMS manage-
ment tools.
• Command Line Utility—Provides command line ac-
cess to management information as well as control
of the Remote Manager process. This utility uses the
RPC Interface.
• Simple Network Management Protocol (SNMP)
Interface—Provides network access to ACMS man-
agement information using the industry standard
SNMP protocol. This protocol is supported by most
system management consoles and tools.
ACMS system managers control the data being col-
lected, including ACMS process monitoring, and the
management interfaces themselves through either
SNMP or RPC commands.
The Remote Manager enables ACMS system managers
to do the following:
• Remotely manage agents, including user-written
agents, HP-supplied agents (such as HP TP Web
Connector, HP TP Desktop Connector and HP TP-
ware .NET Plugin), and agents supplied by other ven-
dors.
• Remotely manage data collection including configur-
ing SNMP traps and viewing management informa-
tion on line.
• Remotely modify ACMS run-time systems.
• Write programs that remotely access management
information online using ONC RPC and SNMP.
Client/Server Processing
ACMS uses the client/server model to distribute and
separate functions. This model can be implemented on
a single node or on multiple nodes in a DECnet network.
The terminal and menu functions are handled on the
client, or front end, of the transaction processing sys-
tem, while task flow control, data processing, and com-
putations are performed on the server, or back end, of
the system.
Because the ACMS client/server model always provides
separate front and back ends, users can at any time
offload the front-end to another computer system without
reprogramming the application code.
The ACMS Systems Interface (SI) lets users write front
end programs, or agents, to support specialized de-
vices such as bar-code readers and automatic teller ma-
chines.
ACMS includes support for failover in a distributed envi-
ronment. If one OpenVMS node is not available to pro-
cess a transaction, ACMS can automatically route the
transaction to another application running on an avail-
able node.
3