Here are the alphabetized list of the most common terms used in BizTalk Server:
.brl File: A business rules definition file.
.btm File: A BizTalk Server map file.
.btp File: A BizTalk Server pipeline file.
.btproj File: A BizTalk project file.
.btt File: The file extension signifying tracking profiles.
.odx File: A BizTalk Server orchestration file.
.xsd File: A BizTalk Server schema file.
.itinerary File: An ESB Toolkit Itinerary
.xml File:XML file type is primarily associated with 'Extensible Markup Language'
.xsl File:XSL file type is primarily associated with 'FileMaker Database Design Report Template'.
ACID: Atomicity,Consistency,Isolation and Durability.
Action: One or more functions corresponding to the "THEN" part of a rule and used to specify what is to be done when a condition evaluates to true.
Activate Property: A property of the Receive shape, used to indicate that the orchestration is activated when a message is received. The Receive shape can only be marked as activated if it is the first send or receive activated shape in
Adapter: An adapter is a software component (COM or .NET-based) that enables you to easily send messages out of or receive messages into BizTalk Server with a delivery mechanism that conforms to a commonly
recognized standard, such as SMTP, POP3, FTP, or Microsoft Message Queuing (MSMQ). As Microsoft BizTalk Server has evolved, the need for adapters that quickly enable connectivity with commonly used applications and technologies has increased. BizTalk Includes
over 25 multi-platform adapters that simplify the integration with Line of Business (LOB) Applications (such as Siebel, SAP, JD Edwards, Oracle, and Dynamics CRM), database (Microsoft SQL Server, Oracle, DB2) and other technologies (Tibco, Java EE). (see more
Adapter Handler: An adapter handler is an instance of a BizTalk host in which the adapter code runs. When you specify a send or receive handler for an adapter you are specifying which host instance the adapter code will run in the context
of. An adapter handler is responsible for executing the adapter and contains properties for a specific instance of an adapter. A default BizTalk Server configuration will create adapter handlers for all of the installed adapters, but you may want to create
additional adapter handlers for purposes of load balancing or to provide process isolation for a particular adapter handler. (see more
Adapter Framework: The BizTalk Adapter Framework offers a stable, open mechanism for all adapters to implement or access work from the BizTalk Server Messaging Engine. The interfaces described in the Microsoft.BizTalk.Adapter.Framework namespace
enable adapters to provide a means to modify configuration property pages. It also is a means to import services and schemas into the BizTalk project. (see more
Adapter Provider: [ESB Toolkit] An Adapter Provider component sets specific properties of registered Microsoft BizTalk Server adapters. The BizTalk ESB Toolkit includes the following built-in adapter providers: FILE, FTP, SMTP,MQSeries,
WCF-BasicHttp, WCF-WSHttp, and WCF-Custom. The name of each adapter provider is identical to the name of the associated adapter (transport type) in BizTalk Server. You can extend the Adapter Provider Framework by creating and registering your own custom adapter
providers to set specific properties of registered BizTalk adapters.
Advanced Functoids: Functoids that you can used to create various types of data manipulation, such as implementing custom script (C#, Visual Basic .NET, XSLT), value mapping, and managing and extracting data from looping records.
Affiliate Application: A logical entity in Enterprise Single Sign-On (SSO), defined by the administrator, that represents a system or subsystem such as a host, back-end system, or line-of-business application to which you are connecting
using SSO. An affiliate application can represent a non-Windows system such as a mainframe or UNIX computer. It can also represent an application such as SAP, or a subdivision of the system, such as the "Benefits" or "Pay stub" sub-systems.
Agreement: The central item in relationship configuration is an agreement. An agreement defines two distinct two-way channels of communication between the associated buiness profiles, and deliniates the expectations of each party. Agreements
build on lower level technical items to fulfill the requirements of today's dynamic business needs. The agreements are based on underlying business process and party management items.
Ancestors: A node at the bottom and the top of a cycle in the tree.
ANSI X.12: A message format developed by the American National Standards Institute. X.12 is used primarily in the United States.
Application: A running BizTalk Server business solution.
AS2:AS2 (Applicability Statement 2) is a specification about how to transport data securely and reliably over the Internet. Security is achieved by using digital certificates and encryption.
Assemble Pipeline Component (Assemble Stage): A send pipeline component responsible for assembling or serializing (writes) messages to a file and converting it to or from XML, and may combine individual messagess into a batch. The syntax
transformations should occur at this stage.
Assembly: Regarding BizTalk, a dll file that contains a collection of BizTalk artifacts such as schemas, maps, orchestrations, or pipelines.
Assembly Deployment Wizard: A wizard that guides you through the steps required to add, remove, import and export assemblies; import and export bindings; and install or uninstall assemblies from the global assembly cache (GAC).
Assembly Version: An identifier for an assembly, made up of a combination of a major and a minor version.
Atomic transactions: BizTalk orchestrations can be designed to run discrete pieces of work, following the classic 'ACID' (Atomic,Consistent,Isolated and Durable) concept of a transaction. These discrete or atomic units of work, when performed,
move the business process from one consistent state to a new, consistent and durable state that is isolated from other units of work. This is typically done by using the Scope construct that encapsulates the units of work with the transactional semantics.
The entire orchestration can also be defined as an atomic transaction without the use of scopes. (see more
Attribute: In XML, an XML construct used to associate additional information with XML elements.
Authentication Trusted: A means of marking each host indicating that the host can submit messages into the message box with a Party ID (PID) that is different from (that is, not aliased by) the Windows Security
ID (SSID) of the application instance service account.
BAM: Business Activity Monitoring (BAM) is used to monitor business milestones and key metrics in near real-time throughout a process in BizTalk. Business Activity Monitoring (BAM) is a module in BizTalk that captures business data and process
milestones to allows business decision makers to gain insight of their in-flight processes. Using BI tools to derive up-to-date metrics and key performance indicators from the BAM databases, users can forecast process trends and monitor processes in real-time.
BAM also provides a mechanism to alert users to situations that require their intervention to prevent undesirable outcome or to encourage a beneficial result.
BAM Activities: identify the milestones and tracking data an individual is interested in tracking. Milestones are the steps in an activity that are measured in time, and tracking data is the key data points in a process you are interested
in tracking (such as a customer ID or name).
BAM Alerts: BAM alerts allow you to configure and receive alerts related to specific changes in business data. Alerts are set up per BAM view.
BAM Configuration: The XML file that contains the settings for BAM manifests such as the BAM Primary Import database and server names.
BAM Definition: An XML representation of a BAM observation model, i.e., it describes business activities and business views.
BAM Observational Model: A high-level definition of visibility requirements for a business process that specifics the milestone and data events to collect (the BAM activity); a description of any data aggregations; and the presentation of
information to users (the BAM view).
BAM View: A BAM view is a representation of the milestones and business data tracked in one or more activities.
BAMAnalysis Database (BAM Analysis): This database contains Business Activity Monitoring (BAM) OLAP cubes for both online and offline analysis.
BAMArchive Database (BAM Archive): This database archives old business activity data. Create a BAM Archive database to minimize the accumulation of business activity data in the BAM Primary Import database.
BAMAlertsApplication Database (BAM Notification Services Application): This database contains alert information for BAM notifications. For example, when you create an alert using the BAM portal, entries are inserted in the database specifying
the conditions and events to which the alert pertains, as well as other supporting data items for the alert.
BAMAlertsNSMain Database (BAM Notification Services Instance): This database contains instance information specifying how the notification services connect to the system that BAM is monitoring.
BAMPrimaryImport Database (BAM Primary Import): This is the database where BAM collects raw tracking data.
BAMStarSchema Database (BAM Star Schema): This database contains the staging table, and the measure and dimension tables.
Binding: In BizTalk, the term 'binding' refers to the configuration of orchestration ports in order to control the creation of subscriptions and/or 'promoted' properties. Binding is used to control how messages will be routed to or from
orchestration ports by the subscription mechanism. Hence, binding often involves additional creation and configuration of messaging Send and Receive ports so that these messaging ports can be bound to orchestration ports. Orchestration ports can also be bound
to other orchestration ports. The term binding is also used to define the association of a map or pipeline within the messaging port. In BizTalk objects that will be bound to other objects must be in the same (or a referenced) application.
Binding File: A binding file is an .xml file that contains binding information for each BizTalk orchestration, pipeline, map, or schema in the scope of a BizTalk assembly, application, or group. The binding file describes what host each
orchestration is bound to and its trust level as well as the settings for each send port, send port group, receive port, receive location, and party that has been configured. You can generate binding files and then apply the bindings they contain to an assembly,
application, or group to avoid needing to manually configure bindings in different deployment environments.
BizTalk: Microsoft BizTalk Server, often referred to as simply "BizTalk" or "BizTalk Server", is Microsoft’s Integration and connectivity server solution. With a robust messaging infrastructure, dehydration
and rehydration functionalities, more than 25 multi-platform adapters, rules engine (BRE), ability to obtain performance information on critical business processes, debug, persistence, treatment and error recovery, transactions,… Makes BizTalk Server a tool
and infrastructure unique, ideal to be used primarily for Enterprise Application Integration (EAI), Business to Business (B2B) Integration and Business Process Management (BPM) solutions. (see more
BizTalk Administrator: a system administrator will have other concerns such as the health of servers and their activity (HAT - Health and Activity Tracking), he has overall responsibility for the BizTalk Environment, such as: installation,
configuration and system maintenance, deploying and managing BizTalk Applications, monitoring (unlocking messages and processes or ensuring proper flow of messages), disaster recovery.
BizTalk Administration console: A Microsoft Management Console (MMC) used to administer a BizTalk Server group.
BizTalk Administrators Group: The group that administers BizTalk Server. Administrative tasks include accessing the Suspended queue, updating the Configuration database, and so on.
BizTalk Application: The BizTalk application is a feature introduced in BizTalk Server 2006 that makes it quicker and easier to deploy, manage, and troubleshoot BizTalk Server business solutions. A BizTalk
application is a logical grouping of the items, called "artifacts," used in a BizTalk Server business solution. (see more
BizTalk Application 1: The application created by default in every new BizTalk Server installation. This application is created mainly for backwards compatibility. Artifacts that were deployed without an application specified are shown in
this folder. Also, new artifacts that are deployed without an application specified are deployed to the Default Application. Any application may be set as the default by changing a user setting. As the default appliction cannot be deleted, specifying a critical
appliction as the default protects it from accidental deletion.
BizTalk Application Users Group: The group of users (generally the service or host accounts) who can access MessageBoxes for a particular BizTalk Group.
BizTalk Application View: One of two views (along with BizTalk Deployment View) that appears when the System Center Operations Manager console for BizTalk Server is opened. A BizTalk administrator uses
this view to monitor the health of BizTalk artifacts and applications such as orchestrations, send ports, and receive locations.
BizTalk Architect: knower of the entire system integration: backup and recovery plans, security, logging, message flow, communication interface, etc. An architect leverages their knowledge of the capabilities
and limitations of the tools at his disposal (BizTalk engine, BAM, BRE, etc.) to design; and work with programmers to build, projects that fulfill the requiremnts of the required system.
BizTalk Artifacts: Artifacts in BizTalk can be a lot of things it includes: Receive Ports and Locations, Send Ports and Send Port Groups, Schemas, Maps, Pipelines, Adapters,
Orchestrations, Role Links and Service Link Roles, Parties, Policies, the assemblies, security certificates, business rules policies, BAM configuration files, bindings, and so forth that are necessary for a BizTalk application to function. (see more
BizTalk Assemblies: All BizTalk Server artifacts; maps, schemas, orchestrations, and pipelines, get compiled into .NET assemblies. These BizTalk assemblies (as well as any other .NET helper assemblies that BizTalk
will invoke) must be registered in the Global Assembly Cache (GAC) of each BizTalk runtime server and as such they must be string-named. This strong naming also provides support for versioning. The main implication of this is that a BizTalk project, once built
against a particular version of another .NET project or assembly (including BizTalk projects), continues to use that version until it has been rebuilt against a newer version. (see more
BizTalk Benchmark Wizard: The BizTalk Benchmark Wizard (BBW) is a tool built by Mikael Håkansson and Ewan Fairweather. This tool is intended to validate a BizTalk installation. The benchmark wizard performs
load to BizTalk Server in relation to specific scenarios.
BizTalk CAT Instrumentation Framework Controller: is an easy-to-use GUI for the BizTalk CAT Instrumentation Framework. This controller enables you to start and stop a trace and
adjust filter options, and can easily enable real-time tracing to Microsoft SysInternals DebugView (or other debuggers), to a log file or to both at the same time.
BizTalk Consultant: A BizTalk consultant is a BizTalk developer/administrator with deep knowledge regarding the administration of BizTalk, configuring the environment, architecting, building, testing and deploying
BizTalk Deployment Framework: The BizTalk Deployment Framework (BTDF) supports deployments for BizTalk applications that goes far beyond BizTalk’s out-of-the-box deployment functionality.
BizTalk Developer: implements and extends the basic functionalities, taking advantage of the different tools. Here there are many areas completely orthogonal and a programmer may not master them all at the same
level: Orchestration, Adapters, Pipelines, Mappings, Functoids, Routing, Rules, Tracking, OLAP, and many more.
BizTalk Documenter: it's a tool that can automatically generate a Technical (design) documentation (compiled chm, and even HTML for 2010 version) of BizTalk solution and its configuration.
BizTalk Editor: BizTalk Editor is a tool that runs within the Microsoft Visual Studio environment. You can use it to create, edit, and manage schemas for use with your application. BizTalk Editor uses its own graphical
system of hierarchical records and fields to represent the structure of instance messages, and uses the XML Schema definition (XSD) language to store the schemas that it defines.
BizTalk Environment: A BizTalk environment is a complete installation of BizTalk, including all the artifacts required to run. SQL, BizTalk etc. This can be on a stand-alone environment or over many different
servers in a multi-server environment
BizTalk Environment Config Loader: This tool build by Rudolf Henning automates the configuration of hosts, hosts instances, adapters and adapter handlers. This helps to configure the BizTalk environment
quickly without all the manual steps usually needed.
BizTalk Explorer: A BizTalk Server 2004 tool hosted within Visual Studio that enables you to view and manage the configuration details of your project, this tool displays the contents of assemblies, ports, orchestrations,
and parties in the BizTalk Configuration database. the tool was deprecated with BizTalk Server 2006 and later in favor of the BizTalk Server Administration Console.
BizTalk Explorer Object Model: The BizTalk Explorer Object Model is a managed object model that enables programmatic configuration of BizTalk artifacts. The API allow us to automate the post-deployment
tasks such as creating ports, binding orchestrations, or managing party properties.
BizTalk Expression Editor: is an editor found in Orchestration Designer and it's a standard Visual Studio text editor, which means it offers IntelliSense and allows to enter .NET code. You use BizTalk
Expression Editor to enter an expression in textual form.
BizTalk Flat File Schema Wizard: is a template inside Visual Studio that allows you to converting Flat File into XML message which BizTalk can understand in a graphical a simple maner.
BizTalk Framework: A platform-neutral e-commerce framework that is based on Extensible Markup Language (XML) schemas and industry standards. The framework enables integration across industries and between business
systems, regardless of platform, operating system, or underlying technology.
BizTalk Group: The BizTalk group is a unit of organization that usually represents an enterprise, department, hub, or other business unit that requires a contained BizTalk Server implementation. The BizTalk group
has a one-to-one relationship with a BizTalk Server Management database.
BizTalk Mapper Designer: is a tool that runs within the Microsoft® Visual Studio® .NET environment. You use Mapper to create and edit maps to translate or to transform messages. Maps are used in orchestrations,
as the following figure suggests, and may also be used in send port message processing. Using BizTalk Mapper, you define the relationship between an input and an output schema by using links and functoids. A link defines a direct data copy of a record or field.
Links may directly connect to items in the other schema, or they may form connections to functoids. Functoids perform more complex data manipulations. (see more
BizTalk Orchestration Designer: BizTalk includes an Orchestration Designer, integrated into Visual Studio that enables developers to represent the business process in a visual way (association of
links between shapes, representation of ports and some configurations) making it easier to manage and read than textual language (C#, Java). It simplifies the process of creating orchestration models of business processes that are compiled into executable
BizTalk Project: The BizTalk project system is shipped with a Visual Studio template called the BizTalk Server Project template. Also refers to a development project utilizing Microsoft BizTalk Server.
BizTalk Schema: BizTalk Server supports the following four types of schemas: XML schema, Flat file schema, Envelope schema and Property schema. Any XML schema has the potential to be used by BizTalk Server however
some schemas utilize extentions to the W3C standards to implement special BizTalk functionailty. Envelope and Property schemas are exampls of these "extended capabilities".
BizTalk Server: Microsoft BizTalk Server, often referred to as simply "BizTalk" or "BizTalk Server", is Microsoft’s Integration and connectivity server solution. With a robust
messaging infrastructure, dehydration and rehydration functionalities, more than 25 multi-platform adapters, rules engine (BRE), ability to obtain performance information on critical business processes, debug, persistence, treatment and error recovery, transactions,…
Makes BizTalk Server a tool and infrastructure unique, ideal to be used primarily for Enterprise Application Integration (EAI), Business to Business (B2B) Integration and Business Process Management (BPM) solutions. (see more
BizTalk Server 2000: First version of the product was released in 12/12/2000. Introducing: Messaging, XML tools, XLang. Over 500 Customers.
BizTalk Server 2002: Second release of the product was been enhanced with the following features: Deployment Tools, XSD, EAI (partner adapters), Vertical B2B. Over 2000 Customers.
BizTalk Server 2004: The third version of the product was a technology revolution, was the first version to run on Microsoft .NET 1.0, introduced the mapper, CBR, PubSub and so on. it was been enhanced with
the following features: VS + .NET, Messaging + Orchestration, BRE, Routing, BAM, Scale-out. Over 4000 Customers.
BizTalk Server 2006: The fourth version of the product was the first version to run on Microsoft .NET 2.0. It was been enhanced with the following features: Simple configuration, Adapters in Box, HIS, Runtime+,
BAM+. Over 7000 Customers.
BizTalk Server 2006 R2: The fifth version of the product was the first version to utilize the new Windows Communication Foundation (WCF) via native adapter. It was been enhanced with the following features:
SOA/ESB, EDI/AS2, RFID, WCF Adapter Pack 1.0, Adapter SDK. It was release in October 2, 2007. Over 8500 Customers.
BizTalk Server 2009: The sixth version of the product was the first version to work with Visual Studio 2008. It was been enhanced with the following features: ALM Support, B2B Enhancements, RFID Mobile platform,
Adapter Pack 2.0, ESB 2.0 Toolkit, BAM+, Hyper-V Support. Over 10500 Customers.
BizTalk Server 2010: The seventh version of the product was the first version to work with Visual Studio 2010 and Microsoft .NET 4.0. It was been enhanced with the following features: Windows AppFabric, ESB
2.1, SharePoint 2010 BCS, Data Mapper, Trading Partner Management, Secure FTP, Updated Swift & HIPAA, SQL Server 2008 R2, Windows Server 2008 R2. Over 12000 Customers.
BizTalk Server 2013: The eighth version of the product was the first version to work with Visual Studio 2012 and Microsoft .NET 4.5. In this release, Microsoft is focused on the “One BizTalk” vision and have
invested both in the on-premises server and in the cloud. (The cloud offerings, which will be released soon, include Infrastructure as a Service (IaaS) capabilities as well as Platform as a Service (PaaS) capabilities).
BizTalk Server Best Practices Analyzer: The BizTalk Server Best Practices Analyzer performs configuration-level verification by reading and reporting only. It gathers data from different
information sources, such as Windows Management Instrumentation (WMI) classes, SQL Server databases, and registry entries and use that data to evaluate the deployment configuration.
BizTalk Server Functoids Wizard: or BizTalk MapperExtensions Functoid Wizard is a Custom Functoid Project Wizard for Visual Studio that allows you to create new Functoids project for BizTalk Server
without having to create manually the project. Supports both C# and VB.NET.
BizTalk Server Pipeline Component Wizard: The Pipeline Component Wizard is intended to ease the development of pipeline components used within a BizTalk Server environment. Supports both
C# and VB.NET.
BizTalk Software Factory: is a community tool that helps BizTalk developers build consistent BizTalk solutions.
BizTalk SSO Configuration Data Storage Tool: useful utility tool to store/retrieve BizTalk configuration settings (key/value pairs) in Enterprise SSO database.
BizTalk SQL Server: This is the SQL server for BizTalk running the databases used by BizTalk and the SQL Agent jobs
BizTalk Terminator: This tool was created by the BizTalk support team to resolve common database integrity issues typically found in the BizTalk MsgBox Viewer output. Common tasks include removing instances
and purging large tables.
BizTalk XML Schema Editor: or BizTalk Editor, it's a tool that runs within the Microsoft Visual Studio environment. You can use it to create, edit, and manage schemas for use with your application. BizTalk
Editor uses its own graphical system of hierarchical records and fields to represent the structure of instance messages, and uses the XML Schema definition (XSD) language to store the schemas that it defines.
BizTalkMgmtDb Database (BizTalk Management): This database is the central meta-information store for all instances of BizTalk Server
BizTalkMsgBoxDb Database (BizTalk MessageBox): This database is used by the BizTalk Server engine for routing, queuing, instance management, and a variety of other tasks.
BizTalkDTADb Database (BizTalk Tracking database): This database stores health monitoring data tracked by the BizTalk Server tracking engine.
BizTalkRuleEngineDb Database (Rule Engine): This database is a repository for: Policies, which are sets of related rules; Vocabularies, which are collections of user-friendly, domain-specific names
for data references in rules.
Business Activity Monitoring (BAM): BAM is used to monitor business milestones and key metrics in near real-time throughout a process in BizTalk. Business Activity Monitoring (BAM) is a module in BizTalk
that captures business data and process milestones to allows business decision makers to gain insight of their in-flight processes. Using BI tools to derive up-to-date metrics and key performance indicators from the BAM databases, users can forecast process
trends and monitor processes in real-time. BAM also provides a mechanism to alert users to situations that require their intervention to prevent undesirable outcome or to encourage a beneficial result.
Business Activity Services (BAS): An optional BizTalk Server feature that allows business users to configure and interact with business processes and trading partners through a website hosted by Windows
BizTalk BAS Users: Users in the business user group role can access the BAS site and have permission to use some aspects of the trading partner publishing Web service. For example, these users can create partner
profiles, but they cannot deploy the profiles to a BizTalk Server computer.
BizTalk BAS Managers: Users in the business manager group role can access the BAS site and have permission to use Trading Partner Management (TPM) tools. They can perform tasks in BAS that configure business
processes in BizTalk Server such as deploying partners or activating agreements.
BizTalk BAS Administrators: Users in the business administrator group role can access the BAS site and perform administrative tasks on the site, such as registering BizTalk Server computers.
BizTalk BAS Web Services: The technical group role contains the different service accounts used to run BAS; it does not contain individual user accounts. Service accounts have access to the TPM database
and to the Business Activity Service Windows SharePoint Services Web service.
BizTalk Host: A logical process and security boundary within BizTalk Server. Each host has a security group assigned to it and may contain multiple host instances, each on an individual machine, that perform the work
of the host. In turn, each host instance belongs to exactly one host, and the service account of the host instance belongs to the security group of the host. The security group may be used to grant permissions to physical resources such as databases for use
by any host instances in the host.
BizTalk Server Management Pack: BizTalk Server Management Pack offers monitoring capabilities for BizTalk artifacts and BizTalk-related platform components. It allows administrators to monitor health
state of various BizTalk artifacts such as Send Ports, Orchestrations etc. and platform artifacts such as Host Instances (BizTalk service). Further, this mp includes performance views, diagnostic capability and alerts.
BizTalk Server Messaging Engine: A set of services required in a middleware product to facilitate solutions to customer scenarios. These run-time services are an essential part of the BizTalk Server
platform. Among these services are performant pipeline processing of messages. Pipeline processing provides data format normalization and property extraction.
BizTalk WCF Consuming Wizard: wizard to generate the BizTalk artifacts, such as BizTalk orchestrations and types, to consume a WCF service based on the metadata document of the WCF service.
BizTalk WCF Service Publishing Wizard: wizard to create and publish BizTalk orchestrations as WCF services, and to publish schemas as WCF services for the isolated WCF adapters hosted by Web
applications running in IIS.
BizTalk Web Services Publishing Wizard: wizard to create and publish BizTalk orchestrations as Web services, and to publish schemas as Web services.
BizUnit: this tool enables automated tests to be rapidly developed. BizUnit is a flexible and extensible declarative test framework targeted that rapidly enables the automated testing of distributed systems, for example
it is widely used to test BizTalk solutions.
BTSTask: A command-line tool that enables you to manage applications and assemblies. You can use BTSTask to add a BizTalk application to the BizTalk Management database, add a resource to an application, export an application
to an MSI file, export binding information to a file, import an application from an MSI file, import binding information from a file, list all of the resourcesin an application, list all applications in the BizTalk Management database, list the contents of
an MSI file, remove an application from the BizTalk Management database and BizTalk Administration Console, and remove a resource from an application.
Business Analyst: A user who possesses business management and economics analysis skills. The primary responsibility of the business analyst is to consume business-level data and analyze it for business trends.
Business Rules Composer: In Microsoft® BizTalk® Server, the Business Rule Composer is a graphic tool used for authoring, versioning, and deploying policies and vocabularies.
Business Rules Engine: A run-time inference engine that can link highly readable, declarative, semantically rich rules to any business objects (.NET components), XML documents, or database tables. It can
evaluates rules against facts and initiates actions based on the results of that evaluation.
Business Rules Engine Framework: BizTalk Server includes the Business Rules Framework as a stand-alone .NET-compliant class library that includes a number of modules, support components, and tools.
The primary modules include the Business Rule Composer for constructing policies, the Rule Engine Deployment Wizard for deploying policies created in the Business Rule Composer, and the Run-Time Business Rule Engine that executes policies on behalf of a host
Business Rule Language: A rule markup language in XML format for declarative rule definitions.
Business-to-Business: Relating to the sales category pertaining to transactions and related activity between a business and buyers who are not consumers, such as government bodies, companies, and resellers. Refers to one business communicating
with or selling to another.
Call Orchestration Shape: Orchestration shape that enables your orchestration to call another orchestration synchronously.
Custom scripts: Custom scripts are commonly used in maps to accomplished more complex transformations or to facilitate some mapping conditions. The Scripting functoid enables you to use custom script or code at run time to perform functions
otherwise not available and supports the following languages for the Scripting functoid: C#, .NET, JScript .NET, Visual Basic .NET, Extensible Stylesheet Language Transformations (XSLT) and XSLT Call Templates.
Data Dimension: A specific node created in the hierarchical view of the Tracking Profile Editor as an immediate child of the specific tracking profile in order to describe a logical grouping or dimension of data.
Each data dimension is uniquely named and is made up of one or many data fields.
Data Item: A specific node created in the hierarchical view of the Tracking Profile Editor that is a direct child of Data Category. The data field exists as a specific field from the business payload.
Database Functoids: Functoids that you can used to look up data from a database and to perform simple cross-referencing operations (sometimes called ID mapping).
Date and Time Functoids: Functoids that you can this is a set of operations applicable on dates like, add date, time, date and time, or add days to a specified date, in output
DebugView: enables you to trace what is happening inside your application by letting you monitor debug output on your local system, or any computer on the network that you can reach via
TCP/IP. It is capable of displaying both kernel-mode and Win32 debug output, so you don't need a debugger to catch the debug output your applications.
Decide Shape: Orchestration shape that enables you to conditionally branch in your orchestration.
Decode Pipeline Component (Decode Stage): A receive pipeline component responsible for decode or decrypt the message. The MIME/SMIME Decoder pipeline component or a custom
decoding component should be placed in this stage if the incoming messages need to be decoded from one format to another. The syntax transformations can occur in this stage through a custom component.
Dedicated Hosts: The term dedicated hosts are brought up every now and then. Dedicated hosts performs dedicated tasks, and makes it easier to both control and have creates a better
overview of you environment configuring throttling and thresholds is also a lot easier when you have split them up, also take a look at.
Dedicated Send Host: Dedicated send hosts are hosts primarily dedicated to sending out information from BizTalk.
Dedicated Receive Host: Dedicated receive hosts are hosts primarily dedicated to receiving information to BizTalk.
Dedicated Orchestration Host: The dedicated orchestration host should only be run for orchestration.
Dedicated Tracking Host: This host however is maybe one of the more important once. It is the host dedicated to move tracking data from the message box to the tracking database. This host however should have the option “Allow host tracking”
checked. And should never run any receive location, orchestration or send ports. It should primarily only move tracking from the message box to the tracking database.
Default Application: When you install BizTalk Server, a default application named BizTalk Application 1 is created in the BizTalk Management database and appears in the BizTalk Server Administration console. When you upgrade from an earlier
version of BizTalk Server, your artifacts are automatically placed in this application. In addition, when you import a Windows Installer (.msi) file by using BTSTask without specifying an application, the artifacts in the .msi file are imported into the default
Default Host: Administration objects that facilitate deployment and orchestration enlistment. These objects are identified in the BizTalk Server Administration console with a checkmark symbol. During the orchestration enlistment process,
the default host is automatically used to host the orchestration, unless the user explicitly selects a different host.
Default Pipelines: When you create a new application, the default pipelines are created and deployed by default and appear in the Microsoft.BizTalk.DefaultPipelines assembly in the \References folder for every BizTalk project. The default
pipelines cannot be modified in Pipeline Designer. These pipelines can be selected when configuring a send port or receive location in BizTalk Explorer.
Dehydration: The engine might determine that an orchestration instance has been idle for a relatively long period of time. It calculates thresholds to determine how long it will wait for various actions to take place, and if those thresholds
are exceeded, it will dehydrate the instance. This save the state of a running orchestration to a persistent storage and remove it from memory when the orchestration has been idle for a certain length of time.
Delay Shape: Orchestration shape that enables you to build delays in your orchestration based on a time-out interval. For more information, see Using the Delay Shape.
Delimited Flat Files: A delimited flat file contains one or more records separated by a specified delimiter. BizTalk Editor does not read delimiters as part of the data. However, if the delimiter character does appear as data, the data can
be formatted (placed within quotation marks, for example) so that the data and the delimiter are distinguishable.
Deploy: is the act of published or to install a new software or application up and running properly in its environment.
Destination Schema: The schema used in a BizTalk Server map that represents the structure of the output message instances.
Direct binding: BizTalk offers four binding models, each with different characteristics. Each model is really a set of higher level abstractions of the basic BizTalk subscription mechanisms. One of these models is called 'Direct Binding'.
The term 'direct binding' is used to suggest that the techniques involved are all about binding one orchestration port directly to another. In this model, orchestration ports do not automatically use or exploit BTS.SPID, BTS.ReceivePortID or other related
properties. BizTalk therefore does not manage the binding of orchestration ports to messaging Receive and Send ports. Instead, it is entirely up to developers to control subscriptions and message context in order to route messages. Developers are free, if
they wish, to route messages to other orchestration ports. External binding configuration cannot be used with directly bound orchestration ports. Direct binding is the most flexible model, but at a cost. You cannot configure your orchestration ports using
binding files, and you generally need to do more programming in order to fully exploit the flexibility on offer.
Disassembler Pipeline Component (Disassemble Stage): A receive pipeline component responsible for parse or disassemble the message. The syntax transformations should occur at this stage. In the example that will be demonstrated in this article,
we will use the "Flat file disassembler" to transform a text file into XML.
Distinguished Fields: are message elements that are written into the message context. They differ with promoted properties in 2 main aspects: They are not flagged as promoted in the message context and so are not available for routing by
the Messaging Engine (adapters, pipeline…). Their typical use is instead for the orchestration engine.; They are not defined using a property schema.
Distributed Transaction Coordinator (DTC): A service, integrated with COM+, that makes distributed transactions work. DTC makes it possible to scale transactions from one to many computers without the need for special code.
Document Type Definition (DTD): A Document Type Definition (DTD) is a set of markup declarations that define a document type for an SGML-family markup language (SGML, XML,
HTML).This is one of the several ways in which the structure of an XML document can be described. BizTalk Server can open a schema described using a DTD, but converts it to XSD in the process.
DTA: DTA is the tracking data for BizTalk, it standas for Data Tracking Archive. Its used to talk to the refernce of the tracking data or in the SQL database BizTalkDTADb (BizTalk trracking database)
Duration: An element that instructs the BAM Compiler to create additional column in the View that represents the duration between checkpoints.
Dynamic Binding: BizTalk offers four binding models, each with different characteristics. Each model is really a set of higher level abstractions of the basic BizTalk subscription mechanisms. One of these models is called 'Dynamic Binding'.
This model has similarities to the 'Specify now' model in that BizTalk collects pipeline information at design time and auto-generates messaging Send ports. Receive ports are not generated, as there is no concept of a 'dynamic' Receive port. However, transport
information is not configured in the same way. Instead, developers create expressions in orchestrations to assign transport location URIs using the 'address' property of orchestration ports. The auto-generated messaging Send ports are dynamic, rather than
static. Messages passing from an orchestration through dynamic Send and Send-Receive ports are routed solely on the basis of the orchestration port's address property which is used to create BTS.OutboundTransportType and BTS.OutboundTransportLocation 'promoted'
context properties. When a dynamic messaging Send port is enlisted, it creates a set of subscriptions, with one subscription for each adapter. Each subscription tests that the BTS.OutboundTransportLocation property exists, and that the BTS.OutboundTransportType
property contains a value identifying the adapter. Hence, not only can dynamic binding route messages to any location based on the address, but also via any registered adapter.
Dynamic Send Port: A send port that does not have a destination address and adapter type associated with it. A dynamic send port allows the association of the destination address and adapter type with itself during runtime execution, thus
providing flexibility in using the same port for sending messages to different destinations using different adapter types.
DTCPing: This tool is designed to assist with troubleshooting Microsoft DTC Firewall Issues, which you'll often see in a multiserver BizTalk deployment.
DTCTester: is utility is to verify transaction support between two computers, if SQL Server is installed on one of the computers (multi-server BizTalk environment).
EDIFACT: or United Nations/Electronic Data Interchange For Administration, Commerce and Transport (UN/EDIFACT) is the international EDI standard developed under the United Nations. he EDIFACT standard provides: a set of syntax rules to structure
data; an interactive exchange protocol (I-EDI); standard messages which allow multi-country and multi-industry exchange.
EDIFACT UNOA Syntax: An EDIFACT syntax that allows the following characters only: uppercase letters, all digits, blank, exclamation mark (!), quotation mark ("), percentage sign (%), ampersand (&), opening and closing parentheses ( "(" and
")"), asterisk (*), comma, dash (-), decimal point (.), forward slash (/), semicolon (;), less-than sign (<), and greater-than sign (>).
EDIFACT UNOB Syntax: An EDIFACT syntax that allows the following characters only: lowercase and uppercase letters, all digits, blank, exclamation mark (!), quotation mark ("), percentage sign (%), ampersand (&), single quotation mark ('), opening
and closing parentheses ( "(" and ")"), asterisk (*), plus sign (+), comma, dash (-), decimal point (.), forward slash (/), colon (:), semicolon (;), less-than sign (<), equal sign (=), greater-than sign (>), and question mark (?).
Electronic Data Interchange (EDI): is a method for transferring a structured and normalized documents (data) between different computer systems or computer networks, using a set of standards to control the transfer of documents. It is commonly
used by big companies for e-commerce purposes, such as sending orders and invoices to warehouses or tracking their order.
Element: In EDI, the lowest level of information in a document. For example, invoice number. In XML, an XML construct used to organize information in a hierarchical manner by nesting some elements within other elements to a potentially unlimited
Element Groups: Groupings of sibling elements in an XML structure according to different constraints: ordered sequence (Sequence Group), unordered sequence (All Group), and one-of-many (Choice Group).
Encode Pipeline Component (Encode Stage): A send pipeline component that encode or encrypt the message. Place the MIME/SMIME Encoder component or a custom encoding component in this stage if message signing is required. The syntax transformations
can occur in this stage through a custom component.
Encoding Agreement: An agreement between the business profiles of two trading partners to use a specific encoding protocol (X12 or EDIFACT) while exchanging messages.
Encoding Protocol: A protocol that governs the structure and content of a business-to-business message. The encoding protocol settings for a business profile define the encoding protocol that a business division uses to send and receive business-to-business
messages. Some examples of encoding protocols are X12, EDIFACT, HIPAA, and EANCOM.
Encryption Key: A string used to encrypt or decrypt credentials information.
Endpoint: The logical representation of a location, typically expressed in URL form, providing a physical address for data received or sent.
Enlist/Enlisted/Unenlisted: The process of associating an orchestration with the physical environment in which it will run including, the adapters needed to transport messages to and from the orchestration, the application process in which
the orchestration is hosted, and creating the MessageBox subscriptions indicated by the routing.
Enterprise Application Integration (EAI): The process of bringing data or a function from an enterprise application together with that of another application. Enterprise application integration
is an integration framework composed of a collection of technologies and services which form a middleware to enable integration of systems and applications across the enterprise.
Enterprise Service Bus (ESB): is an architectural pattern and a key enabler in implementing the infrastructure for a service-oriented architecture (SOA). Real-world experience has demonstrated that an ESB is only one of many components required
to build a comprehensive service-oriented infrastructure (SOI). The term "ESB" has various interpretations in the market, which have evolved over time; however, the basic challenge it addresses is the same. Its primary use is in enterprise application integration
(EAI) of heterogeneous and complex landscapes.
Enterprise Single Sign-On System (ESSO): A Credential database, a master secret server, and one or more Enterprise Single Sign-On (SSO) servers. These servers do the mapping between the Windows and non-Windows credentials, look up the credentials
in the Credential database, and are used for administering the SSO system. The Credential database is also used as a configuration store to hold custom configuration data for adapters.
Envelope: A structured set of information that wraps and accompanies an instance message, often describing delivery and processing information. Envelopes can be nested.
Exception Handler (Catch Exception block): The Catch
Exception block represents an exception handler. Catch
Exception blocks are attached to the end of a Scope shape
in Orchestration Designer. Exception handling code is placed inside the Exception Handler.
External Message Format: The format of the message before or after it is processed by BizTalk Server. Sometimes the term "wire" format is also used when referring to external message format.
Fact: User data to which rule conditions are applied. At design time a fact is a reference to that data.
Fact Base: A collection of facts against which rule conditions are evaluated.
Failover Transport: A secondary transport.
Fallback Trading Partner Agreement:
A collection of settings that BizTalk Server uses for business-to-business message handling, when no explicit agreement is present.
Fault tolerance: Transactions support fault tolerance for recovery from both internal faults (such as machine failures and software faults) and external faults (such as cancel messages). Partial updates within
long-running transactions are not rolled back automatically when a transaction failure occurs, as they are in ACID transactions. The exception code block for the long-running transaction is called when a fault occurs. The exception code block contains a set
of fault handlers that you write to deal with any of the faults that can arise during the execution of the transaction. You can rely on the last known state of the messages, variables, and objects in handling the fault.
Fiddler: is a Web Debugging Proxy which logs all HTTP(S) traffic between your computer and the Internet.
File Adapter: The File adapter transfers files into and out of Microsoft BizTalk Server. The File adapter consists of two adapters: a receive adapter and a send adapter. Basically it can read messages from the file
system and submit them to the server, as well as write messages from the server to a file on the file system. (see more
Functoid Toolbox: A dockable window in Visual Studio that serves as the palette of functoids available for use during map construction. Functoids are organized into different toolbox tabs based on their intended purpose.
Global Assembly Cache (GAC): A container on a BizTalk server for a group that holds the same assemblies that are deployed to the configuration database for that group.
Group Shape: Orchestration shape that enables you to group operations into a single collapsible and expandable unit for visual convenience.
Handler: An instance of a BizTalk host on which an adapter is running.
HTTP adapter: HTTP adapter enables you to exchange information between Microsoft BizTalk Server and an application by means of the HTTP protocol. Applications can send messages to a server by sending HTTP POST or HTTP GET requests to a specified
HTTP URL and similarly, BizTalk Server can transmit messages to remote applications by sending HTTP POST requests to a specified HTTP URL. The HTTP adapter consists of two adapters: a receive adapter and a send adapter. (see more
Import/Export: In BizTalk Settings Dashboard, to import/export settings and bindings. The current BizTalk settings for group, host, and host instance are exported and saved as an XML file. BizTalk administrators import these settings to
apply them to another BizTalk environment.
Itinerary-Service: [ESB Toolkit] An itinerary-service is a step of the itinerary, this can be an Messaging service (aka: Pipeline component that runs in the context of a receive/send handler), Orchestration service (orchestration which performs
processing). The itinerary-services are typically started in an on-ramp and subscribe using specific filters (ServiceName, ServiceType, SeviceState)
JD Edwards EnterpriseOne Adapter: Microsoft BizTalk Adapter for J.D. Edwards EnterpriseOne enables you to use JD Edwards EnterpriseOne business functions within BizTalk Server. (see more
JD Edwards OneWorld Adapter: Microsoft BizTalk Adapter for JD Edwards OneWorld enables you to use JD Edwards OneWorld business functions within BizTalk Server. (see more
Key Performance Indicator (KPI): Customizable business metrics provided by Analysis Services. KPIs consist of relevant attributes and associated calculations that generate industry-standard goals and benchmarks. A KPI collection includes
a measure, a goal, display properties, and variances. Companies use KPIs to track performance and improve decision-making abilities.
Late Bound Port: A port defined in the orchestration, which has the Binding property set to Specify later. A late bound port is configured when it is bound to a physical port. The binding is performed using the BizTalk Administration Console.
Log Parser 2.2: Log parser is a powerful, versatile tool that provides universal query access to text-based data such as log files, XML files and CSV files, as well as key data sources on the Windows® operating system such as the Event Log,
the Registry, the file system, and Active Directory.
Macro: is a pre-defined variable processed by a component (e.g. adapter or pipeline) before it moves on to its main task. A user assigns macros to the properties of the component, either statically (through an adapter configuration dialog)
or dynamically (from within an orchestration). Macros are defined using the percent character (%) at the beginning and end of the macro. For example, if you wanted to include a date and time in your filename, simply use the DateTime macro as follows - %DateTime%.
Macros can be used either on their own or in combination with other macros.
Map: Maps are graphical representations of XSLT (Extensible Stylesheet Language Transformation) documents that allow us to perform, in a simple and visual manner, transformations between
XML messages. A map file basically is the XML file that defines the correspondence between the records and fields in one schema and the records and fields in another schema. You create a map when you want to transform or translate data that you receive or
send from one schema to another. (see more
Multi-part Message Type: A definition of the structure of a message, including the data types of its elements. A multi-part message type can contain a single part or many parts.
Native adapter: The adapters supplied by BizTalk Server, which includes MQSeries, File, FTP, HTTP, SMTP, SOAP, and SQL adapters.
Node: The entry in a schema tree displayed within BizTalk Editor and BizTalk Mapper.
Off-Ramp: [ESB Toolkit] An Off-Ramp corresponds to a BizTalk dynamic send port. As an itinerary is being processed, values are promoted to the context properties of the associated message using the System-Properties.xsd schema. The BizTalk
publish-subscribe mechanism uses these promoted properties to route a message through a dynamic send port (off-ramp) to complete a message delivery.
OLAP (Online Analytical Processing): A technology that uses multidimensional structures to provide rapid access to data for analysis. The source data for OLAP is commonly stored in data warehouses in a relational database.
One-way Port Type: A port type consists of a communication pattern, a set of operations (requests or responses), and the message types that those operations can work on. The pattern can be either one-way or request-response
(two-way), and all operations defined on that port type must use the same pattern. One-way - input only: The endpoint receives or send a message.
On-Ramp: [ESB Toolkit] A BizTalk receive location responsible for receiving ESB-destined messages.
Operation: A request or request-response pairing on a port that is associated with either a send or receive action.
Operations Views: On the Group Hub page, views that enable the user to view but not track live data.
Operations/Message Details View: A detailed view of all known information for a given message in the MessageBox.
Operations/Messages View: A live view of messages used by services in the MessageBox database.
Operations/Service Instance Details View: A detailed view of all known information for a given service instance in the MessageBox.
Operations/Service Instances View: A live view of services (active or suspended) in the MessageBox database; in BizTalk Server 2002, the WorkQ/SuspendedQ.
Oracle Database ODBC Adapter: Microsoft BizTalk Adapter for Oracle Database, enables you to access stored procedures, tables, and views for Oracle databases that run on Oracle 8i or 9i Database. The interfaces are made available as schemas
that you can use when Oracle Database items are imported into BizTalk Server projects. (see more
Parallel Actions Shape: Orchestration shape that enables your orchestration to perform two or more operations independently of each other.
Publishing: The act of storing a message instance in the MessageBox database so that it can be matched to a subscription from a consuming application.
Query Builder View: A view in the old Health and Activity Tracking (HAT) tool that you use to create and run queries against the DTA database.
Queue: is a particular kind of abstract data type or collection in which the entities in the collection are kept in order and the principal (or only) operations on the collection are the addition of entities to the rear terminal position,
known as enqueue, and removal of entities from the front terminal position, known as dequeue. This makes the queue a First-In-First-Out (FIFO) data structure.
Range Dimension: In BAM, a dimension used to create ranges of crirteria. For example, you could create Low (0-100), Medium (100-500), and High (500-1000) ranges to describe sales of numerical units.
Rules Store: A location for persisting policies. A SQL Server database is the default rule store.
SAP Adapter: Microsoft® BizTalk® Adapter v2.0 for mySAP™ Business Suite (the Adapter) enables you to integrate the functionality of BizTalk Server with mySAP™ Business Suite. (see more
Syntax Transformations: or Data Translation, this type of transformations occurs in the receive or send pipelines and aim to transform a document into another representation, e.g. CSV to XML. Here the document maintains the same data (semantics),
but changes the syntax that is represented. I.e. we translate the document, but typically we don't modify the structure. Normally, this type of transformation is bidirectional, since we still have the same semantic content, we can apply the same transformation
logic and obtain the document in its original format.
Target Database/Environment: Identified when deploying an assembly and its bindings into a target environment.
Transport Protocol: A protocol that governs the transport channel used for sending messages back and forth between two partners. With respect to trading partner management (TPM), only the AS2 protocol is supported.
Undeploy: The process of deleting a BizTalk application from the BizTalk Server databases and Administration Console, as well as removing the application from any computers on which it was installed.
Updategram: An updategram is a data structure that you can use to express a change in the data. INSERT, UPDATE, and DELETE commands are represented in an updategram by the difference of the image of the data before and the image of the data
after a change
Versioning: The act of updating the implementation of an artifact and incrementing its version number.
Vocabulary Element: A human-readable name for facts.
WCF Adapter: The BizTalk Adapters for Windows Communication Foundation (WCF) allow BizTalk Server to communicate with WCF-based applications. The BizTalk WCF adapters include five physical adapters that represent the WCF predefined bindings—BasicHttpBinding,
WsHttpBinding, NetTcpBinding, NetNamedPipeBinding, and NetMsmqBinding. The WCF adapters for the predefined bindings are provided to enable you to easily configure necessary information for most application requirements. (see more
WSS Adapter: The BizTalk Server adapter for Windows SharePoint Services provides a tighter integration with Windows SharePoint Services and Microsoft Office InfoPath. Basically it enables you to send BizTalk Server XML and binary messages
to SharePoint document libraries and receive messages from any view of any document library and archive them to a specified document library using the specified file name. (see more
X.509 Certificate: The standard certificate format used by Windows certificate-based processes. An X.509 certificate includes the public key and information about the person or entity to whom the certificate is issued, information about
the certificate, plus optional information about the certification authority (CA) issuing the certificate.
XML (Extensible Markup Language): is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable designed to represent and exchange a wide variety of
XML Schema: or XSD (XML Schema Definition) describes the structure of a business document that is represented in XML. XML Schema is a specification developed and maintained under the auspices of the World Wide Web Consortium.
XSLT (Extensible Stylesheet Language Transformations): is a style sheet language for XML documents (stands for XSL Transformations), it defines the transformation rules of the messages
Zombie Message: The terms "orphans” and "zombies" are often used interchangeably. An orphaned or zombie message is a message that does not have an associated service instance, typically because the service instance has terminated before
the message was received. An orphaned or zombie service is a service that does not have any associated messages.
Zombie Resurrector: An orchestration that listens at the MessageBox database for zombies and resurrects those that meet certain criteria.
Another important place to find a huge amount of BizTalk related articles is the TechNet Wiki itself. The best entry point is
BizTalk Server Resources on the TechNet Wiki.