Last month I held a presentation at the Bouvet BizTalk Innovation Event (26 – 27 September) along with fellow MVPs: Steef-Jan Wiggers, Nino Crudele, Saravana Kumar and two distinguished community members: Lex Hegt and our host Tord G. Nordahl. This was the biggest BizTalk event organized in Norway (Stavanger) this year with a total of […]
Blog Post by: Sandro Pereira
Ive recently published a sample guide based on a real-world project where we implemented an on-premise WCF routing solution to connect SAAS applications to our on premise line of business applications.
The guide will discuss:
This contains some useful contextual information around the reference scenario and hopefull this will be very useful to others undertaking similar projects.
Ive also included this on the technet wiki page for Windows Azure Service Bus resources:
http://social.technet.microsoft.com/wiki/contents/articles/13825.windows-azure-service-bus-resources.aspx
Migrating to a new BizTalk version can give lots of opportunities to remove the dust of old applications. Use new technologies to offer the same functions to the client and improve performance or configurability. To change your old exposed SOAP-services to WCF services, you will have to perform some tricks explained in this blogpost.
I’m extremely delighted to announce the immediate availability of BizTalk360 version 5.0. Most of you following us closely know, we apply a typical start-up/agile methodology for BizTalk360. We pick up 3-4 core features and deliver it on our new version (roughly 4-5 months cycle). Our previous version 4.0 was released on 5th June, exactly 4 […]
The post What’s new in BizTalk360 version 5.0? Available for immediate download appeared first on BizTalk360 Blog.
Blog Post by: Saravana Kumar
The new Windows Azure Management Portal now supports Service Bus management and monitoring. This is one of the new improvements of the new portal. This will a mean a new experience for the user compared to the older management portal based on Silverlight. The functionality remains similar as per creating a namespace, creating queues and topics.
Above you see a screenshot of Service Bus management in the old portal and below a screenshot for the new portal.
As you can see the look and feel is totally different. The ALL tab gives an overview of all the Queues, Topics, and Relays. Compared to the old portal the relays are now visible. Queues, topics and relays can be viewed separately by clicking the its tab. For instance the relay tab in my case will show the relays.
You will find more on working with relays using the new portal through Trying Out the New Windows Azure Portal Support for Relay Services blog post by Richard Seroter. On each tab you will find + NEW button on the left hand corner below. If you click NEW a dialog will appear.
Now you have to ability to create a new queue, topic or relay. You can create a new queue for instance through QUICK CREATE with default settings or CUSTOM CREATE with custom settings. If you for instance want to create a custom queue you can click CUSTOM CREATE. A Wizard will start and you will have to fill in a Queue name, region (i.e. data center), subscription (one you create when signing up for Azure) and Namespace (which can be created through Service Bus service view by clicking CREATE button in menu below).
Next step is configuring the queue by determining the max size, message time to live, move messages to dead letter queue, lock duration, duplication detection and enable session.
If you now click the check mark button the queue will be provisioned.
As you can see the queue is created and visible in the portal. You can click the newly created queue and see some characteristics in a dashboard.
You have to ability now to view the connection string of the queue, delete, disable it or view the access key. By click the access key a dialog will pop up showing you the connection string, default issuer, default key and link to ACS Management Portal.
The walkthrough above showed you how to create and manage a newly created queue. For creating a topic the steps are similar. For relays see Richard’s post. As you can see new portal gives you a new user experience, yet same functionality and new enhancements compared to the old portal.
Finally I also like to point out that you can also manage the service bus through Visual Studio 2012, or Service Bus Explorer. I did a comparison between the too in my Visual Studio Service Bus Explorer versus Standalone Service Bus Explorer blog post.
Cheers,
Steef-Jan
Here is a list of enhancements to Application Pools in IIS 8.
Start Mode
A few web applications take a significant amount of time to start up. IIS by default only launches a worker process when the first request for the web application is received. So for the web applications that require a longer time to initialize, users might see slow responses.
For such applications it is a good idea to launch the worker process as soon as IIS is started. The application pools have a startMode setting which when set to AlwaysRunning launches the worker process for the application pool as soon as IIS is started.
IIS 8 provides you this setting in the Application Pool Settings UI.
This feature is also available in IIS 7.5, but you will have to edit the applicationHost.config directly to enable this feature.
<applicationPools>
<add name="DefaultAppPool" startMode="AlwaysRunning" />
CPU Throttle
IIS 7.5 and earlier have a CPU monitoring feature that you could use to terminate a worker process, when its CPU usage goes beyond a certain limit. Its very useful in shared hosting scenarios.
In IIS 8 this feature has been enhanced. You can now instead of terminating the worker process, throttle it.
The KillW3wp will terminate the worker process like IIS 7.5. But if set to Throttle or ThrottleUnderLoad instead of terminating the worker process it will limits its CPU usage to the value set.
This is an application pool setting, so the limit you set applies to all the worker processes (web garden) of an application pool. So for an application pool with 5 worker processes, if the value for limit is set to 50000 the combined CPU usage of all the 5 worker processes is throttled at 50%.
Process Affinity Mask (64 Bit)
The UI now also exposes the smpProcessorAffinityMask2 metabase key. This is used when you enable the Processor Affinity setting.
Generate Process Model Event Log Entries
The logEventOnProcessModel metabase setting controls if an event has to be written when an application pool is shutdown because it was idle.
<applicationPools>
<add name="DefaultAppPool" startMode="OnDemand">
< processModel logEventOnProcessModel="IdleTimeout" />
When set to True an event similar to the one below is logged in the System Event Log when WAS shutdown the application pool.
Blog Post by: Shinva
December 2011 almost a year ago I wrote a blog post for TechNet Wiki on Windows Azure- and Server AppFabric. Now on the Server part a cookbook has been released written by fellow Microsoft Integration MVP Rick G. Garibay and Microsoft Architect Hammad Rajjoub. I know both Rick and Hammad (both very active community leaders) have done a great job. Windows Server AppFabric can be viewed as a part of the Microsoft Integration Stack together with BizTalk, SQL Server and Azure ServiceBus. For lightweight integration Windows Server AppFabric together with WF (Windows Workflow) and WCF (Windows Communication Foundation) can be a right fit within your enterprise without using the more scalable, robust BizTalk Server or Windows Azure Service Bus.
I have teamed up with Packt Publishing and am organizing a give away especially for you my blog readers. All you need to do is send me an email with your view on Microsoft integration at SteefJan @ msn dot com and you might win a free copy of Microsoft Windows Server AppFabric Cookbook. Three lucky winners stand a chance to win an e-copy of the book. This contest will end at end of this month 31 October. Lucky winners will be announced on 1st of November.
This book will enable you to:
What I like about Packt cookbooks is that it provides you as professional practical guidance on how to leverage the technology. This book focusses on Windows Server AppFabric or as it is now named AppFabric for Windows Server. This technology is a set of integrated technologies that makes it easier to build, scale, and manage Web and composite applications that run on IIS. I believe this book will tell you the complete story on how to use this technology, how to set it up and how to create robust, and state-of-the-art solutions on it. To conclude I think the content of this book will be very valuable for WF/WCF developer and also for us Microsoft integration guys.
Cheers,
Steef-Jan
BizTalk allows you to use several macros for defining a file name in a biztalk send port.
The following table lists the supported macros and describes how the File send handler replaces them.
| Macro name | Substitute value |
|---|---|
| %datetime% | Coordinated Universal Time (UTC) date time in the format YYYY-MM-DDThhmmss (for example, 1997-07-12T103508). |
| %datetime_bts2000% | UTC date time in the format YYYYMMDDhhmmsss, where sss means seconds and milliseconds (for example, 199707121035234 means 1997/07/12, 10:35:23 and 400 milliseconds). |
| %datetime.tz% | Local date time plus time zone from GMT in the format YYYY-MM-DDThhmmssTZD, (for example, 1997-07-12T103508+800). |
| %DestinationParty% | Name of the destination party. The value comes from the message context property BTS.DestinationParty. |
| %DestinationPartyQualifier% | Qualifier of the destination party. The value comes from the message context property BTS.DestinationPartyQualifier. |
| %MessageID% | Globally unique identifier (GUID) of the message in BizTalk Server. The value comes directly from the message context property BTS.MessageID. |
| %SourceFileName% | Name of the file from which the File adapter read the message. The file name includes the extension and excludes the file path, for example, Sample.xml. When substituting this property, the File adapter extracts the file name from the absolute file path stored in the FILE.ReceivedFileName context property. If the context property does not have a value-for example, if a message was received on an adapter other than the File adapter-the macro will not be substituted and will remain in the file name as is (for example, C:\Drop\%SourceFileName%).
Note
Correct implementation of this macro requires that the output message is the same message as the received message.
|
| %SourceParty% | Name of the source party from which the File adapter received the message.
Note
Correct implementation of this macro requires that the output message is the same message as the received message.
|
| %SourcePartyQualifier% | Qualifier of the source party from which the File adapter received the message.
Note
Correct implementation of this macro requires that the output message is the same message as the received message.
|
| %time% | UTC time in the format hhmmss. |
| %time.tz% | Local time plus time zone from GMT in the format hhmmssTZD (for example, 124525+530). |
The File send handler does not replace the macros with a value if any of the following are true:
There are however some restrictions when using the macros in SMTP headers.
See this post for more details on this matter.
Below is a short overview of the use of macros in SMTP headers.
| Macro | Description | For use with To | For use with CC | For use with Subject |
|---|---|---|---|---|
| %MessageID% | Globally unique identifier (GUID) of the message in BizTalk Server. The value comes from the message context property BTS.MessageID. | No | No | Yes |
| %datetime_bts2000% | UTC date time in the format YYYYMMDDhhmmsss, where sss means seconds and milliseconds (for example, 199707121035234 means 1997/07/12, 10:35:23 and 400 milliseconds). | No | No | Yes |
| %datetime% | UTC date time in the format YYYY-MM-DDThhmmss (for example, 1997-07-12T103508). | No | No | Yes |
| %datetime.tz% | Local date time plus time zone from GMT in the format YYYY-MM-DDThhmmssTZD, (for example, 1997-07-12T103508+800). | No | No | Yes |
| %time% | UTC time in the format hhmmss. | No | No | Yes |
| %time.tz% | Local time plus time zone from GMT in the format hhmmssTZD (for example, 124525+530). | No | No | Yes |
| %SourceParty% | Name of the source party from which the File adapter received the message. | No | No | Yes |
| %SourcePartyQualifier% | Qualifier of the source party from which the File adapter received the message. | No | No | Yes |
| %DestinationParty% | Name of the destination party. The value comes from the message context property BTS.DestinationParty. | Yes | Yes | Yes |
| %DestinationPartyQualifier% | Qualifier of the destination party. The value comes from the message context property BTS.DestinationPartyQualifier. | No | No | Yes |
Source: http://msdn.microsoft.com/en-us/library/aa578022(v=bts.20).aspx
Scott Guthrie announced a handful of changes to the Windows Azure Portal, and among them, was the long-awaited migration of Service Bus resources from the old-and-busted Silverlight Portal to the new HTML hotness portal. You’ll find some really nice additions to the Service Bus Queues and Topics. In addition to creating new queues/topics, you can […]
Blog Post by: Richard Seroter
I recently found myself in need of adding a username and password to a BizTalk 2010 application binding file. By default, WCF bindings at least, do not save any password currently assigned to a WCF-Custom send port when you export the application bindings from within Management Console. In order to add a password to a […]
Blog Post by: Kevin Morillo