Hi Domagoj,
This behavior you see is because of the cxf-rt-bindings-soap-3.4.5.jar being shipped in to the NX_ROOT\java\lib\CXF folder of 17.3 RU18 to support SOAP CXF Webservices. This is a bug and has been fixed in the upcoming rollup of 17.3 RU19 (currently in the testing cycle).
As a workaround for now until RU19 gets delivered, please follow the steps outlined below:
1. Stop the CA Service Desk Manager Services.
2. Navigate to NX_ROOT\java\lib\CXF folder and cut(ctrl +x) the file cxf-rt-bindings-soap-3.4.5.jar and paste it into the NX_ROOT\java\lib folder.
3. Navigate to NX_ROOT\pdmconf folder and open pdm_startup.i file in notepad++.
4. Look for the entry
$NX_ROOT/java/lib/CXF/cxf-rt-bindings-soap-3.4.5.jar and change it to $NX_ROOT/java/lib/cxf-rt-bindings-soap-3.4.5.jar
5. Do the step 4 action also in pdm_startup.i.tpl file.
6. Start the CA Service Desk Manager Services.
Apologies for the inconvenience caused.
Regards,
Rajesh Chitrapu
Original Message:
Sent: Nov 29, 2022 09:38 AM
From: Domagoj Hrzic
Subject: REST web services 404 Not Found
Hi,
I'm having issues with REST web service after upgrading to 17.3.0.18.
When trying to obtain rest_access key I'm getting 404 Not Found response.
Tried to redeploy, but did not help. The folder caisd-rest and its content is being re-created when re-deploying.
Pdm_rest_util -deploy (-undeploy)
Pdm_tomcat_nxd -t REST -c start/stop
Testing with Postman, and the REST port is up and running:
Option rest_webservice_resource_to_expose it not installed.
Also in the web.xml file I've enable REST API external adress, as following:
Maybe someone had similar issues, any help would be appreciated. Opened Support case, but no help for now.
Best Regards,
Domagoj