Availability Guide for Change Management

Making Application Subsystem Changes Online
Availability Guide for Change Management–125506
4-24
The NonStop TUXEDO Environment
Because the NonStop TUXEDO system uses the Tandem core services, however, there
are administrative tasks that are unique to the NonStop TUXEDO system. These tasks
are described later in the subsection “Administration of the Core Services.”
This section and the subsections following provide an overview of the NonStop
TUXEDO administrative environment. For more detailed information, see the NonStop
TUXEDO System Administration Guide.
Dynamic Reconfiguration
NonStop TUXEDO administrators can alter key application definitions without bringing
the application down. For example:
•
New machines, servers, and services can be added to the configuration without
taking the application out of service.
•
Services can be made available on a selective basis.
•
Various parameters, such as timeout intervals and priorities, can be changed
dynamically.
To make online configuration changes, administrators use the tmconfig program, an
interactive tool that guides the administrator through the reconfiguration process.
Online Service Management
Administrators can manage services for a running application by using the tmadmin
program. This program provides commands that enable administrators to:
•
Query the state of the application
•
Add (advertise) or remove (unadvertise) services from the bulletin board
•
Change the load for a service
•
Change the transaction timeout value for a service
These commands change the information in the current bulletin board structure, but they
do not make permanent changes to the configuration file.
Administration of the Core Services
The NonStop TUXEDO system uses the Tandem core transaction-processing services as
follows:
•
NonStop TS/MP for process management and link management (which enables
communication between clients and servers)
•
NonStop TM/MP for transaction management
The NonStop TS/MP infrastructure is virtually transparent to the NonStop TUXEDO
administrator. For example, when the administrator starts a NonStop TUXEDO
application, the underlying NonStop TS/MP processes are automatically started and
maintained. The administrator will notice a few added parameters in the configuration
file, however, and might want to use PATHCOM to check the status of the underlying
service.