DX UIM 23.4 CU5, now Generally Available!

[Ravishu Arora]

Hi All,

We are pleased to announce the general availability of our DX Unified Infrastructure Management (DX UIM) 23.4 Cumulative Update (CU) 5.

This release (DX UIM 23.4 CU5) provides key capabilities and enhancements such as:

• Launch of integrated dashboarding and reporting in 'UIM Business Intelligence' (UIM BI)
• Powerful RESTful reporting APIs through 'UIM Data Services'
• Product-wide upgrade to Java 21
• Access-controlled Inventory Management
• Fixes for a bunch of customer-reported issues and security vulnerabilities

Please note: Considering the significant leap in Java version adoption and the changes to in-product reporting capabilities, this CU also supports a full, fresh installation, in addition to the standard upgrade scenarios.

Details of both installers (Server and OC) can be reviewed in their respective solution documents listed on our Cumulative Updates and Patches page.

For details, please refer to the Release Notes.

We encourage you to download the latest Generally Available software, from Broadcom Support. 

------------------------------
Principal Product Manager
Broadcom Software
------------------------------

[Joakim E]

Hello Ravishu,

The CU5 upgrade instructions for OC are a bit unclear.

"If "cabijs" is deployed on an Operator Console robot or primary hub, migrate it to an alternative robot (with WASP 23.4.4.x) prior to commencing the 23.4 CU5 upgrade process."

There is no WASP 23.4.4.x version. Will WASP 23.4.3 be ok or is it necessary to update to WASP 23.4.4 before the OC upgrade?

If I deploy cabi to the OC robot, will I have to migrate it to an alternative robot before all future upgrades, or is it this time only?

-------------------------------------------

[Sitaram Karancheti]

Hello Joakim,

For UIM 23.4 CU5, it is a prerequisite to deploy 'cabijs' on a separate robot that runs WASP version 23.4.4.x. WASP version 23.4.4.2 is available for download from the UIM Web Archive via the 'Previous Versions' tab on the Nimsoft support portal: https://support.nimsoft.com/.

Please note that CABI Jaspersoft Reports is reaching End-of-Service (EOS), as previously announced.
https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/CriticalAlerts/0/25489.

We recommend transitioning to alternative reporting mechanisms available with 23.4 CU5. For more information, please join our upcoming webinar on August 26, 2025 (Register here: https://engage.broadcom.com/IMS-events). Additionally, we suggest reviewing the previous presentation on CABI replacement options.

Best Regards,
Ram.

-------------------------------------------

[Joakim E]

Thanks Ram,

I'm confused, shall I keep cabi or not? It was my understanding that CU5 would have the cabi replacement, is that not the case? Why are you otherwise informing how to deal with it during the upgrade?

-------------------------------------------

[Sitaram Karancheti]

Hi Joakim,

UIM Data Services, released with 23.4 CU5, are available for dashboarding and reporting. CABI was also included in CU5, specifically for migration purposes.

Best Regards,
Ram.

-------------------------------------------

[Matthias Gruber]

Hi!

Thanks a lot! Keep up the good work.

But can you sign the oc-installer-23.4.5-windows_x64.exe? Has an unknown publisher, Defender is "crying", thought everything comes signed these days, at least the SHA is correct :-)

cheers
Matthias

-------------------------------------------

[Sitaram Karancheti]

Hello Matthias,

Thank you for your feedback. We got to know about the missing digital signature and shall take the necessary steps going forward.

Best Regards,
Ram.

-------------------------------------------

[Vaclav Tomec]

Hi,

after upgrade of OC, the wasp probe does not start with 

Aug 21 17:10:09:748 [5484] Controller: Max. restarts reached for probe 'wasp' (command = <startup java21>)

 Has anyone seen this? I tried restarting robot, server, deactivate/activate....

-------------------------------------------

[Jason Allen]

Do you happen to have CABI installed on the same robot as Operator Console?  This can cause that behavior as now it is required to move CABI to its own dedicated server.

https://knowledge.broadcom.com/external/article/272181/move-cabi-to-a-different-server.html

In the wasp folder (e.g. probes\service\wasp\) there should be a _wasp.log which may contain more details/errors than the wasp.log does, can you check this for any errors?

-------------------------------------------

[Vaclav Tomec]

CABI is not installed on OC robot.  And wasp.log contains only the mentioned message.  Change in loglevel for wasp does not seem to get more detail....

-------------------------------------------

[Christopher Pearson]

Can you check to see if the following is in the wasp.cfg regardless if cabi is there or not:

https://knowledge.broadcom.com/external/article?articleNumber=407631

-------------------------------------------

[Vaclav Tomec]

Hi Christopher,

there was only one line:

max_perm_size = -XX:MaxPermSize=4096m

when I removed it from wasp.cfg, it started.

Thank you very much.

-------------------------------------------

[Jason Allen]

There is another log in the wasp folder called _wasp.log (with an underscore on the filename) which may have the details.   If the wasp.log only has the "max restarts" version, you can usually find more details by looking in the "underscore" version of the log.   This is only accessible by looking at the filesystem, you cannot get to it from the "View Log" functions.

-------------------------------------------

[Franklin Ravi D'souza]

Also have you have upgraded the OC robot to 23.4.5 which is required for the new Java 21?

-------------------------------------------