You’ve probably seen the buzz on social media about the completely revamped Tealeaf 9.0. Perhaps you’re wistfully looking at the bottom of your browser where it shows that you’re still running Tealeaf 7.2 or earlier but know that upgrading the system is quite the undertaking. Not that you shouldn’t upgrade; you’ll love the way you can slice and dice data with dimensions, but setting up those new reports is no small task.
Success with Tealeaf in 2015.
Think about it, wouldn’t it be a great goal for 2015 to refresh Tealeaf, utilizing the advanced event and reporting that come with it to achieve your business objectives? Maybe your employer’s fiscal year is the same as the calendar year; there’s probably still time to get it into the budget. Let’s be honest, though - your servers are chugging along, serving up 7.2 and might not be adequate to run the upgraded version of Tealeaf. If you’re running SQL 2005 you’ll definitely need to replace that with a newer, supported version of Microsoft SQL.
Chances are good that Tealeaf isn’t the only thing you’re responsible for– maybe you don’t have the time to go through the entire planning and sizing cycle, much less actually executing the upgrade. By partnering with Stratigent, you’ll have access to experienced consultants who can translate IBM’s sizing recommendation into your server environment. We can write your upgrade plan and assist with translating that plan into bite-sized pieces suitable for your change control process. Then there’s the buzz in the media about a Microsoft patch breaking TMS and browscap.csv not being compatible with the new version. Our team has seen it all and can help provide solutions for any issue, which we will outline some of these throughout this post.
A Tealeaf 9.0 upgrade isn’t all dimensions and roses, however (well, the dimensions are there). You’ve probably seen the foreshadowing of the Microsoft patch breaking TMS. If you’ve been a Tealeaf administrator or manager for any length of time, I’m quite certain you’ve seen the security scan FAIL items for the self-signed certificates that are baked into the software. I don’t know that IBM should really be faulted for the browscap issue, though. Browscap was one of those free, open source projects and was minimally supported by the industry – although liberally used. There’s something of a parallel in the OpenSSL/Heartbleed story.
There is no denying, however, that it might have been a better use of Big Blue’s time to create a mechanism whereby customers could insert their own certificates that would pass the scans! While we can’t provide a patch, we can surely help you work around it.
There are Tealeaf Experts out there.
Your application development team may have already made their QA environments effectively invisible to 7.2 by moving into a virtualized cloud environment like Amazon. Did you know that Tealeaf 9 supports cloud based capture? Ok, you probably did – but did you also know that Stratigent has deployed it for clients? We have experience implementing Tealeaf 9 in the Amazon cloud and would be more than happy to share our expertise to help you with the deployment for your organization.
Whether you’re choosing to migrate all your events and data or just starting fresh, our team has years of experience executing and planning Tealeaf upgrades, large and small. We’d be happy to guide you through the process of working with your IBM rep to determine proper sizing for your upgraded environment. And starting the process now just might put you in a position where you’re shopping for hardware, say, a month or two from now: just in time to make one of those Q4 price deals with your hardware vendor!
Start the process today! Have questions, need help?
I can be reached at email@example.com or leave a comment below!