The recovery script will depend on the desired action and will need to be developed based on the user's specific environment. After the agent-side script is written, the Uptime Infrastructure Monitor agent will need to be configured to execute it. As a minimum, configure the following settings for each agent-side command:
\\
!worddav4751b8e51cd0dc242a5fed679ed122c4.png|height=4,width=4! For agents running on non-Windows systems, define a password and command pair in the agent-side password file by completing the following steps:
Ensure that a file named .uptmpasswd is created in the Uptime Infrastructure Monitor agent bindirectory (either /opt/SPYNuptm/bin/ or
/opt/uptime-agent/bin depending on the agent version). This file must be owned and readable by the user that the agent is run as. Open the .uptmpasswd file in a text editor.
Enter a password and command pair for each command that you want to run on the agent system. The following is an example format and contents of an agent-side command script:
*Format{*}: \[password\] \[command path, no arguments\]

The next step is to write a monitoring station script that will attempt to execute your agent-side script so the action profile can perform the task based on the script's output. The monitoring station script can be written in any language and format provided that it adheres to these general rules:
!worddav8161d869a94537873eda7e99815b9d1c.png|height=4,width=4! The script must exit with a success status (i.e. no errors during the execution).
!worddav9ac74e1d248b168d4ebbe04842f8e2ef.png|height=4,width=4! The script must accept the host name of the agent system as the third argument (Uptime Infrastructure Monitor will automatically add this argument to the arguments that are passed to the script).
In most cases the monitoring station script will contact an agent system and attempt to run a pre-defined agent-side script. You can use any transport tool (e.g. rexec, rsh or ssh) to contact the agent system. However, we recommend using the bundled agentcmd or netcat utility to contact your agent systems from your monitoring station script.
\\
The agentcmd utility is commonly called in the format listed below to execute a command on the agent-side system. The following example uses the settings that were configured above to execute the agent-side script:
!worddav9ac74e1d248b168d4ebbe04842f8e2ef.png|height=4,width=4! Format: /usr/local/uptime/scripts/agentcmd \[-s/+s\] -p \[agent port\] \[agent hostname\] rexec \[password\] \[path\]
!worddav8161d869a94537873eda7e99815b9d1c.png|height=4,width=4! Example: /usr/local/uptime/scripts/agentcmd my-agent -p 9998 rexec secretpassword /opt/uptime-agent/my-scripts/show_temp.sh my-arguments !worddav9ac74e1d248b168d4ebbe04842f8e2ef.png|height=4,width=4! For more information on agentcmd syntax, see [<span style="color: #0052cc">Using the agentcmd utility.</span>|http://docs.uptimesoftware.com/display/KB/Using%2Bthe%2Bagentcmd%2Butility]
The netcat utility is commonly called in the format listed below to execute a command on the agent-side system. This example uses the settings that were configured above to execute the agent side script:
!worddav9ac74e1d248b168d4ebbe04842f8e2ef.png|height=4,width=4! Format: echo -n rexec \[password\] \[path\] | /usr/local/uptime/bin/netcat \[agent hostname\] \[agent port\]
!worddav9ac74e1d248b168d4ebbe04842f8e2ef.png|height=4,width=4! Example: echo -n rexec secretpassword /opt/uptime-agent/my-scripts/show_temp.sh my-arguments | /usr/local/uptime/bin/netcat my-agent 9998 !worddav8161d869a94537873eda7e99815b9d1c.png|height=4,width=4! Note: the rexec text above does not indicate use of the rexec system utility, it is simply a key word used to indicate to the agent that you are
attempting to run a pre-defined command.
For monitoring stations running on Windows: