This document outlines the resources and support available for a project. It details that all necessary resources, documentation, people, information and experts will be provided. It also states that the infrastructure is of the highest quality. The document provides guidance on defining objectives, achievements, results and preparing an organized schedule and activity plan for the project.
9. • You will have all resource you need
• You will have all documentation you need
• You’ll can use all people you want
• You will have all information you need
• You will have all experts you need
• The infrastructure is the best that you’ll can
see ever
• You must only ask and you’ll have a correct
response
25. BizTalk Server
Memory
Disk
Network
Adapter
Processor
SQL Server
Memory
Disk
Network
Processor
Circumscribe!!!
26. BizTalk Server
Memory
Disk
Network
Adapter
Processor
SQL Server
Memory
Disk
Network
Processor
27. BizTalk Server
Memory
Disk
Network
Adapter
Processor
SQL Server
Memory
Disk
Network
Processor
Circumscribe!!!
28. BizTalk Server
Memory
Disk
Network
Adapter
Processor
Antivirus!!!
SQL Server
Memory
Disk
Network
Processor
29.
30. BizTalk Server
Memory
Disk
Network
Processor
SQL Server
Memory
Disk
Network
Processor
31. BizTalk Server
Memory
Disk
Network
Processor
SQL Server
Memory
Disk
Network
Processor
Hinweis der Redaktion
stand stillthrow
I’m not theoreticalI put my hands in the mud I’ve seen things you people wouldn’t believe...You will not find anything in net or booktrow
Quando un assessment è grandeBorder line?
How many technoglogies we must cover
We can focus Focalizzare le più fequentiFocus the most frequentChiedi anche quali sono
What must to know today a BizTalk expert
I want tell you a storyRacconta la storia, tu entri dal cliente e il cliente ti dice...Avrai tuttoPerfect assesssmentma quando parti con l’assessment....
Ma prima vogliomostravialcunecosa
There are a ton of BizTalk related tools, technologiesbisogna catalogare i più frequentishould categorize the most frequent
This slide is simply here to give you an idea of some of the best counters to use in BizTalk. Unfortunately, there isn’t enough time in this presentation to cover them all and there are certainly a *lot* more counters than this. These are the counters you should initially check.Fortunately, the PAL tool analyzes most of these counters for thresholds for us.
Likewise, here are the initial operating system counters I use in analysis. I use “Shane Creamer’s Vital Signs” when analyzing them for thresholds. Again, I don’t have time to cover them all in this presentation.Again, the PAL tool analyzes these counters for thresholds for us.
This was a customer production environment, so no performance baseline existed.Group Hub simply showed what the customer considered normal message flow. They simply wanted to know if they are running into any bottlenecks, so I moved on to the next step.We checked the event logs and “whoa”. BizTalk came right out and said “high stress levels on BizTalkMsgBoxDb”. Well, you can’t get more straight forward than that. Fortunately, the customer was already well aware of this and needs to know more, so we moved to the next step.We gathered a performance monitor log of the BizTalk and OS counters.I used the PAL tool to automate the majority of the performance analysis and we found more symptoms. On the SQL server, the M: drive which contains the BizTalkMsgBoxDb database and the N: drive which contains the tracking database are showing clear signs of being bottlenecks.
After identifying a lot of contention on the BizTalkMsgBoxDb database, I discussed this with the customer and found out they were tracking nearly everything.We recommended that they go through their tracking settings and disable what is not needed in production. After that, it’s a matter of increasing the response times of the disks through hardware changes.
This was a customer production environment, so no performance baseline existed.Group Hub simply showed what the customer considered normal message flow. They simply wanted to know if they are running into any bottlenecks, so I moved on to the next step.We checked the event logs and “whoa”. BizTalk came right out and said “high stress levels on BizTalkMsgBoxDb”. Well, you can’t get more straight forward than that. Fortunately, the customer was already well aware of this and needs to know more, so we moved to the next step.We gathered a performance monitor log of the BizTalk and OS counters.I used the PAL tool to automate the majority of the performance analysis and we found more symptoms. On the SQL server, the M: drive which contains the BizTalkMsgBoxDb database and the N: drive which contains the tracking database are showing clear signs of being bottlenecks.
After identifying a lot of contention on the BizTalkMsgBoxDb database, I discussed this with the customer and found out they were tracking nearly everything.We recommended that they go through their tracking settings and disable what is not needed in production. After that, it’s a matter of increasing the response times of the disks through hardware changes.
Another customer example using the methodology.No performance baseline since this was a new deployment of their application.Group Hub showed an increasing trend of durations.No significant events in the event logs.Gathered a performance counter log.Found the operating system was starving for memory and the process consuming memory is a BizTalk process (BTSNTSvc.exe).
New deployment, but a baseline of around 30 seconds was established which is far higher than what the customer expected.We used HAT to verify the durations.The Event logs and the servers showed no clues.We gathered a performance monitor log.Analysis of the perfmon log showed all of the systems as relatively idle on resources…. So what is the problem?Once I started gathering my data off of the servers I noticed the file copies were taking a very long time.On a 100Mbit network a 100MByte file should take less than 20 seconds to copy.On a 1Gbit network a 100MByte file should take less than 5 seconds.Copy times of 100MByte files were taking *minutes* to copy.
Come to find out, the network adapters were set to auto-detect and negotiated down to 10Mb half duplex.We explicitly change to 100Mb full duplex and everything was *much* faster.The point: The methodology I am presenting is not fool proof. It is simply guidance on how to methodically solve more BizTalk performance issues.