CMS to Excel

Updated simplified interface with build-in analytical features

Problems:

Analyze CMS DB objects in table

Solution:

Query CMS DB for any objects

Analyze available properties with tree and property view. Average object has around 50 properties only on the first level

Hide/unhide first level properties as columns and add/remove them as filters

Flatten embedded collections (UserGroups -> Users, Reports -> DataSources, Objects -> Rights…) with regex as Path to collection or/and low level Property Name

Filter duplicates after flattening with Distinct, in some cases it is drastically reduce result set to useful information

Resolve IDs to names, as in most cases collections are presented as SI_ID

Rights Explorer

Check/Export rights for given object(s) or user(s)/group(s)

Problems:

Check who has rights for particular object(s)

Check which rights particular user(s)/group(s) has for given objects

Export rights

Solution:

Select objects with BiWhy’s AdminTool and retrieve effective or explicit (set on this object) rights for them or check which rights given user(s)/group(s) has for selected objects.

Compare configuration

Compare properties (lines) in configuration files

Problem:

One node is functioning smoothly, while another is experiencing issues, particularly following recent configuration changes or upgrades, along with additional modifications.

To diagnose the issue, you must compare a dozen configuration files, each containing numerous parameters spanning hundreds of lines.

It's a tedious and time-consuming task that you'd rather avoid, mainly because there could be various other factors causing the issue and several parties before you already rechecked configuration.

So, you may spend several hours of your time merely to verify that the issue doesn't stem from there, and there's still a possibility of overlooking a misconfiguration.

Solution:

BiWhy compares configuration just in seconds. And in this particular case found two critical differences (in 35 common configuration files, after filtering numerous backups and not relevant files like jsp, jks, in hundreds and hundreds lines, differences were only in 10 of them).

Actually, I was starring in the second typo (see screenshot) for couple minutes trying to figure out what is the difference. I was looking in URL, but typo was one digit in the port number.

Without BiWhy on a Linux machine, customers could have potentially spent days or rather weeks trying to diagnose the problem.