We currently have two web applications which are working completely separate
from each other, now we are going to implement a single-sign on
functionality among them in a way that when a user logins to each
application can redirect his browser to the other one without any
authentication required.
As a router for passing authentication info between two app we want to use
MSMQ to send this info and BizTalk MSMQT as a central point to receive these
info (from MSMQ) process them and send to the other app as a BizTalk
subscriber. (It seems that we have to use MSMQ to be able to send messages
to BizTalk MSMQT.)
Now the main question is how much is the total lag time of MSMQ and BizTalk
together to route Single Sign-On token between apps? it is very important
for us to have very small lag time otherwise user won't be able to log in
both application at approximately same time.

Any idea or experience in this regard is welcomed.

Thanks

[ Post a follow-up to this message ]

MSMQ and MSMQT is an asynchrounous communication protocol. This means that
the lag could be considerable. You could try other means of passing this
information like HTTP adapter.
--------------------[vbcol=seagreen] 
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13
.phx.gbl[vbcol=seagreen] 
separate[vbcol=seagreen] 
these[vbcol=seagreen] 
BizTalk[vbcol=seagreen] 

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

[ Post a follow-up to this message ]

Adrian, Thanks for your reply.
The reason that we chose MSMQ (or MSMQT) is guaranteed delivery through
queues (because we use it for other scenarios as user profile updates as
well), so do you think using other protocols and adapters like HTTP will
guarantee message delivery even in case of any short or long term
communication failure.

"Adrian Hamza[MSFT]" <adrianhamza@online.microsoft.com> wrote in message
news:JxV7JPWXEHA.2616@cpmsftngxa10.phx.gbl...
> MSMQ and MSMQT is an asynchrounous communication protocol. This means that
> the lag could be considerable. You could try other means of passing this
> information like HTTP adapter.
> -------------------- 
>
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13
> phx.gbl 
> separate 
use[vbcol=seagreen] 
> these 
messages[vbcol=seagreen] 
> BizTalk 
important[vbcol=seagreen] 
in[vbcol=seagreen] 
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> EBusiness Server Team
>

[ Post a follow-up to this message ]

From an orchestration, you can use the "delivery notification" property of
the send port to determine if a message was transmitted successfully. To do
so:

- Create a scope
- Put the send shape inside a scope
- Add an exception handler to the scope
- Create a send port
- Set the send port "delivery notification" property to "transmitted"

If transmission fails, whatever you put in the exception handler will run.

I love this pattern  -- we use it all the time.

HTH,

Brian
Neudesic
Microsoft MVP BizTalk Server 2004


"masoud bayan" <masoud_bayan@hotmail.com> wrote in message
news:%23047ULYXEHA.2544@TK2MSFTNGP10.phx.gbl...
> Adrian, Thanks for your reply.
> The reason that we chose MSMQ (or MSMQT) is guaranteed delivery through
> queues (because we use it for other scenarios as user profile updates as
> well), so do you think using other protocols and adapters like HTTP will
> guarantee message delivery even in case of any short or long term
> communication failure.
>
> "Adrian Hamza[MSFT]" <adrianhamza@online.microsoft.com> wrote in messa
ge
> news:JxV7JPWXEHA.2616@cpmsftngxa10.phx.gbl... 
that[vbcol=seagreen] 
>
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13
 
> use 
> messages 
> important 
> in 
> rights. 
>
>

[ Post a follow-up to this message ]

Thanks Brian.


"Brian Loesgen" <bloesgen-at-m-s-n-d-o-t-c-o-m> wrote in message
news:u5whcWeXEHA.716@TK2MSFTNGP11.phx.gbl...
> From an orchestration, you can use the "delivery notification" property of
> the send port to determine if a message was transmitted successfully. To
do
> so:
>
> - Create a scope
> - Put the send shape inside a scope
> - Add an exception handler to the scope
> - Create a send port
> - Set the send port "delivery notification" property to "transmitted"
>
> If transmission fails, whatever you put in the exception handler will run.
>
> I love this pattern  -- we use it all the time.
>
> HTH,
>
> Brian
> Neudesic
> Microsoft MVP BizTalk Server 2004
>
>
> "masoud bayan" <masoud_bayan@hotmail.com> wrote in message
> news:%23047ULYXEHA.2544@TK2MSFTNGP10.phx.gbl... 
> that 
this[vbcol=seagreen] 
>
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13
 
to[vbcol=seagreen] 
receive[vbcol=seagreen] 
log[vbcol=seagreen] 
>
>

[ Post a follow-up to this message ]