by community-syndication | Apr 19, 2006 | BizTalk Community Blogs via Syndication
Life’s been hectic for the past couple of months. And my list of “things to blog about” is growing day by day. But, here’s some news that I could not resist stop all my work and blog. J
Another incredible effort from my colleague Jesus and team. Two Connect has done it again with 3 new adapters for BizTalk
- SalesForce.com adapter for BizTalk Server 2006
- Web Services Enhancements (WSE) 3.0 adapter for BizTalk Server 2006
- SQL Server Service Broker adapter for BizTalk Server 2006 v1.5
There is also a MSDN Webcast coming up tomorrow where Jesus will be introducing the SalesForce.com adapter along with colleagues Javier and Ben. Please do register for the same.
For more details check Jesus’s blog http://weblogs.asp.net/gsusx/archive/2006/04/18/443275.aspx
by community-syndication | Apr 19, 2006 | BizTalk Community Blogs via Syndication
A Member of the Microsoft BPI Virtual Technical Specialist Team
by community-syndication | Apr 19, 2006 | BizTalk Community Blogs via Syndication
In a recent MSDN webcast given by Richard Seroter somebody asked about how to avoid “first hit latency” caused by JIT compiling web service code which is deployed not compiled by default. In my post about web project deployment I wrote about precompiling BizTalk web services using aspnet_compiler that will cure this problem. I just wanted to highlight some details.
First, the project can not be compiled in-place, otherwise files get overwritten. It’s better to create separate folder for precompiled web artifacts and pass it as -targetDir to aspnet_compiler.exe.
Second, since you most likely use some script to add assemblies to the BizTalk application its good to use -fixednames option to get consistent file names and directory structure across builds.
Third, if you still want to have some source files updateable (let’s say documentation aspx pages), you’ can provide -u switch to the compiler.
And the last, it’s always good to sign your assemblies with strong key so there are -keyfile, -delaysign, -aptca compiler switches to do that.
by community-syndication | Apr 19, 2006 | BizTalk Community Blogs via Syndication
Jesús has been very busy building adapters. They include:
SalesForce.com adapter for BizTalk Server 2006
Web Services Enhancements (WSE) 3.0 adapter for BizTalk Server 2006
SQL Server Service Broker adapter for BizTalk Server 2006 v1.5
A Webcast on the SalesForce Adapter will be given tomorrow (April 20), and a Webcast on the WSE 3.0 adapter will be given on May 5. You can read more about the adapters and Webcasts HERE
by community-syndication | Apr 19, 2006 | BizTalk Community Blogs via Syndication
Jesús has been very busy building adapters. They include:
SalesForce.com adapter for BizTalk Server 2006
Web Services Enhancements (WSE) 3.0 adapter for BizTalk Server 2006
SQL Server Service Broker adapter for BizTalk Server 2006 v1.5
A Webcast on the SalesForce Adapter will be given tomorrow (April 20), and a Webcast on the WSE 3.0 adapter will be given on May 5. You can read more about the adapters and Webcasts HERE
by community-syndication | Apr 18, 2006 | BizTalk Community Blogs via Syndication
Our MSIT group has just released a whitepaper on moving from BizTalk 2002 & 2004 to BizTalk 2006. It goes into quite a bit more technical detail than our typical case study particularly in regards to their consolidation onto 64bit hardware.
-Kris
by community-syndication | Apr 18, 2006 | BizTalk Community Blogs via Syndication
The download for BizTalk Server 2006’s ODBA (Orchestration Designer for Business Analysts) was recently rev’d on April 14th. Be sure to download the latest version at:
http://www.microsoft.com/downloads/details.aspx?FamilyID=5c731f68-5a4c-4faf-a18d-43d3479187c8&displaylang=en
by community-syndication | Apr 18, 2006 | BizTalk Community Blogs via Syndication
BizTalk 2006 RTMd last month, and the BizTalk Betaplace has been closed for a few weeks now. Many people have asked me for access to the WSS Adapter videos that were shared on the betaplace and finally, here they are.
The videos are shared on this SharePoint site: http://wssadapter.members.winisp.net/default.aspx, in the Shared Documents document library, WSS Adapter Webcasts folder.
This posting is provided “AS IS” with no warranties, and confers no rights.
Use of included videos are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm. Some of the content was developed for the BizTalk Beta builds, but it is still generally applicable to the RTM version.
by community-syndication | Apr 18, 2006 | BizTalk Community Blogs via Syndication
Direct Bound Ports
In BizTalk Server 2004/2006 orchestrations can have direct bound ports.
Direct bound ports are logical one-way or two-way ports in your orchestration that are not explicitly bound to physical ports that allow you to have different communication patterns amongst your services. To create a direct bound port select the binding of the logical port to be direct then choose as the ’Partner Orchestration Port’ what this port will be bound to.
There are three types of direct bound ports that you can choose as the Partner Orchestration Port; message box, partner, and self-correlating.
Message box direct bound ports allows for publish-subscribe design patterns. Messages sent on a message box direct bound port are published to the message box without any explicit intent of the message recipients. Logical receive ports configured as message box direct bound ports get messages directly from the message box whose subscriptions are based only on message type and filter expression (for activating receive shapes) or correlation set (for non-activating receive shapes).
Figure 1 Message Box Direct Bound Ports
Partner direct bound ports provide for inter-orchestration communication. Messages sent on a direct bound port can be sent to an intended recipient orchestration and messages received on a partner direct bound port can be received from an intended sender orchestration.
Figure 2 Partner Direct Bound Ports
Self-correlating direct bound ports assists you in designing asynchronous inter-orchestration communication. Messages sent to a self-correlating direct bound port are routed to the instance of the orchestration that created the receiving end of the self-correlated direct bound port.
Figure 3 Self-Correlating Direct Bound Ports
A commonly misunderstood aspect of direct bound ports is its interaction with the message box with some incorrectly thinking that there is direct communication with another instance of an orchestration without traversing the message box. This is not the case; any message sent through any type of logical port always travels through the message box.
Figure 4 All logical ports communicate through the message box
Direct bound ports are only logical ports and therefore only a design time configuration feature. An administrator cannot bind a direct bound port to a physical port nor change the partner it is currently configured for.
To see each of these different types of ports in action and in context you can look at the Business Process Management (BPM) scenario that ships as part of the SDK in BizTalk Server 2006.
I will have a separate posting and go into more detail on each type of direct bound port.
by community-syndication | Apr 18, 2006 | BizTalk Community Blogs via Syndication
BizTalk 2006 RTMd last month, and the BizTalk Betaplace has been closed for a few weeks now. Many people have asked me for access to the WSS Adapter videos that were shared on the betaplace and finally, here they are.
The videos are shared on this SharePoint site: http://wssadapter.members.winisp.net/default.aspx, in the Shared Documents document library, WSS Adapter Webcasts folder.
This posting is provided “AS IS” with no warranties, and confers no rights.
Use of included videos are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm. Some of the content was developed for the BizTalk Beta builds, but it is still generally applicable to the RTM version.
