The Axeda® Platform will not run Groovy scripts (or any other scripts) that may harm the Platform or its performance. The Platform will detect and then not run scripts with the following definitions:
o The script is defined to access restricted classes, packages or methods (from the Axeda® SDK or a third-party library)
o The script is defined to loop without interruption
o The script is defined to handle exceptions to loop interruptions, security violations, or errors
If it stops running a script due to a security violation, the Platform will generate information to the log file for custom objects and to the Audit log. You can view the customobjects.log file from the View and manage custom objects page (Axeda® Configuration application - View menu). For example, if your custom script attempts to access a restricted package, class, or method, the log file will identifies the exception.
To ensure that your scripts are supported and will run as expected, make sure you test your custom object before defining it in the Configuration application for runtime operations. If it determines that your script is defined to access a restricted object, the Platform creates an exception. The test output identifies the class name and method name that triggered the exception.
The Axeda® Platform note, "Available APIs from Custom Object Scripts", details which Axeda API and Web services, and which 3rd party API are supported for Axeda Custom Objects.
Restricted services
Depending on how the Security policy for the Platform is configured, custom objects may have limited or no access to the Axeda Web services. Again, if a custom object attempts to access a web service to which it doesn't have access (because of the security policy restrictions), the Platform will return an HTTP 403 (Forbidden) Error.
For complete details about your Platform's security policy, contact your local Platform administrator.