ICN Search Response Filter – Doesn’t work with more than 200 search results

We have implemented a plug-in to display FoldersFilledin property in a column of ICN search results. The plug-in uses /p8/search response filter to fetch this value for result set and and displays it in result set by updating JSONResultSetResponse.

Plug-in is working fine but when search returns more than 200 results, all the entries from 201 have blank folder property. It seems ICN loads maximum 200 results in background when search is performed. When user scrolls further below after 200th entry, more results are loaded and here probably plug-in not invoked. How can i deal with it? User’s doesnt want to limit search results to 200. Is there any way to handle this in plug-in or by configuration.



  • No Related Posts

Why won’t Installation Manager GUI start?

I’ve successfully installed OMNIbus 8.1. When I wanted to install Fix Pack 4 and ran IBMIM command to start Installation Manager, the GUI doesn’t get displayed.

I checked the IM logs and found the following exception:

!ENTRY org.eclipse.e4.ui.workbench.swt 4 2 2016-10-04 10:09:10.632
!MESSAGE Plug-in code from “org.eclipse.e4.ui.workbench.swt”
A problem occurred when starting up.
at com.ibm.cic.agent.core.Agent.setProxyPreferences(Agent.java:671)
at com.ibm.cic.agent.core.Agent.initializeAgentPreferences(Agent.java:3444)


7021423: iManager – Multiple Reflected Cross-Site Scripting (CVE-2017-7425)

This document (7021423) is provided subject to the disclaimer at the end of this document.


iManager 2.7.7
iManager 3.0.1
Identity Manager iManager Plug-ins
Identity Manager 4.5


PEN tests were executed against the Identity Manager Plug-in, hosted on iManager In certain scenarios, it was possible to execute arbitrary JavaScript code in the context of vulnerable application.

Note: Special thanks to Pawel.Batunek@ingservicespolska.pl for finding and reporting this issue.


Fixed in the IDM 4.6.1 Identity Manager Plug-ins, dated July 10, 2017 or newer.


Security Alert


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.


7021173: iManager – XML External Entity (CVE-2017-7426)

WAS Deploy Plugin – Application Source field?

I’m doing a refresh of deploying an ear file into WAS, and I am creating a component process, and as I was adding the ‘Install Application’ step to the component process, which is part of the WAS Deploy plug in, I was curious to know why in the properties ‘Application Source’ is a required property, when I’ve already defined the location of the ear file in the ‘Basic Settings’ for the component and have imported its current version in the Component confiugration. Seems kinda redundant