Welcome Guest!   Register | Login | Login Assistance
Extending your Citrix and Terminal Server
environment using .NET and other technologies.

Web Interface for Resource Manager 3.0 Architecture Update

 

When the Web Interface for Resource Manger Roadmap was posted, I mentioned that Web Interface for Citrix Resource Manager version 3.0 would include a major architectural shift toward a Service Oriented Architecture (SOA). This shift is well underway and the purpose of this post is to share some of the progress as well as some of the nuts and bolts behind the architecture. Disclaimer – the following may get a little boring.

Web Services
I have been toying with this idea for a while and finally made the decision to move everything to Web Services. Web Services allow for a greater separation of presentation and data. The thought behind creating sets of Web Services in Web Interface for Citrix Resource Manager is to allow other applications to consume the data WIRM produces. Other applications such as Microsoft SQL Server Reporting Services, SharePoint, custom portals, Project S-Bend, etc. can all consume these Web Services. And remember, WIRM is moving beyond the bounds of the Citrix Resource Manager Summary Database so there will be Web Services for the Configuration Logging database, Active Directory, MFCOM, WMI providers, third party data sources, etc. as well as the Web Services for the Citrix Resource Manager Summary Database.  Here is a screen shot of some of the Resource Manger Web Service's rendered WSDL:

Web Services


Generic Database Access, DAL, and DAAB

One of the challenges of querying the Citrix Resource Manager Summary Database from a generic application is that the database can be Microsoft SQL or Oracle. What I have done in the past with Web Interface for Citrix Resource Manager is maintain separate data access blocks – one for SQL and one for Oracle. Depending on the database provider specified in the database connection string in web.config, I would utilize the System.Data.SqlClient or System.Data.OracleClient namespace. This has proven to be a cumbersome and time consuming process to code and test.

Enter the Microsoft Enterprise Library Patterns and Practices Data Access Application Block (a.k.a. DAAB). Web Interface for Citrix Resource Manager implements a Data Access Layer (DAL) which is a common SOA component. The DAL is responsible for physically getting the data from the source(s) and delivering the data to the Web Service(s) - sometimes there is a façade’ in between, but that is another discussion. One of the major pieces of the DAL for Web Interface for Citrix Resource Manager is the DAAB. The DAAB allows for generic database access which means one (reduced) set of code that allows access to either Microsoft SQL or Oracle (or any other ODBC compliant database for that matter).

SOA Architecture


"Sneak Peek" of Version 3.0
The above mentioned architecture makes the information aggregation possible in version 3.0.  To get a better idea of how this all fits together, I have included this screen shot of the new configuration page.  The more information you provide on the configuration page, the more information you get in the Web Interface.




So, stay tuned, there is still more to come...





Published: March 16, 2008
Last Modified: March 16, 2008
Tags: Citrix Presentation Server Resource Manager Web Interface Databases
Current Rating: This post has not been rated.



Comments

Edgesight
As Edgesight is due to replace Resource Manager how does WI for RM propose to integrate with this?

Reply
Re: Edgesight
Edgesight still writes information to a back end database. Writing a provider for that database is on my agenda as well. Anyway, that means more information to link together - which means more functionality for this Web Application. I am still thinking about a new name for this product since it is moving beyond Resource Manager.

Reply
I'll be a beta tester
Jason, Things look great. I'm very much open to beta testing for you. TSD

Reply
Release
What is the expected realease for 3.0?

Reply
Re: Release
I guess I should have expected that question. The answer is - hopefully soon. Everything I develop (including this site) is done in my spare time (since I have a full time job and family). That being said - I have most of the new back-end coded. I am working on adding some new high level reports for the 3.0 release. When all that is stable in my lab, I will send the code out for beta testing and translation. Then, I will release to the public.

Reply
Very nice
Jason, looks really nice... Can be ability to connect to MFCOM (Datastore) expected in first release?? I find reporting by BrowserName as limitation of all Citrix reporting tools - and Citrix recently released patch that is turning on "randomization" of browser name (last 8 characters are random), so in reports you see Appx%JS3Jkf$ instead of AppX.

If I get it right, you should be able to get data from datastore and you them in display, so for example use AppDN as unique ID instead of browser name??

Thanks, keep up good work.

Martin

Reply
cool
Lets god, new options also look interesting

Reply
Great job Jason!
I'm open to beta testing for you!

Reply

 
Post your comment:
Posting as: Guest. Don't want to post as Guest? Login or Register.
Title:  
Comment:  
Verification Code: