Here, we are going to explore how to optimize your workflows and how to make your workload easier.

Configurations come in handy when you have multiple workflows that need the same inputs. For instance, you have multiple workflows that send e-mails. Instead of having all needed mail settings stored in each workflow, you can put them in a configuration and have them stored centrally. This makes it easier for you when you need to change a setting, such as updating a password.

Another example is that you have one workflow that you use in two environments, like development and production. You design and upkeep one workflow instead of two just by duplicating it, and then storing the different variables in a configuration.

A resource is basically a file that is stored in Orchestrator and can be used within a workflow. A typical example is the language packs, which are basically text files stored as resources. Another example for resources is to store information in them such as the configurations of connections. The following screenshot shows that when you use the AD plugin, Orchestrator will create a resource element containing all the required information:

The tags are not yet very well used; however, they do have some merits. You can use them to tag any element in Orchestrator.

The language packs come in handy when you use Orchestrator workflows with vCenter across multiple language areas; however, if you are using REST or the Orchestrator Client it doesn't help that much.

The Locking System can be used for a lot of good work. When you have multiple users or processes that need to use the same resources, such as files or databases, the Locking System can help make sure that only one process is using the resource.

The policies will make Orchestrator actively monitor certain things, such as vSphere objects, SNMP, or AMPQ connections. A policy allows Orchestrator to react to events that are monitored. For example, if Orchestrator registers an SNMP trap, a workflow can be executed.