Smarts NCM: After upgrade to 9.4.1, external API access no longer works; error seen "HTTP Status 404 - /ws/api/91/services/ApiService ", "The requested resource is not available."

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:




When trying to run code in the API, the following error message is seen with the API not responding :
 

HTTP Status 404 - /ws/api/91/services/ApiService 

type Status report

message /ws/api/91/services/ApiService

description The requested resource is not available.

 

Customer had altered their code to reflect the changes according to the API 9.4.1 User Guide as follows:
Change made to location of ApiService assigned to soap_proxy:

$main::date = strftime "%m/%d/%Y", gmtime; 
#$soap_proxy = "https://easyXXXX:XXXXX\@pink.rabbit.com:8880/ws/api/41/services/ApiService";
$soap_proxy = "https://easyXXXX:XXXXX\@pink.rabbit.com:8880/Api/services/ApiService";
 

However, this did not work. 

 

Environment

VMware Smart Assurance - NCM

Cause

The API Service location has been changed.

Resolution

Change the url to

https://<ipaddress>:8880/ncm-webapp/services/ApiService

so code will read: 
 
$soap_proxy = "https://easyXXXX:XXXXX\@pink.rabbit.com:8880/ncm-webapp/services/ApiService";