7.4

Table Of Contents
The following is an example of a complete operation configuration file:
<?xml version="1.0" encoding="utf-8" ?>
<customOperations xmlns="http://www.dynamicops.com/schemas/2009/OperationConfig/">
<operation name="WFMachineMenu1" displayName="Execute Machine Menu task">
<authorizedTasks>
<task>VRM User Custom Event</task>
<task>VRM Support Custom Event</task>
<task>Group Administrator Custom Event</task>
<task>Enterprise Administrator Custom Event</task>
<task>VRM Administrator Custom Event</task>
</authorizedTasks>
<machineStates>
<state>On</state>
<state>Off</state>
</machineStates>
</operation>
</customOperations>
Install an Operation in the Model Manager
You install an operation in the Model Manager by using the CloudUtil command-line utility.
Prerequisites
Create an Operation Configuration File.
Procedure
1 Open an elevated command prompt.
2 Run the CloudUtil.exe command with the following arguments.
n
CloudUtil.exe Operation-Create -c <path to operation definition file>
n
Optionally, you can specify a Model Manager host and request a stack trace in case of error.
CloudUtil.exe Operation-Create -c <path to operation definition file>
--repository <Model Manager Root URI> -v
What to do next
If the menu operation is intended to be used in the service catalog, it must be registered with the service
catalog so that it can be entitled to users. Register New Menu Operations with the Service Catalog.
Register New Menu Operations with the Service Catalog
After installing new menu operations, the workflow developer must register them with the service catalog
so they can be entitled to users.
Prerequisites
n
Configure a Menu Operation.
Life Cycle Extensibility
VMware, Inc. 68