System Properties are special attributes that give users the ability to change Orchestrator internal system behavior directly by modifying\adding those properties from the Control Centre. These properties are basically part of a configuration file in Orchestrator. In this post, we will some of the important system properties that can help you to enhance your Orchestrator experience.
Process of adding these properties will be same as mentioned below. You don’t really have to add them until needed.
List of System Properties
Usage | Description | Key | Value (example) |
---|---|---|---|
Set the number of vAPI Metamodels | This property will set the number of the vAPI metamodels that can be added from Orchestrator vAPI Plug-in. Adding more that 20 may use excessive memory and cause instability | vapi.metamodels.count | 20 (default) |
Enable safe mode | If safe mode is enabled, all running workflows are canceled and are not resumed on the next Orchestrator node start. | ch.dunes.safe-mode | false |
Number of concurrent running workflows | The number of workflows that run simultaneously. | com.vmware.vco.workflow-engine.executors-count | 300 |
Maximum amount of running workflows in the queue | The number of workflow run requests that the Orchestrator server accepts before becoming unavailable. | com.vmware.vco.workflow-engine.executors-max-queue-size | 10000 |
Maximum number of preserved runs per workflow | The maximum number of finished workflow runs that are kept as history per workflow. If the number is exceeded, the oldest workflow runs are deleted. | ch.dunes.task.max-workflow-tokens | 100 |
Log events expiration days | The number of days that log events are kept in the database before they are purged. | com.vmware.o11n.log-events-expiration-days | 15 |
Set JavaScript Access to Java Classes | Allow the JavaScript engine full access to the Java virtual machine (JVM) | com.vmware.scripting.rhino-class-shutter-file | vco/usr/lib/vco/your_configuration_file_subdirectory |
Adding a JDBC Connector for the vRealize Orchestrator SQL Plug-In | Provides the path to the JDBC connector | o11n.plugin.SQL.classpath | /var/run/vco/plugins/SQL/lib/your_mysql_connector.jar |
Set Custom Timeout Property | The number of milliseconds Orchestrator will wait for the response from vCenter | com.vmware.vmo.plugin.vi4.waitUpdatesTimeout | 30000 |
Access to Operating System Commands for Workflows and Actions | Grant permission to use the Command class | com.vmware.js.allow-local-process | true |
Scheduled Task and Policy Authentication Token Renewal | To make sure that the scheduled workflows or policies in the Orchestrator deployment continue running even after eight hours | com.vmware.o11n.auth.csp.renewTokens | true |
Enables Basic Authentication | enables basic authentication in Orchestrator for Multi-Node plugin and REST API. | com.vmware.o11n.sso.basic-authentication.enabled | true |
Purge workflow tokens at set interval | The cron syntax to purge/delete workflow tokens automatically, changes the frequency of purging | com.vmware.o11n.purge.execution.cron | 0 0/5 * * * ? |
Enable Workflow Profiler in the vRealize Orchestrator Client | Enables profiler service to gather useful metric data about your workflow runs | com.vmware.vro.extensions.profiler.enabled | true |
Enable Profiler for Every Workflow Run | After you enable the Profile all workflow runs option, Workflow Profiler will generate statistics for every workflow run | com.vmware.o11n.extensions.profiler.profile-all-workflow-runs | true |
Enable Profiler for Scripting API | Should the profiler record metrics for scripting API calls | com.vmware.o11n.extensions.profiler.record-scripting | true |
Enable Profiler for Action Runs | Should the profiler record metrics for standalone action runs | com.vmware.o11n.extensions.profiler.record-action-runs | true |
Enable TokenReplay | enables tokenreplay service by setting it to true | com.vmware.vro.extensions.tokenreplay.enabled | true |
Record token replay for all workflow runs | After you enable the TokenReplay, it will record for every workflow run | com.vmware.o11n.extensions.tokenreplay.record-all-workflow-runs | true |
Record scripting API calls | it will record for every Scripting API call | com.vmware.o11n.extensions.tokenreplay.recordScripting | true |
Procedure to add in Orchestrator
- Log in to Control Center as root.
- Click System Properties.
- Click New.
- In the Key text box, enter property.name (for eg.
com.vmware.o11n.auth.csp.renewTokens
). - In the Value text box, enter
value
(for eg. true). - In the Description text box, enter a description for the system property.
- Click Add.
- Click Save changes from the pop-up menu. A message indicates that you have saved successfully.
- Wait for the vRealize Orchestrator server to restart.
Leave a Reply