There are two ways to get requestor count

1) use the requestorManagement class in Pega/private API to get a list of requestors

reqResults.setValue(((PegaAPI)tools).getManagementAPI().getPegaRequestorManagement().getRequestors(estimateDataSize));

2) use the requestorManagement mbean. The mbeans are normally accessed via JMX to support prsysmgmt, but also can be accessed through undocumented method executeMbeanOperation.

PRPC ships an activity executeMbeanOperation in PegaAESRemote ruleset to allow AES to leverage the same API's as prsysmgmt using SOAP rather than platform-specific JMX RMI.

String result = (String)com.pega.pegarules.priv.management.MBeanManagement.executeMBeanOperation(aMBeanName, aOperationName, aParam1, aParam2, aParam3);

The jmx mbeans are documented in a zip files on PRPC media. If you have PRPC personal edition, you can go to jdk/bin/jconsole, attach jconsole to tomcat and explore the beans.

The PZREQUESTORMANAGEMENT  rules use requestorManagement API's. PZREQUESTORMANAGEMENT  rules have pyMethodStatus = Internal.

When a rule is marked as internal, it is normally hidden from rule search.

There are two ways to find a hidden rule

1- Use the 'old school' search. Since Pega 5 or 6, rule search has been based on full text. Prior to using text for rule search, rule search used rule names only using table pr4_rule_vw, which has rule names from all the rule types / tables. The 'old:' search syntax searches rule names against pr4_rule_vw. This is a very useful tool to keep in your back pocket for when full text search is broken, as well as to find the hidden internal rules.

2-  Make yourself a 'pegaDeveloper'. Internal rules are not hidden to Pega Developers. If you look at when rule isAPegaDeveloper, you'll see that to be a 'PegaDeveloper' you create a ruleset named PegaDeveloper and add it to your application or access group. The ruleset can, and should, be empty -- just having it gives you access to the hidden rules.