7 considerations for your TeamSite Upgrade

Share Button

There could be multiple business reasons to consider when you upgrade your enterprise content management system based on HP TeamSite. However, the following 7 technical factors should not be ignored.

1. Consider “modernizing” your website, not just your Content Management System. If your website front-end (HTML/CSS/JS) has been built more than 3 years ago, it is probably not using HTML5. It is probably not using CSS3 and more likely than not, it is not using one of the latest Javascript frameworks. What do the new front-end development tools provide that your old-site does not have? Think, Responsive Design. Think Cross-Browser compatibility. Think Customer Experience.

2. Consider upgrading your hosting hardware and software. Were you a 90’s Sun Microsystems fan and your enterprise web properties hosted on, dare I say, Solaris 8? It’s 2014 and time to move on. If you are on Windows 2003, it’s time to move on to more the secure Windows 2008 servers. Virtualization has come a long way and whether you want to move to  Oracle LDOMs ( Oracle’s virtualization technology – you can read about it here) or VMWare, consider making this a priority in 2014.


3. Consider upgrading to a Reusable Component Model of Website construction. Older TeamSite implementations were typically based on providing templates on a page basis. SitePublisher – the WYSIWYG site building tool within TeamSite, provides a rich, reusable Component model. Moving to a SitePublisher approach allows you to build a reusable, Component library that content contributors can benefit from.


4. Consider moving away from esoteric Perl to the more widely-accepted Java platform. While most HP customers have moved on and adopted Java as their CMS platform (and some have even moved to .NET), there are still others who are still dependent upon non-secure, difficult-to-troubleshoot Perl code that was written in the early 2000’s. With the new CSSDK API that TeamSite provides, there is no reason to depend on Perl code and you can move to the more secure, Java platform.


5. Get rid of TPL and move on to XSLT.
TPLs – a strange combination of Perl and proprietary “IWOV” tags, were the corner stone of building templated pages in old HP TeamSite implementations. Do yourself a favor and move to the more widely accepted XSLT. The latest version of HP TeamSite comes with the XALAN 2.x XSLT pre-processor that has rich functionality and there is no real need to use TPLs.


6. Consider upgrading TeamSite workflows to Workflow Modeler technology. Using  Workflow Modeler provides a more seamless, integrated feel to content workflows. For advanced, back-end integrations to your workflows, consider using TeamSite’s Content Services SDK (CSSDK) for more robust and reliable technology.


7. Consider taking back control of your presentation platform using LiveSite. If you are not using HP TeamSite-LiveSite technology to take control of your web-user experience, it is now time to do so. Context, whether it is end-user device recognition or understanding user analytics, is critical to understand your customer. With LiveSite, you, as a business user, “own” the presentation layer. Using Segmentation and Targeting modules (or even if you don’t), you have plenty of options to control the user experience.