uimapi / rest getalarm error for account user with alarm filter ACL

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

When I try to get alarms using webservices_rest or uimapi while logged in with an account user with an ACL with alarm filters I'm getting a HTTP Stauts 500 error. 

http://<UMP>/rest/alarms does not retrieve any alarms (SERVER ERROR) if the ACL assigned to the user contains an alarm filter.  

 

 

Steps to Replicate:

 

1. Create an ACL and assign an alarm filter: 

 

2. Assign the ACL to an account/contact 

3. Go to

 

http://<ump_server>/rest/alarms

or to:

http://<ump_server/uimapi/docs/index.html --> alarms --> Execute Getalarms.

 

4. Log in as the account/contact user that has the ACL assigned with an alarm filter

 

And see the error:

HTTP Stauts 500 - java.lang.NoClassDefFoundError: flex/messaging/util/XMLUtil

Environment

Environment: UIM 9.02, 9.2, 20.1, 20.3.1, 20.3.2

Component : UIM - WEBSERVICES_REST / UIMAPI

Cause

missing jar files.

Resolution

Permanent fix:

A new version of uimapi (20.33) delivered with teh UIM 20.3.3 patch  resolves this issue

 

 

Previous workaround:

1. download the 2 jar files:

"flex-messaging-common-4.7.1.jar"

"flex-messaging-core-4.7.1.jar"

2. Stop the wasp probe

3. Connect to the UMP server and copy the 2 jar files in the following folders:



Nimsoft_install_Dir\probes\service\wasp\webapps\uimapi\WEB-INF\lib



AND



Nimsoft_install_Dir\probes\service\wasp\webapps\rest\WEB-INF\lib



4. Start the UMP wasp.



5. Test if the issue is resolved:



As this issue affects both webservices_rest and uimapi the fix is for both. Now you can test:



REST:

http://rest/alarms

(While logged as the account user with the ACL that has a filter)



UIMAPI:

http://<ump_server/uimapi/docs/index.html

--> Execute Getalarms.

(While logged as the account user with the ACL that has a filter)

Additional Information

For the umapi 20.3.3 fix to resolve this specific issue, the robot running on the OC server where uimapi is deployed, must be upgraded to robot 9.33. If running an old version or the robot_update, the alarm call would still fail similarly.