Availability Guide for Application Design

Instrumenting an Application for Availability
Availability Guide for Application Design—525637-004
8-13
A Framework for Planning and Developing Your
Instrumentation
Figure 8-4 shows an example of a dynamic model that might apply to a server process.
“Running” would be considered an up state and “stopped” would be considered a down
state. “Starting,” abending,” and “stopping” would all be considered odd states.
Designing Event Messages
Having established the state transitions that should generate event messages, you
must design each event message to contain appropriate information. The operations
environment will use this information to perform a suitable response.
Event messages should be designed to use the Event Management Service (EMS)
message format for compatibility with other HP subsystems, HP tools, and
applications. Refer to The Subsystem Programmatic Interface (SPI) on page 8-19 for
some hints on message content.
Defining Command and Control
The next step in planning instrumentation for your application is to define the command
messages that management applications will use to control your application.
Command messages should be designed to use SPI format for compatibility with other
HP subsystems, HP tools, and applications. Refer to The Subsystem Programmatic
Interface (SPI) on page 8-19 for some hints on message content.
Figure 8-4. Server Process State Changes—A Dynamic Model
RunningAbending
Starting
Stopping
Stopped
Run-Time Errors
Generate Run-Time
Error Events
Process Stopping
Generate Process
Stopping Event
Saveabend File
Created
START SERVER PROCESS Command
Initialization
Errors
Generate Initialization
Error Events
Process Running
Generate Process
Running Event
VST704.vdd