Web Interface for Resource Manager Roadmap
Web Interface for Citrix Resource Manager has been steadily growing since it was first released back in April 2006. Find out where this project is heading in this roadmap and what it will take to get there.
Web Interface for Resource Manager has been steadily growing since it was first released back in April 2006. The purpose of this post is to serve as a roadmap for the direction of where Web Interface for Resource Manager is heading. Version 1.0 of Web Interface for Resource Manager included a few basic usage reports and user reports. Since then, many new features have been added including:
- Report Filtering
- User Level Reporting
- Client Level Reporting
- Concurrent Usage Reporting (for both applications and users)
- Server Metric Reporting
- Support for exporting reports to Microsoft Excel
- Configuration GUI
- Support for Microsoft SQL and Oracle
- Multiple Language Support including: English Dutch – provided by Michel Roth French – provided by Laurent FALGUIERE German – provided by Josef Zeiler Italian – provided by Francesco Dipietromaria Spanish – provided by Gustavo Gurmandi
- Configuration Encryption
That is where we have been, so where are we going? As I stated earlier, this is a roadmap of what is to come. So, here is a list of a few of the new features slated for future releases:
AJAX Enhancements – this will improve the user experience. MFCOM Integration – this integration will allow real-time reporting. Farm Level Reports – these reports will aggregate information to give more of a “bird’s eye view” of your Citrix farm. These reports will include drill down capabilities in to some of the more granular existing reports. Citrix Presentation Server 4.5 Configuration Logging Integration – this will allow reporting on historical changes.
How do we get there from here? Since Web Interface for Resource Manager is moving beyond the bounds of the Resource Manager Summary Database, a major architectural shift will occur. This shift will implement SOA (Service Oriented Architecture) principles. This will allow a loosely coupled layer approach. Why is this important? This will facilitate implementing a provider model where each provider is something you can turn on or off. Depending on what you have turned on, you will get more information in the reports. The providers currently in development are:
» Summary Database Provider » MFCOM Provider » Configuration Logging Provider » Third party providers (stay tuned for more on this in the future).
That’s great – when do we get this stuff? In order to get to the next (provider model) release, I first need to complete the architectural shift I talked about earlier. The good thing about this re-architecture is that it will allow more flexibility. The bad news is that it will not add any new features for end users. So, the next release of Web Interface for Resource Manager will include this new architecture and the AJAX enhancements. This will be a 3.0 release. Each new piece I add after that will be an incremental 3.x release. So, stay tuned, there is more on the way.