Variables for Windows Script Monitor

Hi people,

I've wrote a little VBS script to test TNSPing times for our Oracle databases. The script itself is not that important, but it must take the Oracle SID as its argument to perform the TNS ping operation on the SID.

However, it seems that the Windows Script Monitor does not support any variables other than ${IP}, ${USERNAME} and ${PASSWORD}, am I correct? I've tried to put ${NodeName} and ${Caption} as parameters and they were not translated, differently from ${IP} which translates correctly each time I test it on the Web interface. However, I can't TNSPing IP address but only Oracle SIDs.

Here we run Orion 9.1 SP5 and APM 2.5.

TIA,

Paulo Fessel

Find more posts tagged with

oracle_sid

tnsping

vbscript

Accepted answers

Yann

Hi,

Only ${IP}, ${USER} and ${PASSWORD} variables are automatically populated, you are correct about this.

You could define the other variables you need statically in the script arguments and then catch them with code such as below at the top of your script:

OracleSID1 = wscript.arguments(0)

OracleSID2 = wscript.arguments(1)

etc.

Creating a Windows Script Monitor

HTH,

Yann

All comments

Yann

Hi,

Only ${IP}, ${USER} and ${PASSWORD} variables are automatically populated, you are correct about this.

You could define the other variables you need statically in the script arguments and then catch them with code such as below at the top of your script:

OracleSID1 = wscript.arguments(0)

OracleSID2 = wscript.arguments(1)

etc.

Creating a Windows Script Monitor

HTH,

Yann

aLTeReGo

The following additional macros are now available in the SAM 6.0 RC (available now)

${USER}
${PASSWORD}
${PORT}
${Node.SysName}
${Node.Caption}
${Node.DNS}
${Node.ID}
${Component.ID}
${Component.Name}
${Application.Id}
${Application.Name}
${Application.TemplateId
${Threshold.Warning}
${Threshold.Critical}
Node Custom Property Macros ${Node.CustomPropertyName}
Application Custom Property Macros ${Application.CustomPropertyName}