After reviewing the report produced by the assessment check, you patch the upgrade request to indicate that you have viewed the results.


Satisfy the following conditions before performing any tasks for this use case.

  • Use POST /lcm/api/v1/login to log in to vRealize Suite Lifecycle Manager.

  • Verify that you have a valid authentication token that matches your login credentials. See Request an Authentication Token.


  1. Patch the vRealize Operations Manager upgrade request.
    curl -X PATCH "https://LCM-HostName/lcm/api/v1/action/assessment/product" \
      -H "accept: application/json" \
      -H "x-xenon-auth-token: $token" \
      -H "content-type: application/json" \
      -d "{ 
        "environmentId": "<Environment-ID>",  
        "requestId": "<request-ID>"
        "viewed": "<is-viewed>"
    Table 1. Input Parameters to Patch vRealize Operations Manager Upgrade Request




    Environment ID is in the response to the request for a list of all environments managed by vRealize Suite. See List All Products in an Environment


    ID received from the response of the call POST /action/upgrade/product. See Create Product Upgrade Request.


    If you reviewed the report from Assess Readiness for a vRealize Operations Manager 6.7 Upgrade and determined that the discontinued or disabled metrics will have no impact on your vRealize Operations Manager 6.7 deployment, set the value to True. Otherwise, set the value to False to prevent an upgrade to vRealize Operations Manager 6.7.

  2. Examine the response.

    The output of the request includes:

    • id = Product upgrade request ID, provided as input.

    • status = Patch request status