Lotus Quickr : Die zweiVersionenFILE/T4S6-Quickr.pdf · IBM ® Lotus ® Quickr ™: Die zweiVersionen Barbara B Koch –[email protected] Channel Technical Leader derLaaLaa-Brand

IBM® Lotus® Quickr™ : Die zwei Versionen

Barbara B Koch – [email protected]

Channel Technical Leader der LaaLaa - Brand

Go to www.ibm.com/lotus/quickrPlans are subject to change at any time without notice

IBM Confidential

2

Agenda

Key Functional & Non-functional Differences3

Appendix A: Micro-differences4A

Lotus Quickr Functional Overview2

Appendix B: A few illustrations4B

Deployment Options & Recommendations1


IBM Confidential

3

Deployment Recommendations

Selecting the optimum platform for a deployment will be based on a few factors:

1. Technology affinities

• Which skillsets (Domino or J2EE) are more readily available ?

• Current and future infrastructure

• Is there a strategic technical direction expressed by IT ?

2. Functional and non-functional affinities

• What are the must-have requirements for the short (ex: next 12-18 months) and long term ?

• Are there specific SW/HW mandates for deploying a new product ?

3. Existing collaboration content

• Are there any QuickPlaces or WCS content to upgrade account for ?

If there is no clear preference...

Start with the “Domino services” option where the collaboration experience is currently more complete


IBM Confidential

4

Understanding the deployment options

Core functionality of Lotus Quickr is similar between the two deployment options. For example:

Experience for “My places” and the creation of places from templates is similar

Connectors are the same: they are independent of the back-end services

A set of collaborative components - wikis, blogs, tasks – and basic document services (check-in/out, versioning, workflow, access control) is available on both platforms

Do I get the exact same experience ?

No. There are functional and non-functional differences between the deployment options:

• In general, the Domino services provide more functionality than what is available with the J2EE services, such as: offline access, team calendar, forms/lists, replication, etc.

Lotus

DominoJCR


IBM Confidential

5

Is there functional symmetry ?

Core functionality of Lotus Quickr is similar between the two deployment options. For example:

Experience for “My places” and the creation of places from templates is similar

Connectors are the same: they are independent of the back-end services

Some collaborative components - wikis, blogs, tasks – and basic document services (check-in/out, versioning, workflow, access control) is available on both platforms

Do I get the exact same experience ?

There are functional and non-functional differences between the deployment options:

Many initial differences from Lotus Quickr 8.0 have already been addressed. Some others are planned to be addressed over the next releases.


IBM Confidential

6

Deployment Recommendations

The optimum platform for your deployment can be based on multiple factors, some tactical, some strategic:

1. Existing collaboration content• Content from existing “Lotus QuickPlace” or “Workplace Team Collaboration” deployments needs to be

upgraded to the same technology

2. Technological affinities• Skillsets (Lotus Domino and/or J2EE) that are more readily available will often drive the type of deployment• Current and future infrastructure (SW/HW) requirements. For example, AIX or iSeries are only supported on

Lotus Domino services, while Linux RedHat is only supported on the J2EE services.

3. Functional affinities• The J2EE services have strong document management • The Lotus Domino services have richer out-of-the-box collaboration capabilities (for components “above and

beyond” document management), automatic mail notifications, offline access, and support for nested places.

4. Deployment strategy• The J2EE services are better positioned for a centralized architecture (ex: single multi-lingual server), while the

Lotus Domino services excel in distributed environments (ex: replication)• A stand-alone environment built on Domino services is usually easier to deploy and maintain than one built on

J2EE services. However, the J2EE services will be a better fit for a high-end customized environment, thanks to the component-based architecture (portlets) that provides for powerful customization and integration.

Summary:

The J2EE services are based on open, extensible standards and provide rich integration capabilities

The Lotus Domino services rely on the strengths of the Domino architecture (ex: replication)


IBM Confidential

7

Product Strategy

Technical DirectionsIncreasing use of a common set of UI components and Web services will provide a virtualization of the underlying repository � Benefits: more consistency on user experience, and more potential for extensibility

Functional DirectionsFocus is not on “functional feature parity” between the different deployment options, but rather on improving the end-user experience, overall functional capabilities, and product extensibility

• Lotus Quickr will keep leveraging and extending the unique strengths of the respective infrastructures (ex: records management is only available with an ECM system)

Provide co-existence and interoperability with more repositories

• Provide an aggregated view of the content and collaboration, so end users are more productive, and don’t have to worry about where the content is physically stored

Business commitments

Preserve and extend our customers’ investments and skills

• Ensure that the content and applications created by our customers are taken forward to the next releases, regardless of their deployment options

Services

Web interface

Repositories

NSF RDB ECM SP?

Connectors

Services

Web interface

Domino

servicesNSF

Connectors

J2EE

servicesRDB

From today to tomorrow


IBM Confidential

8

Agenda







IBM Confidential

9

Lotus Quickr - Functional Overview

Shared

ContentTeam

Workspaces

WorkflowAnywhere

Anytime

Wikis

Team

Blogs

Business

templates

Quickr

content stores

Lotus Domino IBM JCR FileNet * IBM CM * Other

* Platforms will require a separate purchase when interoperability

with Quickr is supported

Library management, check in & out, version control,

views, security, custom

meta-data for a variety of

business content types

A collection of reusable collaborative

components (libraries,

calendars, tasks, blogs,

lists, Web content authoring...) to build

powerful applications

Offline services, extranet access, versatile portlets, to expand and

facilitate collaboration

Self-service, customizable

team sites with an extensible

infrastructure (membership

mgmt, search capabilities), that support a full team

lifecycle

Templates for immediate

out-of-the-box value and

support of common

business processes,

including project mgmt, wikis, blogs, innovation...

Work flow for document routing and dynamic

applications

Native support


IBM Confidential

10

Share files and documents virtually

• Securely share documents with colleagues, customers and partners

• Supports a wide range of content sharing –Enterprise library, Team library, and Personal library

Quickly set up libraries to store and share content securely


IBM Confidential

11

Check in, check out and version control

Drag and Drop upload

Security on multiple levels

Email links instead of attachments


IBM Confidential

12

Collaborate on content using wikis

• Create team sites

collaboratively

• Create content

collaboratively

• Safeguard your

information

– Automated versioning


IBM Confidential

13

Lotus Notes Email IntegrationAccess your team places in

the side shelf

Easily drag attachments from your inbox to a team place

Access your Activities in the side shelf

Send links, not attachments to your team members


IBM Confidential

14

Microsoft Outlook

Access your files in the Side shelf

Person Card integration for quick access to people

Add emails to Activities


IBM Confidential

15

Microsoft Office


IBM Confidential

16

Lotus SymphonyLotus Symphony

Contribute new content a project directly from the

editor

Check in, check out, and versioning to manage

collaborative authoring

Workflow Integration


IBM Confidential

17

Access to Quickr content

Access to content using the connectors, feeds and the browser is possible for both deployment options

“My places” and “Feed reader” portlets, and the “Web Application Integrator” toolkit, provide for access to both types of Quickr places.

Integration with WebSphere Portal

Places on two different infrastructures can be accessed from a single consolidated view (“my places”) using a browser

Note: “onespace” functionality is currently tech preview

Note: It is also possible to federate places from multiple servers transparently when running on the Domino services

My places

ATOM feeds are available on all end-user pages to subscribe to content from Lotus Quickr

Producing Feeds

Common FunctionalityKey Area

Ability to access any page, piece of content in Lotus Quickr with a URLURL Addressability

Sametime connector, Lotus Notes connector, MS Office connector, MS Windows Explorer connector, MS Outlook & Lotus Symphony connectors (new in Lotus Quickr 8.1) provide indiscriminate access to files from both repository types in one single view

Connectors


IBM Confidential

18

Place infrastructure

The following functionality is available at the place level, regardless of the deployment option selected

Note: Having similar capability does not mean the user experience is exactly the same

Use of LDAP directory(ies) for secured authentication to Quickr content

Secured Access

Templates (ex: standard project place), can be customized, or obtained from third party companies. Places are then created offtemplates (note: list of templates will differ)

Template-based architecture

Places can be edited and deleted. Places can archived and restored.Managing places


Different access levels (roles) are available out of the box. Users can be assigned to these different access levels.

Places can be opened up for global authenticated access

Member management

Creating a place is a two-step process where a user first selects a template, and then provides key data (ex: title, description). Places are created in less than a minute

Creating places


IBM Confidential

19

Content management

The following functionality is available for managing content, regardless of the deployment option selected


Possible to send link to a document (using the browser or connectors)Send link

Out-of-the-box serial and parallel workflowDocument workflow

Comments can be added to different types of contentDocument collaboration

Content can be uploaded (single or multiple files). Use the browser to drag-and-drop files between folders.

Upload / import

Custom meta-data can be definedMeta-data

Folder structure can be defined to organize content. Documents can be checked in & out. Standard versioning (revisions) is available. Security is available at document or library level.

Library Services


Content (meta-data and attachments) can be searched across placesSearch


IBM Confidential

20

Collaboration components

The following functionality for team collaboration is available, regardless of the deployment option selected


Ability to associate presence to names and chat with individualsusing the browser (requires Lotus Sametime)

Online Presence

Managing tasks with owners, deadlines, and descriptions (note: additional capabilities may be available on both deployments)

Tasks

Posting blogs (with rich text, pictures, etc. ) and commentsBlogs

Managing individual contacts with names, contact information androles (note: contacts can be either defined as members or on a custom form on the Domino services)

Contacts

Creating wiki pages that get saved as different versions automatically. Older versions can be used to supersede latest changes. Comments can be added.

Wikis


Creating web pages to display list of announcements in the placeAnnouncements


IBM Confidential

21

Customization

The following customization and configuration functionality is available, regardless of the deployment option selected


Creation and editing of skins and themes to customize the user interface (colors, branding, fonts, logos)

UI customization

Ability to add and remove components (ex: document library, tasks, etc.) from a place.

Note: adding and removing components is more easily done with the WebSphere Portal architecture

Reorder pages.

Adding / removing components



IBM Confidential

22

Non-functional characteristics

The following non-functional requirements are available, regardless of the deployment option selected

Windows 2000, Windows XP, Windows Vista

IE6, IE7, Firefox 2.0 (*)

Client OS / Browsers

Lotus Notes 6.5 & 7.02 & 8.x, Sametime 7.51 & 8.x , Windows Explorer, MS Office (XP, 2003, 2007) on Windows 2000, XP, 2003 and Vista

Note: not all combinations are supported. See release notes for details

Client Connectors

MS Windows Server 2003Server OS

Simplified Chinese, Traditional Chinese, English, French, German, Italian, Japanese, Korean, Brazilian Portuguese, Spanish, Czech, Danish, Dutch, Finnish, Greek, Hungarian, Norwegian, Polish, Portuguese, Russian, Swedish, Turkish

Languages

Domino Directory, Active Directory, etc.User Directories


(*) Capabilities running on ActiveX components (ex: “round-tripping”) are not available with Firefox on the Lotus Domino services


IBM Confidential

23

Agenda







IBM Confidential

24

Product Roadmap for Deployment Options

The following slides provide a review of the key areas where the functionality is different between the two deployment options of Lotus Quickr

Information about current product plans that relate to any “convergence” of the functionality between the two deployment options is also provided

Current release, as of writing, is Lotus Quickr 8.1 for both deployment options Enhancements were delivered for both deployment options but focus of that release was mostly on the Domino services

A follow-on release (“Lotus Quickr Next”) is currently being planned for 1Q ‘09

• Content for that release is not finalized at this point

• Enhancements will be delivered for both deployment options but focus of that release is expected to be mostly on the J2EE services

Information in this presentation is provided to the best of our knowledge, subject to change, and does not reflect a commitment from IBM


IBM Confidential

25

High level functional summary

(*) Can back-up content on file systemYes (*)YesArchive and restore

(*) some limited offline access (see next page)Target TBD (*)YesOffline access

(*) includes custom rolesYes (*)YesMember management

(*) also includes feed readerYes (*)YesProduce ATOM feeds

(*) Using agents (placebots)Target TBDYes (*)Extending server functionality

(*) New in Lotus Quickr 8.1Yes (*)YesTeam Calendar, discussion forums

(*) Includes Hebrew & Arabic and multi-lingual on single server

Yes (*)YesGroup 1 & 2 Languages

Using templates, skins, themesYesYesUI customization

(*) announcements & contacts available today. Advanced users can also use underlying WCM capabilities.

Target TBD (*)YesCreate custom forms (Lists) to capture structured content beyond content library

(*) also includes announcementsYes (*)YesWikis, Team blogs, tasks, contacts

(*) includes flexible property sheets & viewsYes (*)YesContent Library

Same experience for both optionsYesYesConnectors (Notes, ST, Office, etc.)

CommentsJ2EE ServicesDomino ServicesCapabilities


IBM Confidential

26

26

FeedReaders

ConnectorsBrowsers

Quickr Architecture

User’s View

NSF

Domino

NSF

NSF

NTF

NTF

NTF

Quickr Content Services

(Domino, REST, SOAP)

Domino

Quickr Components

(Docs, Wiki, Blog …)

RDB

WebSphere Application Server

WebSphere Portal Server (subset)

Quickr Content Services

(Java, REST, SOAP)

Quickr Components

(Docs, Wiki, Blog …)

J2EE


IBM Confidential

27

Architecture – A Domino Clustered Deployment

Domino

7.0.2WAS 5.1 or 6.0

Portal Server

5.1 or 6.0.xDeployment Manager

WAS 6.1

Lotus ConnectionsDeployment

Manager

Directory ServerDatabase Servers

Conn

DB

Quickr

DB

WP

DB

HTTP Server HTTP Server

Dispatcher

Domino

7.0.2

File System File System

Quickr

NSF

Quickr

NSFQuickr

NSF

Quickr

NSF

Quickr

NSF

Quickr

NSFQuickr

NSF

Quickr

NSF

Lotus

Quickr

Lotus

Quickr


IBM Confidential

28

Architecture – A J2EE Clustered Deployment

WAS 6.0.2.17

Lotus Quickr on

Portal 6.0.1.1 (subset)Deployment Manager

WAS 5.1 or 6.0

Portal Server

5.1 or 6.0.xDeployment Manager

WAS 6.1

Lotus ConnectionsDeployment

Manager

Database Servers

Conn

DB

Quickr

DB

WP

DB

HTTP Server HTTP Server

Dispatcher

Directory Server


IBM Confidential

29

Lotus Quickr and WebSphere Portal

Lotus Quickr on J2EE services is built on Portal technology

Quickr places are implemented as Composite Applications

Portlets can be deployed into Quickr places, but Lotus Quickr and Quickr

components (e.g. Blog) are not deployable into an existing WebSphere Portal

Business components (such as those built with Lotus Component Designer) can

be deployed into Quickr places

Most Quickr components (Blog, Wikis, Lists) are implemented using WCM (this allows customization of these components using the WCM authoring included in Quickr)

The Lotus Quickr roadmap includes a portlet that can be deployed into

WebSphere Portal 5.1 or 6.0 to list your places (on whatever Quickr server they

are deployed – Domino or J2EE)


IBM Confidential

30

Lotus Quickr and WebSphere Portal - Licensing

Customers can not use the embedded Portal to aggregate applications where the

content resides outside of Quickr. There are a few exceptions:

Domino content: customers can use their Domino content within a Quickr place even if the content is outside of the Quickr database – though the DEPP Portlets will not be specifically tested

External feeds can be used in a Quickr place

Google gadgets can be used in a Quickr place

It will be possible to "turn on" portal capabilities on the Quickr server, which will allow for the use of additional business Portlets (such as to access SAP), but this will require the customer to purchase a Portal license

The embedded Portal Server is a subset of WebSphere Portal Multiplatform

6.0.1.1 but does not include:

Business Process Choreographer,

Virtual Portals

Not all the same server OS’s, databases, directory servers and clients are supported as

WebSphere Portal Multiplatform


IBM Confidential

31

Functional differences based on deployment option- “Key” differences

Not yet. Functionality is planned for follow-on release (possibly in “Lotus Quickr Next”). Feeds functionality is often a good alternative.

Yes. Newsletters can be sent on a regular schedule (users’ preference) when documents are changed

Email notifications on content changes

Not yet. Support for multiple LDAP directories (to include external users) and segmentation of user information is targeted for follow-on release (possibly in “Lotus Quickr Next”)

Yes. Users can be easily added to a place just with their email address, without being explicitly part of an LDAP directory

Extranet collaboration

Availability on J2EE servicesAvailability on Lotus Domino servicesCriteria

Six templates are available: Custom, Library, Meeting Place, Project Library Place, Team Blog, Team Wiki

Note: J2EE templates are available in all available languages. Some Domino templates are only available in English

Note: customizing and extending templates can be done more easily using the portal infrastructure

>Twelve templates are available: standard Place, Wiki, Blog, Doc Library, IPhotoLibrary (*), Idea Sharing (*), Issue mgmt (*), Presentation Development (*), Project mgmt (*), Team Announcements (*), Public Survey (*), Contact mgmt (*), Agenda mgmt (*)

(*) templates available on Snapps site

Templates available out-of-the-box

Limited. Individual documents can be checked-out online, edited offline, then synched up automatically later with the server by the “Quickr monitor”. Offline access for documents is currently planned for “Lotus Quickr Next”

Yes. It is possible to take entire places (content, business logic, user interface) offline and use the browser for access

Offline Access


IBM Confidential

32

“Non-functional” differences based on deployment option

Yes. Supports multiple HTTP servers: Apache Server, IBM HTTP Server, Microsoft Internet Information Services 6.0, IBM Lotus Domino (as Web server), Sun Java System Web Server

Limited: only supports the HTTP server included with the Lotus Domino server

Web Server

Both services support Simplified Chinese, Traditional Chinese, English, French, German, Italian, Japanese, Korean, Brazilian Portuguese, Spanish, Czech, Danish, Dutch, Finnish, Greek, Hungarian, Norwegian, Polish, Portuguese, Russian, Swedish, Turkish

Additional support for Arabic, Hebrew, Catalan, Slovak, Slovenian, Thai, Ukrainian

Both services support Simplified Chinese, Traditional Chinese, English, French, German, Italian, Japanese, Korean, Brazilian Portuguese, Spanish, Czech, Danish, Dutch, Finnish, Greek, Hungarian, Norwegian, Polish, Portuguese, Russian, Swedish, Turkish

Languages

Availability on J2EE servicesAvailability on Domino servicesCriteria

Yes. Migration toolkit from WCS 2.61. No toolkit yet available from PDM.

Yes. In-place upgrade (no migration) from QuickPlace 6.5 & 7.0 to Quickr 8.0.

Migration from existing IBM products

Both services support IE6, IE7, Firefox 2.0 on Windows XP & Vista

Both services support IE6, IE7, Firefox 2.0 on Windows XP & Vista. Additional support for:- Firefox 1.7 on Red Hat Enterprise Linux- Safari 2.0 and 3.0 on Mac OS X 10.4

Client OS support

Both services support Windows 2003. Additional support for RedHat Linux 4.0

Note: AIX support currently targeted for 2008

Both services support Windows 2003. Additional support for IBM System i (i5/OS V5R4), IBM System p (AIX V5.3)

Server OS support


IBM Confidential

33

Agenda







IBM Confidential

34

Functional differences based on deployment option- “Cross place” differences

Yes. Can lock places based on (lack of) activity and size quota (includes warnings and email notifications)

Yes. Can lock places based on (lack of) activity and size quota (includes warnings and email notifications). Email body can be customized.

Policies

Yes. List of templates to choose from is limited to the ones that a user is authorized to choose from

Limited. Requires creating a custom UI to filter the templates

Personalizing the place creation process

No. Not available as a core service in “WebSphere Application Server”

Note: clustering for fail-over / high availability isavailable on J2EE services (through horizontal clustering)

Yes. Places can be replicated across servers located in different geographical locations to provide optimized user experience

Note: clustering for fail-over / high availability is available on Domino services

Server-to-server replication

Yes. Possible to dynamically switch the UI between different languages (using browser preference). Note: content is of course not translated dynamically or switched automatically.

No. Each language requires deployment of a separate server to serve the UI in different languages (possibly targeted for “Lotus Quickr Next”)

Multi-lingual capabilities


Yes. Full text search can take place across places on a single server. Search across all content types, meta-data and files.

Search engine can also be set up to search http content. Connector is available for DB2 Omnifind.

Yes. Full text search can take place across places on a server. Or across servers (using Domain search). Search across all content types, meta-data and files.

Connector for Omnifind EE is available

Search


IBM Confidential

35

Functional differences based on deployment option- “Place level” differences

No. Possible to create views of all documents in library but this won’t include other components (ex: wikis)

YesWhat’s new & index views

Somewhat: this could be achieved by changing the roles/policies for the place

Yes. Places can be easily locked to freeze all activities on a place

Locking a place

Yes. Statistics about activity and size are available to place owners. More granularity is planned for follow-on release (possibly targeted for “Lotus Quickr Next”)

Yes. Statistics about activity, size, member roles, largest docs, logins, nbr. of docs, etc.. are easily available to place owners and administrators.

Place Statistics

Yes. Places can be flagged as “favorites” and displayed accordingly on the list of “my places”

No. Functionality is planned for follow-on release (possibly targeted for “Lotus Quickr Next”)

“Favorite”places

No. Functionality is planned for follow-on release (date TBD). It is possible to drag and drop an email into place using the connectors.

Yes. Emails can be sent to a place. Email content can then be managed in the place. It is also possible to drag and drop an email into place using the connectors.

Mail-in to a place

Availability on J2EE servicesAvailability on Lotus Domino servicesCriteria

Somewhat, using portal pages and providing limited access with specific roles but this requires the use of a single component (ex: doc library) at a time (vs. all components of a room) and no separate user mgmt. More functionality is planned for follow-on release (date TBD)

Yes. Rooms can be created within a place to provide access to a subset of users

Nested Places


IBM Confidential

36

Functional differences based on deployment option- “User management” differences

No local groups. No group expansion is currently available (date TBD).

Yes. Local groups can be created and used in a Quickr place. LDAP groups can be expanded (ieshow all users) in a few limited operations. LDAP groups can be expanded when adding users to rooms and for document level access. Other operations (ex: adding to places or workflow) are possibly planned for “Lotus Quickr Next” release.

Groups management

Not available (date TBD)Yes. Individual profiles can be created and extended for each user.

User profiles

Limited. List of member profiles is only available to place managers (in “customize” section). Possible to customize the Quickr “theme” to display the member list to all users.

Members cannot be searched specifically but users in the overall directory can be searched. LDAP groups cannot be expanded (ex: for task assignments, ACL or notifications).

Yes. List of member profiles is visible to all users and can be updated by managers. Members can be searched.

Place membership and profiles

Yes. Very granular security. Users can be assigned specific roles for specific components. Custom roles can be created.

Limited. A number of access control levels (readers, etc.) is available across the entire place

Roles

No. Functionality is planned for follow-on release (date TBD)

Yes. Individual places can be opened up to allow anonymous access

Anonymous access



IBM Confidential

37

Functional differences based on deployment option- “Content management” differences

No. One single type of content (ex: files, web pages, events, etc.) is available in each view. Note: search can be used to aggregate different types of content.

Yes. Different types of content (ex: web pages and files) can be listed in one single view

“Unified” content views (compound views)

Yes. More than 200 document types can be previewed, including PDF, AutoCAD, etc.

Limited. “Preview” is available for MS Office files (as HTML generated on upload)

Document Viewers

Limited: serial & parallel. More advanced workflow is planned for follow-on release (date TBD)

Limited: serial, parallel, editors, multiple editors. Pending documents can be assigned to folder

Document workflow

Yes. Automatic versioning can be turned on in a document library for specific document types. Previous versions can no longer be changed.

Yes. Automatic versioning can be turned on in a document library.

Also available as part of the wiki template.

Automatic document versioning

Yes. Separate ACL levels are available for document library, folders and individual documents

Limited. ACL can be set up to specific documents, but setting an ACL to a specific folder requires the use of a “room” instead of a “folder”.

Access Control for content and folders

Yes. Flexible document types can be associated to multiple property sheets, templates and workflow.

Yes. Document types (page types) can be created using the “forms” functionality. Custom attributes can be associated to page types.

Document Types & custom meta-data

No. One attachment maximum per page. No “compound documents”. Work-around is to use a “Zip” file.

Yes. Multiple attachments can be bound together in a single page, thus providing a “compound document”

Multiple attachment support (compound docs)



IBM Confidential

38

Functional differences based on deployment option- “Collaboration components” differences

Yes. Multiple calendar views are available. Sending ical invitations to personal calendars is notavailable

Yes. Multiple calendar views are available. Events can be sent to Lotus Notes & MS Outlook calendars as ical invitations.

Team Calendar component

Yes. Threads are only one level deep.Yes. A folder option is to display content in a discussion thread format, with multiple levels

Discussion forum component

Attachments can be added by changing the WCM templates for these components.

Ability to attach documents to any pageBlogs, wikis, tasks, etc.

Partial: announcements, contacts, tasks (no Gantt charts)

Yes. Different components available in different templates: document, discussion thread, event, tasks (with simple Gantt chart representation), surveys, presentations, contacts, etc. Some need to be downloaded from Snapps site (not supported and not translated to all languages).

Out of the box collaborative components

No. Functionality is planned for follow-on release (“Lotus Quickr Next”)

Yes. Web conferences can be created and managed from Quickr interface.

Web Conferencing integration

This requires custom development (with services or using advanced WCM expertise). Functionality targeted to end-users is planned for follow-on release (date TBD) exposing the WCM list functionality used for announcements, etc.

Yes. End users can use the “forms” functionality to create diverse forms with different field types

Customizable “Lists”for end users


Yes. Feed component can be added to a place to display external feeds

No, but can easily be done as customization. Full functionality is planned for follow-on release (date TBD).

RSS/ATOM Feeds consumption


IBM Confidential

39

Functional differences based on deployment option- “Customization and extensibility” differences

REST API’s used by the connectors are common but some differences in Web Services

REST API’s used by the connectors are common but some differences in Web Services

API’s

Yes. Extension using Portal Composite Application Model. (portlets can be created and added to a place). Easy wiring of components.

Integration of standard Java Portlets (JSR 168) to run portlets. Integration of standard Web services for Remote Portlets (WSRP)

No. Requires custom coding and use of other Lotus tools / products.

Composite application support

Yes+. Skins and themes can be created by developers and selected by end-user

Page layouts can be changed. Components (portlets) can be easily added to pages (“Customize” button)

Yes. End users can switch themes entirely change the branding, logo, colors, styles... Pages can be re-ordered.

Skins can be created by developers

End User UI customization

Use of semantic tags (hCard microformat) in markup to display context menus dynamically

TBDMisc. extensibility


Yes. Use any portlet creation tool (WebSphere Portlet Factory, RAD, etc.) accessing the content Services API’s & WCM API’s.

Yes. Use of Domino Designer. Extensions using Domino API’s and LotusScript

Programming tools

No.Yes. Placebots can be added to place to automate processes (scheduled or on event)

End user managed agents

Yes. End users can easily create a view of their content using a filter based on document properties and displaying columns of their choice

Limited. End users cannot create a filtered view of their content. Creating a custom view requires the use of a design tool.

Custom Views


IBM Confidential

40

Lotus Quickr Content Integrator

MicrosoftSharePoint sites

Microsoft ExchangePublic Folders

Lotus NotesTeam Rooms

Lotus DominoDocument Manager

Lotus QuickrContent Integrator

Provide migration, and transitional co-existence, from existing applications/repositories into Lotus Quickr


IBM Confidential

41

Agenda







IBM Confidential

42

Appendix B: Custom document meta-data

J2EE services

Domino Services


IBM Confidential

43

Appendix B: Comparing the Workflow

J2EE services

Domino Services


IBM Confidential

44


IBM Confidential

45

Relative Strengths of J2EE and Domino Services

Domino services

Support for offline places via DOLS

Support for Domino server replication

Extension using Domino API’s and LotusScript (in addition to web technology, java and xml)

Support for more IBM platforms (e.g. i-series)

Migration from Quickplace

Use of Domino Designer

Mature set of out of the box components (for example Team Calendar and Discussion Forums)

Anonymous access and extranet support

Nested places

J2EE services

Extension using Portal Composite Application Model

Extension using WCM API’s and templates

Extension using Document Services (e.g. customized document metadata)

Advanced Document Management (e.g. autoversioning)

Extension using Portal Services (e.g. click to action)

Migration from Portal Document Manager

Migration from WCS 2.6.1

Use of tools that can build business components and portlets (e.g. Lotus Component Designer)


IBM Confidential

46

Danke für Ihre Aufmerksamkeit !

Barbara B Koch

Channel Technical Sales

[email protected]

Mobil 0172 7279370