Azure search is an indexing service where you can look for content in documents. You could compare it with your personal Bing search engine for your own indexed documents. You can configure and search your documents by using the Azure Search REST API. This blog post tells you more about it.
Recently I work in a project when I need to communicate with Oracle database in which I encountered some platform configuration problems. In general, communicate with Oracle is very simple and somewhat similar to SQL Server. In development phase I didn’t have any problem, but notice that before you start developing you need to make […]
Blog Post by: Sandro Pereira
Thanks to all participants, however only 59% of the responses were correct, all due to a small trap – I apologize for that – that I put the third question. The correct answers for the questions were: Does BizTalk Services Bridges applies the VETER (Validate, Enrich, Transform, Enrich and Route)? Correct answer: A) Yes Where […]
Blog Post by: Sandro Pereira
I think the answer is no unless you are prepared to accept the risk of duplicates and/or lost messages. Let me explain why below. This is a summary of conversations that I have had with my colleagues and external parties about this topic over the last two months and I have at times copied directly […]
Blog Post by: mbrimble
A couple of months ago I released theBRE Pipeline Frameworkv1.5 (since superseded by v1.5.1) to CodePlex. One of the new features in this version of the framework is support for dynamic transformation. In this blog post I’ll explain some scenarios in which this feature might be useful to you and show you how you can […]
Blog Post by: Johann
Introduction
Before we start learning PostSharp we must understand the idea of Aspect Oriented Programming.
Aspect oriented programming, or “AOP”, is the programming style which allows the separation of distinct, independent functions. This inevitably increases code modularity and in turn drives towards cohesive functionality. We tend to classify these distinct functions as cross-cutting concerns due to the […]
Blog Post by: Alex Chantharasouk
The .NET Framework’s standard System.Diagnostics.Trace component is often being used for instrumenting .NET applications but when event capture is enabled in the DebugView tool it significantly impacts application performance. Therefore it’s not suitable to use in a production environment.
If you want to use tracing in all your environments you can use the BizTalk CAT Instrumentation Framework. It’s is a high performance tracing/logging framework for BizTalk that builds upon the Event Tracing for Windows (ETW) infrastructure. Microsoft used essentially the same framework to instrument BizTalk itself, as well as many recently released adapters.
You can use ETW tracing in regular BizTalk artifacts but also in custom ESB Toolkit components it’s possible to implement it.
Instrumentation of Itinerary Messaging Services
Itinerary Messaging Services can be instrumented using TraceManager.PipelineComponent which is dedicated for this type of BizTalk artifacts.
Instrumentation of Itinerary Orchestration Services
As Itinerary Orchestration Service can be complex, the instrumentation is becoming a key factor in helping to diagnose and troubleshoot behavioral problems, performance-related issues and other bottlenecks that were not foreseen or manifested themselves during development.
Instrumentation of Custom Components
Custom .NET components that are executed in Itinerary Services can be instrumented by invoking the trace methods provided by TraceManager.CustomComponent
The examples below illustrates how to use the TraceManager component inside an Itinerary Orchestration Service.
The BizTalk CAT Instrumentation Framework Controller is an easy-to-use GUI for the BizTalk CAT Instrumentation Framework. The Controller lets you start and stop a trace and adjust filter options. It can easily enable real-time tracing to Microsoft SysInternals DebugView , to a log file or to both at the same time.
When you trace to file you can open the file in a Text Editor by clicking on the “Open Log in Text Editor” button.
For more information on ETW tracing see:
BizTalk Service currently requires that Service Bus entities that do not have partitioning enabled. A new feature was introduced late last year in Service Bus that now enables partitioning in Service bus entities by default. Once this property is set, it cannot be changed.
If one tries to deploy a project from Visual Studio which has Queue at the source with partitioning enabled, the following error can be expected:
Error 1 QueueSource1 deployment failed at ‘https://test.biztalk.windows.net/default/passSB/sources/QueueSource1’.
Failed to connect to the Service Bus using specified configuration.
Deployment of a project from Visual Studio having Queue\Topic with partitioning enabled as a destination completes successfully. However, during runtime, when a message is actually being sent to the Queue\Topic, the following error can be expected:
This client is not supported for a partitioned entity. The client version should be greater or equal than version ‘2013-10′..58ca562e-49ef-4c92-823d-1a219c3f52bd_G8
Following are some of the ways to address this issue:
1. Customer can use a queue created from SB Explorer. Queues created this way, do not have entity partitioning enabled by default
2. Use custom create option while creating queues\topics. In the second page, user should disable partitioning
Blog Post by: BizTalk Blog
Microsoft Azure BizTalk Services August 2014 Update is now live!
We are pleased to announce the August 2014 update of Microsoft Azure BizTalk Services and the associated SDK.
The release provides ability to configure and manage agreements and bridges separately, new features for EDI, enhanced encryption for AS2, supports advanced XML schema constructs in transforms and is Drummond certified.
While these features are immediately available in any new BizTalk services you create, existing services will be upgraded over in next few days. There would be no impact to availability of existing services as we roll out the upgrade. There are no pricing changes with this announcement.
Key features you can now leverage with this release are:
Ability to Configure and Manage Agreements and Bridge Separately
You can now change settings in a bridge (transforms, transport settings …) without having to redeploy the corresponding agreement. Additionally one bridge can now cater to multiple agreements. Agreements and bridges can be configured and managed separately enabling reuse of configurations and ease of management.
Visit BizTalk Portal now to try it out…
Note: all your existing agreements and bridges continue to function as before. This feature update decouples existing agreements and its associated bridges but does not break functionality in any way
EDI Delimiters at a Transaction Set Level
When sending messages to a B2B partner via an agreement you could use only one pair of delimiters for that partner. With this release Azure BizTalk Services allows configuration of delimiter set per message type on the outbound side. This is applicable for both X12 and EDIFACT protocols. Acknowledgements generated during receive side processing can also choose to use the delimiter set of the incoming message for which they were generated.
Enhanced digest and encryption algorithms for AS2
Supported symmetric key encryptions:
Existing: RC2, 3DES
New: AES-128, AES-192, and AES-256
Supported algorithms for MIC calculation:
Existing: MD5, SHA1
New: SHA2-256, SHA2-384, and SHA2-512
AS2 Drummond Certified
We are happy to announce that with this release Azure BizTalk Services is now AS2 Drummond Certified. See the same being announced by the Drummond Group here and here.
Support for Advanced XML Schema Constructs
All advanced XML schema constructs used in complex schemes, including derived types (xs:extension and xs:restriction types), are now fully supported in Transforms. These derived types are typically used in OAGIS, Salesforce and GJXDM schemas. When you create links from elements under a “derived type” node in the Source schema, that link is only executed when the “xsi:type” value in the input XML instance matches the type value for that specific node. For “derived type” node in the Target schema, the correct “xsi:type” is stamped automatically in the output XML instance based on the incoming mapping links.
Following is the list of the XML schema constructs that are newly supported.
Azure BizTalk Services Team
Blog Post by: BizTalk Blog
There are a few common deployment errors in Microsoft Visual Studio when redeploying a previously deployed BizTalk project.
“Failed to add resource(s). Change requests failed for some resource. BizTalkAssemblyResourceManager failed to complete end type change request. Failed to update binding information. Cannot update receive port “”. Transform “” not found”
There are a few other similar errors […]
Blog Post by: Kevin Morillo