Introscope uses the Rhino JS Engine (Rhino - Mozilla | MDN).
Beyond that, you will only have access to features exposed by Introscope to Rhino.
Why not just add your configurations as global variables in the script?
Thank you for this information. With Rhino this works great. As reference for other people, have a look at: Tutorial: Embedding Rhino - Mozilla | MDN
> Why not just add your configurations as global variables in the script?
Thank you again,
Calculators can be deployed to the MOM, which will then distribute to Collectors, so there's no complicated replication needed.
Calculators can be hotdeployed, so no need to restart to apply.
Also, because Introscope uses Rhino, you have access to the java.io.* packages and classes to do any file reading or writing, should you choose.
Yep, just remember that all of your actions must be completed in the timeframe that the script is executed.