1. BAC 7 Features BAC JMX Console

2. 2 Types of Logins

3. 3 So what you can do with it under BAC JMX is some sort of a layer that can invoke BAC APIs without actually been logged to BAC. BAC will be under Topaz section. The funny thing you might access it without actual BAC admin login. Use it with caution, 90% of the stuff will kill your BAC.

4. 4 Example 1: Active Topaz Sessions showLoggedUsersMonitorResult() –Show number of logged users to BAC with some sort of health status. showActiveSessions() –Will show you the actual users plus login details.

5. 5 Example 2: Connection Pool Information retrievePoolLastStackTrace() –The last time there was DB issue, you will get the ful stack trace of the exception. showActiveConnectionStatus() –If there is a connection live at the moment. executeTestQuery() –Help you check and see if BAC have issues connecting to the DB.

6. 6 Managing BAC via JMX When there is a problem login to BAC. –Such as HA issues. –Managing Online, offline engines. –CMDB issues. –Stop start processes such as ‘Partition Manger’.

7. 7 New Type Of Monitoring Use the Site Scope URL monitor: –Use that URL Monitor: http://192.168.8.11:8080/jmx- console/HtmlAdaptor?action=invokeOpByName&name=Topaz:service=MSAM% 20monitors%20manager&methodName=showAvaliableMonitors http://192.168.8.11:8080/jmx- console/HtmlAdaptor?action=invokeOpByName&name=Topaz:service=MSAM% 20monitors%20manager&methodName=showAvaliableMonitors –Result Set is: “ BLE Online Monitor,Adapters Monitor,NOA Monitor,BLE Offline Monitor” –Later apply a content check to see if you getting the result set, otherwise there is a problem. You can use this for capturing the specific status of services The good news is that the BAC self health monitor already uses some of it but we can expand it further.

8. 8 DOs and DON’Ts Do: –When it says: show get Don’t: –When it says: Stop Destroy Reset Launch Delete Set Clear Unregistered reload