| Author |
Message |
Neil Stansbury
Guest
|
 Posted:
Tue Dec 06, 2005 5:58 pm Post subject:
Exchange Server and SOAP |
|
|
Hi all,
Apologies if this is not the correct NG.
I am trying to find out how to access MS Exchange Server via SOAP. There
don't appear to be any specific SOAP interfaces for exchange, is this
simply a case of accessing standard COM+ interfaces via SOAP?
I'd appreciate it if anyone here can shed some light/point me in the
right direction.
Cheers,
N
|
|
| Back to top |
|
 |
Glen Scales [MVP]
Guest
|
| Posted:
Thu Dec 08, 2005 1:59 am Post subject:
Re: Exchange Server and SOAP |
|
|
There is no SOAP interface to access the Exchange store (maybe next version)
the closest thing is WebDAV or you could write a Web Service that leverages
one of the other Exchange API to access the store. For more details on
WebDAV and other Exchange API have a look at the Exchange SDK which you can
download from http://msdn.microsoft.com/exchange
Cheers
Glen
"Neil Stansbury" <neil.stansbury@redbacksystems.remove-reply.com> wrote in
message news:uPx3Hio%23FHA.4028@tk2msftngp13.phx.gbl...
| Quote: | Hi all,
Apologies if this is not the correct NG.
I am trying to find out how to access MS Exchange Server via SOAP. There
don't appear to be any specific SOAP interfaces for exchange, is this
simply a case of accessing standard COM+ interfaces via SOAP?
I'd appreciate it if anyone here can shed some light/point me in the
right direction.
Cheers,
N |
|
|
| Back to top |
|
|
Dan Mitchell
Guest
|
| Posted:
Thu Dec 08, 2005 1:59 am Post subject:
Re: Exchange Server and SOAP |
|
|
"Glen Scales [MVP]" <gscales@outlookexchange.com> wrote in
news:uJsbuN4#FHA.3096@TK2MSFTNGP14.phx.gbl:
| Quote: | There is no SOAP interface to access the Exchange store (maybe next
version)
|
http://blogs.technet.com/exchange/archive/2005/09/15/410941.aspx for more
on the APIs that Exchange 12 will have (and which ones it won't..)
-- dan
|
|
| Back to top |
|
|
Neil Stansbury
Guest
|
| Posted:
Thu Dec 08, 2005 5:58 pm Post subject:
Re: Exchange Server and SOAP |
|
|
Hi Glen thanks for that.
| Quote: | the closest thing is WebDAV or you could write a Web Service that leverages
one of the other Exchange API to access the store.
|
I had seen the WebDAV stuff, but the docs don't say what you can and
can't do with WebDAV vs anything else. There seem to be so many Exchange
APIs.
I keep seeing tantalising hints mentioning "Web Services". Can you
clarify what you mean by "Web Services"?
I'm new to developing to the MS Enterprise space, and for me "web
services" is an umbrella of multiple different technologies (XML,CSS,
ECMA etc), I get the impression though there is some form of Microsoft
solution called "Web Services" is that right?
There are so many NG for "Web Services" I am utterly lost:
public.webservices
public.br.webservices
public.mscom.webservices.general
public.dotnet.framework.webservices
public.dotnet.framework.webservices.wsdk
public.dotnet.framework.aspnet.webservices
Any pointers would be very appreciated!
Cheers,
N
Glen Scales [MVP] wrote:
| Quote: | There is no SOAP interface to access the Exchange store (maybe next version)
the closest thing is WebDAV or you could write a Web Service that leverages
one of the other Exchange API to access the store. For more details on
WebDAV and other Exchange API have a look at the Exchange SDK which you can
download from http://msdn.microsoft.com/exchange
Cheers
Glen
"Neil Stansbury" <neil.stansbury@redbacksystems.remove-reply.com> wrote in
message news:uPx3Hio%23FHA.4028@tk2msftngp13.phx.gbl...
Hi all,
Apologies if this is not the correct NG.
I am trying to find out how to access MS Exchange Server via SOAP. There
don't appear to be any specific SOAP interfaces for exchange, is this
simply a case of accessing standard COM+ interfaces via SOAP?
I'd appreciate it if anyone here can shed some light/point me in the
right direction.
Cheers,
N
|
|
|
| Back to top |
|
|
Neil Stansbury
Guest
|
| Posted:
Thu Dec 08, 2005 5:58 pm Post subject:
Re: Exchange Server and SOAP |
|
|
| Quote: | There is no SOAP interface to access the Exchange store (maybe next version)
the closest thing is WebDAV
|
Ok, now I'm really confused, from "Using XML Web Services on Exchange":
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/wss/_exch2k_creating_xml_web_services.asp
<snip>
An XML Web service is a programmable entity that shares business logic
over a network through a standard interface. Web services communicate
through Simple Object Access Protocol (SOAP), which uses HTTP and XML to
encode and transmit messages. Clients of an XML Web service do not need
to know anything about the platform on which it is built; they only need
to know how to send and receive SOAP messages. Microsoft ASP.NET makes
programming XML Web services and their clients relatively easy because
the necessary SOAP functionality is built into the Microsoft .NET Framework.
XML Web services can be used to expose the functionality of Component
Object Model (COM) components on Microsoft Exchange, such as the
Collaboration Data Objects (CDO) components, to remote applications and
users.
</snip>
Um..... and CDO is listed as a “de-emphasized” API in the blog link from
Dan (thanks for that BTW).
Found this:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/wss/_esdk_reference_cdoex.asp
So look like it might be a place to start.
Cheers,
N |
|
| Back to top |
|
|
Dan Mitchell
Guest
|
| Posted:
Thu Dec 08, 2005 5:58 pm Post subject:
Re: Exchange Server and SOAP |
|
|
Neil Stansbury <neil.stansbury@redbacksystems.remove-reply.com> wrote in
news:#3I1HAA$FHA.3908@TK2MSFTNGP10.phx.gbl:
| Quote: | [...]
XML Web services can be used to expose the functionality of Component
Object Model (COM) components on Microsoft Exchange, such as the
Collaboration Data Objects (CDO) components, to remote applications
and users.
|
What they mean by this is that you can use ASP.Net to write your _own_
web service; your code will sit somewhere (possibly on your exchange
server, possibly elsewhere), your code takes in the SOAP requests, and
handles them appropriately. It would be your code that uses CDO
(Ex/1.21/etc) to talk to the exchange server.
Exchange 12 will provide its own web services so you can talk SOAP
directly to the server, but Exchange 12 isn't released yet.
| Quote: | Um..... and CDO is listed as a “de-emphasized” API in the blog link
from Dan (thanks for that BTW).
|
Though as pointed out in the comments, you still have 10 years after the
launch of Exchange 12 before that'll be a "real" problem, which may be
long enough you don't have to worry about it. Extended MAPI is still good
for the forseeable future, if you're feeling low-level.
-- dan |
|
| Back to top |
|
|
Dan Mitchell
Guest
|
| Posted:
Thu Dec 08, 2005 5:58 pm Post subject:
Re: Exchange Server and SOAP |
|
|
Dan Mitchell <djmitchella@yahoo.com> wrote in
news:Xns9726624DD34EBdjmitchellayahoocom@207.46.248.16:
| Quote: | What they mean by this is that you can use ASP.Net to write your
_own_ web service [...]
|
Just to clarify, it doesn't have to be ASP.Net -- C#, VB.Net, and the
other various .Net languages will work just fine as well, or if you really
wanted to you could use C,C++,Delphi, etc, you just wouldn't have all the
nice built-in support that .Net gets you so you'd be writing your own SOAP
code. (or find a library that does it)
-- dan |
|
| Back to top |
|
|
Neil Stansbury
Guest
|
| Posted:
Thu Dec 08, 2005 5:58 pm Post subject:
Re: Exchange Server and SOAP |
|
|
Hi Dan,
Thanks so much for this, I get it now...
MyRemoteApp => My.NET => CDOEX
CDOEX => My.NET => MyRemoteApp
I take then really .NET is the glue between traditional Win32 COM and
"web" interfaces.
Cheers,
N
Dan Mitchell wrote:
| Quote: | Neil Stansbury <neil.stansbury@redbacksystems.remove-reply.com> wrote in
news:#3I1HAA$FHA.3908@TK2MSFTNGP10.phx.gbl:
[...]
XML Web services can be used to expose the functionality of Component
Object Model (COM) components on Microsoft Exchange, such as the
Collaboration Data Objects (CDO) components, to remote applications
and users.
What they mean by this is that you can use ASP.Net to write your _own_
web service; your code will sit somewhere (possibly on your exchange
server, possibly elsewhere), your code takes in the SOAP requests, and
handles them appropriately. It would be your code that uses CDO
(Ex/1.21/etc) to talk to the exchange server.
Exchange 12 will provide its own web services so you can talk SOAP
directly to the server, but Exchange 12 isn't released yet.
Um..... and CDO is listed as a “de-emphasized” API in the blog link
from Dan (thanks for that BTW).
Though as pointed out in the comments, you still have 10 years after the
launch of Exchange 12 before that'll be a "real" problem, which may be
long enough you don't have to worry about it. Extended MAPI is still good
for the forseeable future, if you're feeling low-level.
-- dan |
|
|
| Back to top |
|
|
Dan Mitchell
Guest
|
| Posted:
Fri Dec 09, 2005 12:39 am Post subject:
Re: Exchange Server and SOAP |
|
|
Neil Stansbury <neil.stansbury@redbacksystems.remove-reply.com> wrote in
news:eanLbuB$FHA.4088@TK2MSFTNGP09.phx.gbl:
| Quote: | Thanks so much for this, I get it now...
MyRemoteApp => My.NET => CDOEX
CDOEX => My.NET => MyRemoteApp
|
Exactly. You'd be using SOAP here as the transport to/from MyRemoteApp --
back in the olden days, you'd be using sockets or RPC or DCOM or whatever,
but the same basic structure would apply.
| Quote: | I take then really .NET is the glue between traditional Win32 COM and
"web" interfaces.
|
In this situation, yes -- ".Net" a bunch of other things as well, but
here it's a way to make it easy to write SOAP clients/servers.
Your SOAP server doesn't have to use COM to do its work, either, it could
do raw filesystem stuff, math, whatever -- the .Net runtime library
provides a lot of useful bits and bobs, and you can also use interop to
pull in general Win32 functions and/or talk to DLLs, etc.
-- dan |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in