Computer Associates SQLSTQ99000600 Diagnostics Guide - Page 22

Common Application Framework and Startup

Page 22 highlights

Common Application Framework and Startup The MDB schema includes the database objects used by CA products and their components. These include tables, columns, views, and procedures. The MDB manages operational and transactional data, as well as the analytical data used for intelligence and data mining. The DSM MDB resides at the Domain Manager and the Enterprise manager levels, though it is not necessarily co-located on the same physical machine as the manager. Common Application Framework and Startup Nearly all of the Unicenter DSM components rely on the Common Application Framework (CAF) which provides a rich, extensible runtime environment. CAF comprises a cross-platform service control manager (known simply as "caf") and a Common Component Library (known as "CCL"), which provides a library of re-usable, shared functionality. For the sake of illustration, let us consider what happens when a computer that is running a full Unicenter DSM Domain Manager with all products (UAM, URC, USD) and components installed (including Scalability Server, Agent and Web components) boots up. Since nearly all Unicenter DSM processes are controlled by CAF, essentially the first thing that happens is that CAF starts up and then starts all configured plug-ins. There are a few exceptions to this, and these are listed below for the sake of completeness: „ cfusrntf.exe, which is used to capture user accounts, is invoked transiently whenever a user logs in to a system. „ sxplog32.exe, which is used to apply sxp package settings within a user context (i.e., it is only used when an sxp package is installed), is invoked persistently whenever a user logs in to a system. This is started through the following registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Ru n\DsmSxplog „ cf_SysTray.exe, which is used to provide a menu applet within the system tray area of the desktop, is invoked persistently whenever a user logs in to a system. It is started through the following registry key : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Ru n\CAF_SystemTray 3-4 CA-Product User Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70

Common Application Framework and Startup
The MDB schema includes the database objects used by CA products and their
components. These include tables, columns, views, and procedures. The MDB
manages operational and transactional data, as well as the analytical data
used for intelligence and data mining.
The DSM MDB resides at the Domain Manager and the Enterprise manager
levels, though it is not necessarily co-located on the same physical machine as
the manager.
Common Application Framework and Startup
Nearly all of the Unicenter DSM components rely on the Common Application
Framework (CAF) which provides a rich, extensible runtime environment. CAF
comprises a cross-platform service control manager (known simply as “caf”)
and a Common Component Library (known as “CCL”), which provides a library
of re-usable, shared functionality.
For the sake of illustration, let us consider what happens when a computer
that is running a full Unicenter DSM Domain Manager with all products (UAM,
URC, USD) and components installed (including Scalability Server, Agent and
Web components) boots up.
Since nearly all Unicenter DSM processes are controlled by CAF, essentially the
first thing that happens is that CAF starts up and then starts all configured
plug-ins.
There are a few exceptions to this, and these are listed below for the
sake of completeness:
cfusrntf.exe
, which is used to capture user accounts, is invoked
transiently whenever a user logs in to a system.
sxplog32.exe
, which is used to apply sxp package settings within a user
context (i.e., it is only used when an sxp package is installed), is invoked
persistently whenever a user logs in to a system. This is started through
the following registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Ru
n\DsmSxplog
cf_SysTray.exe
, which is used to provide a menu applet within the
system tray area of the desktop, is invoked persistently whenever a user
logs in to a system. It is started through the following registry key :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Ru
n\CAF_SystemTray
3–4
CA-Product User Guide