Launching remote actions

From the BMC ProactiveNet Infrastructure Management interface, you can use right-click pop-up menus to run actions on components and applications that are running on remote systems.

Before you begin, you must have a registered cell component installed on a remote system.

To launch remote actions

1. Right-click the child component under a BMC ProactiveNet Service Impact Management Cell or BMC ProactiveNet Event Management Cell to select a cell residing on a remote system.

2. Choose Actions to display a list of all possible actions for that component.
   
   

    

3. Choose Stop Cell Server Process, click Stop, and enter the logon credentials for the remote system.
   
   If the selected component resides on an Microsoft Windows system, your logon credentials should have administrative rights to the system. The Additional Command Credentials are needed check box is disabled.
   
   When the component on the remote system has stopped, its status changes to Unavailable.
4. Return to the BMC ProactiveNet Infrastructure Management interface, right-click the cell component to display the pop-up menu, and select Actions> Start Cell Server Process.
5. Verify that the cell has started. For example, you can run an mcstat command to check the status of the cell. Verify that the status of the selected component is changed to OK.
6. Repeat steps 1 through 5 for a BMC ProactiveNet Server component, such as publishing server or IBRSD.
   The actions permitted on the server component are limited to Stop Process and Start Process only.
   
   You can also launch remote actions for selected components by clicking one of the Action toolbar icons of the BMC ProactiveNet Infrastructure Management view.
   
   Depending on the type and state of the selected component, you can select from the following actions: 
   • Start Cell Server Process (Start) 
   • Stop Cell Server Process (Stop) 
   • Restart Cell Server Process (Restart) 
   • Pause Events Admittance (Pause) 
   • Resume Events Admittance (Resume) 
   • Set to Active 
   • Set to Standby

Different actions are enabled based on the status and type of component. For example, if a component in an unknown state is already started and you select Actions > Start, you receive a status message notifying you that the component is started already. For more information, see Remote-actions.