GPA: Plugin for OS Command With Solution Manager 7.1

Transcription

1 GPA: Plugin fr OS Cmmand With Slutin Manager 7.1 The plugin OS Cmmand can be used in yur wn guided prcedures. It ffers the pssibility t execute pre-defined perating system cmmand n each hst part f the selected managed bject. This guided prcedure plugin is an extensin f the existing OS Cmmand Cnsle applicatin. Availability Slutin Manager 7.1 SP10 and higher Dcument versin Versin

2 Table f Cntents Overview... 3 Use case... 3 Required Managed bjects... 3 Pre-requisites... 3 Design Time... 4 Runtime View... 5 Overview... 5 Executin Flw Example... 6 Step 1 Adjust executin status... 6 Step 2 - OS Cmmand Executin... 6 Step 3 - OS Cmmand Output Analysis... 7 Step 4 - OS Cmmand Lgs... 8 Cpyright/Trademark

3 OVERVIEW Use case With GPA plugin OS Cmmand, fllwing peratin can be perfrmed n managed system: Check if a specific OS prcess is running r is stpped Check file system remaining space Check netwrk utilizatin Here are all cmmands available gruped by categry: Categry Netwrk System Envirnment FileSystem Cmmand NetStat IPCnfig Ping Tracert TaskList DateTime CpuStat MemStat DiskStat PrcessStat Set Ech Df (Unix nly) Required Managed bjects Any managed bject that is referencing a hst can be used in scpe (ABAP Technical System, Database ) Pre-requisites Fllwing pre-requisites are necessary t execute GPA Plugin OS Cmmand: All hsts references by the managed bject shuld have diagnstics agents up and running. Cpyright/Trademark

4 DESIGN TIME During design time, fllwing pre-defined parameters can be set thse parameters will be used by default during runtime. Grup OS cmmand are rganized per grup fr classificatin (refer t sectin Use Case t have cmplete list). Cmmand OS cmmand t be executed n the managed system hst. This cmmand name is nly an alias name as defined within the OS Cmmand applicatin The OS cmmand triggered n the system will depend n the perating system type (windws r Unix). Example:TaskList Windws: tasklist Unix: ps a The OS prcess cmmand definitin can be fund within SMD Agent Administratin Applicatin Applicatin Cnfiguratin agelet cm.sap.smd.agent.applicatin.remtes Applicatin Resurces cmmands.xml Parameters Any additinal parameter t be passed t the selected s cmmand, can be entered in this field. Cpyright/Trademark

5 RUNTIME VIEW Overview At runtime, when the guided prcedure is started the selected cntext is passed t the plugin and all hsts part f the managed bject are displayed within table view. The displayed view cntains fllwing infrmatin: Cntext: name f the managed bject mre than ne managed bject can be passed t this GP plugin. Hst: all hsts part f this managed bject. Agent Status: the s cmmand will be triggered by the diagnstics agent assigned t the respective hst it has t be up and running. OS Cmmand/Parameter: OS cmmand and parameter t be executed n managed hst as defined during design time. OS Cmmand Output: display the utput f the triggered OS cmmand. Cmment: allws adding cmment t the generated utput f the OS cmmand. Example: NetStat is triggered n the managed system The peratr identify a high netwrk usage within the OS cmmand utput The peratr can add wn cmment t emphasis the high netwrk usage. Open URL: Jump-in link t the OS Cmmand applicatin. Executin Status: can be used t cntrl the executin f the OS Cmmand available ptins are: Execute: the cmmand will be executed n the managed hst Pstpned: the cmmand will nt be executed n the managed hst shuld be used if the diagnstics agent is nt running and yu dn t want t reprt an exceptin. Manually Perfrmed: the cmmand is triggered but whatever the rating is returnedby the OS cmmand executin, yu want t reprt a green status. Manually perfrmed with errr: the cmmand is triggered but whatever rating is returned by the OS cmmand executin, yu want t reprt a red status. Cpyright/Trademark

6 Executin Flw Example Step 1 Adjust executin status As already described abve, sme diagnstics agent may be unavailable in such case the first step is t adjust executin status if necessary in rder t nt execute the OS cmmand. Example: Ldai1sd7: Diagnstics agent is up and running and we want t execute the OS cmmand Executin status is set t Execute. Ldai2sd7: Diagnstics agent is dwn and we want t reprt the errr Executin status is set t Execute Ldcisd7: Diagnstics agent is dwn but we d nt want t execute the OS cmmand Executin status is set t Pstpned. Step 2 - OS Cmmand Executin Once the executin status is defined fr each hst we may trigger the OS cmmand n all hsts. A new clumn displayed the status f the OS cmmand executin: Green: the OS cmmand is executed successfully n managed hst Red: the OS cmmand is executed with errr n managed hst. Example: Ldai1sd7: df cmmand has been executed successfully and the result can be displayed with the View link Cpyright/Trademark

7 Ldai2sd7: df cmmand cannt be executed n managed system SMD Agent nt running errr is reprted. Ldai1sd7: df cmmand executin is skipped and reprted status is gray. Step 3 - OS Cmmand Output Analysis Once the OS cmmand has been executed n the managed hsts the peratr may need t analyze the utput f each cmmand. Example: Ldaisd7: The peratr is identifying that 2 disks are used at 100% The peratr can add cmment and edit utput t remve unnecessary infrmatin As the peratr fund an issue n disk space he can set the executin status Manually Perfrmed with Errrs. And save the result. The status f the cmmand is nw updated t red. Cpyright/Trademark

8 Step 4 - OS Cmmand Lgs Once saved all changes perfrmed by the peratr are stred with the Lg sectin The Shw link available within the Details clumn displays mre infrmatin. Cpyright/Trademark