Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Server & Application Monitor (SAM) > Configure Windows Script Monitor

Configure Windows Script Monitor

Table of contents
Created by Chris Foley, last modified by Rodim Suarez on Jul 12, 2016

Views: 80 Votes: 1 Revisions: 2

Updated

Overview

This article aims to explain what is needed to interpret different script languages and how to configure Windows Script Monitor to use these.

Environment

  • All SAM versions
  • Windows systems

Steps

Requirements to be installed on the system hosting the Orion Poller:

vbScript

  • None.  Included with Windows.

JScript

  • None.  Included with Windows.

Perl:

Python:

 

To test:

  1. On the system hosting the Orion Poller, open a CMD prompt.
  2. Type the following command:
    cscript //E:{Interpreter} {Script Path and Filename}

    Examples: 

    cscript TestScript.vbs

    cscript //E:Python TestScript.py

    cscript //E:PerlScript TestScript.pl

  3. If the command fails, the interpreter is not installed correctly. Consult the manufacturer of the interpreter.
  4. If the command succeeds, specify the {Interpreter} value used in the command, as the "Script Engine" value within the Windows Script Monitor.

 

Note: If the 32-bit version of the interpreter is installed, make sure to set the platform within the Application's Settings page to x86.  On the other hand, if the 64-bit version of the interpreter is installed, make sure to set the platform within the Application's Settings page to x64.

 

Last modified
16:51, 12 Jul 2016

Tags

Classifications

Public