tag:blogger.com,1999:blog-29246602677831695852024-03-18T01:42:21.221-04:00Business Transaction ManagementBusiness Transaction Management - an up and coming paradigm in Systems and Application Performance Management.
This Blog seeks to help define and track the evolution of this groundbreaking discipline.Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.comBlogger32125tag:blogger.com,1999:blog-2924660267783169585.post-5905863704240455672011-04-19T13:46:00.001-04:002011-04-19T13:49:43.078-04:00CMG in the Clouds<br />April fool’s day this year brought with it the Rocky Mountain CMG conference. Best view of any CMG show I have been at.<br /><br />David Halbig from First Data Corp. (also the guy who organizes the show) kicked off with a surprisingly refreshing presentation for a CMG region. He talked about the cloud in an extremely practical way – as well as laying out the management of performance in the cloud.<br />David laid out some very compelling examples of issues that can potentially emerge when moving to the cloud. David broke up the monitoring approach into:<br />1. Continuous Monitoring<br />2. Specialized – intermittent use monitoring (the fire hydrant)<br />3. Middleware monitoring (application deepdive)<br />4. Business Transaction Monitoring – for a cross tier understanding of what is going on<br />David talked about how many vendors say that they are “BTM capable” – but really do not have the “real thing” – his “sure fire” list of requirements included:<br />• Horizontal view of aggregate and single transactions across all tiers of interest<br />• Resource consumption information from each monitored tier – basically saying that a network tap based solution cannot cut it.<br />• Auto-discovery of transaction path (said that some products needed to be “trained” on transaction paths)<br />• Capture path to non-monitored tiers<br />• Continuous operation at volume<br />• Low transaction path overhead<br />We (Correlsense) also presented; focusing on how Cloud (public/Private), Agile, SOA and Virtualization create an ever changing environment where the only things that stay the same are the user’s expectation of sub second response times and the transactions that run the business. <br />Although – as usual – the vast majority of the audience was not anticipating and migration to the cloud in the near future – the sessions were very informative because they dealt with managing performance in a constantly changing environment – something that everyone has to deal with.Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com2tag:blogger.com,1999:blog-2924660267783169585.post-73385341741508263152011-04-05T09:50:00.003-04:002011-04-05T09:58:33.876-04:00Improving Conversion RatesThere is a clear and obvious correlation between the time it takes a landing page to load and the conversion rate of the call for action on that page. We know now that the time it takes to load your site will affect not only your conversion rate but your ranking at Google as well. If you agree with these statements, continue reading... If not, I suggest you to read <a href="http://googlewebmastercentral.blogspot.com/2010/04/using-site-speed-in-web-search-ranking.html">this article</a> and <a href="http://www.aberdeen.com/Aberdeen-Library/5136/RA-performance-web-application.aspx">this one</a> as well.<br /><br />Today, the main tools for optimization are dealing with questions like "where the traffic is coming from" and "what people are doing on my site before they convert". The traditional set of tools available for the web analyst are tools like google analytics that provides information about where the visitors are coming from, funnel analytics tools that provide information about the steps in your acquisition funnel, AB and MVT testing tools to run experiments on the traffic to your site and user recording tools and life-cycle tools that let you view your users flow. <br /><br />None of the above deals with site performance while we all agree there is a significant weight for this issue on your conversion rate.<br /><br />Few months ago, one of our clients decided to put his site on CDN. His optimization manager told him that like any other change done to the site, they should run a test and evaluate the ROI of such change. They agreed to run a simple AB test on their Brazilian display traffic (traffic from banners) - 50% will be redirected to the regular site and 50% to the CDN version.<br /><br />Before starting the test, they went to their IT manager and asked him to check using his monitoring tool how long it takes to load each version. The IT manager did not have a robot/agent in brazil so he bought a virtual server there and installed the agent and came back two weeks after with the following results: it took the original site to load 25 seconds while the new version took 6 seconds. Although it was clear 19 seconds is a huge difference, they decided to run the test after all.<br /><br />Few days after, they got the results: the conversion rate of the new version was <span style="font-weight:bold;">65% LOWER</span> than the original version... Based on the results, it appeared that the longer the user waited, the better chance he will convert (original version: 25 seconds to load, 6.4% conversion rate, new version: 6 seconds to load, 2.2% conversion rate)...<br /><br />This is obviously wrong. By looking at the amount of page views of each variation they noticed that the amount of pageviews of the original version was much less than the amount of pageviews of the new version (about 1:3 while it should be 1:1) which lead them to the conclusion that because of the load time, most of the users left the page before it was fully loaded and before the web analytics tool sent the event to the server. The users who did wait 25 seconds for the page were more likely to convert...<br /><br />Another thing they found was that when they measured the actual time it took for the visitor to load the page, it was much more than 25 seconds (closer to 40 seconds). The IT manager did not include the rendering time or the actual time it took the visitor to load all the files (relying on the network speed determined by the server will never be accurate). <br />You can assume visitors who are waiting 40 seconds for a page are really interested in its content...<br /><br />The main things you should take from this story are:<br />- Page load time and abandonment rate during page load should be part of the basic metrics your analysts are using<br />- You should have a real site performance analytics tool that will capture 100% of your traffic and not count on robots or other sniffing tools<br />- You have all kinds of KPIs that provide you with a clear view of all of your SLAs and response time through the funnel except for one of the most important steps - when the visitor arrives to your store. <br /><br /><br />RUM measures the load time of each and every request for 100% of your traffic, from all around the world, and in the most accurate way. It does not rely on robots and synthetic request or calculates the processing time on the server or the size of the response or guessing the network speed of your visitors. Instead, it uses both client and server agents to calculate the actual time it took from the time the user requested the page till the page was fully rendered. It also tells you how many visitors left before getting the page (and before you got a pageview event to your web analytics tool). RUM has a simple yet powerful user interface that was designed not only for IT people. <br /><br />Please <a href="http://www.correlsense.com/company/contactus">contact us</a> to schedule a demo or <a href="http://www.real-user-monitoring.com/">download</a> the free addition of the tool.Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com3tag:blogger.com,1999:blog-2924660267783169585.post-74123886949464141632010-11-08T14:32:00.009-05:002010-11-12T15:31:56.362-05:00Videos: Business Transaction Management by Correlsense<a href="http://www.correlsense.com">Correlsense</a> is an industry leader when it comes to helping enterprises achieving <a href="http://www.correlsense.com/IT%20Reliability">IT Reliability</a>. With their product, <a href="http://www.correlsense.com/products">SharePath</a>, they are changing the way enterprise companies monitor applications. In these videos, Lanir Shacham, CTO and founder, talks about what Correlsense is all about and what SharePath does:<br /><br /><object width="480" height="385"><param name="movie" value="http://www.youtube.com/v/AzBb6L2wCgQ?fs=1&hl=en_US"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/AzBb6L2wCgQ?fs=1&hl=en_US" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="480" height="385"></embed></object><br /><br /><br /><object width="480" height="385"><param name="movie" value="http://www.youtube.com/v/R-EVGH23Ih4?fs=1&hl=en_US"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/R-EVGH23Ih4?fs=1&hl=en_US" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="480" height="385"></embed></object>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com4tag:blogger.com,1999:blog-2924660267783169585.post-76450217260048116662010-08-25T13:32:00.004-04:002010-08-25T13:38:12.837-04:00More Information on Business Transaction ManagementThe market has continued to grow. There is now free options out there to get your toes wet with some software one definitely worth checking out is this free offering from <a href="http://www.correlsense.com">Correlsense</a>, it's their free R<a href="http://www.real-user-monitoring.com">eal User Monitoring</a> tool., brought to you by Correlsense. Make sure to check them out on the web and also on <a href="http://www.twitter.com/correlsense">Twitter</a> and <a href="http://www.facebook.com/pages/Correlsense/309518081337">Facebook</a>.<br /><br />Also Check out this video from CEO Oren Elias about their free <a href="http://www.real-user-monitoring.com">Real User Monitoring</a> offer.<br /><br /><object width="480" height="385"><param name="movie" value="http://www.youtube.com/v/gRw8_9l9up4?fs=1&hl=en_US"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/gRw8_9l9up4?fs=1&hl=en_US" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="480" height="385"></embed></object>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com4tag:blogger.com,1999:blog-2924660267783169585.post-63662039378984865342010-02-08T12:53:00.005-05:002010-04-22T18:28:39.313-04:00Why IT Operations is like an Action TV Series<p>I like watching the series "24", I can’t really explain why. Every time they nearly get the bad guys something wrong happens, there’s some sort of twist in the plot and they need to start all over again. For example, I’m sure that you are familiar with the following classic scene: The CTU (Counter Terrorism Unit) chopper is following a suspect that is driving a black van. The suspect’s van enters a tunnel, but the van doesn’t leave the tunnel. Instead, a number of different vehicles leave the tunnel at the same time, and the suspect is probably in one of them. By the time they figure out that the black van has been left empty in the tunnel – they have already lost the suspect. They shout “We have lost visual!!!” and are back to looking for the bad guys all over again - then they call Jack Bauer…</p> <p>IT Operations is just like the CTU; the CTU is responsible for making sure that life goes on without any unpleasant surprises. Similarly, IT Operations needs to do the same in its own space and make sure that the business keeps on running and that business transactions are being executed properly and on time.</p> <p>When something is about to go wrong, the CTU and IT Operations are expected to prevent it before it affects anyone. So they set up the war room, call everyone in, and start doing their detective work to find the needle in the haystack. If they don’t find it and something goes wrong then the results are significant; either people get hurt (in the CTU's case), or business is impacted.</p> <h3>IT Operations' War Chest</h3> <p>So which tools could IT Operations use to find out that there is a problem, identify the root cause of it and resolve the issue?</p> <p>For example, IT Operations could use HTTP network appliances that help see every HTTP transaction and measure its response time. These network appliances are just like the CTU's choppers, they do not have adequate visibility into the datacenter. They can indicate that something is wrong with the response time of a transaction, but they cannot show why the response time of the transaction is high and cannot provide the visibility needed for resolution.</p> <p>IT Operations also uses Event Correlation and Analysis (ECA) tools. ECA tools are like CSI detectives (yes… that’s another one I watch…), and rely on other tools to collect information for them, just like a the CSI detective who collects evidence from a crime scene. ECA tools are just as effective as the products that they rely on to provide them with the data. The issue with ECA tools is that, just like in a crime scene, the thief does not usually leave his ID behind, so all you are left with is just clues, and no accurate data to work with.</p> <p>Additional tools that IT Ops relys on are; dashboards that monitor server resource consumption, <a href="http://en.wikipedia.org/wiki/J2EE">J2EE</a>/<a href="http://en.wikipedia.org/wiki/.NET_Framework">.Net</a> tools that are capable of performing drill down diagnostics in application and database layers, synthetic transaction tools and <a href="http://www.real-user-monitoring.com">Real User Measurement (RUM) tools</a>. With all of these monitoring tools IT Operations still finds itself in a situation where all lights are green while users are complaining about bad response times. In spite of all of the investment in monitoring tools; the infrastructure that IT Operations is accountable for is still unpredictable. Why?</p> <h3>A Simple Example</h3> <p>Perhaps it’s best to take a look at this classic example: One of our customers had a problem with a wire-transfer transaction. The liability for the problem kept on going back and forth between Operations and Applications, who were pointing fingers at each other as to who was responsible for the issue. “All lights are green” said Operations, “We tested the application and it works just fine” said Applications. Simply put, no existing monitoring tool could point out the problem.</p> <p>So what was the problem? The answer is simple; it appears that, by design, wire-transfers for over $100K were querying the mainframe nearly 100 times, while other transfers would query it only a couple of times. Same end-user, same application, same transaction, but just a single parameter made the transaction take a whole different path, and made the difference between a 3 second and a 2 minute response time.</p> <h3>What Exactly Are You Monitoring?</h3> <p>Now the question is: why can't existing monitoring tools identify the problem? The reason is simple. Traditional monitoring tools monitor the infrastructure and not the transactions. In a complex heterogeneous infrastructure, there are many tools for monitoring each and every component, but no single spinal cord that is able to show how transactions behave across components. None of the tools are able to deterministically correlate a single request coming into a server with all of the associated requests going out of a server and keep on doing so throughout the Transaction Path. Just like the chopper which could not figure out which of the vehicles coming out of the tunnel contained the suspect who came into the tunnel in the first place. </p> <p>This situation raises some strategic questions regarding your monitoring approach. How effective is a monitoring framework without that business context? Are you supposed to just to make sure the servers are up and running and applications are responding, or is your real goal is to make sure that the business transactions are being executed as intended and on time?</p> <h3>“In God we trust; all others must bring data”</h3> <p>Applications are tricky, transactions are tricky, and they become even trickier in a complex heterogeneous infrastructure that is composed of multiple platforms, operating systems, application nodes, tiers, databases and where communication between components is in different protocols back and forth for every single click of a button by an end-user.</p> <p>Only by being able to trace each and every single transaction activation throughout its entire path - 100% of the time, for all transactions, across all components - will you be able to systematically collect necessary granular information in order to get business-contextualized visibility into your datacenter. This kind of visibility is a key factor in being able to identify problems effectively when, or even before they arise. </p> <p>W. Edwards Deming said; “In God we trust; all others must bring data”. I think he was absolutely right. IT Operations can use choppers, or CSI crime-lab detectives, or Jack Bauers. They all have their roles, but when it comes to fast and effective problem identification as well as many other IT related decision making processes (that’s a whole different article…) real accurate data is required – no partial data, no assumptions.</p> <p>Business Transaction Management provides you with that data, and by doing so, it provides your IT Organization with visibility and predictability. Wouldn’t it be great if you could go to sleep at night knowing that your infrastructure is reliable? That is, unless you want to play the role of the CTU Director…</p> <p>The 8th season of 24 will be premiered on January 17th, 2010. 'Till then – why don’t you get yourself a Business Transaction Management solution…</p>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com13tag:blogger.com,1999:blog-2924660267783169585.post-31664703908225192382009-07-15T08:05:00.006-04:002009-07-15T08:19:01.420-04:00IT Reliability through Business Transaction Management<div style="text-align: center;"><br /></div><div>...Continued from the last post</div><div><span class="Apple-style-span" style="font-size:large;">Enabling Reliable IT – Managing Performance</span></div><div>How do you know when an end user is experiencing bad response times?</div><div><ul><li>They call into the help desk to complain – usually only after a number of past events where they were un-happy with the application’s reliability.</li><li>An end user monitoring tool measures bad response times</li></ul></div><div><span class="Apple-style-span" style="font-size:x-large;">End User Measurements</span></div><div>There are a great number of tools on the market today that perform this task in a variety of ways, below is a summary of the different approaches.</div><div><span class="Apple-style-span" style="font-size:large;">Software Based Real User Measurements</span></div><div><b>Desktop Agent</b></div><div><ul><li>Strength – enables the monitoring of the end user’s desktop and can measure response times for fat client based applications</li><li>Weakness – must be installed at each desktop</li></ul></div><div><b>Javascript Injection</b></div><div><ul><li>Strength – no need for end user installation</li><li>Weakness – Javascript needs to be added to web application code</li></ul></div><div><b>Browser Plug-In</b></div><div><ul><li>Strength – easy installation without code modification</li><li>Weakness – still requires end user installation</li></ul></div><div><span class="Apple-style-span" style="font-size:large;">Network Appliance Based Real User Measurements</span></div><div>All of these solutions utilize a network sniffer installed at a port mirror in order to guess end user response times. The advantage of using this solution is the ease of installation; the disadvantage is the cost of putting these probes at all of the points where the network is accessed and the</div><div> accuracy of the data.</div><div><span class="Apple-style-span" style="font-size:large;">Synthetic End User Measurements Performed by “Robots”</span></div><div>The classic availability monitors use this approach - scripts are used to “ping” the system and check its availability. The advantage is that availability can be monitored overnight and before the morning workload, the disadvantage is that real user response times are not being measured and scripts have to be modified with every change of the application.</div><div><span class="Apple-style-span" style="font-size:x-large;">Finding the Location of the Problem</span></div><div>Now that you know that there is a problem - since the end user is experiencing reliability issues with an application, narrowing down the location of the problem is the next step. Research has shown that 80% of time spent on troubleshooting performance problems is spent on finding the actual location of the problem.</div><div style="text-align: center;"><br /></div><div>In the picture below “John the User” is experiencing poor response times – the IT department is tasked with resolving this issue.</div><img src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiAGVK09avY0NMnj3G6rwxlhyphenhyphen0n2vw1MELqRgDjaOYcg3jbI8YpHOc2pzxNBfdRc7dWOfu57OAl34M7zq4dahHDRLtm0rWLAHY_znVBx5kMSoY-u5E4i6oYLQ0lkgWOqnI44ahfu_KigSat/s320/john+the+user.png" style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 243px;" border="0" alt="" id="BLOGGER_PHOTO_ID_5358659524669245506" /><div>To be continued next week...</div>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com13tag:blogger.com,1999:blog-2924660267783169585.post-37822401889707063722009-07-05T03:53:00.008-04:002010-02-08T13:05:58.468-05:00IT Reliability through Business Transaction Management<div>I just got back from a regional CMG conference where the majority of attendees identify themselves as IT performance and capacity professionals. Ultimately the objective of their work is to make the organization’s IT systems more reliable.</div><div><ul><li>By planning for tomorrow’s capacity they ensure that the applications that our co-workers and customers rely on will continue to be reliable throughout increased usage and new changes.</li></ul></div><div><ul><li>By managing IT performance they enable the day to day reliability of these applications so that revenue can be generated and growth achieved.</li></ul></div><div>By focusing our efforts on the greater goal of <b><a href="http://www.correlsense.com/IT%20Reliability">IT reliability</a></b> we are able to heal the great disconnect that happens much too often between the business and IT. Showing the business graphs of increased CPU consumption or bandwidth utilization does not enable them to relate to the performance and capacity issues that they are concerned with. IT resource consumption metrics may be the “vital signs” of IT systems, but this is kind of like checking a patient’s pulse and respiratory rate and saying that they are healthy enough even though the patient may be suffering from a terminal disease. The lights may be on, but are the IT systems you manage perceived as reliable by the end users and the business?</div><div><br /></div><div><span class="Apple-style-span" style="font-size:x-large;">What is <a href="http://www.correlsense.com/IT%20Reliability">IT Reliability</a>?</span></div><div>Put yourself in the shoes of the end user; you want any action that you perform within an application to have a quick and valid response. That is reliability in the eyes of the business and the end user and that is exactly what your work as a performance or capacity professional is seeking to enable.</div><div><br /></div><div><span class="Apple-style-span" style="font-size:x-large;">Transactions</span></div><div>What connects between all of the various parts of the puzzle? What links the business, the end users, the network, firewalls, proxy servers, web servers, application servers, load balancers, message brokers, databases, and mainframes? Transactions.</div><div>When posing the question <b>"how do YOU define a transaction?"</b> to a room full of IT professionals you are likely to receive a handful of different answers.</div><div>Typically one would define an HTTP request, database call, <a href="http://en.wikipedia.org/wiki/CICS">CICS</a> transaction or <a href="http://en.wikipedia.org/wiki/SOAP">SOAP</a> request as a transaction. In this paper these are defined as transaction segments that are part of a greater transaction.</div><div>A transaction is the most elementary unit of work that can be performed by a user of an application. Whenever a user clicks a button within an application, they have performed a “transaction activation”. This “transaction activation” can trigger any number of IT processes within the datacenter that are used to get the work done. A transaction could be a transfer of funds, a purchase, an update of information, or the opening of a new account – any user interaction with the application – also known as a business service or unit of work.</div><div><br /></div><div>To be continued next week...</div>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com1tag:blogger.com,1999:blog-2924660267783169585.post-36301244278862464842009-05-15T17:10:00.002-04:002010-02-08T14:47:40.009-05:00BTM & IT Service Management<div><p class="MsoNormal" style="margin-bottom: 6pt;">From managing incidents to managing changes, availability, security, and compliance, BUSINESS TRANSACTION MANAGEMENT has been leveraged by large IT organizations to augment their <a href="http://en.wikipedia.org/wiki/ITSM">ITSM</a> activities.</p> <p class="MsoNormal" style="margin-bottom: 6pt;">Let’s look at the impact of BUSINESS TRANSACTION MANAGEMENT to each key ITSM process as well as compliance and auditing activities.</p> <p class="MsoNormal" style="margin-bottom: 6pt;"><i>Incident Management – </i><span style="">BUSINESS TRANSACTION MANAGEMENT<i> </i></span>feeds to help desk systems business transaction events and <st1:place st="on">SLA</st1:place> violations (in addition to current component based events).</p> <p class="MsoNormal" style="margin-bottom: 6pt;"><i>Problem Management – </i><span style="">BUSINESS TRANSACTION MANAGEMENT<i> </i></span>pinpoints exactly where a problem is in the entire data center topology from a business transaction perspective (instead of wasting hours or days pointing fingers in a war room).</p> <p class="MsoNormal" style="margin-bottom: 6pt;"><i>Change and Release Management - </i><span style="">BUSINESS TRANSACTION MANAGEMENT assesses in pre-production the impact of change to transaction performance by comparing detailed transaction metrics across builds (providing a more holistic view of performance and more granular drill-down information).<o:p></o:p></span></p> <p class="MsoNormal" style="margin-bottom: 6pt;"><i>Configuration Management - </i><span style="">BUSINESS TRANSACTION MANAGEMENT automatically discovers and models your topology based on real transactions, keeping your CMDB up to date (instead of relying on static modeling).<o:p></o:p></span></p> <p class="MsoNormal" style="margin-bottom: 6pt;"><i>Availability Management - </i><span style="">BUSINESS TRANSACTION MANAGEMENT monitors SLA compliance across all tiers (instead of being limited to specific tiers) – <st1:place st="on">SLA</st1:place> thresholds are defined automatically, based on transaction averages; or can be manually defined.<o:p></o:p></span></p> <p class="MsoNormal" style="margin-bottom: 6pt;"><i>Capacity Management - </i><span style="">BUSINESS TRANSACTION MANAGEMENT monitors transaction volume trends and identifies candidates for consolidation.<o:p></o:p></span></p> <p class="MsoNormal" style="margin-bottom: 6pt;"><i>Continuity Management - </i><span style="">BUSINESS TRANSACTION MANAGEMENT provides business transaction measurements for your disaster recovery testing and failover scenario management.<o:p></o:p></span></p> <p class="MsoNormal" style="margin-bottom: 6pt;"><i>Security Management - </i><span style="">BUSINESS TRANSACTION MANAGEMENT tracks all transactions including the location they are coming from, exactly where they are going and what they are doing – powerful data for both detection of security risks and forensic analysis.<o:p></o:p></span></p> <p class="MsoNormal" style="margin-bottom: 6pt;"><i>Compliance Management - </i><span style="">BUSINESS TRANSACTION MANAGEMENT leverages its full transaction monitoring data to prove regulatory compliance even across virtual servers. And it provides application developers production metrics without access to production (SoD).<o:p></o:p></span></p> <p class="MsoNormal" style="margin-bottom: 6pt;"><i>Auditing - </i><span style="">BUSINESS TRANSACTION MANAGEMENT provides a full transaction audit trail and trending metrics.</span></p></div>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com2tag:blogger.com,1999:blog-2924660267783169585.post-51329543846638389652009-04-25T22:54:00.001-04:002009-04-25T22:59:09.337-04:00Configuration Management Data Base (CMDB) and BTM<meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 12"><meta name="Originator" content="Microsoft Word 12"><link rel="File-List" href="file:///C:%5CUsers%5CAlon%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link rel="themeData" href="file:///C:%5CUsers%5CAlon%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CAlon%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:trackmoves/> <w:trackformatting/> <w:donotshowrevisions/> <w:donotprintrevisions/> <w:donotshowmarkup/> <w:donotshowcomments/> <w:donotshowinsertionsanddeletions/> <w:donotshowpropertychanges/> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:donotpromoteqf/> <w:lidthemeother>EN-US</w:LidThemeOther> <w:lidthemeasian>X-NONE</w:LidThemeAsian> <w:lidthemecomplexscript>HE</w:LidThemeComplexScript> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> <w:splitpgbreakandparamark/> <w:dontvertaligncellwithsp/> <w:dontbreakconstrainedforcedtables/> <w:dontvertalignintxbx/> <w:word11kerningpairs/> <w:cachedcolbalance/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathpr> <m:mathfont val="Cambria Math"> <m:brkbin val="before"> <m:brkbinsub val="--"> <m:smallfrac val="off"> <m:dispdef/> <m:lmargin val="0"> <m:rmargin val="0"> <m:defjc val="centerGroup"> <m:wrapindent val="1440"> <m:intlim val="subSup"> <m:narylim val="undOvr"> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"> <w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"> <w:lsdexception locked="false" priority="39" name="toc 1"> <w:lsdexception locked="false" priority="39" name="toc 2"> <w:lsdexception locked="false" priority="39" name="toc 3"> <w:lsdexception locked="false" priority="39" name="toc 4"> <w:lsdexception locked="false" priority="39" name="toc 5"> <w:lsdexception locked="false" priority="39" name="toc 6"> <w:lsdexception locked="false" priority="39" name="toc 7"> <w:lsdexception locked="false" priority="39" name="toc 8"> <w:lsdexception locked="false" priority="39" name="toc 9"> <w:lsdexception locked="false" priority="35" qformat="true" name="caption"> <w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"> <w:lsdexception locked="false" priority="1" name="Default Paragraph Font"> <w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"> <w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"> <w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"> <w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"> <w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"> <w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"> <w:lsdexception locked="false" unhidewhenused="false" name="Revision"> <w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"> <w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"> <w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"> <w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"> <w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"> <w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"> <w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"> <w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"> <w:lsdexception locked="false" priority="37" name="Bibliography"> <w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} @font-face {font-family:"Wingdings 2"; panose-1:5 2 1 2 1 5 7 7 7 7; mso-font-charset:2; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:6.0pt; margin-right:0in; margin-bottom:2.0pt; margin-left:0in; line-height:15.0pt; mso-pagination:widow-orphan lines-together; font-size:10.5pt; mso-bidi-font-size:10.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-bidi-language:AR-SA;} p.Bullets, li.Bullets, div.Bullets {mso-style-name:Bullets; mso-style-unhide:no; margin-top:4.0pt; margin-right:0in; margin-bottom:2.0pt; margin-left:.25in; text-indent:-.25in; line-height:15.0pt; mso-pagination:widow-orphan lines-together; mso-list:l0 level1 lfo1; font-size:10.5pt; mso-bidi-font-size:10.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-bidi-language:AR-SA;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:1990552587; mso-list-type:hybrid; mso-list-template-ids:1823393738 928645280 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l0:level1 {mso-level-number-format:bullet; mso-level-style-link:Bullets; mso-level-text:; mso-level-tab-stop:1.0in; mso-level-number-position:left; margin-left:1.0in; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Wingdings 2"; color:#63A9E1;} @list l0:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";} </style> <![endif]--> <p class="Bullets"><!--[if !supportLists]--><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 12"><meta name="Originator" content="Microsoft Word 12"><link rel="File-List" href="file:///C:%5CUsers%5CAlon%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link rel="themeData" href="file:///C:%5CUsers%5CAlon%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CAlon%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:trackmoves/> <w:trackformatting/> <w:donotshowrevisions/> <w:donotprintrevisions/> <w:donotshowmarkup/> <w:donotshowcomments/> <w:donotshowinsertionsanddeletions/> <w:donotshowpropertychanges/> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:donotpromoteqf/> <w:lidthemeother>EN-US</w:LidThemeOther> <w:lidthemeasian>X-NONE</w:LidThemeAsian> <w:lidthemecomplexscript>HE</w:LidThemeComplexScript> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> <w:splitpgbreakandparamark/> <w:dontvertaligncellwithsp/> <w:dontbreakconstrainedforcedtables/> <w:dontvertalignintxbx/> <w:word11kerningpairs/> <w:cachedcolbalance/> </w:Compatibility> <m:mathpr> <m:mathfont val="Cambria Math"> <m:brkbin val="before"> <m:brkbinsub val="--"> <m:smallfrac val="off"> <m:dispdef/> <m:lmargin val="0"> <m:rmargin val="0"> <m:defjc val="centerGroup"> <m:wrapindent val="1440"> <m:intlim val="subSup"> <m:narylim val="undOvr"> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"> <w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"> <w:lsdexception locked="false" priority="0" qformat="true" name="heading 2"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"> <w:lsdexception locked="false" priority="0" qformat="true" name="heading 5"> <w:lsdexception locked="false" priority="0" qformat="true" name="heading 6"> <w:lsdexception locked="false" priority="0" qformat="true" name="heading 7"> <w:lsdexception locked="false" priority="0" qformat="true" name="heading 8"> <w:lsdexception locked="false" priority="0" qformat="true" name="heading 9"> <w:lsdexception locked="false" priority="39" name="toc 1"> <w:lsdexception locked="false" priority="39" name="toc 2"> <w:lsdexception locked="false" priority="39" name="toc 3"> <w:lsdexception locked="false" priority="39" name="toc 4"> <w:lsdexception locked="false" priority="39" name="toc 5"> <w:lsdexception locked="false" priority="39" name="toc 6"> <w:lsdexception locked="false" priority="39" name="toc 7"> <w:lsdexception locked="false" priority="39" name="toc 8"> <w:lsdexception locked="false" priority="39" name="toc 9"> <w:lsdexception locked="false" priority="35" qformat="true" name="caption"> <w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"> <w:lsdexception locked="false" priority="1" name="Default Paragraph Font"> <w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"> <w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"> <w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"> <w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"> <w:lsdexception locked="false" unhidewhenused="false" name="Revision"> <w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"> <w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"> <w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"> <w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"> <w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"> <w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"> <w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"> <w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"> <w:lsdexception locked="false" priority="37" name="Bibliography"> <w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} @font-face {font-family:"Arial Black"; panose-1:2 11 10 4 2 1 2 2 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:647 0 0 0 159 0;} @font-face {font-family:"Futura Md BT"; mso-font-alt:"Futura Md"; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:1 0 0 0 27 0;} @font-face {font-family:Algerian; mso-font-charset:0; mso-generic-font-family:decorative; mso-font-pitch:variable; mso-font-signature:3 0 0 0 1 0;} @font-face {font-family:"Wingdings 2"; panose-1:5 2 1 2 1 5 7 7 7 7; mso-font-charset:2; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:6.0pt; margin-right:0in; margin-bottom:2.0pt; margin-left:0in; line-height:15.0pt; mso-pagination:widow-orphan lines-together; font-size:10.5pt; mso-bidi-font-size:10.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-bidi-language:AR-SA;} h2 {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; mso-style-link:"Heading 2 Char"; mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:0in; margin-left:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan lines-together; page-break-after:avoid; mso-outline-level:2; tab-stops:1.0in 1.25in; font-size:22.0pt; mso-bidi-font-size:20.0pt; font-family:"Calibri","sans-serif"; color:#63A9E1; mso-ansi-language:FR; mso-bidi-language:AR-SA; mso-bidi-font-weight:normal;} h5 {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; mso-style-link:"Heading 5 Char"; mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:0in; margin-left:0in; margin-bottom:.0001pt; text-indent:0in; mso-pagination:widow-orphan lines-together; page-break-after:avoid; mso-outline-level:5; mso-list:l0 level5 lfo1; mso-layout-grid-align:none; font-size:12.0pt; font-family:"Calibri","sans-serif"; color:#63A9E1; letter-spacing:.25pt; mso-bidi-language:AR-SA; mso-bidi-font-weight:normal;} h6 {mso-style-unhide:no; mso-style-qformat:yes; mso-style-link:"Heading 6 Char"; mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:2.0pt; margin-left:.75in; text-indent:0in; mso-pagination:widow-orphan lines-together; page-break-after:avoid; mso-outline-level:6; mso-list:l0 level6 lfo1; tab-stops:.75in 1.25in; font-size:10.5pt; mso-bidi-font-size:10.0pt; font-family:"Arial Black","sans-serif"; letter-spacing:.25pt; mso-bidi-language:AR-SA; font-weight:normal;} p.MsoHeading7, li.MsoHeading7, div.MsoHeading7 {mso-style-unhide:no; mso-style-qformat:yes; mso-style-link:"Heading 7 Char"; mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; text-indent:0in; line-height:15.0pt; mso-pagination:widow-orphan lines-together; mso-outline-level:7; mso-list:l0 level7 lfo1; font-size:10.0pt; font-family:"Arial","sans-serif"; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-bidi-language:AR-SA;} p.MsoHeading8, li.MsoHeading8, div.MsoHeading8 {mso-style-unhide:no; mso-style-qformat:yes; mso-style-link:"Heading 8 Char"; mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; text-indent:0in; line-height:15.0pt; mso-pagination:widow-orphan lines-together; mso-outline-level:8; mso-list:l0 level8 lfo1; font-size:10.0pt; font-family:"Arial","sans-serif"; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-bidi-language:AR-SA; font-style:italic; mso-bidi-font-style:normal;} p.MsoHeading9, li.MsoHeading9, div.MsoHeading9 {mso-style-unhide:no; mso-style-qformat:yes; mso-style-link:"Heading 9 Char"; mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:12.0pt; text-indent:0in; line-height:15.0pt; mso-pagination:widow-orphan lines-together; mso-outline-level:9; mso-list:l0 level9 lfo1; font-size:9.0pt; mso-bidi-font-size:10.0pt; font-family:"Arial","sans-serif"; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-bidi-language:AR-SA; font-weight:bold; mso-bidi-font-weight:normal; font-style:italic; mso-bidi-font-style:normal;} span.Heading2Char {mso-style-name:"Heading 2 Char"; mso-style-unhide:no; mso-style-locked:yes; mso-style-link:"Heading 2"; mso-ansi-font-size:22.0pt; mso-bidi-font-size:20.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-hansi-font-family:Calibri; color:#63A9E1; mso-ansi-language:FR; mso-bidi-language:AR-SA; font-weight:bold; mso-bidi-font-weight:normal;} span.Heading5Char {mso-style-name:"Heading 5 Char"; mso-style-unhide:no; mso-style-locked:yes; mso-style-link:"Heading 5"; mso-ansi-font-size:12.0pt; mso-bidi-font-size:12.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-hansi-font-family:Calibri; color:#63A9E1; letter-spacing:.25pt; mso-bidi-language:AR-SA; font-weight:bold; mso-bidi-font-weight:normal;} span.Heading6Char {mso-style-name:"Heading 6 Char"; mso-style-unhide:no; mso-style-locked:yes; mso-style-link:"Heading 6"; mso-ansi-font-size:10.5pt; font-family:"Arial Black","sans-serif"; mso-ascii-font-family:"Arial Black"; mso-hansi-font-family:"Arial Black"; letter-spacing:.25pt; mso-bidi-language:AR-SA;} span.Heading7Char {mso-style-name:"Heading 7 Char"; mso-style-unhide:no; mso-style-locked:yes; mso-style-link:"Heading 7"; font-family:"Arial","sans-serif"; mso-ascii-font-family:Arial; mso-hansi-font-family:Arial; mso-bidi-language:AR-SA;} span.Heading8Char {mso-style-name:"Heading 8 Char"; mso-style-unhide:no; mso-style-locked:yes; mso-style-link:"Heading 8"; font-family:"Arial","sans-serif"; mso-ascii-font-family:Arial; mso-hansi-font-family:Arial; mso-bidi-language:AR-SA; font-style:italic; mso-bidi-font-style:normal;} span.Heading9Char {mso-style-name:"Heading 9 Char"; mso-style-unhide:no; mso-style-locked:yes; mso-style-link:"Heading 9"; mso-ansi-font-size:9.0pt; font-family:"Arial","sans-serif"; mso-ascii-font-family:Arial; mso-hansi-font-family:Arial; mso-bidi-language:AR-SA; font-weight:bold; mso-bidi-font-weight:normal; font-style:italic; mso-bidi-font-style:normal;} p.Bullets, li.Bullets, div.Bullets {mso-style-name:Bullets; mso-style-unhide:no; margin-top:4.0pt; margin-right:0in; margin-bottom:2.0pt; margin-left:.25in; text-indent:-.25in; line-height:15.0pt; mso-pagination:widow-orphan lines-together; mso-list:l1 level1 lfo2; font-size:10.5pt; mso-bidi-font-size:10.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-bidi-language:AR-SA;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:1391223969; mso-list-template-ids:-1077654900;} @list l0:level1 {mso-level-start-at:2; mso-level-suffix:none; mso-level-text:"Chapter %1"; mso-level-tab-stop:none; mso-level-number-position:left; margin-left:0in; text-indent:0in; mso-ansi-font-size:20.0pt;} @list l0:level2 {mso-level-number-format:none; mso-level-suffix:none; mso-level-text:""; mso-level-tab-stop:none; mso-level-number-position:left; margin-left:0in; text-indent:0in;} @list l0:level3 {mso-level-number-format:none; mso-level-suffix:none; mso-level-text:""; mso-level-tab-stop:none; mso-level-number-position:left; margin-left:0in; text-indent:0in;} @list l0:level4 {mso-level-number-format:none; mso-level-suffix:none; mso-level-text:""; mso-level-tab-stop:none; mso-level-number-position:left; margin-left:0in; text-indent:0in;} @list l0:level5 {mso-level-number-format:none; mso-level-style-link:"Heading 5"; mso-level-suffix:none; mso-level-text:""; mso-level-tab-stop:none; mso-level-number-position:left; margin-left:0in; text-indent:0in;} @list l0:level6 {mso-level-number-format:none; mso-level-style-link:"Heading 6"; mso-level-suffix:none; mso-level-text:""; mso-level-tab-stop:none; mso-level-number-position:left; margin-left:0in; text-indent:0in;} @list l0:level7 {mso-level-number-format:none; mso-level-style-link:"Heading 7"; mso-level-suffix:none; mso-level-text:""; mso-level-tab-stop:none; mso-level-number-position:left; margin-left:0in; text-indent:0in;} @list l0:level8 {mso-level-number-format:none; mso-level-style-link:"Heading 8"; mso-level-suffix:none; mso-level-text:""; mso-level-tab-stop:none; mso-level-number-position:left; margin-left:0in; text-indent:0in;} @list l0:level9 {mso-level-number-format:alpha-upper; mso-level-style-link:"Heading 9"; mso-level-suffix:none; mso-level-text:"Appendix %9"; mso-level-tab-stop:none; mso-level-number-position:left; margin-left:12.0pt; text-indent:0in; mso-ansi-font-size:24.0pt; font-family:"Futura Md BT","sans-serif"; mso-hansi-font-family:Algerian; mso-ansi-font-weight:bold; mso-ansi-font-style:normal;} @list l1 {mso-list-id:1990552587; mso-list-type:hybrid; mso-list-template-ids:1823393738 928645280 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l1:level1 {mso-level-number-format:bullet; mso-level-style-link:Bullets; mso-level-text:; mso-level-tab-stop:1.0in; mso-level-number-position:left; margin-left:1.0in; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Wingdings 2"; color:#63A9E1;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";} </style> <![endif]--> </p><p class="MsoNormal">Any organization that has or is planning to implement the ITIL methodology will find great value in a Business Transaction Management (BTM) solution. BTM contributes significantly to the population and utilization of your CMDB, along with the auto creation of a service model relationship within your CMDB. <o:p></o:p></p> <p class="MsoNormal"><strong><span style=";font-family:";" >CMDB Population:</span></strong> Business Transaction Management solutions auto discover your application dependency map by monitoring the real transactions that run through an application's full topology. Additionally, the auto discovered transaction types are then added to the CMDB. Anyone accessing the CMDB that wants to see more specific information about various transactions will be referred directly to the BTM tool's transaction repository.<o:p></o:p></p> <p class="MsoNormal"><strong><span style=";font-family:";" >Enhanced Utilization:</span></strong> BTM solutions enable better utilization of a CMDB by linking true business activities to IT processes, enabling the management of IT from the business perspective. Additionally, BTM solutions connect specific transaction segments and servers – virtual or real – to service degradations enabling rapid resolution.<o:p></o:p></p> <h2><a name="_Toc227754051"><span lang="FR">BTM Enables the Real Time Population of Your CMDB</span></a><span lang="FR"><o:p></o:p></span></h2> <p class="MsoNormal">BTM solutions are designed to operate around the clock in production environments and collect important data on all transactions that flow through all of the IT components in the datacenter.<span style=""> </span>This enables your CMDB to be continuously populated with the critical business processes that are linked to their underlying IT counterparts.<o:p></o:p></p> <p class="MsoNormal">Some examples of Configuration Items (CIs) that a BTM solution can populate a CMDB with are:<o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>Business services (transaction types)<o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>Data flows - the full structure of the infrastructure that supports each transaction - down to the methods that are executed - enabling much more granular impact analyses in change management<o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>The Topology of each transaction type (true service models)<o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>IP addresses of clients and servers<o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>All of the possible physical servers that transactions may run through<o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>All of the possible virtual servers that may be brought up on the fly in response to increasing load<o:p></o:p></p> <p class="MsoNormal">The advantage of defining business relationship CIs with the help of a BTM solution is that those relationships are 100% accurate and are based on the flow of real transaction activations in the production environment, as opposed to other CMDB populating tools which must rely on assumptions, or manual input. <o:p></o:p></p> <p class="MsoNormal">It is now possible to understand which changes affect which transactions – or business services - so that the criticalities of each change can be better understood from a true business perspective.<b><o:p></o:p></b></p> <h2><a name="_Toc227754052"><span lang="FR">CMDB and the Help Desk Ticket</span></a><span lang="FR"><o:p></o:p></span></h2> <p class="MsoNormal">A BTM solution will automatically detect slow or hanging business transactions and open an Incident.<span style=""> </span>By doing so, the IT Service Support or Help Desk team can be proactive in dealing with the incident.<span style=""> </span>They can proactively start working on the root cause of the problem and fix it – possibly even before any users feel the negative impact of the degradation. <o:p></o:p></p> <p class="MsoNormal">Tickets that are opened by the help desk are automatically put in the context of the CMDB since the BTM solution links the IT components that are involved in the transaction degradation to that ticket. This not only enables tickets to be sent to the appropriate administrator for resolution, it also enables that administrator to utilize CMDB information to help resolve the issue.<b><o:p></o:p></b></p> <h2><a name="_Toc227754053"><span lang="FR">BTM – CMDB Scenarios</span></a><span lang="FR"><o:p></o:p></span></h2> <h6 style="text-indent: 0in;"><span dir="ltr"></span>A Service degradation <o:p></o:p></h6> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>The BTM solution identifies the degradation of a specific transaction type’s SLA<o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>An incident is created and a help desk ticket is opened - flagging the server which is causing the latency - for example – the latency is due to a specific application server<o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>The Help Desk forwards the ticket to the Application Team as part of the problem resolution process<o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>The Application Team can now look at the change history of that specific application server within the CMDB and identify the cause of the problem <o:p></o:p></p> <h6 style="text-indent: 0in;"><span dir="ltr"></span>A Change is Being Contemplated<o:p></o:p></h6> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>A change to a specific application in the application server is being contemplated<o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>The Change Manager identifies all of the real business transactions that are associated with the change<o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>The Change Manager will be able to anticipate the business impact that the change will have on the business users and will later be able to measure the impact with real user measurements<o:p></o:p></p> <h6 style="text-indent: 0in;"><span dir="ltr"></span>Prioritization of Incidents<o:p></o:p></h6> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>Two servers fail at the exact same time<u><span style="font-variant: small-caps; color: rgb(192, 80, 77);"><o:p></o:p></span></u></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>The system administrator knows which server is more critical to the business and can prioritize the recovery - something that is not possible to perform without the true model<u><span style="font-variant: small-caps; color: rgb(192, 80, 77);"><o:p></o:p></span></u></p> <h6 style="text-indent: 0in;"><span dir="ltr"></span>Change Verification <o:p></o:p></h6> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>Measuring the impact of a change that has been conducted<o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>A change to the application has been implemented<o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>The BTM solution will show the impact of that change by comparing the performance of transactions and transaction segments before and after the change<o:p></o:p></p> <h6 style="text-indent: 0in;"><span dir="ltr"></span>Roll Back Has Been Performed<o:p></o:p></h6> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>The performance of all transactions in the current time frame is compared to the time frame of the last known consistent state in order to verify the roll back<o:p></o:p></p> <h6 style="text-indent: 0in;"><span dir="ltr"></span>Comparisons <o:p></o:p></h6> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>The performance of specific transaction segments on two identical servers is compared in order to verify the consistency of performance<b><o:p></o:p></b></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style="">›<span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><span dir="ltr"></span>The topologies of two similar applications are compared in order to validate the quality of implementation<b><o:p></o:p></b></p> <b style=""><span style="color: rgb(99, 169, 225);font-size:22;" lang="FR"><o:p></o:p></span></b> <h2><a name="_Toc227754054"><span lang="FR">A CMDB for the Cloud</span></a><span lang="FR"><o:p></o:p></span></h2> <p class="MsoNormal">Cloud Computing's value proposition to the enterprise is a substantial one - maintaining a CMDB for the cloud introduces new challenges. These challenges are related to the real time scalability of applications in the cloud. <o:p></o:p></p> <p class="MsoNormal">Business Transaction management solutions can at any given moment provide a real time snapshot of the cloud enabling a CMDB to keep up with the constant change.<o:p></o:p></p> <p class="MsoNormal">Additionally, BTM's ability to effectively support a federated environment contributes to the stability and scalability of a CMDB in the cloud.<o:p></o:p></p> <p class="MsoNormal">The CMDB can define a template that is fed in by the Business Transaction Management solution. In this manner the current status of the cloud can be shown – this can only be done with a real time BTM tool.<b><o:p></o:p></b></p> <h2><a name="_Toc227754055"><span lang="FR">BTM Brings Value to Your CMDB Investment</span></a><span lang="FR"><o:p></o:p></span></h2> <p class="MsoNormal"><strong><span style=";font-family:";" >Consider the following scenario;</span></strong> an application utilizes twenty different servers within the datacenter, a specific business critical service that the application provides really only utilizes only four of those servers. When building a CMDB with traditional tools it is nearly impossible to crack this scenario since most models are based on theories and assumptions. The only way of achieving this accurate level of granularity with the CMDB – short of going line by line through the application’s code - is by using BTM to help populate the CMDB with real data.<o:p></o:p></p> <p class="MsoNormal">Implementing a CMDB is not a small investment, not to mention maintaining it, utilizing it, keeping it up to date and ensuring its validity. <em><span style=";font-family:";" >Business Transaction Management solutions enable organizations to better utilize and maintain their CMDB</span></em> by filling in the gaps that occur in real time. BTM solutions are the only solutions that can link the degradation of a business service to the problematic IT component. This enables the location of the relevant CMDB data needed in order to resolve the problem.<o:p></o:p></p> <p></p> Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com12tag:blogger.com,1999:blog-2924660267783169585.post-60567416054631991432009-04-10T10:31:00.001-04:002009-04-10T10:35:54.260-04:00BTM and Real User Measurements (RUM)<meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 12"><meta name="Originator" content="Microsoft Word 12"><link rel="File-List" href="file:///C:%5CUsers%5CAlon%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link rel="themeData" href="file:///C:%5CUsers%5CAlon%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CAlon%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:trackmoves/> <w:trackformatting/> <w:donotshowrevisions/> <w:donotprintrevisions/> <w:donotshowmarkup/> <w:donotshowcomments/> <w:donotshowinsertionsanddeletions/> <w:donotshowpropertychanges/> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:donotpromoteqf/> <w:lidthemeother>EN-US</w:LidThemeOther> <w:lidthemeasian>X-NONE</w:LidThemeAsian> <w:lidthemecomplexscript>HE</w:LidThemeComplexScript> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> <w:splitpgbreakandparamark/> <w:dontvertaligncellwithsp/> <w:dontbreakconstrainedforcedtables/> <w:dontvertalignintxbx/> <w:word11kerningpairs/> <w:cachedcolbalance/> </w:Compatibility> <m:mathpr> <m:mathfont val="Cambria Math"> <m:brkbin val="before"> <m:brkbinsub val="--"> <m:smallfrac val="off"> <m:dispdef/> <m:lmargin val="0"> <m:rmargin val="0"> <m:defjc val="centerGroup"> <m:wrapindent val="1440"> <m:intlim val="subSup"> <m:narylim val="undOvr"> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"> <w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"> <w:lsdexception locked="false" priority="0" qformat="true" name="heading 2"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"> <w:lsdexception locked="false" priority="39" name="toc 1"> <w:lsdexception locked="false" priority="39" name="toc 2"> <w:lsdexception locked="false" priority="39" name="toc 3"> <w:lsdexception locked="false" priority="39" name="toc 4"> <w:lsdexception locked="false" priority="39" name="toc 5"> <w:lsdexception locked="false" priority="39" name="toc 6"> <w:lsdexception locked="false" priority="39" name="toc 7"> <w:lsdexception locked="false" priority="39" name="toc 8"> <w:lsdexception locked="false" priority="39" name="toc 9"> <w:lsdexception locked="false" priority="35" qformat="true" name="caption"> <w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"> <w:lsdexception locked="false" priority="1" name="Default Paragraph Font"> <w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"> <w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"> <w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"> <w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"> <w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"> <w:lsdexception locked="false" unhidewhenused="false" name="Revision"> <w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"> <w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"> <w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"> <w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"> <w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"> <w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"> <w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"> <w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"> <w:lsdexception locked="false" priority="37" name="Bibliography"> <w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} @font-face {font-family:"Wingdings 2"; panose-1:5 2 1 2 1 5 7 7 7 7; mso-font-charset:2; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:6.0pt; margin-right:0in; margin-bottom:2.0pt; margin-left:0in; line-height:15.0pt; mso-pagination:widow-orphan lines-together; font-size:10.5pt; mso-bidi-font-size:10.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-bidi-language:AR-SA;} h2 {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; mso-style-link:"Heading 2 Char"; mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:0in; margin-left:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan lines-together; page-break-after:avoid; mso-outline-level:2; tab-stops:1.0in 1.25in; font-size:22.0pt; mso-bidi-font-size:20.0pt; font-family:"Calibri","sans-serif"; color:#63A9E1; mso-ansi-language:FR; mso-bidi-language:AR-SA; mso-bidi-font-weight:normal;} span.Heading2Char {mso-style-name:"Heading 2 Char"; mso-style-unhide:no; mso-style-locked:yes; mso-style-link:"Heading 2"; mso-ansi-font-size:22.0pt; mso-bidi-font-size:20.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-hansi-font-family:Calibri; color:#63A9E1; mso-ansi-language:FR; mso-bidi-language:AR-SA; font-weight:bold; mso-bidi-font-weight:normal;} p.Bullets, li.Bullets, div.Bullets {mso-style-name:Bullets; mso-style-unhide:no; margin-top:4.0pt; margin-right:0in; margin-bottom:2.0pt; margin-left:.25in; text-indent:-.25in; line-height:15.0pt; mso-pagination:widow-orphan lines-together; mso-list:l0 level1 lfo1; font-size:10.5pt; mso-bidi-font-size:10.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-bidi-language:AR-SA;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:1990552587; mso-list-type:hybrid; mso-list-template-ids:1823393738 928645280 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l0:level1 {mso-level-number-format:bullet; mso-level-style-link:Bullets; mso-level-text:; mso-level-tab-stop:1.0in; mso-level-number-position:left; margin-left:1.0in; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Wingdings 2"; color:#63A9E1;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";} </style> <![endif]--> <h2><a name="_Toc224100810"><span lang="FR"></span></a><span lang="FR"><o:p></o:p></span></h2> <p class="MsoNormal"><strong><span style=";font-family:";" >A complete BTM solution cannot ignore the “first mile”</span></strong> – the segment from the end-user to the data center. Real User Measurements (RUM) should be part of any complete BTM solution, since the origin of every user related transaction, is at the user. <o:p></o:p></p> <p class="MsoNormal">Enterprises must have the ability to measure the level of service that their users are actually receiving - from their own desktop - and provide fast answers when performance degradation occurs. <o:p></o:p></p> <p class="MsoNormal">Whether response times are degrading, or transaction failures are proliferating, IT staff must provide fast answers. <o:p></o:p></p> <p class="MsoNormal"><strong><span style=";font-family:";" >RUM must address two separate needs</span></strong>: <o:p></o:p></p> <ul><li><!--[if !supportLists]-->Web based applications used by remote users at their home or on a mobile device<o:p></o:p></li></ul> <ul><li><!--[if !supportLists]-->Internal corporate users with desktop or Citrix based applications <o:p></o:p></li></ul> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style=""><span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><strong><span style=";font-family:";" >For home users</span></strong>, installation on the home user desktop is usually not an option. BTM must provide the technology for measuring latencies from the home user’s browser, without installation on the desktop. <o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style=""><span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]--><strong><span style=";font-family:";" >Enterprise users</span></strong>, tend to use numerous applications, some based on fat clients (no browser) installed on their desktop. In such cases a local agent has to be deployed to capture every transaction issued by the user in order to measure its latency and successful completion.<span style=""> </span><o:p></o:p></p> <p class="Bullets"><!--[if !supportLists]--><span style=";font-family:";font-size:10;" ><span style=""><span style=";font-family:";font-size:7;" > </span></span></span><!--[endif]-->Agent based RUM solutions also provide inventory metrics – how many applications are actually being used, what applications are installed and executed within the user’s operating system, and so forth.<o:p></o:p></p> Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com2tag:blogger.com,1999:blog-2924660267783169585.post-67031464324207763642009-03-11T14:07:00.001-04:002009-03-11T14:10:28.672-04:00BTM Benefits Both Business and IT<!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:trackmoves/> <w:trackformatting/> <w:donotshowrevisions/> <w:donotprintrevisions/> <w:donotshowmarkup/> <w:donotshowcomments/> <w:donotshowinsertionsanddeletions/> <w:donotshowpropertychanges/> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:donotpromoteqf/> <w:lidthemeother>EN-US</w:LidThemeOther> <w:lidthemeasian>X-NONE</w:LidThemeAsian> <w:lidthemecomplexscript>HE</w:LidThemeComplexScript> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> <w:splitpgbreakandparamark/> <w:dontvertaligncellwithsp/> <w:dontbreakconstrainedforcedtables/> <w:dontvertalignintxbx/> <w:word11kerningpairs/> <w:cachedcolbalance/> </w:Compatibility> <m:mathpr> <m:mathfont val="Cambria Math"> <m:brkbin val="before"> <m:brkbinsub val="--"> <m:smallfrac val="off"> <m:dispdef/> <m:lmargin val="0"> <m:rmargin val="0"> <m:defjc val="centerGroup"> <m:wrapindent val="1440"> <m:intlim val="subSup"> <m:narylim val="undOvr"> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"> <w:lsdexception locked="false" priority="0" qformat="true" name="heading 2"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"> <w:lsdexception locked="false" priority="39" name="toc 1"> <w:lsdexception locked="false" priority="39" name="toc 2"> <w:lsdexception locked="false" priority="39" name="toc 3"> <w:lsdexception locked="false" priority="39" name="toc 4"> <w:lsdexception locked="false" priority="39" name="toc 5"> <w:lsdexception locked="false" priority="39" name="toc 6"> <w:lsdexception locked="false" priority="39" name="toc 7"> <w:lsdexception locked="false" priority="39" name="toc 8"> <w:lsdexception locked="false" priority="39" name="toc 9"> <w:lsdexception locked="false" priority="35" qformat="true" name="caption"> <w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"> <w:lsdexception locked="false" priority="1" name="Default Paragraph Font"> <w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"> <w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"> <w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"> <w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"> <w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"> <w:lsdexception locked="false" unhidewhenused="false" name="Revision"> <w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"> <w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"> <w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"> <w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"> <w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"> <w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"> <w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"> <w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"> <w:lsdexception locked="false" priority="37" name="Bibliography"> <w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:6.0pt; margin-right:0in; margin-bottom:2.0pt; margin-left:0in; line-height:15.0pt; mso-pagination:widow-orphan lines-together; font-size:10.5pt; mso-bidi-font-size:10.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-bidi-language:AR-SA;} h1 {mso-style-name:"Heading 1\,h1\,Level 1 Topic Heading"; mso-style-unhide:no; mso-style-qformat:yes; mso-style-link:"Heading 1 Char"; mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:0in; margin-left:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan lines-together; page-break-after:avoid; mso-outline-level:1; font-size:26.0pt; mso-bidi-font-size:10.0pt; font-family:"Calibri","sans-serif"; color:#63A9E1; mso-font-kerning:0pt; mso-bidi-language:AR-SA;} h2 {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; mso-style-link:"Heading 2 Char"; mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:0in; margin-left:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan lines-together; page-break-after:avoid; mso-outline-level:2; tab-stops:1.0in 1.25in; font-size:22.0pt; mso-bidi-font-size:20.0pt; font-family:"Calibri","sans-serif"; color:#63A9E1; mso-ansi-language:FR; mso-bidi-language:AR-SA; mso-bidi-font-weight:normal;} span.Heading1Char {mso-style-name:"Heading 1 Char"; mso-style-unhide:no; mso-style-locked:yes; mso-style-link:"Heading 1\,h1\,Level 1 Topic Heading"; mso-ansi-font-size:26.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-hansi-font-family:Calibri; color:#63A9E1; mso-bidi-language:AR-SA; font-weight:bold;} span.Heading2Char {mso-style-name:"Heading 2 Char"; mso-style-unhide:no; mso-style-locked:yes; mso-style-link:"Heading 2"; mso-ansi-font-size:22.0pt; mso-bidi-font-size:20.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-hansi-font-family:Calibri; color:#63A9E1; mso-ansi-language:FR; mso-bidi-language:AR-SA; font-weight:bold; mso-bidi-font-weight:normal;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><a name="_Toc224100808"></a> <p class="MsoNormal">Business Transaction Management is becoming a strategic investment for any enterprise since it sits at heart of IT management. <o:p></o:p></p> <p class="MsoNormal">With a complete BTM solution, <strong><span style=";font-family:";" >every single transaction</span></strong> is captured and traced; from the moment the end user hits a button in any application, be it browser or desktop based, to the last CICS program call in the Mainframe. <o:p></o:p></p> <p class="MsoNormal">Complete BTM solutions do this within a <strong><span style=";font-family:";" >production environment</span></strong> - are always turned on - in order to assure the <strong><span style=";font-family:";" >reliability</span></strong> of complex modern applications. <o:p></o:p></p> <h2><a name="_Toc224100809"><strong><span style=";font-family:";" lang="FR">The Benefits</span></strong></a><strong><span style=";font-family:";" lang="FR"><o:p></o:p></span></strong></h2> <p class="MsoNormal"><strong><span style=";font-family:";" >BTM enables IT to align with business requirements</span></strong> by making sure every business transaction is processed successfully in a timely manner along with putting every IT process within the datacenter in the context of an end user activated transaction. <o:p></o:p></p> <p class="MsoNormal"><strong><span style=";font-family:";" >End-to-end transaction tracing enables full accountability</span></strong> for every transaction processed within the IT topology. Whether it spans through proxys, load balancers, web servers, application servers - based on J2EE/.NET, C/C++ or even proprietary home grown applications (e.g Cobol) - down to message brokers/hubs, databases and legacy systems within the Mainframe. <o:p></o:p></p> <p class="MsoNormal"><strong><span style=";font-family:";" >No tier is ignored, no transaction is lost</span></strong>. Real time alerts are propagated - proactively - from the moment a performance degredation starts to occur. Root-cause-analysis can always be done in a scientific and accurate manner. <o:p></o:p></p> <p class="MsoNormal">By creating a <strong><span style=";font-family:";" >Performance Management Database</span></strong> (PMDB) – IT staff can now speak to each other in a common language. No more talking about packets, HTTP, SQL, or CICS – but a single transaction that encapsulates all relevant information on how it is doing, where, and when.<o:p></o:p></p> <p class="MsoNormal"><strong><span style=";font-family:";" >Automatic topology mapping</span></strong> is a byproduct of any BTM solution.<span style=""> </span>By tracing the transaction along the IT topology, a complete map of IT relations – what logical component is interacting with what – emerges. At a granularity that has never before been available. Every web server instance, every message broker, every database and every external application that is part of a transaction flow will be located in the relevant path within the topology map. Real time measurements allow constant monitoring of latencies between different tiers, and actual transaction volumes.<o:p></o:p></p> <p class="MsoNormal"><strong><span style=";font-family:";" >Proactive management</span></strong> – Proactive resource allocation management per transaction instance, or in other words prioritization of transactions according to business context, or blocking of transactions/transaction segments according to security requirements, are all part of the potential of the BTM solution.<o:p></o:p></p>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com2tag:blogger.com,1999:blog-2924660267783169585.post-30148008493734139212009-02-10T18:06:00.002-05:002009-02-10T18:09:56.089-05:00Do not Confuse BTM with Traditional Tools!<span xmlns=""><p>Even experienced IT professionals can confuse traditional monitoring tools and the newer generation of transaction monitoring tools. In today's market, all of the marketing messages are the same so it is very hard to differentiate between the old and the new. The following provides insight into the difference which needs to be understood before considering the purchase of any monitoring tool.<br /></p><p><em>Disclaimer</em>: There is nothing wrong with traditional tools, they do their job well and all of the vendors that have been listed are good competent vendors. As with any technology, newer generations tend to improve on the old ones. Additionally, BTM has yet to fully mature and vendors of traditional tools are bound to jump to the newer generation at some point.<br /></p><h3>Traditional Monitoring:<br /></h3><p><strong>Traditional Tools</strong> monitor the performance of each component <em>individually</em> and display all of these metrics on a "single pane of glass".<br /></p><p><strong>"End to end"</strong> performance monitoring means that you can see the performance of every component in a single centralized console. So for example you see the resource consumption of your servers, the threads that your application is running, the throughput of your network components and the calls to your database all displayed in their own section.<br /></p><p><strong>When traditional tools monitor transactions</strong> what they do is pick up various segments of transactions throughout the data center without stitching them together into one full transaction flow.<br /></p><p><strong>For example: </strong>The database monitor picks up all of the SQL statements that it sees and displays them on the central dashboard along with their response times, while the real user monitor picks up all of the requests that are sent out to the datacenter and displays them on the same dashboard along with their response times. Now say that an application slow down occurs and both monitors (including the application server monitor which was not mentioned) are showing erratic response times for various "transactions" – the real user measurements only show that the user is experiencing a problem but cannot show where the problem is within the datacenter – and the silo specific tools do not have the context of the CICS program names, SQL statements, web service calls which are showing erratic performance. The IT professional is stuck with a glut of confusing information on the dashboard that is not connected.<br /></p><p><strong>How to identify traditional monitoring tools: </strong>Vendors<strong><br /> </strong>that provide these tools typically sell them as suites. What they will do is develop or acquire separate server monitoring tools, network monitoring tools, application performance management tools and real user measurement tools - and then offer them bundled as an end to end package. These tools tend to be pricey and hard to implement not to mention their limited visibility due to the lack of correlation between tiers. On the up side they can provide more thorough metrics within the tier – that is why the new generation seeks to complement the traditional tools as opposed to replacing them.<br /></p><p><strong><em>Some examples of vendors</em></strong>: Opnet, Compuware, Quest, NetScout, CA, IBM<strong><br /> </strong></p><h3> The New Generation of Monitoring Tools:<br /></h3><p><strong>The new tools</strong> connect every single process within the datacenter to a click of a user within the application that initiated all of the activity within the datacenter.<br /></p><p><strong>"End to End"</strong> means that the user request and the related activity within the proxy, web server, app server, database server, MQ and mainframe are all connected as a single transaction instance.<br /></p><p><strong>The resource consumption</strong> at each component can still be seen – but at the granularity of a single transaction segment.<br /></p><p><strong>For Example:</strong> If service levels are starting to degrade, this new generation of tools not only pick up the performance degradation that the user is experiencing but they also immediately know what is causing the specific degradation down the line.<br /></p><p><strong><em>Some examples of vendors</em></strong>: Optier, Correlsense, HP Transaction Vision, SeaNet</p></span>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com2tag:blogger.com,1999:blog-2924660267783169585.post-44959997083971090522009-01-26T19:55:00.001-05:002009-01-26T19:55:45.845-05:00Service Level Management Made Easy with BTM<span xmlns=''><p>Implementing <strong>Service Level Management</strong> successfully requires appropriate technology support. Service Level Management involves both business processes and IT processes that need to be carried out. Business Transaction Management provides the tools that both the Business and IT need in order to perform the tasks that are critical for a successful implementation. This article reviews some of the steps that need to be taken in order to implement <strong>Service Level Management</strong> and how Business Transaction Management supports each one of those steps.<br /></p><h2>Service Level Management Step 1 – Review Existing Services<br /></h2><p>By auto-discovering all of the services that are being provided by a monitored system, Business Transaction Management makes this step an especially easy one. Believe it or not, most organizations aren't even aware of all of the services that they are providing. Since Business Transaction Management solutions see all of the services that are being provided - in the form of business transactions - all of the information about the services, what resources they consume, who is using them and how often they are being utilized is readily available.<br /></p><h2>Service Level Management Step 2 – Negotiating With Customers<br /></h2><p>Most organizations are not aware of the <strong>service level</strong> that they are providing – most customers have no idea what the <strong>service levels</strong> they are receiving are. Business Transaction Management solutions provide all of the metrics that are needed for this negotiation to occur in the most accurate fashion possible by providing in depth data about all of the service levels.<br /></p><h2>Service Level Management Step 3 – SLA Management and Monitoring<br /></h2><p>SLAs can be easily produced based on current metrics that are provided by the Business Transaction Management solution. Out of the box, SLAs are defined based on the average latencies that the system records. The SLAs can then be modified according to the outcome of the agreement between the customer and the IT service provider. The Service Level Agreements are then monitored for every single transaction activation - continuously. An alert is sent out the moment SLAs begin degrading so that they can be taken care of before a major service disruption occurs. <strong>SLA management</strong> becomes automatic once a BTM solution is implemented<br /></p><h2>Service Level Management Step 4 – Implementation of a Service Improvement Policy <br /></h2><p>Business Transaction Management is a key tool in improving service. It not only reports the service level – it also shows the breakdown of every single transaction across the entire infrastructure so that the areas that are in the greatest need of improvement can be identified.<br /></p><h2>Service Level Management Step 5 – Establishing Priorities <br /></h2><p>Business Transaction Management solutions provide Valuable metrics that aid in the establishment of priorities. Some examples of those metrics are; what users are using specific services, how many times a minute is a specific service being called upon and which services are in need of the greatest improvement.<br /></p><h2>Service Level Management Step 6 – Planning for Service Growth<br /></h2><p>Business Transaction Management solutions provide resource consumption metrics of services across all of the servers that they utilize making service capacity planning easy. The Service Level Manager can see what part of the total resource consumption is being consumed by an individual service. The consumption profile of an individual service can be seen across all tiers and the breakdown of how the service is consuming resources at each tier can be seen. With the help of this data the Service Level Manager can accurately plan for service growth.<br /></p><h2>Service Level Management Step 7 – Charging for Services<br /></h2><p>Business Transaction Management solutions provide the IP address of each and every service call making chargeback easy. If a specific user name is needed this can also be provided. The level of service being provided is monitored continuously so that SLAs can be easily proved out.<br /></p><h2>Availability Management and SLA Management<br /></h2><p>Traditionally availability management looks at the availability of individual silos. The problem with performing availability management in this manner is that even if each one of the silos is managed to an availability of 99.9% the actual <em>availability</em> of a <em>service</em> that depends on four separate silos is 99.9%^4 or 99.5%. Therefore the only kind of availability management that truly keeps the business in mind is <strong>SLA Management</strong>.<br /></p><h2>The First Step towards Service Level Management – BTM<br /></h2><p>In conclusion; Business Transaction Management supports Service Level Management's responsibilities by:<br /></p><ul><li>ensuring that agreed IT services are delivered when and where they are supposed to be<br /></li><li>liaising between Availability Management, Capacity Management, Incident Management and Problem Management to ensure that SLAs are achieved within the resources that are defined by the Business Management<br /></li><li>Provide data that will help produce and maintain a service catalog<br /></li><li>Helping to ensure that services are provided in a cost effective, secure and efficient manner<br /></li></ul><p><br /> </p><p><br /> </p></span>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com15tag:blogger.com,1999:blog-2924660267783169585.post-71794530711424549522009-01-22T21:16:00.003-05:002009-01-22T22:11:22.456-05:00BTM vs. Traditional Monitoring<span xmlns=""><p style="text-align: justify;">Business Transaction Management (BTM) is an IT systems management paradigm that seeks to manage IT from the business perspective. The transactions that Customers and Employees execute represent the Business. The IT department's number one goal is to ensure that those transactions are being executed in a timely and reliable manner. BTM solutions are able to trace the path of these business transactions throughout the Data Center, across all of the tiers, so that if something goes wrong the exact problematic location is identified instantly.<br /></p><p style="text-align: justify;"><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiETHpDhnvZSw4Zd_WGk6K-Gz5Q5WxwNgjhsZ_MS6zCVYyMwf959RF941BLfMc9i66y9wYemS3MkLIhwJVqAbqzw6Mqvdb_5IQMZ3jk7Tj7S9AWc-AqIaTdh6ACWVqQP9FZc6is3F09sOTJ/s1600-h/BTM+vs+Traditional.png"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 443px; height: 254px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiETHpDhnvZSw4Zd_WGk6K-Gz5Q5WxwNgjhsZ_MS6zCVYyMwf959RF941BLfMc9i66y9wYemS3MkLIhwJVqAbqzw6Mqvdb_5IQMZ3jk7Tj7S9AWc-AqIaTdh6ACWVqQP9FZc6is3F09sOTJ/s320/BTM+vs+Traditional.png" alt="" id="BLOGGER_PHOTO_ID_5294309289254048642" border="0" /></a> </p><p style="text-align: justify;">While traditional monitoring tools seek to monitor the health of individual components, BTM solutions monitor the organization's bottom line – the transaction. The measurement granularity of traditional tools is limited, the can only measure total resource consumption for a specific server, BTM's measurement granularity is a single event which could be a web service call, SQL statement or HTTP request.<br /></p><p style="text-align: justify;">Traditional tools monitor performance as server up time, the problem with this is that while "all lights are green" for a specific server, the transactions that are flowing through that server are not necessarily doing so in a timely manner. BTM tools monitor the performance of what really counts – the user's quality of experience.<br /></p></span>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com2tag:blogger.com,1999:blog-2924660267783169585.post-84898643107572021792009-01-16T21:01:00.002-05:002009-01-16T21:09:53.879-05:00End to End Transaction Monitoring<span xmlns=""><p>The term "end to end" - in relation to <strong>transaction </strong>monitoring is very over used. "End to end" <strong>Website monitoring</strong>, "end to end" Server <strong>performance monitoring,</strong> "End to end" Database monitoring, <strong>monitoring traffic</strong>, "end to end" <strong>Network performance</strong> monitoring; the list goes on of tools that claim to provide "end to end" monitoring solutions when in fact they only provide monitoring for one small part of the bigger picture - the diagram below explains it all.<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiJJHo975W0u_oL-m7wvwQsxf6t5jZDgVlc-tBswqc1N3YNw5u1M4PiIOeE79N3Ug2rbo5Q2094mL3DmtjWwoWWMdAFyxWsJIeOV_Rl9yUhacZO2x9xSisHc7t4mrzmonxXg9d9hiDNVU37/s1600-h/End+to+end.jpg"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 127px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiJJHo975W0u_oL-m7wvwQsxf6t5jZDgVlc-tBswqc1N3YNw5u1M4PiIOeE79N3Ug2rbo5Q2094mL3DmtjWwoWWMdAFyxWsJIeOV_Rl9yUhacZO2x9xSisHc7t4mrzmonxXg9d9hiDNVU37/s320/End+to+end.jpg" alt="" id="BLOGGER_PHOTO_ID_5292079073735463042" border="0" /></a></p><h2>Why True End to End Transaction Monitoring is Different than Monitoring Server Performance<br /></h2><p>Monitoring <strong>server performance</strong> traditionally means that you are trying to make sure that CPU utilization and memory consumption are not maxed out, ensuring that resources are not maxing out does not promise true availability of applications. Traditional "end to end" monitoring tools provide a dashboard that shows the health of each one of the individual components within the data center. But what if someone forgot to re-connect a network cable after maintenance or what if a load balancer was configured incorrectly and is not executing a proper round robin? An alert will indicate that something is wrong with the servers that are still connected when in fact the problem is that traffic is simply not being equally distributed. You could implement some sort of <strong>network performance </strong>monitoring solution which would aid by monitoring the usage of the network, but that is not a single end to end solution anymore.<br /></p><p>What if a runaway process in one server is "bombing" second server with requests? The <strong>server monitoring</strong> solution will blame the poor server that is being bombed by the server which has a runaway process running on it as opposed to indicating the source of the problem.<br /></p><h2>Real User Monitoring – An End to End Solution?<br /></h2><p>If you only take the user's tier into account, real <strong>user monitoring</strong> could be considered an end to end solution for that tier alone. You could also say that with real user monitoring you can see both ends of a transaction – hence the claim to provide "end to end". What about everything in the middle? What action is to be taken when a problem is detected by the end user experience tool? What if the root of the problem resides within the database or the mainframe? Shouldn't an end to end solution be able to take care of everything, including triage within the datacenter? <strong>Website performance monitoring</strong> is important for understanding the quality of service that your customers are receiving and there is a lot of value in that, but an end to end solution should also help you find the cause of the problem along with simply reporting its existence.<br /></p><h2>End to End Transaction Monitoring Tools Deliver<br /></h2><p>What do the following components have in common – the User Desktop, a Firewall, a Proxy, a Load Balancer, a Web Server, an Application Server, a message broker, a Database and a Mainframe? The answer is - you guessed it - transactions. The only way to provide a true end to end solution is by monitoring every transaction from the moment any user clicks any button and all the way through all of the different tiers and only <strong>business transaction management </strong>solutions can promise that.<br /></p><p><strong>Performance monitoring</strong> tools that are not showing end user performance are not focusing on what is most important to the business. <strong>Website monitoring</strong> tools that send synthetic transactions to the website and check response times are not showing what users are really experiencing or monitoring the usage of different services. Database monitoring is important but without knowing the context of that problematic <strong>SQL server transaction</strong>, resolution can be a shot in the dark.<br /></p><h2>Transaction Monitoring With Business Transaction Management<br /></h2><p>End to end solutions must be able to monitor all of the infrastructure's components. <strong>Transaction monitoring</strong> solutions do that automatically since they monitor the object that ties all of those different components together – the transactions. Business transaction management solutions enable a drill down that begins from each transaction type that is running on the system and ends with the smallest event that composes a single transaction instance. In this manner, not only are you ensuring that everything is running smoothly, but when things start to go wrong you can perform immediate triage and resolution.<br /></p></span>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com5tag:blogger.com,1999:blog-2924660267783169585.post-2703376973581502852009-01-04T12:19:00.005-05:002009-01-05T11:15:46.090-05:00Application Performance Management Solutions - Quick Tips<p class="MsoNormal">Any organization that is running business critical – time sensitive applications is in need of some sort of <b>performance management system</b>. When looking into what type of <b>performance management tool</b> to invest in - things can get confusing – surfing the web throws you into a sea of empty marketing messages. The label “<b>application performance management</b>” is vastly over used; the following article covers a few things that are not to be missed when considering an application performance management solution.</p> <h1><span style="font-size:100%;">An Application Performance Management Offering Must Include an End User Monitoring Capability</span></h1> <p class="MsoNormal">How else can you know how your application is <i>really</i> performing?</p> <p class="MsoNormal"><b>End user monitoring</b> tools provide a wonderful presentation of the bottom line of how your applications are performing. When it comes to <b>web application management </b>there is a long list of network appliances that serve the purpose - giving you a plug and play solution – with no need to install anything on the user’s desktop. But what happens when the <b>end user monitoring</b> tool that you are using for your <b>web application management</b> shows that latencies have gone wild? </p> <p class="MsoNormal">You need an <b>application performance management </b>solution that knows how to <i>connect</i> between the latencies that your users are seeing and <i>problem</i> that is causing the latency in the data center. </p><p class="MsoNormal">Now of course in these troubled times the <b>performance management system </b>that you may be looking to invest in must not eat up your entire IT budget. Purchasing more than one <b>performance management tool</b> is simply out of the question and network appliances cannot make that full connection, enabling true application performance management. </p> <h1><span style="font-size:100%;">An Application Performance Management Tool should aid with Data Center Management</span></h1> <p class="MsoNormal">Why settle for an application performance management tool that sees <i>only</i> the application server?</p> <p class="MsoNormal">True application performance management cannot be done with your run of the mill <b>server management software; </b>true <b>performance management solutions</b> offer the ability to perform <b>data center management. </b>The need for <b>application performance monitoring</b> tools to provide data center management comes from the complex, distributed and interdependent nature of applications these days. <b>Application performance monitoring</b> solutions must take into consideration the entire data center if they are to perform proper triage of a problem. A lot of <b>data center management </b>tools these days utilize information that is collected from <b>server management software</b> that is installed on various tiers, the problem with this is that you end up collecting a whole bunch of resource consumption metrics that do not correlate to what the end user sees which directly reflects your performance. Not monitoring what the end user sees means that your users could be experiencing major problems with the application which you will only hear about if those users take the time to call customer service. Since there are many cases where server management software shows that availability is fine but transactions are taking too long to process.</p> <h1><span style="font-size:100%;">Application Performance Management – Monitoring Network Performance</span></h1> <p class="MsoNormal">What is your application without the network that it is sitting on?</p> <p class="MsoNormal"><b>Monitoring network performance</b> also plays a role in application performance management. Imagine that your end user monitoring tool shows that latencies are too high while the latencies that you measure within your application server are only a small percentage of the total latency that your users are seeing. Only by <b>monitoring</b> <b>network</b> <b>performance</b> will your application performance management tool provide the <b>performance management solution</b> that will cover all of your bases. </p> <h1><span style="font-size:100%;">Only Business Transaction Management Provides the Single Solution</span></h1> <p class="MsoNormal">Monitoring every single transaction from the end user - through the network and all the way to the back end of the data center is the only way for an application performance management solution to cover all of the bases that are listed above. The discipline of doing this is called Business Transaction Management or BTM.</p>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com4tag:blogger.com,1999:blog-2924660267783169585.post-62817215281643815662008-12-24T07:40:00.002-05:002008-12-24T07:42:41.962-05:00Business Transaction Management in the News<span xmlns=""><p>As you may or may not know, many of the major Transaction Monitoring players have their R&D centers based in Israel; Correlsense, Optier, Correlix and B-Hive. Considering the important role that "hi-tech" plays in the Israeli economy, it is no surprise that financial publications publish technology related articles on a regular basis; I have taken the liberty to translate parts of a recent article that was published in "<a href="http://www.globes.co.il/news/article.aspx?did=1000405566&fid=594"><span style="font-family:Georgia;">Globes</span></a> Israel".<br /></p><h1>"After evaluating both Correlsense and Optier; we have decided to invest in Correlsense"</h1><p>The article talks about how the IT systems management world is currently going through some "tectonic movements" and that the companies that emerge once the dust clears will have a pivotal role in the market. Similarly, there are forces which are acting on the enterprise computing world in general - virtualization, the large growth in the availability of information and applications within the organization and outside of it and of course, the constant need to reduce operational costs – that are causing executives to think differently.<br /></p><p>There are a number of Israeli companies who are in this position; Optier is an example of a company that is trying to become a big player in the IT systems management market. This is also the case with Correlsense, says Sam Somech. Somech is an Angel that invested in Correlsense, along with the VC firm eXeed, and is now serving as the company's chairman of the board.<br /></p><p>Both Correlsense and Optier have developed technologies for the troubleshooting and optimization of data centers, with the belief that the best way to deal with the complexities of the modern data center is by tracking transactions from the user, through the data center and all the way to the back end data bases.<br /></p><h2>"The surviving company will have a high value"<br /></h2><p>According to the evaluation of Correlsense's investors and founders, the leading IT systems management companies – IBM, HP, BMC, CA or Microsoft – do not have this kind of technology yet. "We evaluated the two companies - Optier and Correlsense", Says Somech, "and in our opinion Correlsense's technology is favorable". Optier had no comment.<br /></p><p>Despite the uncertainties, "if a start-up can provide real innovation that will give it the edge in a sale, then it has what to offer the market", says Somech. "The technological gap between what IBM has to offer in relation to Correlsense is large. In this world, he who has the faster, more economical offering is at an advantage. It is not likely that the companies in the market today [the big four] are going to be able to invest heavily in R&D, they have also been affected [by the financial situation] and they are not going to invest tens of millions of dollars when they do not know what will come out of them. Therefore the start-up companies that will survive this downturn will have a high value".<br /></p><p>With all due respect to Mr. Somech, the IT systems management market will not wait for Correlsense or even Optier. The Gartner Analyst, Will Cappelli for instance told "Globes" at the beginning of the year that Optier will eventually have to find itself as part of a larger company that will acquire it. Even BMC CEO, Bob Beauchamp advises the companies that are active in the field to go for acquisition, as it is a mature field with no room for niche solutions.<br /></p><h2>"We don't want to cut our valuation"<br /></h2><p>"The transaction monitoring market is not mature, it's just starting", replies Somech. Oren Elias, CEO and founder of Correlsense, says "transaction management is a big leap forward. Therefore, in times like these when the "big four" are investing less [in R&D], there is an opportunity for a new corporation to rise up and take business even from the "big four"".<br /></p><p>There are a number of players in the IT Systems Management field and the Israeli ones among them especially stand out; Optier, Correlsense, Precise, B-Hive and Correlix. Elias and Somech are convinced that their solution is unique. "The only companies that built their transaction monitoring technologies from scratch are Correlsense and Optier", they claim.<br /></p><p>In order to turn into one of the hottest names in software in the world, Optier has raised $116M. Correlsense, still at the beginning of their route, has been satisfied by their $1.5M round that was completed half a year ago from eXeed, Vertex and Proseed and is now in the process of raising a few more million.<br /></p><p>"We believe in the company, it's not a good idea for us to go for additional external funding at this point, we don't want to cut our valuation. I think that it is going to be a good investment for our firm, because of the advanced technology. We are looking for just enough money to keep the company going for the next two years at which point the market is going to look much different. At this point there isn't a lot of competition".<br /></p></span>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com5tag:blogger.com,1999:blog-2924660267783169585.post-11495436830590058882008-12-14T11:28:00.002-05:002008-12-14T11:35:15.552-05:00Business Transaction Management’s Challenges<div>Business Transaction Management (BTM) is a natural continuation of the past decade and a half's evolution of IT systems management. In the past few years the modern data center has finally started to stabilize; the number of node types has become constant and each node has had tools developed for it.<br /></div><p>These silo specific tools are now able to solve 90% of the problems; leaving us with the hardest to solve - last ten percent. This last ten percent is characterized, for example, by those application bottlenecks that occur even though all of the silo specific tools are showing 100% availability.<br /></p><p>If the monitoring tools at all tiers are showing 100% availability then how does one know that there is a problem? Well, either the enterprise has put in place an end user measurement tool or the help desk is receiving user complaints.<br /></p><p>The IT organization's number one priority is very simple; <strong>ensure that all transactions are executing correctly and in a timely manner </strong>– it's that simple.<br /></p><p>The <em>demand</em> for Business Transaction Management tools comes from the need fulfill that priority; especially when traditional tools are unable to go that last mile. What has <em>enabled</em> the development of these Business Transaction Management tools is the datacenter's recent stabilization; with the number of node types staying constant for a few years, it is finally possible to catch up and enable the full visibility into the entire datacenter that BTM solutions must provide.<br /></p><h2>BTM Enables True Availability<br /></h2><p>The only way to resolve the problems that traditional monitoring tools cannot cope with is to take into account the interactions between the nodes and to connect every click of the user to the many events that are triggered by that activation. This enables both being able to see everything in the business context - the user's click of a button - and solving problems that have more than one source.<br /></p><p>Business Transaction Management tools are able to monitor the entire system by tracking every single transaction that is activated by the users throughout the entire datacenter, collecting information on all of the interactions along the way. This is the essence of connecting business and IT; understanding the business context by linking every single event in the datacenter to the click of a user.<br /></p><p>With Business Transaction Management, a common language is created, where performance can be measured as the time it takes for the transaction to travel between all of the nodes and back. Since all interactions are recorded along the way, if something goes wrong, i.e. a latency that is out of specification, then the event that caused the problem can be immediately singled out since the latencies at each tier are known and all of the necessary data has been collected. </p><h2>What Qualifies as a BTM Solution?<br /></h2><p>Every Business Transaction Management solution should be able to do the following:<br /></p><p>Track a transaction that was sent out from a browser, through a load balancer and to a proxy. This proxy is not a known vendor's proxy, just some start-up's which developed the proxy five years ago - the code is still there and still working, but no one has the code - just the binary.<br /></p><p>That proxy is sending it to another proxy and its being split to - making it easy - two different applications, each with its own different web server. Each application is running on its own app server - one is java based, the other is not; it's a homegrown C++ program. The first app server is sending out data base requests to four different databases; Oracle, DB2, Sybase and SQL server. The second app server is SOAP based; sending SOAP requests to an external application. There is an MQ at the external application, 'puts' are being sent to the MQ and a Mainframe is receiving the messages from the MQ. </p><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlmY5Ef0T1lq2tfGwDdnwGN4mzjEa8wL-44Uz6ty-xvHKNkoC7lyGjzB9TNCndsaMOuIYSnaeRUZSyWpzTBfMYf484-afhnkCR5KXL3hCsIM28eRUhnNtNcuo8rsEERTYtZJuBRZJwAhfg/s1600-h/BTM+challenge.JPG"><img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 244px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlmY5Ef0T1lq2tfGwDdnwGN4mzjEa8wL-44Uz6ty-xvHKNkoC7lyGjzB9TNCndsaMOuIYSnaeRUZSyWpzTBfMYf484-afhnkCR5KXL3hCsIM28eRUhnNtNcuo8rsEERTYtZJuBRZJwAhfg/s320/BTM+challenge.JPG" border="0" alt="" id="BLOGGER_PHOTO_ID_5279684972189990770" /></a><span xmlns=""><p>If a vendor wants to be called a BTM vendor he has to be able to track the transaction across all of these components. He has to be able to account for the time every transaction spends at every point in the datacenter.<br /></p><h2>Developing a Business Transaction Management Solution<br /></h2><p>Developing this kind of solution is far from trivial. The task of connecting each event within the datacenter to a specific transaction is a big challenge in today's distributed and heterogeneous systems.<br /></p><p>The general concept of how to execute a Business Transaction Management solution is pretty straight forward. Agents must be installed at all tiers, collecting information about everything that flows through that particular tier and all of the collected data is sent back to a central dedicated server that is able to correlate all of the events to the single user's click of a button in the application. The various methods of gluing these events together are the core competency of the solution, along with the ability to develop an agent that complies with all of the different kinds of servers that one finds in the data center.<br /></p><p>Some big players have been claiming to provide these end-to-end solutions for a number of years. Only recently have an extremely limited number of vendors been able to prove Business Transaction Management solutions in production – buyers beware.<br /></p></span>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com1tag:blogger.com,1999:blog-2924660267783169585.post-88365818392236418482008-12-09T13:40:00.007-05:002008-12-09T13:59:51.631-05:00CMG '08 Exhibition Photos<div>Here are some photos of the exhibition area right before opening:<br /></div><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjFedEUmc4c6zB_9AfpF6mIx_tKXLHR8p00NAbGBLQpW-RXRilsDoSf1i4Bg1W2H5eVqXjHXoAG5jaXNnvcVjlt8zu5GiIF3nDqyMiPnFfBpXmwSXdv2_BU9sVd_g_OU0GAZqvB_WXJwWo0/s1600-h/IMG_0061.JPG"><img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 240px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjFedEUmc4c6zB_9AfpF6mIx_tKXLHR8p00NAbGBLQpW-RXRilsDoSf1i4Bg1W2H5eVqXjHXoAG5jaXNnvcVjlt8zu5GiIF3nDqyMiPnFfBpXmwSXdv2_BU9sVd_g_OU0GAZqvB_WXJwWo0/s320/IMG_0061.JPG" border="0" alt="" id="BLOGGER_PHOTO_ID_5277866634586101778" /></a><div><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi5B2_BjHMtf4__rUaWWHgtTYGeCRxUM5M5Xppbesv8XuUcbCiH3VSTsr7rmnhp8MysqbpZoZY3i7DI1Q-ann8jkh8dhHhqTbH47YBVkmI3jT4HlERFeAYHlyX3cHcRKbs_70rG73pjqr0Y/s1600-h/IMG_0059.JPG"><img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 240px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi5B2_BjHMtf4__rUaWWHgtTYGeCRxUM5M5Xppbesv8XuUcbCiH3VSTsr7rmnhp8MysqbpZoZY3i7DI1Q-ann8jkh8dhHhqTbH47YBVkmI3jT4HlERFeAYHlyX3cHcRKbs_70rG73pjqr0Y/s320/IMG_0059.JPG" border="0" alt="" id="BLOGGER_PHOTO_ID_5277866011517484930" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiRG0YtSYmSGNjIc4q6PodPROTZUpYwkAJj-pcw_u7cVX2oGXsDvHa1dGGCLfyAZM6f9ZNZPgW-pc3CvJKdkM4ldcuGmE-OXPIkxhB21qEJoANztUIy5nIMsbRBewBlH_Rze8wrHK6TX4em/s1600-h/IMG_0058.JPG"><img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 240px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiRG0YtSYmSGNjIc4q6PodPROTZUpYwkAJj-pcw_u7cVX2oGXsDvHa1dGGCLfyAZM6f9ZNZPgW-pc3CvJKdkM4ldcuGmE-OXPIkxhB21qEJoANztUIy5nIMsbRBewBlH_Rze8wrHK6TX4em/s320/IMG_0058.JPG" border="0" alt="" id="BLOGGER_PHOTO_ID_5277865755146518210" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgqZ91Sw5-99aj_MU4GL3OZ0B3s5KWdmjg50CY6x7NX1i8raZ-sHiVPZJ-BKqU9jFxabPUnBWdXYb4BJVMdyHrhruQL7Ihxf5BPMAEq562R5ZrjawrI0uQgYJHd1OxuFprydJKwWJaqg_-F/s1600-h/IMG_0056.JPG"><img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 240px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgqZ91Sw5-99aj_MU4GL3OZ0B3s5KWdmjg50CY6x7NX1i8raZ-sHiVPZJ-BKqU9jFxabPUnBWdXYb4BJVMdyHrhruQL7Ihxf5BPMAEq562R5ZrjawrI0uQgYJHd1OxuFprydJKwWJaqg_-F/s320/IMG_0056.JPG" border="0" alt="" id="BLOGGER_PHOTO_ID_5277864868179749762" /></a><br /><div><br /></div><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj0A58atN3e5jLbGVo1HMHEOXcvQz57S-2rMR_nWRhVHl-mta_QJA36d93X06pcFUkRgmKWaLglZg1lfy5y_mkIkYktFfKk9RUgK_RKio30kg1kCO_39i2r_o5DaNEDu7dY4R6se2Xws_BO/s1600-h/IMG_0055.JPG"><br /><img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 240px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj0A58atN3e5jLbGVo1HMHEOXcvQz57S-2rMR_nWRhVHl-mta_QJA36d93X06pcFUkRgmKWaLglZg1lfy5y_mkIkYktFfKk9RUgK_RKio30kg1kCO_39i2r_o5DaNEDu7dY4R6se2Xws_BO/s320/IMG_0055.JPG" border="0" alt="" id="BLOGGER_PHOTO_ID_5277864364524963474" /></a><div><div style="text-align: center;"><br /></div><div><span class="Apple-style-span" style="color: rgb(0, 0, 238); text-decoration: underline;"><br /></span><br /><br /><div><br /></div></div></div></div>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com0tag:blogger.com,1999:blog-2924660267783169585.post-59487773701684080132008-12-06T07:29:00.001-05:002008-12-06T07:29:03.622-05:00G4 IT Systems Management is Here<span xmlns=''><p>Information Technology contributes to the efficiency of the human race like nothing else. Keeping up with the management of complex IT systems requires constant innovation; <strong>systems management</strong> has come a long way since the days of "big iron". The fourth generation of <strong>systems management</strong>, widely referred to as "end to end transaction management", enables IT to reach levels of maturity and stability like never before.<br /></p><h2>Mainframe Systems Management – G1<br /></h2><p>The Birth of <strong>application performance management</strong> tools came with the development of the Mainframe Omegamon and Tmon; these tools monitor program names, Customer Information Control System (CICS) jobs and Job Control Language (JCL) tickets. As far as <strong>application performance management</strong> goes, this was really the first <strong>transaction performance management</strong> solution; where everything was centered on the mainframe.<br /></p><h2>Client/Server – SQL Management – G2<br /></h2><p>Next up was the client/server; back then, your server was essentially the database, the database was the single point of failure, it became the place where all of the data was stored and SQL queries were everything. If you had a problematic SQL query then you had a slow transaction. <br /></p><p>That is really when the true <strong>application performance management</strong> market emerged; with companies like Precise and Quest. The first tools for Data Base monitoring utilized the SQL command line to extract system information. These first <strong>application performance management</strong> vendors built smart agents that would collect all of the information all of the time and sometimes it actually worked in production. These <strong>application performance management</strong> tools had a nice (relative to the time) dashboard and suddenly you had this sexy, easy to work with tool for optimizing your database, DBAs finally had something to work with that gave them value. This was all around 1997, when Windows 95 was just becoming stable. <br /></p><h2>J2EE Profilers and the User Experience – G3<br /></h2><p>G3 is the generation that is currently coming to a close, as will be explained. This generation began with the emergence of <strong>Java Application Servers</strong>, Java's rise within large organizations was seen in 1999-2002, suddenly a lot of application vendors started working with Java, they built these applications and started selling them to enterprises and suddenly you had <strong>Java Application Servers</strong> everywhere. This brought on a whole new black box that needed a tool that could manage its performance – that tool, <strong>Java profilers</strong>, were brought on by Wily, BMC and others. <br /></p><p>At the same time, with the dot com bubble, it became important to track <strong>user experience</strong>; your website was suddenly your business. With the website so critical to doing business, it was important to make sure that things were performing as expected; running <strong>synthetic transactions</strong> with Gomez, Mercury Topaz, and others in order to ensure availability was the way to do it. <br /></p><p>Alongside the JVM profilers and user experience tools, there were always network probes that made sure that the network was working. As TCP/IP became the standard, you had solutions that were parsing and sniffing these protocols, parsing network traffic in order to monitor network performance. <br /></p><h2>What Marks the End of 3G Systems Management?<br /></h2><p>In the last couple of years the last two major silos that we have not yet listed; Middleware and Storage, have had tools developed for them. For example; companies like Onaro (acquired by NetApp) developed tools that extended <strong>application performance management</strong> into the storage tier (Application Insight) and MQSoftware. Today, every silo has its <strong>performance management tool</strong>, all with the objective of achieving greater <strong>application performance</strong>.<br /></p><p>All of this happened over the past 5-6 years; every single silo was developed on its own and was embraced by the industry. What we see happening in the past two years is some kind of stability, we do see new concepts for application servers, other languages - not just java based, and we see a lot of integration - <strong>web services</strong> is the new buzz word - really it's just an easy way to do integration (enterprises where doing http based xml ten years ago). All of these changes not withstanding; you do not see new silos. You do see more and more silos, but not different types of silos. <br /></p><h2>Stability & Maturity => 4G (End to End)<br /></h2><p>The market has matured to a level where you can deploy <strong>end to end solutions</strong>, if you would have tried a few years ago you would have run into complications, right now there is enough stability in new technology as far as <strong>enterprise applications</strong> are concerned in order to enable the proliferation of <strong>end to end management</strong>. Of course there is always constant change and progress in things like storage and network throughput, these technologies will continue to move forward but the technology for tracking a transaction is here to stay for the foreseeable future. TCP/IP is going to stay with us for the next 10-20 years, HTTP protocols aren't going to change in the next 5-10 years, Java will not go away as an application server, there will be new methods for <em>implementing</em> an application server - it will not necessarily be JVM it could be a new process – but eventually it's going to be some sort of process, multi threaded or not, which will handle the transaction. The overall architecture of the application is going to stay more or less the same; a rich, mixed and complex topology that is hard enough to manage as it is. This maturity is exactly what is enabling <strong>transaction management</strong> to become the fourth generation of <strong>IT systems management.<br /></strong></p><h2>4G Systems Management – Bringing IT all together<br /></h2><p>Forget the buzz words for a moment - <strong>Business Service Management</strong>, <strong>Business Transaction Management</strong>, Service Level Management and others - what we are talking about here is the evolution of IT systems management itself - which is defined as everything that is needed in order to make the IT data center work. Transaction management is going to compose 70% of the systems management space – it will be critical (and already is) in making sure that your datacenter actually works.<br /></p><p>A big thanks to <a href='http://www.dougmcclure.net'>Doug McClure</a> of for creating an informative podcast with Lanir Shacham from which the ideas for this article were taken. Take time to listen to Doug's Podcast which aims to shed light on the next generation of IT systems management.<br /></p></span>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com0tag:blogger.com,1999:blog-2924660267783169585.post-74406765484086234392008-11-28T22:10:00.002-05:002008-11-28T22:33:59.409-05:00Linking Business to IT<span xmlns=""><p><span style="font-family:Verdana;">You may have heard recently about the new paradigm of managing your IT by <em>linking</em> it to your Business. The first question that arises when one first hears of this statement is; what do you mean? My IT infrastructure <em>is</em> part of my business; it is integral to it. What is the meaning of linking my IT to my Business?<br /></span></p><p><strong><span style=" ;font-family:Cambria;font-size:13pt;color:#4f81bd;">Business Transaction Management – The Link</span><span style=" ;font-family:Verdana;font-size:18pt;"><br /> </span></strong></p><p><span style="font-family:Verdana;">What is your IT essentially? It is an infrastructure of hardware components that interact in order to provide a service or application to your users, those users are either paying customers or employees who in turn provide services or products to paying customers. Those users are the business, they are the source of revenue that enables the business to thrive or dwindle.<br /></span></p><p><span style="font-family:Verdana;"><strong>Business Transaction Management</strong> solutions provide the <strong>link</strong> between all of those <strong>processes and interactions</strong> that run throughout your IT and the business' source of income, the individual <strong>transaction activations</strong>.<br /></span></p><p><span style="font-family:Verdana;">How does <strong>Business Transaction Management</strong> do this? The <strong>concept</strong> is <strong>simple</strong>, but the <strong>means </strong>have been <strong>sought after</strong> for many years (and have finally been realized). Every single piece of data that enters or leaves every single server, along with the resource consumption of every process in every server is linked back to a transaction activation. In this manner, not only can you connect between the different "dots" within your data center, but you can connect to the most important dot of them all, the User.<br /></span></p><p><span style="font-family:Verdana;">Any problem that arises within the system will always be identified by the user (unless it is a false alarm), with the power to "connect between the dots" and see every parameter and statement within its business context (the transaction activation) resolution of problems becomes child's play.<br /></span></p><p><span style="font-family:Verdana;">The following video gives a clear view of the importance of <strong>Business Transaction Management</strong> and its ability to link Business and IT:<br /></span></p><p><span class="Apple-style-span" style="font-family: Verdana;"><br /></span></p></span><iframe allowfullscreen='allowfullscreen' webkitallowfullscreen='webkitallowfullscreen' mozallowfullscreen='mozallowfullscreen' width='320' height='266' src='https://www.blogger.com/video.g?token=AD6v5dzzWyokZN9Q1qB43KHoPa9F55c6tk8cdmMKIA2lo-E3s03FXBbvspG7rq8Dj3a4ZxTCLJDfTbDpRLVrH82nZw' class='b-hbp-video b-uploaded' frameborder='0'></iframe>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com2tag:blogger.com,1999:blog-2924660267783169585.post-33892585267022179332008-11-12T10:38:00.001-05:002008-11-12T10:39:18.767-05:00The BTM Business Case for Retailers<span xmlns=''><p>Convincing retailers to invest in Business Transaction Management is a big challenge. <br /></p><ul><li>The margins in retail are rather slim<br /></li><li>The impact of a single transaction is low (compared to the Finance Industry for instance)<br /></li><li>Competition is fierce due to today's retail search engine proliferation<br /></li><li>Expanding into online sales has been enough of a challenge as it is<br /></li><li>ROI has to be clearly shown in order to justify the investment<br /></li></ul><p>I have taken the liberty to try and come up with a business case for why retailers should consider a BTM solution; I truly believe that those that will take the step will find it hard to understand how they lived without Business Transaction Management. How can you run a business that is so transaction dependant and not be able to make the connection between business and IT?<br /></p><p>Figures for this case study have been inspired by Aberdeen Research's well cited APM study from June 2008 (available for free). I had a tough time finding any analysts, or vendors that published concrete numbers on the retail industry. If you have seen anything, please let me know.<br /></p><h1>ROI case for Business Transaction Management<br /></h1><p>A large retail company with an annual revenue of $563M in both online sales (30%) and through its chain of nationwide stores was unsatisfied with the performance of the business critical applications they were using. They were unable to identify issues before they impacted end users, their applications were increasing in complexity, and they were unable to test the performance of their applications whose development had recently been moved offshore.<br /></p><p> Growth in their online division had forced them to rapidly increase capacity over the past few years and now they were stuck in a situation where they had very heterogeneous infrastructure, from the old legacy systems that they had implemented in the early nineties, to their newer SOA based applications, things were such a mess, that they were estimating that IT employees were spending 30% of their time just searching for the cause of the problems, let alone resolving them. The Retailer had also estimated a 5-7% revenue loss due not only to their customer facing web applications, but also due to productivity issues with their CRM and ERP applications. They also calculated total downtime cost per hour to be $80,000.<br /></p><p>In order to increase productivity, customer satisfaction, brand image, and to reduce the lost revenue opportunities (in online sales) the Retailer had come to the conclusion that the monitoring tools that they had implemented for each one of their components was not enough, and that it was time to invest in a business transaction management tool. They were looking for a tool that would give them an understanding of the business context of their problems. They needed a single solution that would work for both production and pre-production testing in a way that developers could gain visibility into the interactions between their different applications. Their current tools were retrieving large amounts of data at every node, but the information was useless when it came to increasing productivity and sales, they needed something that would provide visibility across their entire infrastructure. Most importantly they didn't have time to waste weeks or months in order to implement one of the solutions provided by the larger vendors, and didn't want to have professional services people modifying their code. They wanted to go with a solution that was not service intensive, and wouldn't cost them an arm and a leg, due to the tight margins that the retail industry was as a result of a tightening economy and rising fuel costs.<br /></p><p>For all of the reasons stated above, the Retailer should go with a Business Transaction Management Solution. In order to justify this claim, the following presents a hypothetical continuation to this case.<br /></p><p>The organization had requested an initial BTM POC for their online division, in order to better understand the potential ROI that could be yielded from increased sales revenue which is easier to quantify, unlike increased employee productivity and mean time to repair which is tougher to justify. <br /></p><p>On the first day of the POC, the BTM agents were already in place and transactions were being monitored from the user end all the way through the webservers, app servers and to the legacy back end. The value became clear immediately, during peak hours, numerous transactions had been taking much too long. The retailer had always wondered why it was experiencing a high number of abandoned shopping carts online. One guess was that users that were shopping the popular search engines ended up opting for competitors that were able to be more responsive to customers. Not only that, various members of the IT department were able to connect the dots on many of the performance problems that they were experiencing and resolve them immediately.<br /></p><p> A full installation was put into place and suddenly issues with the application's performance could be pinpointed immediately without the need to perform long grueling meetings between the IT department's professionals. In the first few months of using their BTM solution, a steady decrease in empty shopping carts could be charted. They were able to achieve a 600% average improvement for response times on business critical transactions. Developers were very satisfied to have a solution that they could directly log on, test the changes and gain immediate insight as to how the overall application performance had been affected. The MTTR was decreased and problems could be spotted proactively before they reached the customer at an 85% improved success rate.<br /></p><p> Since then, the retailer has expanded the scope of their BTM solution to include its internal applications. They were able to raise employee productivity since they saw an average improvement of application availability of 80%, and best of all, IT headcount, did not have to be increased. The Retailer has also been able to increase capacity exactly where it needs it; the justification for increased capacity becomes easy when IT problems are put in the business context.<span style='font-size:10pt'><br /> </span></p><p>If you can think of any way to make this study more robust, please write!</p></span>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com0tag:blogger.com,1999:blog-2924660267783169585.post-53313271881780024842008-11-08T09:06:00.001-05:002008-11-08T09:06:38.329-05:00Transaction Monitoring – Network Appliances<span xmlns=''><p>Yet another way to implement Transaction Monitoring solutions is via a Network Appliance. This approach is defined here as any approach that collects data by non intrusive "Network Sniffing". Two good examples of vendors that provide this type of solution are B-Hive and Correlix. <br /></p><h3>How it Works<br /></h3><p>Network appliance solutions usually connect to a port mirror in order to collect the traffic, and then try and re-construct the entire transaction. Information needs to be collected directly from every node that is of interest.<br /></p><h3>Applications<br /></h3><ul><li>Any application where transaction latencies need to be monitored in a production environment<br /></li><li>Managing SLAs<br /></li><li>Systems which cannot be tempered with at all and need a "plug and play" solution <br /></li></ul><h3>Advantages<br /></h3><ul><li>Zero Overhead<br /></li><li>Full time monitoring<br /></li><li>Immediate installation<br /></li><li>Instillation only concerns the network administrator<br /></li><li>There is no risk of crashing the system ( <em>some </em>"Deep Dive" solutions will cause system failure if they are used to monitor too many transaction due to high overhead)<br /></li></ul><h3>Drawbacks<br /></h3><ul><li>Uses an algorithmic approach to track transactions which limits accuracy of metrics, latencies are not right, you do not know the accurate flow of the transaction through different tiers and so on.<br /></li><li>Tracking is not really end-to-end since you cannot see what is actually happening within the servers (cannot achieve full visibility)<br /></li><li>Even if you collect data from all nodes, correlating that data into a single transaction path (or topology of the entire transaction) accurately has yet to be done (if you can give a concrete example, then let me know and I will post it)<br /></li><li>Receiving data at the network level makes measuring encrypted data close to impossible <br /></li><li>Once an event has begun processing, it cannot be controlled (say for resource allocation purposes) <br /></li></ul><h2>Disclaimer<br /></h2><p>When trying to give an understanding of a general approach to a solution, all potential advantages and <em>drawbacks</em> (which people who develop or promote the specific solution would prefer to ignore) are listed. Comment with any objections (as people have done in the past) and I will at some point post everything.</p></span>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com7tag:blogger.com,1999:blog-2924660267783169585.post-54237861583760666672008-11-05T13:25:00.002-05:002008-11-08T08:12:23.805-05:00Business Transaction Tracing – BTM’s Unused Synonym<span xmlns=""><p>Let us start off by thanking all of those that contributed their very informative comments on the last post - <a href="http://businesstransactionmanagement.blogspot.com/2008/11/transaction-management-and-deep-dive.html">Transaction Management and "Deep Dive" Java/.NET Profilers</a>. It is great to have feedback from CA Wily, Dynatrace and Jinspired, the objective of this blog is to raise awareness about Business Transaction Management and to set any myths or rumors right, so keep those comments coming.<br /></p><h1>Gartner's Definition of Business Transaction Tracing<br /></h1><p>One definition that was left out of the <a href="http://businesstransactionmanagement.blogspot.com/2008/10/definition-of-business-transaction.html">Business Transaction Management Definition</a> post was Gartner's.<br /></p><p>In their white paper titled "<a href="http://www.gartner.com/DisplayDocument?doc_cd=153398">The Four Dimensions of <strong>Application Performance Monitoring</strong>"</a> Gartner labels "Business Transaction Flow Tracing" as one of the four "functionalities have emerged to circumvent some of the APM difficulties associated with modular, distributed, interdependent and context-sensitive applications".<br /></p><p>Will Cappelli leads off the definition by stating how when a problem with the availability of an application pops up, monitoring component-level health is less helpful when it comes to determining the root cause, and "Used in conjunction with an application dependency map, a report showing a cluster of component latency degradations could be used to guess at the source of the performance issue. More often than not, an insufficient number of components are instrumented and/or the topology plus performance degradation is too ambiguous to be helpful."<br /></p><p>Mr. Cappelli then continues to state that Business Transaction Tracing fills the Application Performance Management void that simply monitoring component-level health leaves by following these steps:<br /></p><ul><li>"First, members of the operations or application support team would be required to instrument path-critical components in the stack and infrastructure, supporting the application being monitored with what amount to sensors."<br /></li><li>"Second, they must define, package and mark a sequence of interactions at an application's interface — defined as a "<strong>business transaction</strong>." An instance is executed and the mark is passed through the application's components as it is exercised and sensed, and progress of its path is reported on in real time or near real time. This makes it possible to trace a performance problem's root cause, particularly when used in conjunction with health statistics gathered by the third type of <strong>APM</strong> functionality."<br /></li><li>"Finally, it would, once again, be prohibitive to place sensors on more than a few components. Thus, having a <strong>good application dependency map</strong> is critical to the effective deployment of this type of <strong>APM</strong> functionality."<br /></li></ul><p>Once again, this is not a clear cut definition of Business Transaction Management, but another thing to think about when attempting to provide a definition.<br /></p><h1>What is Business Transaction Management?<br /></h1><p>Please help define Business Transaction Management – post your comment!<br /></p></span>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com4tag:blogger.com,1999:blog-2924660267783169585.post-42439819017556253202008-11-01T22:29:00.002-04:002008-11-01T22:32:28.656-04:00Transaction Management and “Deep Dive” Java/.NET Profilers<span xmlns=""><p>When an Enterprise finally gets the wakeup call when their applications are performing under par they start looking into <strong>Transaction Monitoring</strong> (or Transaction Tracking/Tracing) solutions. One type of solution is the <strong>"Deep Dive"</strong> Java/.NET solution which is defined as <span style=" ;font-family:Arial;font-size:10pt;">those solutions that use <strong>Bytecode Instrumentations</strong> (or Java/.NET Hooks) in order to collect thorough code level<strong><br /> </strong>metrics for J2EE/.NET experts. These Application Performance Management solutions are used throughout the entire lifecycle of the product; they are a strong tool for the developer, but a very weak tool for the production environment since they are unable to monitor all of the transactions on all tiers all the time due to very <strong>high overhead</strong>.<br /></span></p><h2>Who Offers These Solutions?<br /></h2><p>These solutions tend to be offered by the larger corporations:<br /></p><ul><li>CA Wily – Introscope<br /></li><li>HP – TransactionVision<br /></li><li>BMC – Application Problem Resolution (Identify)<br /></li><li>Dynatrace – PurePath<br /></li><li>Precise – APM<br /></li></ul><h2>Overview<br /></h2><p>These tools provide deep diagnostics into <strong>Java/.NET applications</strong> – to the code level. They are used by J2EE/.NET <strong>experts</strong> in order to locate problems before deployment. These solutions are too low level for use by most operations teams and system administrators as they extract a glut of data and do not enable a high level view of the system, on the other hand, application teams rely on them for development, and they can be use in production to a certain extent in order to monitor synthetic transactions or a small percentage of the real transactions that are flowing through the system.<br /></p><h2>How they Work<br /></h2><p>Bytecode Instrumentations (or Java hooks) retrieve data from the nodes that are running J2EE/.NET applications. This is done by utilizing the class loading mechanism of the interpreter (JVM for J2EE or CLR for .NET) that in order to intercept specific classes or <strong>method calls</strong> within the application. <br /></p><h2>Applications<br /></h2><ul><li>Gives J2EE/.NET experts insight into where the problems are<br /></li><li>Used mainly in the development phase and pre-deployment<br /></li><li>Can be used in production for a few percent of the transactions<br /></li></ul><h2>Advantages<br /></h2><ul><li>Gives <strong>developers</strong> deep insight into problems at the source code transaction data level<br /></li><li>With the help of synthetic transactions, <strong>deep diagnostics</strong> can be performed during production<br /></li><li>You can get a <strong>full method call</strong>, similar to a debugger<br /></li></ul><h2>Drawbacks<br /></h2><ul><li>Lengthy Implementation<br /></li><li>Only works with certain environments<br /></li><li>Cannot trace all transactions in real time<br /></li><li>Not recommended for the production environment<br /></li><li>Difficult for IT support staff to use<br /></li><li>It only helps with Java or .NET<br /></li><li>The solutions are not designed for a high level production view, they do not provide an extensive topology of the system<br /></li><li>Lots of detailed data is collected. application owners and system administrators do not always know what to do with all of the information<br /></li></ul><h2>Business Transaction Management<br /></h2><p>Although the list of drawbacks is long, the objective of this article is not to bash on this kind of solution (really, they will do wonders for your application development team), it is simply to help you understand that if you are looking for a solution that will cover all of your bases during production; these kinds of solutions won't cut it (they provide up to 10% sampling for limited periods of time). These solutions cannot monitor the entire topology of each transaction even though they claim to be end to end, these traits are by design, and no amount of marketing hype will enable these products to solve all of your problems as they claim to do.<br /></p></span>Business Transaction Managementhttp://www.blogger.com/profile/15913359021951098603noreply@blogger.com11