See Also: Home Links Personal Site Blogroll  FriendFeed CV

Topic Image

Plumtree

I'm off to a Plumtree conference shortly so thought I'd knock up a list of issues, queries and mysteries that were worth discussing with other developers and PT clients:

  • Development J2EE v .Net: practical reality of mix of development languages and affect on maintenance, portability, future proofing
  • Centralisation: how much effort goes into rebuilding using PTs apps vs re-purposing existing web infrastructure
  • Decentralisation: how useful (or threatening) is the likes of IBMs Workplace and other smart distributed emerging SOA useable/integratable clients and platforms
  • Hosting - is anybody running (parts of) it on Linux? Redhat enterprise seems to be supported under G6
  • BEA purchase: collaboration vs service niches, likely impact on current platform, benefits of newly avail toolsets (e.g. Workshop/Eclipse), integration, BEAs SOA push, scalabilty comparisons, customer targets, product roadmap
  • Staging: Devel - Test - Live environments, practical? licensing? migration hassles? web based wizard in 6.0?
  • Browser Support - any improvment in support on OSX/Safari? improvement in WYSIWYG, project and CMS explorer and other widgets in Mozilla/Firefox
  • Legacy Apps: adaptive portlets require mixing proprietary PT JS libraries and functions/divs in with existing legacy code output, how best to manage? what about in multi portal vendor environment
  • EDK: compared with PT Server API, Non supported languages (perl) and stragetgy for integrating with Portal, write our own lightwight API/web services connector? Just read the HTTP headers and not worry about writes?
  • JSP vs Servlets: balancing overhead of full blown Java app and Eclipse use and deployment vs JSP, performance difference?
  • Tomcat: vs JBOSS and Weblogic etc, any real performance concerns or tradeoffs (manageability, commercial vs open-source)
  • Content Management: real scalability of content-server, for full on enterprise CMS what about integration w other systems (than Documentum), standards?
  • JSR168/WSRP - EJBs etc, actual use? toolkit avail from PT (cant seem to download it yet), more vendor neutral
  • Migration to 6.0 - full support of Firefox, API changes?, any new browser controls or server calls/access
  • UI customisation: how much work to master pluggable-nav, do nav schemes tend to change much in the life of the portal, is it worth the investment in effort/time when an off-the-shelf solution may do the trick
  • PEI - how much is this used for things other than authentication or UI tweaking
  • WYSIWYG probs - alternatives like Htmlarea, fckeditor and Tiny MCE?
  • Problem Portlets - feasibility of dev of alternatives to portlets we're not happy with, e.g. IMAP / exchange suites, any improvment of these under G6?
  • SOA BEA have tools like Workshop that provide access to rules engines, workflow designers, and business-process modellers etc
  • MVC Approach - how to approach some logic/presentation separation, JSPs as templates calling Java applets?, use a framework like Struts?


Attendees at the conference to hook up with:

Lawrence Carra (Computing Services, Univ of Pittsburgh) http://www.technology.pitt.edu/index.html

There's also the whole issue of BEA's Plumtree Acquisition


See Also: Portals | Notes Index