Initiating remote actions on components from the administrator console
How context-sensitive remote actions are processed
The current state of a selected component is shown in its run_state slot (Run State), which you can view in the Details > General tab in the Infrastructure Management Infrastructure Management tab. The different run_state values are described in the following table:
run_state values for components
run_state value | Description |
|---|---|
unknown | State of the component cannot be determined |
active | Indicates that the cell is the active server component of a high-availability relationship |
unavailable | The connection with the component is disrupted or the component is down |
started | The component is online; unable to determine whether it's the active component in an HA relationship |
stopped | The component has sent is stopped and has sent a status event indicating that it is stopped |
paused | The component is in maintenance mode |
passive | The secondary cell in an HA relationship is in standby mode |
The current run_state of the component determines which context-sensitive actions are disabled or enabled from the Actions option on the right-click menu.
The following table indicates which menu options are enabled (Yes) or disabled (blank) for each run_state of a normal cell or a primary cell in an high-availability configuration.
Component state and menu options for a normal or primary cell in a high-availability configuration
| Menu options | ||||||
|---|---|---|---|---|---|---|---|
run_state | Start Cell Server Process | Stop Cell Server Process | Restart Cell Server Process | Pause Events Admittance | Resume Events Admittance | Set to Standby | Set to Active |
state_unknown | Yes |
|
|
|
|
|
|
state_active |
| Yes | Yes | Yes |
|
|
|
state_unavailable | Yes |
|
|
|
|
|
|
state_started |
| Yes | Yes | Yes |
|
|
|
state_stopped | Yes |
|
|
|
|
|
|
state_paused |
| Yes | Yes |
| Yes |
|
|
state_passive | None | None | None | None | None | None | None |
The following table indicates which menu options are enabled (Yes) or disabled (blank) for each run_state of a secondary cell in an High Availability configuration.
| Menu options | ||||||
|---|---|---|---|---|---|---|---|
run_state | Start Cell Server Process | Stop Cell Server Process | Restart Cell Server Process | Pause Events Admittance | Resume Events Admittance | Set to Standby | Set to Active |
state_unknown | Yes |
|
|
|
|
|
|
state_active |
| Yes | Yes | Yes |
| Yes |
|
state_unavailable | Yes |
|
|
|
|
|
|
state_started |
| Yes | Yes | Yes |
|
|
|
state_stopped | Yes |
|
|
|
|
|
|
state_paused |
| Yes | Yes |
| Yes |
|
|
state_passive |
| Yes | Yes |
|
|
| Yes |
Exceptions
Generally, most component objects receive the actions Start, Stop, Restart, Pause, and Resume.
For cell servers, the Start, Stop, and Restart menu options in the Actions submenu are described as:
- Start Cell Server Process
- Stop Cell Server Process
- Restart Cell Server Process
For other objects other than cell servers, the Start, Stop, and Restart menu options in the Actions submenu are described as: - Start Process
- Stop Process
- Restart Process
Different actions are available for different types of components. The following table lists the main exceptions:
Components and actions
Component | Exception |
|---|---|
High Availability (HA) cell | All actions. The HA cell is the only component that allows the Set to Standby and Set to Active menu options. |
Infrastructure Management Server | Receives the Restart action only. |
Publishing Server | Receives the Start and Stop actions. |
Integration for BMC Remedy Service Desk (IBRSD) | Receives the Stop and Start options. |
normal cell | Receives the Stop, Start, Restart, Pause Events Admittance, and Resume Events Admittance options. |