OSM Migration Guide (G06.28+)

Getting Started With OSM Applications
OSM Migration Guide—527273-015
5-22
OSM Notification Director
OSM Notification Director
The OSM Notification Director (ND) is a component of the OSM client software
package that receives information about the servers for which it is configured in the
form of incident reports. You can display these incident reports within the Notification
Director and forward (or have them automatically dialed out) to remote service
providers.
The Notification Director is also used to configure dial-in to your system console.
Dial-in allows remote service providers to log on and use OSM applications to
diagnose and fix problems on your NonStop S-series systems. Beginning with G06.23,
you can use Microsoft NetMeeting as an alternative to Carbon Copy for dial-in
services.
See Appendix C, Configuring Remote Services for instructions on how to configure
dial-in and dial-out.
The OSM Notification Director looks and functions much like the TSM version, except
for the differences (noted in this section) and new features, such as:
•
The ability to attach system inventory files to Periodic incident reports. To create
the files, the Creation of System Inventory Files feature must be enabled in your
OSMCONF file. To allow attachment of the files to Periodic incident reports, you
must deselect the Suppress Attachment files on Periodic IRs option in OSM
Notification Director Preferences.
•
ND version T0632AAK (and later*) supports the use of HP Instant Support
Enterprise Edition (ISEE), a web-based alternative to using a modem for dial-out of
incident reports.
•
ND version T0632AAN (and later*) automatically installs and configures
RemoteProxy Service, which provides connectivity to NonStop systems that have
OSM configured for Secure Sockets Layer (SSL) support.
* HP recommends that you get the latest version, to get the latest product fixes and
enhancements. See the T0632 softdoc for a complete list of fixes and enhancements.
For more information about configuring or using the OSM Notification Director, see the
OSM Notification Director online help.
Running Automatically
Unlike the TSM ND, the OSM Notification Director runs as a Windows service rather
than an application. It can be configured to start when the Windows operating system
starts and to run without a user logon. (The TSM Notification Director requires a user
log on for continuous functionality.)
During installation, you are asked whether you want the OSM Notification Director to
start automatically and run as a Windows service. Select this option if your workstation
is to be a primary or backup dial-out point, so the Notification Director can receive and
process incident reports continuously as they occur.