Exchange Server

greg · Guest

I've got a project to link a third party Meeting Room booking system
into Exchange in such a way that the end user in outlook can use
standard outlook features to book meeting rooms and request resources.

The idea is that facilities management Department will use the full
features of the third party system - but other users would use
outlook\exchange as a front end booking tool.

Initially I will run this under Exchange 2000 or 2003

So I have identified the following plan:

1. The Booking system has a list of rooms and resources, I intend
creating & maintain these as "Resources" in Exchange. And
subsequently maintain their Free/Busy information.
2. So now users will be able to schedule a Meeting in outlook and
assign delegates and these "Resources".
3. This will result in a Meeting/booking being created in the third
party application - possibly on receipt of a meeting request email.
(But I am sure other options exist here)
4. Other information such as delegate details (accept/decline),
possibly some user defined fields would also need to pass from the
"Meeting request via Exchange to the Third Party Booking System (MS
SQL based VB.ASP application).

Questions:
1. Is this a reasonable approach?
2. If so, what is the best means of interfacing the Third Party
Application with Exchange? XML web service using SOAP? Or Visual
Studio.Net? or something like CDO?

Cheers
Greg

	Exchange Server Forum Index -> Development	All times are GMT
Page 1 of 1