System and method for usage billing of hosted applications
A system, method, and computer readable medium for usage billing of one or more hosted applications serving one or more clients. The hosted applications are contained within one or more isolated environments or run without isolated environments. The system may include usage billing based on one or more of resources open, amount of data flowing through resources, number of open files, number of transactions, number of concurrent users, number of processes, CPU utilization and memory usage, The system may further include a management interface where administrators may add, remove and configure isolated environments, configure client policies and credentials, and force upgrades. If using isolated environments, the isolated environments may be isolated from other applications and the host operating system on the clients and applications within the isolated environments may run without performing an application-installation on the client.
1. A system, comprising:
one or more servers that host isolated environments, comprising application files on one or more hosts with host operating systems, and their applications;
one or more billing interceptors configured to load into one or more of address spaces of the hosted applications or address spaces of the host operating systems upon execution of each of the hosted applications; and
at least one central computing device configured to operate a central billing manager.
2. The system according to claim 1 , comprising at least one local billing manager for each application within one of the isolated environments, wherein for each application within an isolated environment the local billing manager performs at least one of: aggregates all received billing events into one or more billing manager events and adds a client login to the billing manager events.
3. The system according to claim 2 , wherein the local billing manager inserts a client login in all billing events prior to the billing manager events being sent to the central billing manager.
4. The system according to claim 1 , wherein the central billing manager sorts billing manager events by client login and interception identifier (ID).
5. The system according to claim 1 , wherein the central billing manager produces a billing summary in one of XML, Microsoft Excel and a custom export format.
6. The system according to claim 3 , wherein said billing events are sent to the central billing manager via at least one of: sockets, named pipes, and an inter-process communication (IPC).
7. The system according to claim 1 , wherein the one or more billing interceptors are configured to intercept access to at least one or more of the following system resources: application execution time used, application storage used, number of open files by application, number of records in a database, and number of times the application has been launched.
8. The system according to claim 1 , wherein the central billing manager tracks billing manager events via the billing interceptors.
9. The system according to claim 1 , wherein the billing interceptors intercept at least one of a number of resources open, a number of open files, a number of transactions, a number of concurrent users, a number of processes, and an amount of data that flows through a resource.
10. The system according to claim 2 , wherein the local billing manager profiles the applications, creates one or more billing events based on said profiled applications, and aggregates billing information.