This chapter discusses how you can improve your workflows as well as optimize your work much more. We will be looking at the following recipes:
Working with resources
Working with configurations
Working with Orchestrator tags
Using the Locking System
Language packs (localization)
Working with policies
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...
In this recipe, we will work with resources. We will see how we can integrate files with Orchestrator and use them in workflows and for other purposes, such as storing configuration information.
We need a functional Orchestrator. We also need a text file in a directory that Orchestrator can access. To create such a text file, you could use the example workflow 09.02.1 Write a File. Also see the recipe File operations in Chapter 9, Essential Plugins.
This recipe contains multiple parts, each dealing with different aspects of resources.
Let's start by adding a resource to Orchestrator manually:
Switch Orchestrator to Design mode.
Click on Resources (the white page with a blue symbol on it).
Create a new folder where you can store your resources by right-clicking the root in the tree and selecting New folder.
Right-click on the new folder and select Import resources.
Select a file such as an image or text file from your local...
In this recipe, we will see how configurations can improve our design. Configurations are like global variables that are centrally defined and can be used by all workflows.
We just need a working Orchestrator, and you will need the rights to create new workflows and run them. We will work with the Orchestrator Client.
We will use the example workflow 05.05 Workflow Presentation to test the configuration.
We will split the recipe in two sections, creating and using a configuration.
Using the Orchestrator Client in Design mode, click on Configurations (the white paper with a gear icon).
Right-click on the root and create a new folder. Give the folder a name. It's always a good idea to use new folders.
Right-click on the new folder and select New element. Give the new element a name. The new configuration opens up in edit mode. Click on Attributes.
Now, we can create new variables as we used to in a normal workflow. Create...
Let's explore the tagging of workflows. Tagging introduces the same kind of tagging you're familiar with from vCenter server. Tagging allows you to add tags to Orchestrator objects and search for them.
Tagging involves the following procedures.
Let's start by tagging a workflow manually.
Open a workflow for editing.
Go to the General tab and click on the [Type here to add a tag...].
Type a tag name such as glbTest and then press Enter.
Next, we are adding a tag with a value. Enter another tag such as author, then press Ctrl + S and then enter the value for the tag, such as Daniel.
Click on Save and close.
Here we will have a look at the Locking System. We will learn how to lock and unlock objects using locks. Locks are used to make sure objects are only used by one owner.
There are three phases to locking: locking, checking and unlocking.
We will now create a lock:
Create a new workflow and add a scriptable task.
Add the following variables as input:
|
Name |
Type |
Section |
Use |
|
|
String |
IN |
Any string |
|
|
String |
IN |
Any string |
Enter the following script:
LockingSystem.lockAndWait(object ,owner);
Add the workflow Display all Locks at the end.
Save and run the workflow. Enter as object any string, such as Test and as owner or any other string such as Goofy.
Check the logs.
We will now check if an object is locked:
Create a new workflow and add a scriptable task.
Add the following variables as input:
|
Name |
Type |
Section... |
