Transform maps

The Turbonomic Actions application uses different transform maps to perform insert operations. Each transform map name begins with the Turbonomic prefix.

The default behavior is to use a 1:1 mapping between the input fields and the table output columns. If you need to store a different set of data in one or more of the target tables, take the following steps:

• Disable the default Turbonomic Actions transform map for the target table.

• Create a transform map with the same input source as the inactive transform map.

• Specify the custom-mapping logic for the table fields of the new transform map.

This figure shows a different configuration item than the default virtual machine instance in the change request table. The first step is to mark the Turbonomic Web Service Change Request transform map as inactive.

The next step is to create a Custom transform map for the CR. This transform maps all the fields, except the Configuration Item (CI) field, to the same target fields of the CR table.

For the configuration item field, you can define a script to replace the virtual machine with its underlying server CI. The following example is for a Hyper-V virtual machine. Similarly, you can modify the business logic to address VMware, Azure, or AWS virtual machines.

You can map other source fields to different set target fields as needed.