Abstract: Monitoring backend batch processes/agents to identify currently enabled batch processes that running/executing on schedule and those that are not running/executing on schedule. In the event that currently enabled backend batch processes are identified as delayed, a delay time is determined. Such determinations are made on a regular interval, (e.g., hourly or the like), such that, reports is generated and communicated and/or a batch process status portal is updated on the regular interval to reflect the current delayed status of batch process or, in some embodiments, the current status of all of the backend batch processes currently enabled within an enterprise. Identification of backend batch processes that are currently being delayed and the associated delay time provides a basis for determining the cause(s) for the delay and possible corrective action(s), which may be implemented in conjunction with the determinations.

Abstract: Monitoring backend batch processes/agents to identify currently enabled batch processes that running/executing on schedule and those that are not running/executing on schedule. In the event that currently enabled backend batch processes are identified as delayed, a delay time is determined. Such determinations are made on a regular interval, (e.g., hourly or the like), such that, reports is generated and communicated and/or a batch process status portal is updated on the regular interval to reflect the current delayed status of batch process or, in some embodiments, the current status of all of the backend batch processes currently enabled within an enterprise. Identification of backend batch processes that are currently being delayed and the associated delay time provides a basis for determining the cause(s) for the delay and possible corrective action(s), which may be implemented in conjunction with the determinations.

Abstract: A system executes an enterprise framework for enterprise-wide software monitoring using a Software Deployment Management (SDM) environment such as Pega®. The system accesses a plurality of virtual machines running within the enterprise; determine a plurality of applications running in each of the plurality of virtual machines; access each of the management beans provided by each of the plurality of applications in each of the plurality of virtual machines; identify each of the management beans by name and operation; parse each of the management beans to determine associated automated entity (i.e., agent and/or listener) information; and store the automated entity information in an accessible database. Each of the management beans may be accessed periodically and based on a predetermined regular time interval and/or may be accessed substantially concurrently. Likewise, each of the virtual machines may be accessed substantially concurrently. The time of access may also be stored.