|
Home > Archive > BizTalk Server General > June 2004 > BizTalk 2004 and Microsoft Exchange Server
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BizTalk 2004 and Microsoft Exchange Server
|
|
| darin dimitrov 2004-06-26, 10:51 am |
| Is it possible to send an email message from a BizTalk orchestration
using Microsoft Exchange Server instead of the standard SMTP adapter
and if yes how is this achieved?
| |
| Christof 2004-06-26, 10:51 am |
| If you do not want to use the standard SMTP adapter, you would have to code
this in .NET. What is the reason you'd want to do this please? The SMTP
adapter offers you a lot a flexibility like: retries, HAT integration,
tracking, monitoring, ...
Best regards,
Christof
"darin dimitrov" <darin_dimitrov@hotmail.com> wrote in message
news:2b32e7c2.0406230549.224e6e10@posting.google.com...
> Is it possible to send an email message from a BizTalk orchestration
> using Microsoft Exchange Server instead of the standard SMTP adapter
> and if yes how is this achieved?
| |
| Gilles [MSFT] 2004-06-26, 10:51 am |
| Hello,
>Is it possible to send an email message from a BizTalk orchestration
>using Microsoft Exchange Server instead of the standard SMTP adapter
>and if yes how is this achieved?
First, while you can always communicate to the outside world from an orchestration
by calling a class in an assembly you wrote, this is strongly discouraged. You should
only be communicating with the outside world by sending messages through pipeline(s)
and have adapter(s) take care of the actual message(s) send (after the pipeline has processed things).
The SMTP adapter will need an SMTP server to send messages to.
The SMTP adapter does not route messages itself, it just hands them off to a server
that knows how to route e-mails. Therefore, you can point the SMTP adapter to
your exchange server (and make sure it is configured to allow SMTP)
and you will then automatically have exchange route e-mails.
As I am sure you already knew, Exchange complements BizTalk as far as e-mail transport is concerned
However, I may have totally misunderstood your question and maybe you meant that SMTP
is not the protocol you want to use to send messages. If you plan on using something else
than SMTP, then, you will need to either acquire an adapter for this protocol or write your own.
Out of the box, BizTalk 2004 comes with SMTP, FILE, MSMQ, SMTP, SOAP, HTTP, FTP as transports.
Thanks.
-Gilles.
| |
| darin dimitrov 2004-06-26, 10:51 am |
| Gilles@online.microsoft.com (Gilles [MSFT]) wrote in message news:<A8UdhzTWEHA.3788@cpmsftngxa10.phx.gbl>...
> Hello,
>
>
> First, while you can always communicate to the outside world from an orchestration
> by calling a class in an assembly you wrote, this is strongly discouraged. You should
> only be communicating with the outside world by sending messages through pipeline(s)
> and have adapter(s) take care of the actual message(s) send (after the pipeline has processed things).
>
> The SMTP adapter will need an SMTP server to send messages to.
> The SMTP adapter does not route messages itself, it just hands them off to a server
> that knows how to route e-mails. Therefore, you can point the SMTP adapter to
> your exchange server (and make sure it is configured to allow SMTP)
> and you will then automatically have exchange route e-mails.
>
> As I am sure you already knew, Exchange complements BizTalk as far as e-mail transport is concerned
>
> However, I may have totally misunderstood your question and maybe you meant that SMTP
> is not the protocol you want to use to send messages. If you plan on using something else
> than SMTP, then, you will need to either acquire an adapter for this protocol or write your own.
> Out of the box, BizTalk 2004 comes with SMTP, FILE, MSMQ, SMTP, SOAP, HTTP, FTP as transports.
>
> Thanks.
> -Gilles.
I would like to send email messages within the boundries of a
private network and not the outside world. The SMTP protocol is not
used, instead we have an Exchange server to process mail.
| |
| Nick Malik 2004-06-26, 10:51 am |
| Hello Darin,
Exchange has the option of listening on the SMTP protocol, and accepting
messages for sending to other folks both within your organization and to the
outside world. As your exchange administrator if this option is turned on
in your environment, and if so, what is the name of the Exchange/SMTP
"server" that your code can use.
This is far and away the most common way of sending e-mail within an
organization that uses Exchange.
If you really really really really want to take the hard road, you could
submit messages directly to Exchange using WebDAV.
Hope this helps,
--- Nick
"darin dimitrov" <darin_dimitrov@hotmail.com> wrote in message
news:2b32e7c2.0406232247.53122cd4@posting.google.com...
> Gilles@online.microsoft.com (Gilles [MSFT]) wrote in message
news:<A8UdhzTWEHA.3788@cpmsftngxa10.phx.gbl>...
orchestration[vbcol=seagreen]
discouraged. You should[vbcol=seagreen]
pipeline(s)[vbcol=seagreen]
pipeline has processed things).[vbcol=seagreen]
to a server[vbcol=seagreen]
adapter to[vbcol=seagreen]
e-mail transport is concerned[vbcol=seagreen]
meant that SMTP[vbcol=seagreen]
using something else[vbcol=seagreen]
protocol or write your own.[vbcol=seagreen]
HTTP, FTP as transports.[vbcol=seagreen]
>
>
>
> I would like to send email messages within the boundries of a
> private network and not the outside world. The SMTP protocol is not
> used, instead we have an Exchange server to process mail.
|
|
|
|
|