Explore topic-wise InterviewSolutions in Current Affairs.

No, it is not POSSIBLE, TRANSFORM and Message assignment shape MUST run under construct shape.

No, it is not possible, Transform and Message assignment shape must run under construct shape.

YES, but only if the Orchestration Engine DETERMINES that the instance NEEDS to be dehydrated.

Yes, but only if the Orchestration Engine determines that the instance needs to be dehydrated.

The engine will save the state of an orchestration in the FOLLOWING circumstances:

• Send Shape (after a message is sent) 
• Start Orchestration Shape 
• Suspend Shape 
• End of a Transactional Scope (atomic or long-running) 
• An Orchestration Debugger breakpoint is hit 
• Orchestration Engine determines that the instance needs to be dehydrated 

When the Orchestration Engine is shut down; through the controlled SHUTDOWN of the host or abnormal circumstances. The engine tries to PERSIST but if that FAILS, the Orchestration instance will resume from the LAST successful persistence point.

The engine will save the state of an orchestration in the following circumstances:

When the Orchestration Engine is shut down; through the controlled shutdown of the host or abnormal circumstances. The engine tries to persist but if that fails, the Orchestration instance will resume from the last successful persistence point.

UNLIKE traditional programming, BizTalk Server SUPPORTS two distinct TYPES of transactions: ATOMIC and long-running.

Unlike traditional programming, BizTalk Server supports two distinct types of transactions: atomic and long-running.

• CALLING an orchestration will use the same thread to run another orchestration while USING Start Orchestration will create a new thread to run the started orchestration.
•  A Call Orchestration returns the control back to the caller. A Start Orchestration shape starts the orchestration in a non-deterministic WAY.
•  As a conclusion, Calling an Orchestration will be synchronous OPERATION where the caller waits for a response, while Start Orchestration is asynchronous operation.

No. General EXCEPTION in BizTalk is SIMILAR to writing a Try-Catch block but without the exception object THUS not possible to get the exception object.

No. General exception in BizTalk is similar to writing a Try-Catch block but without the exception object thus not possible to get the exception object.

A scope configured with the transaction type of NONE or LONG RUNNING can have exception handling added but not ATOMIC scope.

A scope configured with the transaction type of None or Long running can have exception handling added but not Atomic scope.

Parallel ACTION SHAPE is USED for a AND SITUATION whereas Listen shape is used for OR situation. 

Parallel Action shape is used for a AND situation whereas Listen shape is used for OR situation. 

Scopes are USED for FOLLOWING REASONS: 

• To configure transaction (LONG running and atomic) 
• To handle exceptions 
• To TRIGGER compensating logic 

Scopes are used for following reasons: 

The Receive SHAPE, LISTEN BRANCH and Delay shape are CONDITIONAL persistence points.

The Receive shape, Listen Branch and Delay shape are conditional persistence points.

A correlation TYPE is a list of properties that EVENTUALLY POPULATES with values for USE in routing messages.

A correlation type is a list of properties that eventually populates with values for use in routing messages.

PROMOTED properties can be USED as criteria in MESSAGE routing while written properties cannot. PROPERTY FIELD is a Promoted Property in the context. Distinguished field is a Written property in the context.

Promoted properties can be used as criteria in message routing while written properties cannot. Property field is a Promoted Property in the context. Distinguished field is a Written property in the context.

Promoting a node to a PROPERTY field means to make a node VALUE AVAILABLE in the context of the message. ADAPTERS and pipeline components write in the context.

Promoting a node to a property field means to make a node value available in the context of the message. Adapters and pipeline components write in the context.

CORRELATION is the process of matching an incoming MESSAGE with the APPROPRIATE INSTANCE of an Orchestration.

Correlation is the process of matching an incoming message with the appropriate instance of an Orchestration.

Expression SHAPE ALLOWS for writing XLANG/S STATEMENTS that provide C# -like coding capabilities.

Expression shape allows for writing XLANG/S statements that provide C# -like coding capabilities.

There are no limitations on the NUMBER of branches which can be used in a PARALLEL SHAPE.

There are no limitations on the number of branches which can be used in a parallel shape.

When a VARIABLE is shared ACROSS the BRANCHES of parallel SHAPE.

When a variable is shared across the branches of parallel shape.

It is used in Specify Later PORT BINDING option. In this model the orchestration PORTS are BOUND to messaging ports using BTS.SPID,BTS.ReceivePortID or other RELATED properties.

It is used in Specify Later port binding option. In this model the orchestration ports are bound to messaging ports using BTS.SPID,BTS.ReceivePortID or other related properties.

YES it is POSSIBLE with the HELP of CORRELATION.

Yes it is possible with the help of correlation.

The convoy is used to RECEIVE multiple MESSAGES in sequence or parallel to ACHIEVE a goal/result.

The convoy is used to receive multiple messages in sequence or parallel to achieve a goal/result.

Yes. It is POSSIBLE to USE components like pipeline, business RULE POLICY, .net component ETC.

Yes. It is possible to use components like pipeline, business rule policy, .net component etc.

Pro's:

• Loose coupling
• Not bounded to any physical PORT (explicitly) 

Con's:

• Can lead to SUBSCRIBING to messages PUBLISHED by another PUBLISHER 

Pro's:

Con's:

No, it can only have a COMPENSATION BLOCK.

No, it can only have a Compensation Block.

The correlation SET can have a maximum of three properties USED for correlation on the RECEIVE shapes.

The correlation set can have a maximum of three properties used for correlation on the receive shapes.

It is the only EXCEPTION to the REQUIREMENT of types for variables having to be serializable and treated as special CASE.

It is the only exception to the requirement of types for variables having to be serializable and treated as special case.

At VARIOUS points WITHIN a RUNNING orchestration the STATE can persist.

At various points within a running orchestration the state can persist.

Any exception which is not caught within the exception HANDLERS of the orchestration causes the orchestration INSTANCE to be moved to the Suspended state.

By applying the appropriate ERROR HANDLING in an orchestration it can be prevented entering the Suspended state.

Any exception which is not caught within the exception handlers of the orchestration causes the orchestration instance to be moved to the Suspended state.

By applying the appropriate error handling in an orchestration it can be prevented entering the Suspended state.

• XLANG/s can be viewed as a messaging language with some of the expression capabilities of C#.
• However, code is not portable between XLANG/s and C#.
• The language is USED for orchestrations.

XLANG/s statements generally fall into one of two categories:

simple statements that act on their own, such as receive or send, and complex statements that contain or group EITHER simple statements or other complex statements, such as scope, PARALLEL, and listen.

The semantics embodied in XLANG/s are a reflection of those defined in the Business Process Execution Language for Web Services (BPEL4WS) SPECIFICATION PUBLISHED by Microsoft, IBM, and BEA for the definition of business process semantics.

XLANG/s statements generally fall into one of two categories:

simple statements that act on their own, such as receive or send, and complex statements that contain or group either simple statements or other complex statements, such as scope, parallel, and listen.

The semantics embodied in XLANG/s are a reflection of those defined in the Business Process Execution Language for Web Services (BPEL4WS) specification published by Microsoft, IBM, and BEA for the definition of business process semantics.

No it is not, SINCE it FORMS CYCLIC DEPENDENCY.

No it is not, since it forms cyclic dependency.

Yes it is necessary (GOOD practice) for all .Net components being CALLED to be serializable. If not then Atomic scope is to be USED which has its own LIMITS.

Yes it is necessary (good practice) for all .Net components being called to be serializable. If not then Atomic scope is to be used which has its own limits.

A SCOPE configured as Atomic or Long running can have compensation blocks added, but SCOPES that are configured with no TRANSACTION TYPE cannot.

A scope configured as Atomic or Long running can have compensation blocks added, but scopes that are configured with no Transaction type cannot.

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.

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.

No

No

Two types of MESSAGES:

• Typed message : A message CREATED in Orchestration is bound to the schema 
• Untyped message : A message is bound to System.Xml.XmlDocument INSTEAD of the schema.

Two types of messages:

One of the best practices when IMPLEMENTING orchestrations is to use orchestration patterns when possible.

These patterns are basically design pattern, which is a general reusable solution to a commonly occurring problem within a given context of BizTalk orchestration.

This ARTICLE will PROVIDE some USEFUL resource links to aid you in USING patterns when implementing an orchestration. 

One of the best practices when implementing orchestrations is to use orchestration patterns when possible.

These patterns are basically design pattern, which is a general reusable solution to a commonly occurring problem within a given context of BizTalk orchestration.

This article will provide some useful resource links to aid you in using patterns when implementing an orchestration. 

In Orchestration, the first Receive shape is RESPONSIBLE for CREATING a subscription. Following two properties are involved in it,

Message : This TELLS what message this Orchestration is subscribing to 

Activate : This tells to CONSUME the message when FOUND in a MessageBox

In Orchestration, the first Receive shape is responsible for creating a subscription. Following two properties are involved in it,

Message : This tells what message this Orchestration is subscribing to 

Activate : This tells to consume the message when found in a MessageBox

Yes

Yes

The MESSAGE metadata is called CONTEXT PROPERTIES and on receiving the message, both the ADAPTER and the pipeline will ADD information to the context.

The message metadata is called Context Properties and on receiving the message, both the adapter and the pipeline will add information to the context.

The INFORMATION about the PROMOTED properties is extracted and stored in the bts_DocumentSpec table in the Management DATABASE.

The information about the promoted properties is extracted and stored in the bts_DocumentSpec table in the Management database.

You construct a message any time that you INTRODUCE a message into your orchestration, either by RECEIVING it or by assigning values to a message variable.

There are several ways to create a NEW instance of a message in an orchestration.

You construct a message any time that you introduce a message into your orchestration, either by receiving it or by assigning values to a message variable.

There are several ways to create a new instance of a message in an orchestration.