Using the Process Manager

This chapter provides information on using the Process Manager on a UNIX workstation. The CiscoWorks Blue Process Manager provides an interface for starting, monitoring, and stopping the Maps and SNA View daemons and processes and the Process Manager services.

The Process Manager starts automatically when your system starts. When the Process Manager starts, it starts all the Maps and SNA View processes that are marked as Autostart, and it restarts any processes that have been stopped abnormally and are marked for Restart.

This chapter includes the following main sections:

Starting the Process Manager

This section describes how to start the Process Manager. The Process Manager consists of a server component that monitors and maintains the running processes and a client component that displays the results in a graphical user interface.

This section includes the following information:

Starting the Server Components

UNIX Workstations

CiscoWorks Blue server processes are normally started automatically and kept running. Should you need to manually start them, use the following commands on a UNIX workstation:

From the command line, use the cwb start servers command to start all CiscoWorks Blue servers, including the database server and the Process Manager server. Because starting the database and naming servers requires root authority, you should always run cwb start servers as the root user:

/opt/CSCOcb/bin/cwb start servers

From the command line, use the cwb start pm command to start the Process Manager server:

/opt/CSCOcb/bin/cwb start pm

Windows NT

On a Windows NT system, you can select Start > Programs > CiscoWorks Blue > System Services > Start.

Starting the Client Component

UNIX Workstations

You can start the Process Manager client from the Administration application or from the command line. From the command line, use the cwb start ProcMgrClient command:

/opt/CSCOcb/bin/cwb start ProcMgrClient

From the Administration application, click Process Manager.

Windows NT

On a Windows NT system, you can use the following methods:

Select Start > Programs > CiscoWorks Blue > Start.
Select Start > Programs > CiscoWorks Blue > PM Client
From the taskbar icon, select PM Client.

Viewing the Process Management Information Window

The Process Management Information window contains two tabs:

The CWBlue tab displays the Process Management Information—CWBlue window. This window displays all the Maps and SNA View processes configured to run under Process Manager.
The Services tab displays the Process Management Information—Services window. This window displays the Process Manager services.

Viewing the Process Management Information—CWB Blue Window

The CWBlue window displays a list of the Maps and SNA View processes in a single window, as shown in Figure 7-1. The host name of the connected workstation is displayed in the title bar of the window.

Figure 7-1: Process Management Information—CWBlue Window

Fields

The CWBlue window contains the following fields:


`Field`	`Description`
`Name`	`The name of this process. See the "Maps and SNA View Daemons and Processes" section.`
`Process ID`	`A number identifying a process that is running.`
`State`	`Status of this process. The status colors are as follows: Green means the process is currently active. Blue means the process is in its initial state and has not been started. Red means the process has been run and then stopped. Yellow means the process is being started or stopped.`
`Last Message`	`Last message issued by this process. This is usually a status message that tells you what the process did last or why the process stopped.`

Buttons

The buttons on the CWBlue window provide the following functions:


`Button`	`Description`
`Start`	`Starts the selected process.`
`Stop`	`Stops the selected process.`
`Stop All`	`Stops all running processes.`
`Details`	`Displays the Details window (Figure 7-2) for the selected process.`
`Exit`	`Stops the Process Manager client and closes the window.`
`Help`	`Displays the online help.`

Viewing the CWBlue Details Window

You can see detailed information about each process. Select a process and click Details in the CWBlue window to view the details of the selected process. The Details window is displayed, as shown in Figure 7-2.

Figure 7-2: CWB Details Window

Fields

The Details window contains the following fields:


`Field`	`Description`
`Process Name`	`Name of the Maps process, as listed in the "Maps and SNA View Daemons and Processes" section.`
`Description`	`Description of the process.`
`Version`	`Version of the process.`
`Executable`	`Full path name for the executable file for the process.`
`Arguments`	`Command line switches for the process.`
`Autostart`	`Indicates whether the process is configured to start automatically: Yes means it will be automatically started. No means that it will not be automatically started unless some other process is dependent on it. Restart means that it will be automatically started and, if it stops abnormally, it will be restarted automatically. However, if you use the Process Manager to stop this process, it will not be restarted automatically.`
`Dependencies`	`Lists processes that must be running before this process is started.`
`Timeout`	`Time that the Process Manager waits for an Initialization Complete notification from the started process.`
`Start Time`	`Date and time that the process was last started. If the process was never started, this field is 0.`
`Stop Time`	`Date and time that this process was stopped. If the process is currently running, this field is 0.`
`Process ID`	`Process ID of the named process.`
`State`	`Status of the process.`
`Last Message`	`Last message sent by the process to the Process Manager.`

Maps and SNA View Daemons and Processes

The following table shows the Maps and SNA View daemons and processes that can be monitored in the Process Manager:


`Process Name`	`Description`
`cwbrsrbpollerd`	`RSRB Poller daemon, which polls RSRB MIBs.`
`cwbdlswpollerd`	`DLSW Poller daemon, which polls DLSw MIBs.`
`cwbmonitord`	`(UNIX only) Monitor daemon, which updates Maps Motif applications with changes.`
`cwbtrapd`	`(UNIX only) Trap daemon, which registers with the network management system (NMS) trap process.`
`cwbsnamapsd`	`CiscoWorks Blue Web daemon, which gets requested database information for the web server.`
`cwbhcid_domain_name cwbhcid_server_domain_name cwbhcmd_server_domain_name`	`SNA View host connection interface, which gets messages from the mainframe host. The cwbhcid (tcp) and cwhci_server(lu62) tasks will have multiple entries in the CWBlue.conf file, one for each domain. The process name for each entry has the domain name appended. Only one domain is supported for LU 6.2.`
`cwbhcmdd`	`TCP/IP version of SNA View host command server daemon, which sends commands to the mainframe host. There is an instance of cwbhcmdd for each domain.`
`cwbhmond`	`TCP/IP version of SNA View monitor/discover daemon. There is an instance of cwbhmond for each domain.`

Note The cwbhcmdd and cwbhmond TCP/IP processes are transient daemons. They are started by cwbhcid_domain_name, not by the Process Manager. Once started, their status is displayed by the Process Manager. When cwbhcid stops, these two stop as well, and disappear from the Process Manager window.

Automatic Starts and Dependencies

Depending on the selections you make during configuration, some processes are set up to start automatically when the Process Manager starts, and some processes are dependent on others.

Autostarted Processes

Depending on your configuration options, the following processes are started automatically:


`Configuration Option`	`Processes Autostarted`
`DLSw`	`cwbdlswpollerd and cwbtrapd¹ (UNIX only) start automatically.`
`RSRB`	`cwbrsrbpollerd and cwbtrapd¹ (UNIX only) start automatically.`
`TCP host connection`	`cwbhcid starts automatically. (UNIX only) If you configure an LU 6.2 host connection, you must configure the LU 6.2 transaction programs. The SNA mainframe application will then cause cwbhcid_server_domain to start.`

¹The cwbtrapd process is started only if an NMS was integrated during installation.

Dependent Processes

The following processes start only after other processes are started:


`Process`	`Depends on`
`cwbmonitord`	`(UNIX only) CWBMsgLogServer, CWBDBAdapter`
`cwbhcid cwbhcid_server_domain`	`CWBMsgLogServer, CWBDBAdapter`
`cwbsnamapsd`	`CWBMsgLogServer, CWBDBAdapter`
`cwbdlswpollerd`	`CWBMsgLogServer, CWBDBAdapter`
`cwbrsrbpollerd`	`CWBMsgLogServer, CWBDBAdapter`
`cwbtrapd`	`(UNIX only) CWBMsgLogServer, CWBDBAdapter`

Viewing the Process Management Information—Services Window

The Services window displays a list of all the Process Manager services, as shown in Figure 7-3.

Figure 7-3: Process Management Information—Services Window

Fields

The Services window contains the following fields:


`Field`	`Description`
`Name`	`Name of the service.`
`Process ID`	`Process ID of the service.`
`State`	`Current service status. The status colors are used as follows: Green means the service is currently active. Blue means the service is in its initial state and has not been started. Red means the service has been run and then stopped.`
`Last Message`	`Last message sent by the service.`

Buttons

The buttons on the Services window provide the following functions:


`Button`	`Description`
`Start`	`Starts the selected service.`
`Stop`	`Stops the selected service.`
`Stop All`	`Stops all running services.`
`Details`	`Displays the Details window for the selected service, as shown in Figure 7-4.`
`Exit`	`Stops the Process Manager client and closes the window.`
`Help`	`Displays the online help.`

Viewing the Services Details

You can see detailed information about each service. From the Services window, select a service and click Details to view the Services Details window for the selected service, as shown in Figure 7-4.

Figure 7-4: Services Details Window

Fields

The Services Details window contains the following fields:


`Field`	`Description`
`Process Name`	`Name of the Services process, as described in "Process Manager Services."`
`Description`	`Description of service.`
`Version`	`Version of the process.`
`Executable`	`Full path name for the executable file for the process.`
`Arguments`	`Command line switches for the process.`
`Autostart`	`Indicates whether the process is configured to start automatically: Yes means it will be automatically started. No means it will not be automatically started unless some other process is dependent on it. Restart means it will be automatically started and, if it stops abnormally, it will be restarted automatically. However, if you use the Process Manager to stop this process, it will not be restarted automatically.`
`Dependencies`	`Lists processes that must be running before this service can be started.`
`Timeout`	`Time that the Process Manager waits for an Initialization Complete notification from the started process.`
`StartTime`	`Date and time that the process was last started. If the process was never started, this field is 0.`
`StopTime`	`Date and time that this process was stopped. If the process is currently running, this field is 0.`
`Process ID`	`Process ID of the named process.`
`State`	`Status of the process.`
`Last Message`	`Last message sent by the process to the message log.`

Process Manager Services

The following Process Manager services can be monitored in the Services window:


`Process Name`	`Description`
`CWBMsgLogServer`	`Message log server logs messages from the Maps and SNA View applications and daemons. To view the messages, use the message log viewer (cwb start MsgLogClient).`
`CWBHTTPAdapter`	`Starts and monitors the web server.`
`CWBOSAMonitor`	`(UNIX only) Monitors the osagent process, which provides CORBA naming services.`
`CWBDBAdapter`	`Starts and monitors the database servers.`
`CWBPMMonitor`	`(UNIX only) Monitors the Process Manager server. If the Process Manager server dies, this process stops all Maps processes and restarts the Process Manager server.`

Automatic Starts and Dependencies

Depending on the selections you make during configuration, some services are set up to start automatically when the Process Manager starts, and some services are made to be dependent on others.

Autostarted Processes

The following services are started automatically when the Process Manager server starts:

CWBMsgLogServer
CWBDBAdapter
CWBHTTPAdapter

Dependent Processes

The following services start only after other processes are started:


`Process`	`Depends On`
`CWBMsgLogServer`	`Nothing`
`CWBDBAdapter`	`CWBMsgLogServer`
`CWBHTTPAdapter`	`CWBMsgLogServer`

Configuring the Process Manager

This section provides information about the different ways you can configure how the Process Manager runs.

Monitoring the Process Manager

UNIX Workstations

The CWBPMMonitor process monitors the Process Manager to ensure that it remains active. If the Process Manager is not running, the CWBPMMonitor process stops all other CiscoWorks Blue processes. It then restarts the Process Manager server which in turn starts all the other servers.

Windows NT

On a Windows NT system, use the Configuration application. For more information, see "Using CiscoWorks Blue SNA View Configuration for Windows NT."

UNIX Workstations

On a UNIX workstation, use the CWBProcessMgrWaitTime parameter in the /opt/CSCOcb/etc/cwbinit file to specify how often, in minutes, the CWBPMMonitor process wakes up to check whether the Process Manager is running. The default value is 10 minutes.

**********************************************************

# This section is used by the Process Manager monitor process, which
# monitors the state of the CiscoWorks Blue Process Manager.
# This parameter controls how often, in minutes, the CWBPMMonitor
# process wakes up and makes sure that the Process Manager process is 
# running on the system. If it is not running, this process stops
# all CWBlue processes and restarts Process Manager, which restart
# all servers.
CWBProcessMgrWaitTime = 10

On UNIX workstations, use the showWarnings parameter in the /opt/CSCOcb/etc/cwbinit file to specify whether the Verification program should issue warning messages.


********************************************************************* 
# This section is used by the Verification Utility which validates
# the CiscoWorks Blue installation.
# Flag indicating whether or not the verification utility should issue
# warnings. If "true" warnings are issued, "false" otherwise.
 
showWarnings = true

Windows NT

On a Windows NT system, use the cwb config command. For more information, see "Commands and Processes for Windows NT."

Configuring Process Manager Windows

The Process Manager is configured, during Maps or SNA View installation, to monitor the complete set of processes and to automatically start those processes that support the protocols (DLSw, APPN, and RSRB) that you want to manage. The settings that govern the Process Manager are stored in the following configuration files in /opt/CSCOcwbC/etc:

CWBlue.conf contains the settings for monitoring processes common to both Maps and SNA View.
Services.conf contains the settings for monitoring services, such as the message log server.

UNIX Workstations

Normally you would not need to make any changes in these configuration files. However, you might want to change selected default values (such as the Autostart value) or process dependencies.

The CWBlue.conf configuration file contains entries that describe the Maps and SNA View processes to be monitored and managed by the Process Manager. The Services.conf file contains entries that describe the Process Manager services to be monitored and managed by the Process Manager. Each file is made up of a series of entries, one for each process or service. Each entry is in the following format:

process_name autostart? dependencies executable arguments time_out

The entry contains the following fields:


`Entry`	`Description`
`process_name`	`Name of the process or service.`
`autostart?`	`Indicates whether the process is to start automatically: Y means it is started automatically. Process Manager will try to autostart this process once. N means it is not started automatically. R means it is started automatically and, if it is killed, it is restarted automatically. Process Manager tries to autostart this process for some period. However, if you use Process Manager to stop this process, it is not restarted automatically.`
`dependencies`	`One or more process names separated by commas (,). Each dependent process in the list must be started before the subject process is started. If there are no dependencies, use one hyphen (-) as a place holder.`
`executable`	`Complete directory path and executable command.`
`arguments`	`Set of command-line arguments (switches) and their associated values separated by commas (,) that the Process Manager will use to start the process.`
`time_out`	`Time the Process Manager waits for a notification from the application. When the time expires, the Process Manager does not change the starting state. It reports a timeout error.`

Sample CWBlue.conf File

The following sample CWBlue.conf file shows the file contents after you install CiscoWorks Blue:

# The Process Manager Configuration File for Maps/SNAView processes.
# Each line contains 6 tokens separated by spaces
 
# Format:
# process_name AutoStart Dependencies Executable Args TimeOut
 
# process_name :Name of the process
 
# autoStart :(Y/N) Whether ProcessManager should automatically
# [re]start this process
 
# Dependencies :(A list of process_name each separated by ',')
# Each process in the list has to be started before the particular # # # process can be started. If there are no dependencies, a single '-' 
# is used.
 
# Executable :Complete path to the executable representing the process
 
# Args :Arguments to the process, separated by ',' ; If no arguments # # are required, a '-' should be specified.
 
# TimeOut :(timeout value) The time in seconds, until which the PM 
# waits for a 'InitializationComplete' notification from the 
# started process). Once it receives the notification, the state of 
# the process is moved from starting->Ready.

UNIX Workstations

cwbmonitord N CWBMsgLogServer,CWBDBAdapter /opt/CSCOcb/etc/runprocess cwbmonitord 30 cwbhcid_MVSD R CWBMsgLogServer,CWBDBAdapter /opt/CSCOcb/etc/runprocess cwbhcid_MVSD,MVSD 30 cwbsnamapsd R CWBMsgLogServer,CWBDBAdapter /opt/CSCOcb/etc/runprocess cwbsnamapsd 30 cwbdlswpollerd R CWBMsgLogServer,CWBDBAdapter /opt/CSCOcb/etc/runprocess cwbdlswpollerd 30 cwbrsrbpollerd R CWBMsgLogServer,CWBDBAdapter /opt/CSCOcb/etc/runprocess cwbrsrbpollerd 30

Windows NT

cwbmonitord N CWBMsgLogServer,CWBDBAdapter c:/PROGRA~1/CISCOW~1.0/CSCOcb/etc/runprocess cwbmonitord 30 cwbhcid_MVSD R CWBMsgLogServer,CWBDBAdapter c:/PROGRA~1/CISCOW~1.0/CSCOcb/etc/runprocess cwbhcid_MVSD,MVSD 30 cwbsnamapsd R CWBMsgLogServer,CWBDBAdapter c:/PROGRA~1/CISCOW~1.0/CSCOcb/etc/runprocess cwbsnamapsd 30 cwbdlswpollerd R CWBMsgLogServer,CWBDBAdapter c:/PROGRA~1/CISCOW~1.0/CSCOcb/etc/runprocess cwbdlswpollerd 30 cwbrsrbpollerd R CWBMsgLogServer,CWBDBAdapter c:/PROGRA~1/CISCOW~1.0/CSCOcb/etc/runprocess cwbrsrbpollerd 30

Sample Services.conf File

The following sample Services.conf file shows the file contents after you install CiscoWorks Blue:

CWBMsgLogServer R - /opt/CSCOcwbC/bin/CWB_msgLogServer -MLCname,CWBMsgLogServer,-N,CWBMsgLogServer,-PMCname,CWBMsgLogServer,-
MLCserverName,CWBMsgLogServer,-F,cwblogger.log,-P,/opt/CSCOcb/logs,-PMCserverName,CWBProcessMgr,-ORBagentPort,44542

UNIX Workstations

CWBDBAdapter R CWBMsgLogServer /opt/CSCOcb/etc/runprocess CWBDBAdapter 100 CWBHTTPAdapter R CWBMsgLogServer /opt/CSCOcb/etc/runprocess CWBHTTPAdapter 70 CWBOSAMonitor R CWBMsgLogServer /opt/CSCOcb/etc/runprocess CWBOSAMonitor 50 CWBPMMonitor Y CWBMsgLogServer /opt/CSCOcb/etc/runprocess CWBPMMonitor 50

Windows NT

CWBDBAdapter R CWBMsgLogServer c:/PROGRA~1/CISCOW~1.0/CSCOcb/etc/runprocess CWBDBAdapter 100 CWBHTTPAdapter R CWBMsgLogServer c:/PROGRA~1/CISCOW~1.0/CSCOcb/etc/runprocess CWBHTTPAdapter 70 CWBOSAMonitor R CWBMsgLogServer c:/PROGRA~1/CISCOW~1.0/CSCOcb/etc/runprocess CWBOSAMonitor 50 CWBPMMonitor Y CWBMsgLogServer c:/PROGRA~1/CISCOW~1.0/CSCOcb/etc/runprocess CWBPMMonitor 50

Changing Maps Processes and Services

After you make changes to the Services.conf or CWBlue.conf configuration file, you must activate those changes by stopping and restarting the Process Manager server, as described in "Starting the Process Manager." The Process Manager restarts, starting any processes specified as autostart in the changed configuration file.

Restarting the Process Manager

Use the following information for the different ways you can start the Process Manager servers and client on Unix Workstations and windows NT systems.

Process Manager Server

UNIX Workstations

After you stop the Process Manager server, you can restart it from the command line using the following commands:

/opt/CSCOcb/bin/cwb start pm

Windows NT

From a Console window, enter the following:

install_directory\CSCOcb\bin\cwb start pm

: Where:
: install_directory is the directory in which you installed the product.

Process Manager Client

UNIX Workstations

Restart the Process Manager client from the command line using the following command:

/opt/CSCOcb/bin/cwb start ProcMgrClient

Windows NT

Select Start > Programs > CiscoWorks Blue > PM Client
From the taskbar icon, select PM Client.
From a Console window, enter the following:

install_directory\CSCOcb\bin\cwb start ProcMgrClient

: Where:
: install_directory is the directory in which you installed the product.

In Windows NT systems, you can also restart the Process Manager server or client from the start menu and from the CiscoWorks Blue taskbar icon.

Changing Process Manager Properties

You can edit the Process Manager properties file to change Process Manager properties.

Unix Workstations

The file is /opt/CSCOcwbC/classes/com/cisco/AM/conf/kubit/process/
displayMain.properties.

Windows NT

The file is install_directory\CSCOcwbC\classes\com\cisco\AM\conf\kubit\process\
displayMain.properties

Where:

install_directory is the directory in which you installed the product.

You can change the following values:


`Value`	`Meaning`
`WriteAccess`	`true—Runs the Process Manager client in read/write mode so that the Process Manager client can display processes and can start or stop processes. false—Forces the Process Manager client into read-only mode so that the Process Manager client can display processes, but cannot start or stop processes.`
`PromptUser`	`true—Prompts the user when stopping Process Manager. false—Suppresses the prompt when stopping Process Manager.`

Table of Contents

Using the Process Manager

Autostarted Processes

Dependent Processes

Autostarted Processes

Dependent Processes