LWP 2.0 Day 1 Notes

September 14 2004

Lotus Workplace Overall/General

  • Lotus Workplace is a product in the IBM Workplace brand, which also includes Notes, Domino, the Domino extended applications, Websphere Portal, and Websphere Everyplace
  • Forms and Form Builder is tech preview (meaning not supported in production environments in 2.0, targeted for 2.5)
  • LWP 2.0.1 out this week, incorporates a bunch of the fix packs for a bit easier install
  • LWP 2.5 out by end of year
  • can install LWP 2 on top of Websphere Portal 5.0.2.1 and use them together
  •         LWP becomes a page within your portal
  • No workflow today, coming in a future version ... sounds like 3.0, not 2.5
  • most of the applications are not feature compatable with the domino versions at this time
  • took about 15 minutes to bring up all the components of LWP on the demo machines
  •         IBM DB2 (started with windows as a service)
  •         IBM HTTP Directory (for ldap)
  •         3 components for launch of LWP (server1, websphere_portal, lotusworkplace)
  • jsp have to compile first time you hit a page/do something
  •         very slow for first hit to things like directory lookup, then after first hit quite snappy
  • overall look and feel very much like websphere portal
  • not a replacement for notes/domino!
  • current domino shops should not migrate to LWP
  • at some point, a convergence will happen between lwp and notes/domino
  •         domino server would continue, but goal is to have the rich client be the single client
  • Rich Client is only avaialble via managed betas in 2.0
  •         have to sign up with IBM
  • heavy hardware requirements
  •         suggested hardware is one server per application
  •         for a single server dev box, 4 way processor box with 4 gigs of ram needed for any real world use
  •         single server not supported for production systems

Lotus Workplace Messaging
  • Clean User Interface
  • mail rich text editor very nice, clean and fast
  • No Category for Calendar Entries or Contacts
  • No Tasks
  • No memos
  • folder maintenance not as nice as n/d ... no drag and drop
  • very limited mail and calendar preferences

Lotus Workplace Team Collaboration
  • very clean ui, feels like a yahoo groups version of quickplace
  • no gantt chart ui for tasks
  • team calendar integrates directly with web conferencing
  • no idea of rooms like quickplace
  • documents uses LWP Documents functionality
  • Discussions more like a web discussion board, like ezboard or even dombulletin (got michael!)

Lotus Workplace Documents
  • has built in editors for rich text, spreadsheet, presentation (openoffice)
  • stored in libraries
  • has draft and locked documents
  • importing of documents
  • document notifications (via links)
  • no checkin/checkout
  • has basic versioning
  • has document comments
  • moving to support JSR170 doc managment standard, as will IBM Content Manager (no idea on domdoc)

Lotus Worksplace Web Conferencing and Instant Messaging
  • presence everywhere
  • instant contacts portlet (like 6.5 workplace workspace UI)
  • activex required for powerpoint conversion
  •         means that IE and win32 required for this
  • has additional install for screen shows
  •         not sure if this is win32 only
  • web conferencing has agenda management built right into the product
  • sametime to lwpwc connector coming in the 2.5 timeframe

Lotus Workplace Content Management
  • still 2 version
  •         domino
  •         java
  • still targeted at content in websphere portal
  • personalization built in
  • 2.0 brings tighter integration and more function
  •         internationalization
  •         ibm db2 content manager integration
  •         versioning
  •         external api
  • domino version supports custom subform for specific content type

Lotus Workplace Collaborative Learning
  • future of lotus elearning products
  • lms not being upgrading going forward
  • new portlets for student ui
  • skills management
  • course descriptions
  • integration with lwp messaging
  • integration with lwp team collaboration for team spaces
  • admin updates users in workplace, not external or seperate ui for ldap

Lotus Workplace Tool Strategy
  • Lotus Workplace Builder for low level template creation
  • Websphere Studio Application Developer for high end development
  • The missing piece is the RAD, Domino Designer type tool for current Domino Developers .. which is coming (no target date)

Lotus Workplace Builder
  • Targeted at business users, not developers
  • Low-level customization called templates
  • applications built from templates
  • templates can be built from templates
  • changes to a template do not effect templates created from applications created from templates ... a mouthful, but basicly means not multi-tiered template inheritance/update like Domino today
  • What can be edited
  •         Application and template metadata (name, description, theme, owner)
  •         Page structure and contents (workplace components, portlets, custom components)
  •         Roles and component mappings
  •         Parameters and component mappings (centrailized config of components)
  •         Forms development is there but its just a preview
  • 3 Levels of security like quickplace (reader, editor, manager)
  • Roles allow for specific fucntion assignments
  • Basic Form Design, but still tech preview
  • During the lab, it felt like i was building a Word template or a powerpoint template, or even an HTML page via a wizard in Homesite
  • Very clean user interface
  • changing things such as page names very easy
  • way too many confirmation pages
  • Preview very fast and ability to make changes in preview mode (very nice!)
  • Builder assembles business components and a template into a LWP application
  • parameters for advanced configuration

Lotus Workplace Architecture
  • Built upon reusable business components
  • deployable
  • has a layered architecture
  • formally defined access points (by interface, not implementation)
  •         User
  •         Workspace
  •         Service
  •         Resource
  • Workplace objects built as components
  • Standard pattern for components
  • defined by reference architectures
  • BC (Business Components) is the key concept in the pattern
  • coarse-grained components
  • BC are the base unit of capability
  • BCs can be created by BPs in 2.5

Portalizing Domino Application
  • Domino still at good content store and application server
  • domino preferred for
  •         collaborative applications
  •         mail intensive apps
  •         workflow
  •         applications dealing with semi-structred data
  •         document-centric
  • easy access from users
  • integrate existing apps to new portals without rebuilding apps
  • options without custom development
  •         supplied domino specific portlets
  •         html portlets (iFrames, web clippings)
  •         portlet builders
  • custom integration techniques
  •         http connection
  •         (D) IIOP connection
  •         web services
  • portlet patterns
  •         link (link to launch the native app, notes or browser based)
  •         display (display information from domino, application launched via client or browser)
  •         integrated (user performs tasks in other apps inside the portlet, application launch not needed, only info and logic transfered to portlet)
  •         migrated (replaces application and transforms entire business process inito portlets, requires redesign/rebuild)
  • Integration Techniques
  •         existing portlets (simple, no java or domino development needed, limited to portlet)
  •         portlet builders (middle ground approach, requires less dev skills than tag or java, more capabilities, can not be extended)
  •         domino jdp tag library (easier than java, need understanding of jsps and domino objects, no session pooling)
  •         java (most difficult, highest level of skill required, most robust, longest dev time)
  • domino integration options (lowest dev effort to highest)
  •         out of box notes/domino portlets
  •         portlet builder for domino
  •         xml access to domino view data
  •         lotus collaborative components
  •         domino jsp tags
  •         domino java APIs
  • DWA Portlet, Lotus Notes View portlet, DomDoc portlet (comes with portal and in portlet catalog)
  • HTML portlets - little or no change, little control of content appearance
  • iFrames - containment of existing application in a fixed size, limited to applicationn web ui, compatable with only some browsers
  • web clipping - portal server talks to web server, links are rewritten, can not render all pages
  • domino application portlet
  •         designed to allow domino web apps to be surfaces in lwp or wp
  •         user experience stays the same
  •         no changes to domino app required
  •         reverse proxy: remaps links
  •         single sign on support
  •         ssl transfered
  •         delivered as iframe now, web clipping coming in a future release
  •         latest version is now available as standalone portlet from catalog
  • portlet builder for domino
  •         simple web interface to create portlets that access/manipulate data in domino
  •         no programming required
  •         based on websphere portal application integrator framework
  •         designed for rapidly creating portlets
  •         prebuilt porlets include sap, peoplesoft, siebel, jdbc,oracle
  •         click-to-action and people awareness part of the builder
  •         targeted at business users
  •         can display and edit documents without needing a domino application to be web enabled
  •         requires domino http
  •         2 ways to view documents (dataform and iframe form viewer)
  •         connects to any domino db
  •         no changes to existing domino databases
  •         offline browsing support
  •         mobile support for wml
  •         attachment support
  •         sortable columns
  •         view search
  •         select multiple views & forms in domino db to customize via portlet builder
  •         views customized by selecting columns
  •         forms customized by selecting fields
  •         views are selcted by the users form a list at runtime
  •         view columns are resizable
  • Business Objects
  •         useful for dealing with back-end applications and data
  •         collections of fields
  •         have fixed verbs associated
  •         browed from websphere business integrator

1 Responses to “LWP 2.0 Day 1 Notes”

  1. 1) Call Girls in Mumbai says:

    I appreciate your knowledge and I totally agree with your opinions.

Leave a Reply