| Author |
Ports - A bit confused + SMTP
|
|
| Lastis 2005-12-14, 7:49 am |
| Hi, I've started playing around with Biztalk 2006. This is what I am trying
to do:
1) Receive an xml message that has a node that contains some text
2) Email that text as the body of an email that goes to different recipients
depending on the xml message
My questions are:
1) How do I assign the text to the body of an email
2) What type of port should I use. I dont want to have one port for each
recipient because they are going to be a lot of them. If I use a dynamic port
how do I subscribe to it??
Thanks a lot
Lucas
| |
| Greg Forsythe 2005-12-14, 7:49 am |
| For details on sending email from Biztalk:
http://msdn.microsoft.com/library/d..._email_wgxr.asp
A dynamic port is definitely the way to go.
You can create a dynamic port from the port surface of the orchestration
editor
When you deploy your assembly a dynamic send port is created for you and
bound to the orchestration port. It will have a really long name so it
should stand out.
Within an Expression shape of the orchestration you set the address:
<dynamicportname>(Microsoft.XLANGs.BaseTypes.Address) = "mailto:" +
emailaddress;
Greg
"Lastis" <Lastis@discussions.microsoft.com> wrote in message
news:502666B6-F678-4BA9-96F4-0CF945DA5EB5@microsoft.com...
> Hi, I've started playing around with Biztalk 2006. This is what I am
> trying
> to do:
>
> 1) Receive an xml message that has a node that contains some text
> 2) Email that text as the body of an email that goes to different
> recipients
> depending on the xml message
>
> My questions are:
>
> 1) How do I assign the text to the body of an email
> 2) What type of port should I use. I dont want to have one port for each
> recipient because they are going to be a lot of them. If I use a dynamic
> port
> how do I subscribe to it??
>
> Thanks a lot
>
> Lucas
>
| |
| Lastis 2005-12-14, 5:54 pm |
| Thanks. The article you refer to is for Biztalk 2004. I understand that a few
things have changed from 2004 to 2006 as far as SMTP is concerned. Is there a
similar article for biztalk 2006 that you know of ??
Also is it possible to use this dynamic port in other orchestrations as
well? Ideally I would like to have one dynamic port for outgoing SMTP
messages.
Thanks.
Lucas
"Greg Forsythe" wrote:
> For details on sending email from Biztalk:
> http://msdn.microsoft.com/library/d..._email_wgxr.asp
>
> A dynamic port is definitely the way to go.
> You can create a dynamic port from the port surface of the orchestration
> editor
> When you deploy your assembly a dynamic send port is created for you and
> bound to the orchestration port. It will have a really long name so it
> should stand out.
> Within an Expression shape of the orchestration you set the address:
> <dynamicportname>(Microsoft.XLANGs.BaseTypes.Address) = "mailto:" +
> emailaddress;
>
> Greg
>
>
> "Lastis" <Lastis@discussions.microsoft.com> wrote in message
> news:502666B6-F678-4BA9-96F4-0CF945DA5EB5@microsoft.com...
>
>
>
| |
| Tomas Restrepo \(MVP\) 2005-12-14, 5:54 pm |
| Lastis,
> Thanks. The article you refer to is for Biztalk 2004. I understand that a
> few
> things have changed from 2004 to 2006 as far as SMTP is concerned. Is
> there a
> similar article for biztalk 2006 that you know of ??
There are a few webcasts available on the STMP adapter enhancements in 2006
that you might find useful:
http://msevents.microsoft.com/cui/e...0&culture=en-us
Also, there's an STMP sample included in the SDK, and I have a fairly simple
sample (based off it) that does dynamic ports + HTML messages + attachments
at:
http://www.winterdom.com/weblog/archives/000532.html
> Also is it possible to use this dynamic port in other orchestrations as
> well? Ideally I would like to have one dynamic port for outgoing SMTP
> messages.
You could, but the redeployment stuff in VS currently hoses things up pretty
quickly (it will insist on creating the special port and binding your
orchestration to it), though you can fix that with a bit of scripting. That
said, there's not much "advantage" to having a single dynamic port in the
sense that it contains no settings by itself (except for the pipeline).
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
|
|
|
|