Explore topic-wise InterviewSolutions in Current Affairs.

In BizTalk there are two types of subscriptions. Activation SUBSCRIPTION and Instance Subscriptions.
Activation Subscription: It is a subscription which INDICATES that when the a message which satisfies the subscription should create a new insatnce of the subscriber(Orchestration/Send PORT).
Instance Subscription: It is a subscription which indicates that when a message which satisfies the subscription should be routed to ALREADY running instance.

In BizTalk there are two types of subscriptions. Activation subscription and Instance Subscriptions.
Activation Subscription: It is a subscription which indicates that when the a message which satisfies the subscription should create a new insatnce of the subscriber(Orchestration/Send Port).
Instance Subscription: It is a subscription which indicates that when a message which satisfies the subscription should be routed to already running instance.

That's a Domain Name Server.
It is a software COMPONENT which is part of WINDOWS Server and becomes USED for looking up IP ADDRESSES by domain NAMES.

That's a Domain Name Server.
It is a software component which is part of Windows Server and becomes used for looking up IP addresses by domain names.

• Scaling up =>add better CPU's, more RAM in the CURRENT servers.
• Scaling out => add more servers, create FAILOVER- and Load Balanced clusters, add MessageBoxes.
• Increase RESOURCES AVAILABLE for hosts.
• LOCATE problem integration and prevent possible build ups in the databases.

• A party is an ENTITY outside of BizTalk Server that interacts with an orchestration.
• In BizTalk Server, each organization with which you exchange messages is represented by a party.
• You can DEFINE how the party interacts by ENLISTING it in a ROLE.

• FTP-adapter 
• POP3-adapter 
• SQL-adapter

All the adapters which lack a LOCKING system, like FTP, POP3, and MSMQ.For a high AVAILABLE BizTalk GROUP these adapters NEED to be clustered.

All the adapters which lack a locking system, like FTP, POP3, and MSMQ.For a high available BizTalk Group these adapters need to be clustered.

TDDS stands for TRACKING DATA Decode Service.
This service is responsible for moving tracking event data from the BizTalk SERVER MessageBox DATABASE to the BizTalk Server tracking database and BAM is BAM is used.

TDDS stands for Tracking Data Decode Service.
This service is responsible for moving tracking event data from the BizTalk Server MessageBox database to the BizTalk Server tracking database and BAM is BAM is used.

Just USE it when it's ABSOLUTELY NECESSARY! Turn off any non-default TRACKED ARTIFACTS as soon as possible! It's a pain for your overall performance

Just use it when it's absolutely necessary! Turn off any non-default tracked artifacts as soon as possible! It's a pain for your overall performance

• Global Tracking is the general Tracking SWITCH.
• If it's TURNED off, nothing will be tracked.
• If it's turned on, by default it tracks instances, in and out events for all pipelines.
• All application containing orchestration exported from Visual Studio will by default have all orchestration event tracking turned on, it's recommended to TURN this off in any PRODUCTION ENVIRONMENT.

Much better mapper tool, SUPPORT SQL Server 2008 and SQL Server 2008 R2.
Better administration console. VS 2010(!) is used for development.
There have also been a lot of CHANGES and all host settings have been transferred and moved into the administration console.

Much better mapper tool, support SQL Server 2008 and SQL Server 2008 R2.
Better administration console. VS 2010(!) is used for development.
There have also been a lot of changes and all host settings have been transferred and moved into the administration console.

One cumulative update PACKAGE for Microsoft BIZTALK Server and CONTAINS hotfixes for BizTalk Server, issues that were resolved after the release of a particular version of the BizTalk Server and includes all the component packages.
Cumulative Update package take some minutes to install, and you'll NEED to restart the server after you apply the CU.
The cumulative update should be installed on all servers that run BizTalk components.
 Important note: The cumulative update package updates only those components that are installed on the system.
In BizTalk 2013 the updates for BizTalk is pushed to regular updates, versions prior to this has to be downloaded and installed manually.

One cumulative update package for Microsoft BizTalk Server and contains hotfixes for BizTalk Server, issues that were resolved after the release of a particular version of the BizTalk Server and includes all the component packages.
Cumulative Update package take some minutes to install, and you'll need to restart the server after you apply the CU.
The cumulative update should be installed on all servers that run BizTalk components.
 Important note: The cumulative update package updates only those components that are installed on the system.
In BizTalk 2013 the updates for BizTalk is pushed to regular updates, versions prior to this has to be downloaded and installed manually.

The BIZTALK ADAPTER Pack is a package which contains several ADAPTERS for LoB systems. adapters for SAP, Siebel and Oracle.

The BizTalk Adapter Pack is a package which contains several adapters for LoB systems. adapters for SAP, Siebel and Oracle.

The BizTalk ESB Toolkit provides architectural guidance, patterns, and a collection of BizTalk Server and .NET FRAMEWORK components to simplify the development of an Enterprise Service BUS (ESB) on the Microsoft platform and to allow Microsoft customers to extend their own MESSAGING and INTEGRATION solutions

The BizTalk ESB Toolkit provides architectural guidance, patterns, and a collection of BizTalk Server and .NET Framework components to simplify the development of an Enterprise Service Bus (ESB) on the Microsoft platform and to allow Microsoft customers to extend their own messaging and integration solutions

BizTalk Server 2010 support the following SharePoint versions: SharePoint Services 2010, SharePoint Foundation 2010, WSS 3.0 with Service Pack 2 (SP2), and Microsoft Office SharePoint Server 2007 Service Pack 1 (SP1) (MOSS).
 One of this components must be INSTALLED because is required for using WSS Adapter

BizTalk Server 2010 support the following SharePoint versions: SharePoint Services 2010, SharePoint Foundation 2010, WSS 3.0 with Service Pack 2 (SP2), and Microsoft Office SharePoint Server 2007 Service Pack 1 (SP1) (MOSS).
 One of this components must be installed because is required for using WSS Adapter

It is special, because this job represents the only correct WAY to make BACKUPS from BizTalk, the job also performs a transactional backup so a RESTORE will happen without having invalid and out of SYNC DATABASES.

It is special, because this job represents the only correct way to make backups from BizTalk, the job also performs a transactional backup so a restore will happen without having invalid and out of sync databases.

A JOB that monitors certain ASPECTS of BizTalk Server which are mainly RELATED to MESSAGE and Instance REFERENCE counts.

A job that monitors certain aspects of BizTalk Server which are mainly related to Message and Instance reference counts.

In BizTalk 2009 the HAT (HEALTH and Activity TRACKER) has been removed.
Its FUNCTIONALITY, TRACK and display information relating to live and HISTORICAL message data, is now available from the Group Hub.

In BizTalk 2009 the HAT (Health and Activity Tracker) has been removed.
Its functionality, track and display information relating to live and historical message data, is now available from the Group Hub.

The BizTalk Administration Console maintains a local cache and when the administration console is opened it caches the ENTIRE configuration in ONE go. The refresh INTERVAL can be configured, default is 60 SECONDS.

The BizTalk Administration Console maintains a local cache and when the administration console is opened it caches the entire configuration in one go. The refresh interval can be configured, default is 60 seconds.

When administration console is slow then you NEED to check a few THINGS concerning SQL SERVER LIKE size of BizTalk databases, connectivity with SQL Server, or set the Recovery Mode of all BizTalk databases from Full to Simple (not recommended in production.

When administration console is slow then you need to check a few things concerning SQL Server like size of BizTalk databases, connectivity with SQL Server, or set the Recovery Mode of all BizTalk databases from Full to Simple (not recommended in production.

A BizTalk guideline will give you the benefits of having the availability to improve stability, optimize the work flow for BizTalk and keep a track of information regarding your environment, and the way these things work at your company.

This will make it easier for NEW people coming in working for or at your company to understand how BizTalk works at your company.

 What the guidelines for your company should contain is all up to what you NEED.

You need to keep information regarding routines, setup, configuration, backup routines etc.

So all KNOWLEDGE regarding the company structure for BizTalk is SAVED and stored whenever someone quits or for instance hiring a consultant.

The guidelines can also provide values NEEDED to improve the communication between developers and administrators.

A BizTalk guideline will give you the benefits of having the availability to improve stability, optimize the work flow for BizTalk and keep a track of information regarding your environment, and the way these things work at your company.

This will make it easier for new people coming in working for or at your company to understand how BizTalk works at your company.

 What the guidelines for your company should contain is all up to what you need.

You need to keep information regarding routines, setup, configuration, backup routines etc.

So all knowledge regarding the company structure for BizTalk is saved and stored whenever someone quits or for instance hiring a consultant.

The guidelines can also provide values needed to improve the communication between developers and administrators.

• This DATABASE STORES health monitoring data tracked by the BizTalk SERVER TRACKING engine.
• It stores data of completed processes which comes from the MessageBox
• It stores data of suspended/terminated processes which comes from the MessageBox
• Can be used for report GENERATION
• Can be used for monitoring 
• Can be used for analysis 
• Can be used for Orchestration debugging 

BizTalk Server enables hosts identified as authentication TRUSTED to indicate that the sender of a message that the trusted HOST is queuing to the MessageBox database is an entity other than the trusted host itself.

The primary purposes of authentication trust are to enable pipelines to resolve to a Product ID (PID) and PASS that PID along to consuming services for USE in authorization and outbound party RESOLUTION, and to enable the transmission of the sender Windows Security ID (SSID) along to consuming services for use in orchestration action authorization.

BizTalk Server enables hosts identified as authentication trusted to indicate that the sender of a message that the trusted host is queuing to the MessageBox database is an entity other than the trusted host itself.

The primary purposes of authentication trust are to enable pipelines to resolve to a Product ID (PID) and pass that PID along to consuming services for use in authorization and outbound party resolution, and to enable the transmission of the sender Windows Security ID (SSID) along to consuming services for use in orchestration action authorization.

•  MSMQ stands for Microsoft Message Queue.
• It's a QUEUING mechanism which comes out-of-the-box with Windows Server.
• Be aware that MSMQ lacks a locking mechanism and therefore has to be accessed from a single Host Instance.
• Use a FAILOVER cluster to make this Host Instance HIGH available.

In BizTalk Server 2006/2006 R2 the Global TRACKING can be turned off through a manual action in BizTalk Management DATABASE

In BizTalk Server 2006/2006 R2 the Global Tracking can be turned off through a manual action in BizTalk Management Database

• BAM (BUSINESS Activity Module) has a business driver, while DTA (Data Tracking Architecture ) is used for Tracking purposes.
• With BAM Users can define Views and Notifications based on CERTAIN (Business) events.
• These views can be used from a SharePoint PORTAL.
• This portal is ALSO the PLACE where Notifications are created.

This is the configuration FILE for BTSNTSVC.exe, which runs as a Windows SERVICE and is a Host Instance, INFORMATION regarding the configuration of the HOSTS. 

This is the configuration file for BTSNTSVC.exe, which runs as a Windows Service and is a Host Instance, information regarding the configuration of the hosts. 

• Dehydration is the process of SERIALIZING the state of an orchestration into a SQL Server DATABASE.
• Rehydration is the reverse of this process: deserializing the last RUNNING state of an orchestration from the database.
• When a failure occurs WITHIN an orchestration and no error handling is IMPLEMENTED it will be suspended.

• A STRONG name ENSURES that each assembly name is UNIQUE.
• Each assembly in your BizTalk project requires a strong name in ORDER to DEPLOY successfully.

While BizTalk Server IMPOSES no restriction on message size, practical limits and DEPENDENCIES MIGHT REQUIRE you to MINIMIZE the size of your messages because large messages require more processing resources.

While BizTalk Server imposes no restriction on message size, practical limits and dependencies might require you to minimize the size of your messages because large messages require more processing resources.

• DOP stands for Degree of Parallelism. BizTalk SERVER DATABASE queries are relatively SMALL, and they execute quickly.
• THEREFORE, BizTalk Server database queries do not benefit from a Parallelism setting that specifies using more than one processor.
• Changing the Parallelism setting to specify using more than one processor may have an adverse effect on BizTalk Server database queries

There is no rule about how many hosts you may have. However there are CERTAIN guidelines and its recommended to have hosts for the following 
Receive Host : Used for all in process receiving 
Processing Host : Used for all Orchestration 
ISOLATED Host : Used for all IIS receiving
Send Host : Used for sending of messages 
Tracking Host : Used for moving data from MessageBox to Tracking DATABASE 
There may be more then one for each of these jobs depending on the WORKLOAD and resource usage INCLUDING host settings etc.

There is no rule about how many hosts you may have. However there are certain guidelines and its recommended to have hosts for the following 
Receive Host : Used for all in process receiving 
Processing Host : Used for all Orchestration 
Isolated Host : Used for all IIS receiving
Send Host : Used for sending of messages 
Tracking Host : Used for moving data from MessageBox to Tracking database 
There may be more then one for each of these jobs depending on the workload and resource usage including host settings etc.

You can LOCATE CONFIGURATION INFORMATION both on the BIZTALK MACHINES and the BizTalkMgmtDb.

You can locate configuration information both on the BizTalk machines and the BizTalkMgmtDb.

A ZOMBIE messages is a messages that ARRIVES after an orchestration has FINISHED, and can no longer reference back to the orchestration of it origin.

A zombie messages is a messages that arrives after an orchestration has finished, and can no longer reference back to the orchestration of it origin.

An orphaned messages is a message that has completed and finished its processing in the BIZTALK message BOX HOWEVER the information of this is not updated in the tracking DATABASE and will HOLD space in the tracking database until manually deleted or updated.

An orphaned messages is a message that has completed and finished its processing in the BizTalk message box however the information of this is not updated in the tracking database and will hold space in the tracking database until manually deleted or updated.

Besides the databases, the MASTER Secret Key and all APPLICATION and PROGRAMS on the BIZTALK MACHINE.

Besides the databases, the Master Secret Key and all application and programs on the BizTalk Machine.

There is the risk that Send Ports which are ALSO USED in Send Port Groups, pick up the message multiple times, leading to the DANGER that the message is PROCESSED multiple times, where it should be processed only once. 

There is the risk that Send Ports which are also used in Send Port Groups, pick up the message multiple times, leading to the danger that the message is processed multiple times, where it should be processed only once. 

• BizTalkMgmtDb (contains the configuration of a BizTalk Group)
• BizTalkMsgBox (contains the MESSAGES and work in progress)
• BizTalkDTADb (contains INFORMATION about the COMPLETED processes)
• SSODb (contains CREDENTIAL information)

By using PerfMon and configure COUNTERS for CPU, Memory, I/O, Throttling. Besides using Perfmon, you can use TOOLS like PAL, SQLIO, SQLProfiler, and IOMeter. 

By using PerfMon and configure counters for CPU, Memory, I/O, Throttling. Besides using Perfmon, you can use tools like PAL, SQLIO, SQLProfiler, and IOMeter. 

By ADDING a filter on a SEND PORT, which points to that RECEIVE Port.

By adding a filter on a Send Port, which points to that Receive Port.

A Host Architecture DESCRIBES how BizTalk USES Hosts and Host Instances for spreading its workload. NORMALLY you have Hosts for RECEIVING messages, Processing orchestrations, Sending messages and Tracking COMPLETED messages.

A Host Architecture describes how BizTalk uses Hosts and Host Instances for spreading its workload. Normally you have Hosts for Receiving messages, Processing orchestrations, Sending messages and Tracking completed messages.

• This stands for NETWORK Load BALANCING.
• It's ONE of the possibilities to make IIS high available on machines where BizTalk is installed.
• BizTalk itself HOWEVER has its own load balacing.

BizTalk can be configured in that it USES a FAILOVER- or LOAD Balanced cluster.
By doing so, BizTalk uses several physical or virtual machines to spread the workload.
In CASE one of the machines goes down, BizTalk is still able to process workload on the other MACHINE(s). 

BizTalk can be configured in that it uses a Failover- or Load Balanced cluster.
By doing so, BizTalk uses several physical or virtual machines to spread the workload.
In case one of the machines goes down, BizTalk is still able to process workload on the other machine(s). 

To warn the BizTalk Administrator that BizTalk is under stress or something abnormal is HAPPENING to the environment, these MAY only affect CERTAIN HOSTS or all hosts in the environment DEPENDING on the throttling state

To warn the BizTalk Administrator that BizTalk is under stress or something abnormal is happening to the environment, these may only affect certain hosts or all hosts in the environment depending on the throttling state

From a BizTalk PERSPECTIVE, these are numeric VALUES, which can be configured on your Hosts and host instances, and LEAD to THROTTLING situations once they are crossed. 

From a BizTalk perspective, these are numeric values, which can be configured on your Hosts and host instances, and lead to Throttling situations once they are crossed. 

• The BACKUP BizTalk job (LOCATION of FULL and LOG backups). 
• The DTA Purge and Archive job (at least the location where you want to Archive Tracking data.
• After you have configured the jobs, don't forget to enable them