biztalk

Change page: < 1 2 > | Displaying page 1 of 2, items 1 to 30 of 35.

BizTalk Server 2009 : Executing Business Rules (part 2) - Calling the Engine from a .NET Application, Policy Chaining

Policy chaining is the ability to call one policy from another. Policy chaining is not natively supported through the Business Rule Engine, but can still be accomplished through additional coding. Essentially, a policy can call .NET code that executes another policy.

BizTalk Server 2009 : Executing Business Rules (part 1) - Returning a Value from the BRE to the Calling Orchestration

Sometimes a developer needs a return value from the business rules policy for his code to execute a different piece of logic depending on the policy's results. Despite the fact that the BRE doesn't support return values, it still can "share" a common object with a calling orchestration.

BizTalk Server 2009 : Playing By The Rules? Use The Business Rule Engine - Going to Production

Once all business policies and their required vocabularies are defined and well tested, you can deploy them to your production environment. You have a few deployment options.

BizTalk Server 2009 : Testing Business Rules

Once all business policies and their required vocabularies are defined, you need to test and debug them before deploying them in production.

BizTalk Server 2009 : Playing By The Rules? Use The Business Rule Engine - How Does the BRE Work?

The main activities of the Business Rule Engine fall into one of two main user experience categories, the design-time experience and the runtime experience. At design time, business rule creators can use the business policy authoring tool, namely the Business Rule Composer in BizTalk, to create and update the business rules and policies.

BizTalk Server 2009 : Playing By The Rules? Use The Business Rule Engine - The Business Rule Composer

The Business Rule Composer, illustrated in Figure 1, is the environment used by business rule authors to create, update, version, publish, and deploy vocabularies and policies.

BizTalk Server 2009 : What the Maestro Needs to Know: Advanced Orchestration Concepts - Pitfalls of Orchestration Development

Some BizTalk artifacts lend themselves nicely to particular patterns of solutions, while their use could be devastating to the performance of a different solution. The following sections describe some of these solution patterns and the pitfalls that you as a BizTalk developer need to watch out for.

BizTalk Server 2009 : What the Maestro Needs to Know: Advanced Orchestration Concepts - Dynamic Message Transformations

Dynamic message transformations are an important technique often overlooked by developers. This feature allows you to choose from a series of maps based on a parameter of the incoming message and perform transformations inside orchestrations.

BizTalk Server 2009 : What the Maestro Needs to Know: Advanced Orchestration Concepts - Correlation

Automating a business process tends to require associating multiple messages together to achieve the necessary business transaction. Correlations are used whenever an orchestration does not have an explicit way of associating a message with an instance, such as an activating receive, a request-response, or a self-correlating port.

BizTalk Server 2009 : Advanced Orchestration Concepts - The Cost of Parallel Shapes

If you were to ask seasoned developers whether to use a multithreaded approach to respond to a set of requests, each resulting in a series of calculations followed by the formatting of a response, or simply resorting to using a limited number of threads to respond to these requests, they would likely say that a single threaded approach would be their method of choice.

BizTalk Server 2009 : Threading and Persistence

Threads are a limited resource in BizTalk hosts and persisting a running instance state to the Messagebox is an expensive operation. The orchestration engine balances the use of threads and orchestration persistence and dehydration delicately to ensure the continued execution of the maximum number of instances possible with the minimum overhead required.

BizTalk Server 2009 : Do You Really Need an Orchestration?

Like all eager developers, you probably want to know the answer to this question right away. After all, an orchestration often seems like the best tool for you to use, as it is simply a procedural algorithm in a visual form.

BizTalk Server 2009 : What the Orchestration Engine Provides

The BizTalk orchestration engine, the XLANG engine, consists of a set of SQL Server stored procedures, jobs that run on the BizTalk Messagebox database—msgbox DB—and Management Database as well as a set of managed assemblies that run within BizTalk host instances.

BizTalk Server 2009 : Handling Ordered Delivery

Most know that BizTalk has a mechanism called Ordered Delivery that is available for a port inside an orchestration or within a messaging port. In short, this setting forces the port to deliver the messages out of the Messagebox in the order in which they were received.

BizTalk Server 2009 : Implementing Dynamic Parallel Orchestrations

Microsoft BizTalk Server orchestrations allow parallel business execution branches, using the native Parallel Actions shape. However, the number of branches is static: to add an execution branch, you need to modify and recompile an orchestration.

BizTalk Server 2009 : Administrative Tools (part 4) - MSBuild

MSBuild is Microsoft's build platform and is the technology used by Visual Studio. MSBuild is also included in the .NET Framework and can be used to build Visual Studio projects without requiring Visual Studio to be installed.

BizTalk Server 2009 : Administrative Tools (part 3) - ExplorerOM

The ExplorerOM object model is a set of classes and interfaces from the ExplorerOM namespace used by BizTalk Explorer to configure applications. You can consider ExplorerOM as an API to the Management Database that allows you to perform application management and configuration tasks.

BizTalk Server 2009 : Administrative Tools (part 2) - WMI

Tables 11 and 12 describe the different BizTalk WMI classes and events. To utilize these classes, you must use the WMI COM API or the System.Management assembly, which is a .NET COM Interop assembly.

BizTalk Server 2009 : Administrative Tools (part 1) - BizTalk Administration Console, BTSTask

BTSTask is a command-prompt application that replaces BizTalk 2004's BTSDeploy command-prompt application. Unlike BTSDeploy, BTSTask does not come with a wizard. If developers or administrators want to use a GUI, they must use the BizTalk Administration Console.

BizTalk Server 2009 : Deploying a BizTalk Solution (part 3) - IMPORTING A BIZTALK APPLICATION

The BizTalk Administration Console and BTSTask command-line application are the two applications that allow a user to export, import, and install a BizTalk MSI file. Please note that the BTSDeploy tool from BizTalk Server 2004 has been deprecated and is no longer included; therefore, scripts should be migrated to the BTSTask tool.

BizTalk Server 2009 : Deploying a BizTalk Solution (part 2) - EXPORTING A BIZTALK APPLICATION

Exporting a BizTalk application consists of taking all BizTalk artifacts for a particular application and packaging them into an MSI file. Exercise 2 walks you through the process.

BizTalk Server 2009 : Deploying a BizTalk Solution (part 1) - Steps in Deploying a BizTalk Application

Once a BizTalk application has been imported into the Management Database, all other BizTalk servers in the BizTalk Server Group are now aware of the new BizTalk application and its artifacts.

BizTalk Server 2009 : BizTalk Applications, Important Deployment Artifacts

The BizTalk application becomes the primary scope when dealing with deployment. Remember, the purpose of a BizTalk application is to group BizTalk artifacts. Figure 1 depicts a BizTalk application along with the artifacts associated with it.

BizTalk 2009 : Pipeline Component Best Practices and Examples - Using BizTalk Streams

A stream as a programming construct is a sequence of bytes with no fixed length. When you begin to read a stream, you have no idea how long it is or when it will end. The only control you have is over the size of the data you will read at any one time.

BizTalk 2009 : Pipeline Component Best Practices and Examples - Creating Documents

There are two ways to accomplish this task: the right way and not-so-right way. The not-so-right way is the simplest. What most people do is hard-code the XML for the new empty document in a string and assign it to a new XMLDocument object.

BizTalk 2009 : Creating More Complex Pipeline Components (part 4) - Custom Disassemblers

As in any component development model, it is necessary to store properties that a user selects for your component so you can load them at runtime and also validate that the values chosen by the user are appropriate.

BizTalk 2009 : Creating More Complex Pipeline Components (part 3) - Validating and Storing Properties in the Designer

BizTalk 2009 : Creating More Complex Pipeline Components (part 2) - Schema Selection in VS .NET Designer

The property MyDocSpec in the previous section's MyProber class is actually of type SchemaWithNone. SchemaWithNone is a class that lives in the Microsoft.BizTalk.Component.

BizTalk 2009 : Creating More Complex Pipeline Components (part 1) - Dynamically Promoting Properties and Manipulating the Message Context

The simplest and most common use of a pipeline component is to promote custom properties into the message context for a message. Often the data for the property is not available in the schema or is not easily accessible.

BizTalk 2009 : Custom Components - Key BizTalk API Objects

All pipeline components, regardless of what they do, will use the interfaces described in the following subsections.