|
|
|
|
|
|
|
BizTalk Server 2009 : Using queues within asynchronous scenarios (part 2) |
The MSMQ service endpoint is configured using the netMsmqBinding with the path to the private queue as the service address. As we are hosting our service within IIS 7.0, we do not need a separate MEX endpoint for MSMQ, but rather, can simply apply a standard HTTP metadata behavior to our service. |
|
|
|
|
|
|
|
Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 8) |
In Exchange Server 2003, filters for address lists and e-mail address policies were based on LDAP syntax; Exchange Server 2010 uses OPATH filtering syntax. Although LDAP syntax filters are supported in Exchange Server 2010, they must be upgraded to OPATH syntax if you want to edit them in Exchange Server 2010, and LDAP filters can't be created in Exchange Server 2010 |
|
|
|
|
|
|
|
|
Exchange Server 2010 : Useful Tools for an Upgrade (part 1) |
A new downloadable tool released for Exchange Server 2010 is the Exchange Pre-Deployment Analyzer (ExPDA). This tool provides an Exchange 2010 Readiness Check; previously, the Exchange Server 2007 Readiness Check was provided as part of the downloadable version of the ExBPA. |
|
|
|
|
|
BizTalk Server 2009 : Getting results from asynchronous invocations (part 3) |
Before we use this contract in our client code, we should set up the appropriate endpoint in the client application's configuration. In this case, our endpoint contract is the one constructed above, the binding is the wsDualHttpBinding, and the address should match the value specified by our in-process receive location. |
|
|
|