Messages that are processed by the server go through a fixed
way involving varied components. A message is picked up by a receive port and examined
by a configured adapter, like SOAP, HTTP, File, FTP, SQL or any other adapter. All
the messages are processed by receive pipeline that can implement tasks such as
signing, decryption, etc. Optionally, a message may be converted to some other
format by means of mapping. The message is inserted in the MessageBox that
exists on a SQL Server database and the notifications are sent to the
subscribers. Orchestration obtains a message and works out logic to provide aid
to your business processes. No matter whether the message is processed by the orchestration
or not, in the next phase it is changed into a different output format, prior
to its transmission through mapping. Several functions are implemented through
send pipeline, for example, encryption on the message, before producing the
message in the final output format. The message is sent to the next system via
send port by using the configured adapter.
There are a number of expected bottleneck portions such as
BizTalk server, Message Mapping, Message Endpoints, Operating System, Database,
File System, Pipeline, Orchestrations and others. So there is a need to monitor
the BizTalk server performance on a
regular basis. The Server presents the users with the performance counters to scrutinize
the individual components such as adapters, message box, orchestration, etc. A
great example of the performance counters is the Host Throttling Performance
Counters. These offer information regarding the message throughput as well as
give the warning signal when the high-water marks are attained. Same way there
are other counters that help a BizTalk consultant
in monitoring the performance and then taking steps to overcome the problems
that have occurred.
No comments:
Post a Comment