Explore topic-wise InterviewSolutions in Current Affairs.

MAPS can't be APPLIED to Send Port GROUP.

Maps can't be applied to Send Port Group.

If a SEND port is DIRECTLY bound to an orchestration port,then FILTERS do not APPLY.

If a send port is directly bound to an orchestration port,then filters do not apply.

YES. But this APPLICATION will not FUNCTION PROPERLY.

Yes. But this application will not function properly.

A FILTER on the send port is the first step to ENABLE SUBSCRIPTIONS in BizTalk.

A filter on the send port is the first step to enable subscriptions in BizTalk.

When FAILED message routing is enabled and if an error OCCURS at the port, then the message will have all the regular context PROPERTIES unprompted and INSTEAD have some error-specific context properties promoted - all in the ErrorReport Namespace e.g. ErrorReport.ErrorType, ErrorReport.ReceivePortName etc.

When Failed message routing is enabled and if an error occurs at the port, then the message will have all the regular context properties unprompted and instead have some error-specific context properties promoted - all in the ErrorReport Namespace e.g. ErrorReport.ErrorType, ErrorReport.ReceivePortName etc.

In this scenario we can STOP the SEND port bound to the DESTINATION SYSTEM.

This way the messages will lie in a queue inside Messagebox. Subsequently, we can START the send port when the destination system is available.

In this scenario we can stop the send port bound to the destination system.

This way the messages will lie in a queue inside Messagebox. Subsequently, we can start the send port when the destination system is available.

BIZTALK will no longer NEED to HOLD on the MESSAGE and the message will be removed from BizTalk.

BizTalk will no longer need to hold on the message and the message will be removed from BizTalk.

BizTalk.System is already REFERENCED in all NEW applications, as a result of this we can WORK with several pipelines as soon as a new application is CREATED.

BizTalk.System is already referenced in all new applications, as a result of this we can work with several pipelines as soon as a new application is created.

BizTalk Application deployment can be done using the following: 

• Deploying from Visual Studio 
• Building a MICROSOFT Installer (MSI) PACKAGE that can be exported or imported between environments.
• Using command line-based tools such as MSBUILD and BtsTask. 
• Using community frameworks, such as BizTalk Deployment FRAMEWORK and NANT.

BizTalk Application deployment can be done using the following: 

When we RUN MSI packages, it will register the application with WINDOWS Operating System and then LOAD any related ASSEMBLIES in the Global Assembly Cache.

When we run MSI packages, it will register the application with Windows Operating System and then load any related assemblies in the Global Assembly Cache.

Messages in BizTalk are IMMUTABLE after CONSTRUCTED and the message is CONSIDERED constructed after it is PLACED into the MessageBoxDatabase.

Messages in BizTalk are immutable after constructed and the message is considered constructed after it is placed into the MessageBoxDatabase.

When BACK up TRANSPORT is ALSO APPLIED.

When back up transport is also applied.

Because only ONE THREAD can SUBMIT MESSAGES through the port and each MESSAGE has to wait for messages through the port and each message has to wait for the message before it can be processed.

Because only one thread can submit messages through the port and each message has to wait for messages through the port and each message has to wait for the message before it can be processed.

No only STATIC SEND PORTS can be PART of send GROUP.

No only static send ports can be part of send group.

The group hub gives the user an overview of what is currently GOING on INSIDE BIZTALK.

The group hub gives the user an overview of what is currently going on inside BizTalk.

The reason for having multiple RECEIVE LOCATIONS inside one Receive PORT is to have the ability to receive different messages from different locations and having BIZTALK TREAT them as if they were received from the same place and/or had the same message type.

The reason for having multiple receive locations inside one Receive port is to have the ability to receive different messages from different locations and having BizTalk treat them as if they were received from the same place and/or had the same message type.

In UNLISTED state SEND PORT does not SUBSCRIBE to any messages and no messages will be sent through the port.

In Unlisted state send port does not subscribe to any messages and no messages will be sent through the port.

No. The names of the VARIOUS PORTS must be UNIQUE, not just INSIDE an Application but for the whole BIZTALK group.

No. The names of the various ports must be unique, not just inside an Application but for the whole BizTalk group.

Two types of subscription:

1. Activation 
2. INSTANCE

Instance SUBSCRIPTIONS are removed from the message box while Activation subscriptions remain active as LONG as the orchestration or SEND port is enlisted.

Two types of subscription:

Instance subscriptions are removed from the message box while Activation subscriptions remain active as long as the orchestration or send port is enlisted.

RECEIVE PORT can have any NUMBER of receive LOCATION.

Receive port can have any number of receive location.

The MESSAGE is SUSPENDED when there are no SUBSCRIBERS FOUND for it.

The message is suspended when there are no subscribers found for it.

CHECKING the subscription table is the FIRST thing when MESSAGES come in MESSAGEBOX and a COPY of the message is sent to the subscriber.

Checking the subscription table is the First thing when messages come in MessageBox and a copy of the message is sent to the subscriber.

• Store all MESSAGES and CONTEXT received. 
• Stores all subscriptions. 
• Stores all HOST QUEUES.

MessageBox is a SQL server DATABASE ALONG with MESSAGING agent.

MessageBox is a SQL server database along with messaging agent.