Skip to main content link. Accesskey S
  • Log In
  • Help
  • IBM Logo
  • IBM Sametime wiki
  • All Wikis
  • All Forums
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • IBM Redbooks
Community Articles Product Documentation Learning Center IBM Redbooks This category Sametime Advanced 8.5.2 IFR 1 for administrators Sametime Standard 8.5.2 IFR 1 for administrators Sametime Unified Telephony 8.5.2 IFR 1 for administrators Custom Search Scope...
Search
Community Articles > Deployment scenarios > Interactive version! "Persistent Chat" diagram
  • New Article
  • Share Show Menu▼
  • Subscribe Show Menu▼

About the Original Author

IBM contributorJennifer Heins
Contribution Summary:
  • Articles authored: 1
  • Articles edited: 4
  • Comments Posted: 0

Recent articles by this author

Interactive version! "Persistent Chat" diagram

Community articleInteractive version! "Persistent Chat" diagram

Added by IBM contributor Jennifer Heins on September 23, 2008 | Version 1
expanded Abstract
collapsed Abstract
No abstract provided.
Tags: persistent chat, interactive, how it works, use case

Interactive version! "Persistent Chat" diagram

This use case takes the "Persistent Chat" diagram and uses mousovers to highlight where the action is taking place in the scenario. This prototype is part of the Information Development Center's research into providing information in different formats and with different types of media.

Tell us what you think . . . is this a helpful way to show you how it works?

Hover over a step to see the flow highlighted.

  1. User A logs in to the Sametime Standard server from the Sametime Connect client, and is authenticated using the LDAP server.
  2. The Sametime Advanced server obtains the list of persistent chats from the DB2 database server.
  3. The Sametime Advanced server presents the list of persistent chats to User A, who selects one.
  4. User A joins the selected chat and the Sametime Standard server advertises this to other users.
  5. The Sametime Advanced server notifies the WebSphere Event Broker server that User A has joined the chat.
  6. User B has subscribed to the persistent chat, so the WebSphere Event Broker server notifies User B that User A has joined the chat.
                       
expanded Attachments (0)
collapsed Attachments (0)
expanded Versions (4)
collapsed Versions (4)
Version Comparison     
VersionDateChanged by              Summary of changes
5Jan 9, 2009 3:46:30 PMJack Downing  IBM contributor
4Oct 2, 2008 10:23:40 AMJack Downing  IBM contributor
3Sep 24, 2008 8:52:52 AMWilliam Wise  IBM contributor
This version (1)Sep 23, 2008 5:47:23 PMElizabeth Bowling  IBM contributor
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedHelpAbout
  • IBM Collaboration Solutions wikis
  • IBM developerWorks
  • IBM Software support
  • Twitter LinkIBMSocialBizUX on Twitter
  • FacebookIBMSocialBizUX on Facebook
  • ForumsLotus product forums
  • BlogsIBM Social Business UX blog
  • Community LinkIBM Collaboration Solutions
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Accessibility
  • IBM Terms of use
  • Wiki terms of use