Test the CVR Update connections

After you have installed, configured and enabled the CVR Update module, you can test the connection to verify if the configuration works as expected.

Test the CVR Update Subscription Service - service accessibility

In an internet browser, enter the following address http://<WZ Main Page>/CvrSubscriptionService/liveness where <WZ Main Page> is the name of your WorkZone main page (landing page), for example http://MyOrg.WZLandingPage//CvrSubscriptionService/liveness

Result

The web page will display the result Healthy if the subscription service has been configured correctly and is currently accessible.

The web page will display HTTP != 200 if the subscription service has not been configured correctly or is currently inaccessible.

Test the CVR Update Subscription Service - connection status

In an internet browser, enter the following address http://<WZ Main Page>/CvrSubscriptionService/readiness where <WZ Main Page> is the name of your WorkZone main page (landing page), for example http://MyOrg.WZLandingPage//CvrSubscriptionService/readiness

Result

The web page will display a summary of a sample connection to the KMD Logic platform which may take a few seconds to render, depending on your organization's internet connections and network status.

The summary is split into a connection status for the entire connection, the OData and the KMD Logic part of the conneciton as well as the total duration of the entire connection, the Odata processing part of the connection time and the KMD Logic part of the connection time.

Example: Healthy connection

{"status":"Healthy","totalDuration":"00:00:24.4954484","entries":{"self":{"data":{},"duration":"00:00:00.0000435","status":"Healthy","tags":["liveness","readiness"]},"OData":{"data":{},"duration":"00:00:24.4947925","status":"Healthy","tags":["readiness"]},"Logic":{"data":{},"duration":"00:00:02.2812385","status":"Healthy","tags":["readiness"]}}}

If the connection is faulty or incorrectly configured, the result will report Unhealthy and contain error codes or descriptions, for example BadRequest or Unable to access.

Example: Faulty connection

{"status": "Unhealthy","totalDuration": "00:00:05.3817914","entries": {"self": {"data": {},"duration": 0:00:00.0005463","status": "Healthy","tags": ["liveness","readiness"]},"OData": {"data": {},"description": "Failed to get the access token from http://<WZ Main Page>/oauth2/connect/token. Status code: BadRequest","duration":0:00:05.3506721","exception": "Failed to get the access token from http://<WZ Main Page>/oauth2/connect/token. Status code:BadRequest","status": "Unhealthy","tags": ["readiness"]},"Logic": {"data": {},"description": "Unable to access the token issuer, request returned BadRequest. Reason: unauthorized_client.","duration": "00:00:00.5253802", "exception": "Unable to access the token issuer, request returned BadRequest. Reason: unauthorized_client.","status": "Unhealthy","tags": ["readiness"]}}}