My TeamSite 7.4.1.1 review - A Hot Mess!

We are wrapping up our upgrade from TS 6.7.2 sp2 to 7.4.1.1 and wanted to share our experience/struggles.

Horrible. Basically it looks like they just slapped a new CSS over the old layout? It may look more "modern" but its actually worse than the old version. Difficult to use and buggy. Switching between TeamSite UI and CCP pro breaks the CSS/templates. Numerous devnet threads with feedback from HP support suggest users DONT even use the new TeamSite UI?!?

Browser support

Still only IE8 (really?) per a support case we opened - if you try to use FireFox the administration UI is terrible (tiny fields, scroll bars everywhere, broken CSS, etc)

Bugs bugs bugs:

Case #	Description	Details	Product bug/REA (Request for engineering assistance)/Enhancement Request
1273419	cannot use double quotes in the group descriptions	double quotes (") cannot be used in Group Description or the Admin UI will break.	Product Defect TS-21937
1274387	Issue with Workflow Modeler	our company and other users on the HP support form experience this bug. /t5/TeamSite/TeamSite-UI-throwing-errors/m-p/192282/highlight/true#M122819	Product Defect TS-18951
1274395	cookie_lifetime and ui_login_lifetime settings	These settings to change the timeout sessions in iw.cfg no longer work. (basically HP removed funcationality where you could control how long a user could remain in TeamSite without being forced to login again) See the below /t5/TeamSite/TS-7-2-1-login-cookie-lifetime/m-p/168958#M109402 There is already a case with HP open. TS-13251	REA : TS-21970, Enhancement Request: TS-21971
1276449	OpenSSL security	Hello - our security team ran a scan of our TeamSite 7.4.1.1 installs and noted the below vulnerabilities with OpenSSL. OpenSSL appears to have binaries in Apache which Teamsite is using. "A vulnerable version of OpenSSL is present on all three servers. There are also multiple known vulnerabilities associated with this revision of the service. OpenSSL will need to be upgraded to version 0.9.8zb or later." Is this supported? if not when does HP plan to address the vulnerabilities?	We (HP) are aware of the issue, and our engineering team is currently working on a patch that will update the OpenSSL version to 098.zc. While I don't have an exact release date, I am told that we should see it released in the next few weeks. That is all of the information that I have at this time. Can we close this ticket out for now, and if you don't see the new patch on the support site by the end of the month, open a new ticket at that time? Thanks Robert Hotchkiss HP Software Support
1274384	TeamSite UI Task Grid Display	If you set the due date of a workflow with a normal date…the tasks will not appear in the TeamSite UI Task Grid. We have to convert it to a UNIX timestamp before setting the due_date variable.	Solution from support: Using the unix timestamp to add the due date to the workflow and the the tasks are appearing in TeamSite UI. This seems like it should be fixed to use a date format. NOTE: they closed the ticket without providing an REA or bug number.
1276774	TinyMCE "paste from word" no longer working in IE9 or IE10	TinyMCE "paste from word" no longer working in IE9 or IE10	Only IE8 is officially supported still (really?!?)
1274388	TeamSite UI Error getConfigFileFromTS on branch	FYI: I see this once in a while in the \D$\Interwoven\ApplicationContainer\server\default\log\core.log when I hit TeamSite UI: 2014-11-12 13:32:24,088 [http-0.0.0.0-8080-13] ERROR com.interwoven.ui.teamsite.g11n.blc.PropertiesBranchConfigProvider () - Error getConfigFileFromTS on branch /default/main/branch_name : From Fish in DevNet: I'd say it's a bug - and one that I should have (but haven't) reported to Support. After seeing the "cc loading" message for about a minute (+/-) just do a browser-refresh / re-load the URL - you should cc the "cc loading" message again, but it will shortly actually load. This is generally only needed the first time you try to load the UI after restarting the services, after that you've loaded it once, you should not have to go through the browser-refresh process. You should probably report it to Support (note: it happens in 7.4.1 too) He’s right after any restart of the services…they will see a CC:loading message on the page and this error will be in the core file.	Case reported to HP still waiting for resolution/REA/Product defect #. Fix available via Devnet (thanks Fish!)
1274389	TeamSite UI grid bug (occurs if SitePublisher is not installed)	When opening the TeamSite UI view, if you have one of the items in the Dashboard collapsed, the bottom panel will not render and will throw a JS error.	HP support doesn’t even have an environment w/o SitePublisher installed to verify/replicate. We resolved internally.

TL;DR - Lipstick on a pig! Couldn't have done it without the kind folks of DevNet!

Find more posts tagged with

Comments

nipper

Buggy, certainly. Mess, I wouldn't go that far.

Browser support ? Sucks. I agree. I thought IE8/IE9 were supported, though IE8 support is really stupid.

I use IE11 a ton on 7.4.1 and 7.3.2 with minimal issues. FF I use is 26 but also use higher, this is my primary browser and the admin tab works fine.

Cookie lifetime has been an issue since 7.0, it never worked after 6.7.2 AFAIK.

Double quotes in the group description? OK an annoyance, but anyone who programs JS understands this issue. But I really doubt more than 2 companies have even discovered this.

Rick Poulin

I'll agree that the UI implementation is messy partly because it's a new coat of paint on markup that is nearly 10 years old.. but it's getting a complete rewrite in 8.0, so at least there's that.

RE: TeamSite UI Error getConfigFileFromTS on branch,

I have encountered something similar to your description. In 7.2+, there are hidden branch/workareas, one for each *real* branch/workarea you've created. For some reason, those hidden workareas were getting created with private=true and group=nobody, so only users could read the contents of that branch, leading to the error you're seeing. In particular, the Actions > Localize menu item would often disappear for non-master users because the code behind it couldn't go read the g11n configuration for the branch. Anyway, you can easily shoot yourself in the foot if you fiddle with this yourself, but you might want to ask support about checking the rights on the workarea within the /default/iwconfig branch structure.

bmanilow13

Already had a production crash...the Jboss service stopped unexpectadly over lunch. There are even MORE log files now than the 6.7.2 version...does anyone know which 20 below logs that have errors from today I should be most concerned with?

\\SERVERNAME\Interwoven\ApplicationContainer\bin\hs_err_pid5716.log
\\SERVERNAME\Interwoven\ApplicationContainer\config\odadmin\log\SERVERNAME_adminEventReporting.log
\\SERVERNAME\Interwoven\ApplicationContainer\server\default\log\core.log
\\SERVERNAME\Interwoven\ApplicationContainer\server\default\log\cssdk_soap.log
\\SERVERNAME\Interwoven\ApplicationContainer\server\default\log\iwjboss_server_out.log
\\SERVERNAME\Interwoven\ApplicationContainer\server\default\log\jasperserver.log
\\SERVERNAME\Interwoven\ApplicationContainer\server\default\log\server.log
\\SERVERNAME\Interwoven\OpenDeployNG\log\SERVERNAME_odbase.log
\\SERVERNAME\Interwoven\TeamSite\local\logs\custom.log
\\SERVERNAME\Interwoven\TeamSite\local\logs\iwevents.log
\\SERVERNAME\Interwoven\TeamSite\local\logs\iwserver.log
\\SERVERNAME\Interwoven\TeamSite\local\logs\iwtrace.log
\\SERVERNAME\Interwoven\TeamSite\local\logs\tsreport.log
\\SERVERNAME\Interwoven\TeamSite\local\logs\activemq\db-1.log
\\SERVERNAME\Interwoven\TeamSite\local\logs\iwui\content_center.log
\\SERVERNAME\Interwoven\TeamSite\local\logs\iwui\error.log
\\SERVERNAME\Interwoven\TeamSite\local\logs\iwui\ssl_error.log
\\SERVERNAME\Interwoven\TeamSite\local\logs\iwui\ssl_request.log
\\SERVERNAME\Interwoven\TeamSite\local\logs\iwui\ssl_transfer.log

nipper

iwjboss_server_out.log
server.log

Concentrate on these two.

bmanilow13

Great thanks Andy we have also opened a support case w/ HP. We are seeing a lot of LiveSite errors (I think?) even though we dont own it or have it installed. We also dont use the related files/file associations? (which also seem to be referenced in the below errors)

2014-12-22 12:48:05,036 INFO [STDOUT] 12:48:05,036 ERROR [SimilarFilesUtil] getResults on ResultsDocument for http://localhost:8080/lscs/v1/suggest?context=//SERVERNAME/default/main/non_us-english/WORKAREA/integration&path=daf/pdf/portfolio_holdings/33397.pdf&querysummary=true&start=1&max=10 failed: HTTP/1.1 404 /lscs/v1/suggest
2014-12-22 12:48:05,037 INFO [STDOUT] 12:48:05,036 ERROR [SimilarFilesController] Could not retrieve related files for //SERVERNAME/default/main/non_us-english/WORKAREA/integration/daf/pdf/portfolio_holdings/33397.pdf
com.interwoven.ui.userdashboard.filesys.similar.SimilarFilesException: com.interwoven.ui.userdashboard.filesys.similar.SimilarFilesException: http://localhost:8080/lscs/v1/suggest?context=//SERVERNAME/default/main/non_us-english/WORKAREA/integration&path=daf/pdf/portfolio_holdings/33397.pdf&querysummary=true&start=1&max=10: : //SERVERNAME/default/main/non_us-english/WORKAREA/integration/daf/pdf/portfolio_holdings/33397.pdf
    at com.interwoven.ui.userdashboard.filesys.similar.SimilarFilesUtil.getSimilarFiles(SimilarFilesUtil.java:182)
    at com.interwoven.ui.userdashboard.filesys.similar.action.SimilarFilesController.handle(SimilarFilesController.java:112)
    at org.springframework.web.servlet.mvc.AbstractCommandController.handleRequestInternal(AbstractCommandController.java:87)
    at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
    at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)
    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
    at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at com.interwoven.ui.core.util.UtilityFilter.doFilter(UtilityFilter.java:85)
    at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
    at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at com.interwoven.ui.core.auth.AuthenticationFilter.doFilter(AuthenticationFilter.java:280)
    at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
    at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
    at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
    at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
    at java.lang.Thread.run(Thread.java:662)
Caused by: com.interwoven.ui.userdashboard.filesys.similar.SimilarFilesException: http://localhost:8080/lscs/v1/suggest?context=//SERVERNAME/default/main/non_us-english/WORKAREA/integration&path=daf/pdf/portfolio_holdings/33397.pdf&querysummary=true&start=1&max=10:
    at com.interwoven.ui.userdashboard.filesys.similar.SimilarFilesUtil.getSimilarFiles(SimilarFilesUtil.java:227)
    at com.interwoven.ui.userdashboard.filesys.similar.SimilarFilesUtil.getSimilarFiles(SimilarFilesUtil.java:177)
    ... 42 more
Caused by: org.apache.commons.httpclient.HttpException: HTTP/1.1 404 /lscs/v1/suggest
    at com.interwoven.ui.userdashboard.filesys.similar.SimilarFilesUtil.getResults(SimilarFilesUtil.java:282)
    at com.interwoven.ui.userdashboard.filesys.similar.SimilarFilesUtil.getSimilarFiles(SimilarFilesUtil.java:222)
    ... 43 more

nipper

Those will not be an issue. Because you do not have LS, you will see a bunch of errors.

The large strack trace is for the associated files functionality. Not certain if that requires LSCS, but it certainly could.

Nothing you show looks like a reason for a crash however.