Академический Документы
Профессиональный Документы
Культура Документы
The plugin OS Command can be used in your own guided procedures. It offers the possibility to
execute pre-defined operating system command on each host part of the selected managed
object. This guided procedure plugin is an extension of the existing OS Command Console
application.
Copyright/Trademark
OVERVIEW
Use case
With GPA plugin OS Command, following operation can be performed on managed system:
Check if a specific OS process is running or is stopped
Check file system remaining space
Check network utilization
Pre-requisites
Following pre-requisites are necessary to execute GPA Plugin OS Command:
All hosts references by the managed object should have diagnostics agents up and running.
Copyright/Trademark
DESIGN TIME
During design time, following pre-defined parameters can be set – those parameters will be used by default
during runtime.
Group
OS command are organized per group for classification (refer to section Use Case to have complete
list).
Command
OS command to be executed on the managed system host. This command name is only an alias
name as defined within the OS Command application – The OS command triggered on the system
will depend on the operating system type (windows or Unix).
Example:TaskList – Windows: “tasklist” – Unix: “ps –a”
The OS process command definition can be found within SMD Agent Administration Application
Application Configuration agelet – com.sap.smd.agent.application.remoteos Application
Resources commands.xml
Parameters
Any additional parameter to be passed to the selected os command, can be entered in this field.
Copyright/Trademark
RUNTIME VIEW
Overview
At runtime, when the guided procedure is started – the selected context is passed to the plugin and all hosts
part of the managed object are displayed within table view.
Copyright/Trademark
Execution Flow Example
Step 1 – Adjust execution status
As already described above, some diagnostics agent may be unavailable – in such case the first step is to
adjust execution status if necessary – in order to not execute the OS command.
Example:
Ldai1sd7: Diagnostics agent is up and running and we want to execute the OS command –
Execution status is set to Execute.
Ldai2sd7: Diagnostics agent is down and we want to report the error – Execution status is set to
Execute
Ldcisd7: Diagnostics agent is down but we do not want to execute the OS command – Execution
status is set to Postponed.
Example:
Ldai1sd7: df command has been executed successfully and the result can be displayed with the
View link
Copyright/Trademark
Ldai2sd7: df command cannot be executed on managed system – SMD Agent not running error is
reported.
Example:
Ldaisd7:
o The operator is identifying that 2 disks are used at 100%
o The operator can add comment and edit output to remove unnecessary information
o As the operator found an issue on disk space – he can set the execution status Manually
Performed with Errors.
o And save the result. The status of the command is now updated to red.
Copyright/Trademark
Step 4 - OS Command Logs
Once saved – all changes performed by the operator are stored with the Log section
The Show link available within the Details column displays more information.
Copyright/Trademark