Search

Confusing naming in BizTalk by Tord G.Nordahl

Active

1
1
Sign in
to vote
Type: Bug
ID: 772720
Opened: 11/29/2012 5:19:02 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
I won't call this a bug, rather and improvement of the product.

Global Tracking, this is the most commonly used name for the group-level tracking option in BizTalk. However after this setting was moved into BizTalk Administration Console the names have changed into "Enable Group Level Tracking". This should be changed into "Enable Global Tracking" to remove the confusion.

When it comes to the host settings the thresholds have been moved into the administration console. However confusing naming is done here too.

First of all the way it builds up, like the Tracking and Spool multiplier should be moved closer to the Message Count in DB to show it goes hand in hand.

Resource-based Throttling should be renamed to Resource-based Thresholds (after all you are changing the thresholds not the throttling, since throttling states will always be the same).

Rate-Based Throttling should be renamed into Rates before Throttling to clarify the fact that this involves the rates / time / message count before throttling will begin.

All descriptions on the different thresholds should be rewritten so it actually provides some valid information, as of now, most of them are just confusing.

The chaching of application should be reconsidered and instead of chaching in the entire environment it should be chached based on these steps:

Open group - Get all application names
Open one application - Get information for that application

No it takes it all and eat memory, for larger environment the console will be very slow the way it works now, even with some the Administration Console cannot be used at all.
Details (expand)

Product Language

English

Version

BizTalk private build 3.9.466.0

Category

Maintenance/Operations

Repro Steps

Check the BizTalk administration console.
File Attachments
0 attachments
Sign in to post a comment.
Sign in to post a workaround.