You can set system properties to change the default Orchestrator behavior. What to read next Setting Server File System Access for Workflows and ActionsIn Automation Orchestrator, the workflows and actions have limited access to specific file system directories. You can extend access to other parts of the server file system by modifying the js-io-rights.conf configuration file. Set Access to Operating System Commands for Workflows and ActionsThe Automation Orchestrator API provides a scripting class, Command, that runs commands in the Automation Orchestrator server host operating system. To prevent unauthorized access to the server host, by default, Automation Orchestrator applications do not have permission to run the Command class. If Automation Orchestrator applications require permission to run commands on the host operating system, you can activate the Command scripting class. Set JavaScript Access to Java ClassesBy default, Automation Orchestrator restricts JavaScript access to a limited set of Java classes. If you require JavaScript access to a wider range of Java classes, you must set an Automation Orchestrator system property. Set Custom Timeout PropertyWhen vCenter is overloaded, it takes more time to return the response to the Automation Orchestrator server than the 20000 milliseconds set by default. To prevent this situation, you must modify the Automation Orchestrator configuration file to increase the default timeout period. Adding a JDBC connector for the Automation Orchestrator SQL plug-inThis example demonstrates how you can add a MySQL connector for the Automation Orchestrator SQL plug-in. Set Scheduled Task and Policy Authentication Token Renewal PropertyManage how you can enable the renewal of the authentication tokens used in scheduled tasks or policies by setting a system property. Activating basic authenticationYou can activate basic authentication for your Automation Orchestrator deployment by setting a system property.
