If the resource mapping that fails is a built-in resource mapping, apply the steps below to update the database:
- Make a backup of the database
- Connect to the database
- Open a new transaction:
BEGIN;
- Update the records to have the appropriate action ids assigned:
UPDATE asd_resourcetype set mappingscriptactionfqn='com.vmware.vcac.asd.mappings/mapToVCVM' where mappingworkflowid='425bcb81-####-####-####-########732';
UPDATE asd_resourcetype set mappingscriptactionfqn='com.vmware.vcac.asd.mappings/mapToVCloudVApp' where mappingworkflowid='4310f443-####-####-####-########624';
UPDATE asd_resourcetype set mappingscriptactionfqn='com.vmware.vcac.asd.mappings/mapToVCloudVM' where mappingworkflowid='c8324dc1-8####-####-####-########a63';
- Check for errors and commit or rollback.
- If there are errors, abort the transaction
ROLLBACK;
-
- If no errors, commit the transaction:
COMMIT;
If the resource mapping is a custom resource mapping, wrap the workflow it invokes as an action and call the action instead.