JMX

Monitor a whole BOBJ system similar to what Wily Introscope was doing, but with preliminary configuration as simple as a checkbox tick.

Monitor any JAVA process. Tomcats are usually the most important once in BOBJ deployment.

Problem:

Monitor BOBJ system including OS metrics, with minimal setup efforts, convenient analytical features and persistent storage.

Monitor and configure multiple Tomcats (or any JAVA processes) remotely, from the single from a single, user-friendly interface.

Solution:

Comprehensive BOBJ Monitoring:

BOBJ JMX allows you quickly access all BOBJ Metrics, monitor their dynamic, filter, sort, chart and export them.

With included OS level monitoring, you can see what is going on all your BOBJ hosts (overview metrics), without need to login to machines or relay on other third party tools.

Effortless Tomcat Monitoring:

Monitor one or multiple Tomcats from a single intuitive dashboard.

Tomcat exposes 94 beans and 1,378 metrics for monitoring and configuration. These beans are logically organized, and you can easily search or filter among them.

Each bean and metric comes with detailed developer-provided descriptions, ensuring you always know what you're looking at.

Configuration Made Easy:

Quickly inspect configuration settings.

For example, Tomcat has 19 parameters related to TIMEOUT.

Instead of searching through configuration files, BiWhy displays them all in seconds.

Dynamic Configuration Updates (Future Enhancement):

Do you know that you can change parameters, that require app restart to take effect, without restarting it, if developers exposed corresponding functionality?

Query Additional Data (Future Enhancement):

You can query more data from your app though OPERATIONS with functions exposed by developers.

Data Collection and Sharing:

BiWhy enables the compact storage of all collected data in a local database or your preferred database (functionality on demand).

Share this data with others for in-depth analysis, allowing for collaborative insights into your BOBJ system's performance.

OS Metrics (with multiple hosts, you will see all on the same screen):

Tomcat, timeouts:

Admin Tools

Find a property in CMS DB

Problem:

System is locked out after restore from backup, as there is only one Enterprise user “Administrator” and it’s get disabled on system startup due to password policies.

Solution:

We need to update password policies in CMS console mode, but where to find them?

Check CMS DB (on small/test system or directly use AdminTools) for any object related to secEnterprise (assume you don’t know anything about the subject and start with something like Enterprise then quickly narrow it down).

Turned out there is only one relatable object, but it has 131 properties. Filter them out with few guesses or with text from configuration screen in working system.

Few attempts and you got your properties.

Change property in CMS screen in working system and confirm that it is reflected in the found property.

All search from idea to confirmation took ~5min, without any prior knowledge in this area.

CMS DB actions

CMS DB actions.

Our BiWhy Admin Tools offers a remarkably flexible and user-friendly framework for handling CMS DB actions.

Problem:

Recently, we faced the task of pausing ~13k jobs and then releasing them in smaller batches of 1-2k jobs at a time.

Solution:

The implementation of the Pause/Release actions took just a few hours including testing, adding user-friendly messages and comprehensive logs, plus interactive features, and timings.

No need to say that we are accepting requests for new actions as well as other valuable features for BiWhy.

Screenshot is from a test system: