Resolution
What is the difference between the various service-related bounce scripts and how do I configure them?
fix
The answer to the question is contained in the following questions and answers:
- What is the Service Bounce script?
- What is the difference between the Service Bounce and the Service Bounce Asynchronous script?
- What is the Service Shutdown script?
- What is the Service Start or Continue script?
- If a service dies on its own, will it be detected?
- How do I control how many times a script attempts to restart a service?
- I see no way to get script files into the product except cut-and-paste. Is there some way to import a script file? Do I have to use the ScriptContext object which is only available when the script is running in the product?
- What is the Custom option in creating a new script? What type of scripts can be written?
This is a script designed to stop and restart a service. NOTE: The parameters for any script should always be edited from within a rule at the 'response' tab, and not from the global configuration location at Rules|Advanced|Scripts. Editing parameters in the global configuration location edits the script parameters for all rules that may be associated to it. The Service Bounce parameters available for configuration are 'ServiceName', 'ComputerName', 'NumSecsBetweenRetries" (number of seconds between retries), and 'NumAttempts' (number of times to retry bounce if it fails).
The Service Bounce Asynchronous script stops a service, then starts it again, in a separate process, whereas the Service Bounce stops and restarts the service, but not in a separate process.
This is a script that causes a service to be stopped. Available parameters are 'ServiceName', 'ComputerName', 'NumSecsBetweenRetries" (number of seconds between retries), and 'NumAttempts' (number of times to retry shutdown if it fails).
This is a script that causes a service to start or will continue a service that is stopped or paused respectively. Available parameters are 'ServiceName', 'ComputerName', 'NumSecsBetweenRetries" (number of seconds between retries), and 'NumAttempts' (number of times script will attempt to start running the specified NT service).
Only if the Service Control Manager (SCM) detects the change in condition. When a service is stopped or started, values are normally changed in the registry to reflect its status. Our Service Check Status script reads these values and uses them to detect a change in their state. An event is generated and can be used to signal a response, such as the use of a service start/stop script.
Edit the script parameters for 'NumSecsBetweenRetries" (number of seconds between retries), and 'NumAttempts' (number of times to retry bounce if it fails). You can also use the Service Check Status script to verify the status of a service, then deploy one of the other Service scripts if need be to restart/continue it or shut it down.
Use your favorite text or program editor (such as Visual Basic 6.0) to create (but not necessarily test) the finished script. Some testing can be done by running the script at the Command Prompt using Cscript or Wscript. However, objects that are intrinsic to OnePoint (ScriptContext) cannot be called from outside the OnePoint Process. When the script is complete, paste it into Operations Manager and finish testing within Operations Manager.
The only scripting languages that are supported include Visual Basic and Java. The custom option was added so that you could use another ActiveScripting compliant language. By choosing custom and putting a #!Language at the top of the script you can theoretically run a different scripting language. We have not, however, tested Operati.
ons Manager with scripts other than Visual Basic.