Monday, May 5, 2008

Creating a CWA client with Silverlight 2 beta1 (part 1).

I was wondering if it was possible to create a silverlight application that would function as a CWA client. After some research, I found out that it can be done. In this series I will show you how it can be done and what problems I had to overcome to get it working.

Ideally, you would build a silverlight application that would run in any web application. At the moment this can’t be done.
Silverlight does support cross-domain access but only under certain circumstances:
•    only with http connections no https yet.
•    In root of the Target server there has to be a XML file that

allows silverlight to access that server from another domain(the CWA isapi catches all requests so that is a problem, you can create an extra isapi filter that only serves that xml file).
Therefore, building a Silverlight application and having the possibility to debug has to be done on a CWA server directly. Create a visual studio 2008 web application that actually runs directly on a CWA server.

image

After having overcome the problem of debugging, the next problem popped up: Authenticating.

Using the AJAX sdk there are several ways to authenticate (forms authentication, Integrated authentication). They all use a http-header(CWA-Ticket) after you have been authenticated.
After you logon to the server, you get your CWA-Ticket in the response headers, which you need for all further requests. Now we have a problem.

In silverlight the System.Net.HttpWebResponse doesn’t have any headers. How do we get that CWA-Ticket after logging in? We need that CWA-Ticket for all requests were going to make.
There is a solution for this problem, we have to use the browsers XMLHttpRequest object. I don’t wanted to use this object all the time. For now, I only get synchronous requests to work. So for commands and logging in I use the XMLHttpRequest for the asynchronous calls(asyncdatachannel) I use the System.Net.HttpWebRequest.

I know some people would say Silverlight does support Multithreading so that is not a problem. That is what I thought also. But actually the HttpWebRequest and XMLHttpRequest(ScribtObject) can only run in the UI thread. You do not want synchronous calls in your UI thread (it can block your client).

Here is a code sample to create the external XMLHttpRequest:

image

In part 2 I’m going to explain how to actually logon and initiate the session. Please contact Marc Wetters @
Sip:Marc.Wetters@e-office.com or send him an email on Marc.Wetters@e-office.com . Enjoy and please feel free to give us your feedback.

Saturday, May 3, 2008

place to be...

Michael Dunn Senior Consultant at Microsoft gives an presentation about "Embedding Presence in yoimageur Applications".

Absolutely the place to be to get more knowledge about this amazing product.

Michael will cover why .NET developers should even bother with presence, the difference between the UC APIs, and your options for embedding presence in your applications.  The focus is going to be around the client APIs, Communicator Automation API, UC Client API, UC AJAX and ActiveX Name Controls.

More info about Michael Dunn:

Michael Dunn, Microsoft Corporation
Michael Dunn is a Senior Consultant for Microsoft and former MVP for Office Communications Server. He is a frequent speaking at user groups and conferences across the nation and the author of the APress book, “Pro: Microsoft Speech Server 2007”. In his free time you can catch him blogging or answering questions on various MSDN forums & newsgroups.

Visit his weblog on Am I done?

Microsoft Office Communicator Web Access Management Pack for Microsoft System Center OpsMgr 2007

File Name:
Microsoft Communicator Web Access System Center Operations Manager 2007 MP.MSI

Version:
6.0.5000.0

Date Published:
4/30/2008

Language:
English

Download Size:
611 KB

The Microsoft Office Communicator Web Access 2005 Management Pack for Operations Manager 2007 monitors the health of computers running Office Communicator Web Access server components on Windows Server 2003 and alerts IT administrators about critical health conditions that indicate degraded performance. The management pack monitors and provides alerts for:
• Automatic notification of events indicating service outages
• Performance degradation
• Health monitoring
• Centralized management
This management pack requires the Back Compatibility MP version 6.0.5000.12 (or higher)

Friday, May 2, 2008

Office Integration – like Peanut Butter and Jelly (Beans)

nice story about Office Integration. More information see the Communicator Team Blog. Enjoy!

Microsoft Office Communicator 2007 Hotfix KB 951662

File Name:
communicator.msp

Version:
2.0.6362.64

Knowledge Base (KB) Articles:
KB951662

Date Published:
4/30/2008

Language:
English

Download Size:
4.9 MB

Issues that the update fixes
This update fixes the following issues:

951870 (http://support.microsoft.com/kb/951870/) Event IDs 8239 and 8206 are logged when you schedule and then cancel a meeting in Communicator 2007

949498 (http://support.microsoft.com/kb/949498/) Error message when a Communicator 2007 user sends a message that contains only Japanese characters to Communicator 2005 users: "<Username> cannot receive message in the format you used"

951871 (http://support.microsoft.com/kb/951871/) The presence status changes to Away for all Terminal Server users when an administrator locks the desktop or lets the screen saver run in Communicator 2007

951868 (http://support.microsoft.com/kb/951868/) Registry settings for certain protocols are overwritten, and Communicator 2007 becomes the default application for these protocols when you log on to Communicator 2007

Note This update now enforces HTTPS in High Security mode. Some services that previously worked by using HTTP will now be required to use HTTPS when they are in High Security mode. These services include the address book service, the custom tabs service, and the custom presence service.

Tags van Technorati: