5.8 Resource Object Naming and Renaming

The PlateSpin Orchestrate Resource Grid object type can include resources of various types, including physical machines, virtual machines (VMs), and VM templates, all of which are modeled differently in the Development Client because of their varying roles in the Orchestrate system. Some resource names are generated by the Orchestrate system and can therefore receive generic, arbitrary names such as mysql-1, mysql-2, and so on. Resources you name at installation time or creation time might also change in their purpose or facilities. See Section 5.8.1, Other Resource Object Naming Concerns as an example.

As the quantity of these Resource objects grows in your grid, you might find it helpful or necessary to rename them, assigning more meaningful, intuitive names to suit the purpose of the object. The object’s “display name” is visible in the Development Client interface, the VM Client interface, the Server Portal, and in optional zos and zosadmin commands.

NOTE:Resource object groups (that is, the folders that contain these Resource objects) can also be renamed. Objects such as jobs, events, and users cannot be renamed.

A Resource object’s name is stored in the ${objectType}.displayname fact, which exists on every Grid object type, even those objects that cannot be renamed.

You can rename a Resource object in the Orchestrate Development Client using one of three methods:

As you begin to rename using one of these methods, you will notice that the fact value is pre-populated with the ${objectType}.id fact. This functions as the name value for the object name until you decide to change it.

NOTE:Even after being renamed, the Resource object retains its associated resource ID in the .id fact. This is not editable.

For more information about making the Resource object display names visible from the zos or zosadmin command line, see the PlateSpin Orchestrate 2.6 Command Line Reference.

5.8.1 Other Resource Object Naming Concerns

If you manually install the Orchestrate Agent on a running VM for which there is a corresponding VM grid object, you must use the same name for the agent and for the grid object of the VM that contains the agent. If different names are used, an Under Construction icon overlays the VM icon in the Orchestrate Development Client.

This flag (icon) is used in constraints to prevent the attempted provisioning of a VM that is not yet built or that is not completely set up. The flag is cleared automatically by the provisioning adapters when names match.

If the names do not match, you need to clear the flag by manually adjusting the agent.properties file to match the names or by reinstalling the Orchestrate Agent on the VM and making sure the names match.