PACLUG sametime presentation

3,582 views
3,480 views

Published on

PACLUG presentation by Andy Higgins
"Sametime from the Administrator side"

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
3,582
On SlideShare
0
From Embeds
0
Number of Embeds
1,930
Actions
Shares
0
Downloads
68
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

PACLUG sametime presentation

  1. 1. Sametime from the Administrator side Andy Higgins, IMCollaboration
  2. 2. Sametime Administration• Server Administration • Setup • Management• User Administration • Buddylist conversion • Stand-alone or Embedded – it makes a difference • Plugins
  3. 3. Server Administration - Setup• Check out “Sametime – zero to hero”• LDAP “mail” attribute• WAS properties and Wimconfig• LDAP with SSL• Ports used – e.g. SIP registration uses 5080/5081• Foreign characters in passwords• Windows 2008 IPv6 issues – make sure it’s turned off• Make sure the servers are all pingable• On Windows 2008 server “Run as Admin”
  4. 4. ST – server deployment and upgradesOrder of deployment• Upgrade to LDAP-based ST Community 8.5.2 server first (with mail attribute!) and convert buddylist• DB2 server• ST Console – register Community server with Console• ST Meeting server• ST proxy server can go on Console server• ST Media server should go on it’s own server• All servers at least dual proc with 4GB RAM – meeting (DB2) server needs disk space
  5. 5. Server Administration - Management• Policies – they’ve been moved• WAS management - similar to Domino • Deployment Manager, Nodes and Application servers – how do they work with Sametime? • Security – allows directory authentication, searching and SSL certificate management • Users and Groups • Debug • Media server is special • SPNEGO authentication
  6. 6. Websphere CELLA Cell is a virtual unit that is built of a Deployment Manager and one or more nodes.
  7. 7. WAS - explainedThe Deployment Manager is a process (in fact it is an special WebSphere instance) responsible for managing theinstallation and maintenance of Applications, Connection Pools and other resources related to a J2EE environment. Itis also responsible for centralizing user repositories for application and also for WebSphere authentication andauthorization.The Deployment Manager communicates with the Nodes through another special WebSphere process, the NodeAgent.The Node is another virtual unit that is built of a Node Agent and one or more Server instances.The Node Agent it the process responsible for spawning and killing server processes and also responsible forconfiguration synchronization between the Deployment Manager and the Node. Extra care must be taken whenchanging security configurations for the cell, since communication between Deployment Manager and Node Agent isciphered and secured when security is enabled, Node Agent needs to have configuration fully resynchronized whenimpacting changes are made to Cell security configuration.Servers are regular Java process responsible for serving J2EE requests (eg.: serving JSP/JSF pages, serving EJBcalls, consuming JMS queues, etc).And to finish, Clusters are also virtual units that groups Servers so resources added to the Cluster are propagated toevery Server that makes up the cluster, this will in fact affect usually more than a single Node instance.Thanks to Rafael Ribeiro from IT Developer World !!
  8. 8. WAS Concepts
  9. 9. WAS clusteringDon’t forget the load balancer !!
  10. 10. Sametime 8.5 clustered Domain
  11. 11. WAS menu itemsAt a pinch, the only places you really need to know aboutare the ones in red above
  12. 12. WAS SecurityAllows LDAP access for directory authentication and searching plus SSL certificate management
  13. 13. WAS LDAP access
  14. 14. WAS UsersCheck directory access by listing users
  15. 15. WAS usersNote that what gets returned is actually not correct (long-term bug in display only)
  16. 16. ST Media server
  17. 17. User Administration - buddylistBuddylist conversion – ST convertBuddylist manipulation (www.epilio.com)Ensure you set PC.ini for: • Buddylists from server buddyListContactPref=replaceLocal • Don’t ask the user showBuddyListConflictDialog=false
  18. 18. User Administration client configurationRolling out users• Stand-alone client • Push methods: Plugin_Customization.ini & Managed_settings.xml• Embedded client • Notes 8.5.2 embeds ST 8.0.2 by default • Need additional embedded plugin for ST 852 • Push methods: Plugin_Customization.ini & Managed_settings.xml • Additional push options – Domino Policy & Eclipse advanced options
  19. 19. User administrationUser setup• Domino Policy (embedded only) – manages the ST community server and the SSO policy• Plugin_customization.ini • Case sensitive!! • Special for 8.5.1.1• Managed_settings.xml• Sametime policy – manages other ST parameters
  20. 20. Domino ST PolicySametime community server defined here
  21. 21. Domino ST IM policySametime server defined here with SSO options tooThe policies here were for older versions of the embedded client and today the wayto do it is using plugin_customization.ini
  22. 22. Resetting the community server This will work for both stand-alone and embedded users but is actually the only way you can force the change on the Stand-alone client without a re-install
  23. 23. Key change in V8.5.1.1 ST clientThere was a key change made in the latest Sametime8.5.1.1 client which allows the plugin_customization.inito be read during the Notes client startup vs only onetime when the client is reset. This allowsadministrators to push out the plugin_customization.inito the client and when the client restarts, itll read thefile.So in effect, the best way to manage these settings aswe move forwards is with the plugin_customization.inifile
  24. 24. Policy - EclipseI haven’t seen these work successfully yet
  25. 25. Plugin_Customization.iniFile found in “C:LotusNotesframeworkrcp” for embedded clientor “C:LotusSametime Connectrcp” for standalone clientcom.ibm.collaboration.realtime.community/savePassword=falsecom.ibm.collaboration.realtime.community/loginByToken=truecom.ibm.collaboration.realtime.community/loginAtStartup=truecom.ibm.collaboration.realtime.community/name=STCommunitycom.ibm.collaboration.realtime.meetings/hideLegacyMeetingUI=truecom.ibm.collaboration.realtime.community/host=community.server.comcom.ibm.rcp.managedsettings.provider.file/URL=http://community.server.com/sametime/managed-settings.xmlcom.ibm.collaboration.realtime.community/defaultAuthType=TAM_SPNEGOcom.ibm.collaboration.realtime.community/authServerUrl=http://auth.server.com/snoop/snoopcom.ibm.collaboration.realtime.community/useAuthServer=trueAdditional question to IBM – which managed-settings do we use when we have onehere in the PC.ini file and there is one in ST policies too?
  26. 26. Managed_settings.xml<ManagedSettings><settingGroup name="com.ibm.collaboration.realtime.meetings"> <setting name="hideLegacyMeetingUI" value="true" isLocked="true"/></settingGroup><settingGroup name="com.ibm.rtc.meetings.shelf"> <setting name="serverName" value=“meeting.server.com"/> <setting name="serverPort" value="80"/> <setting name="useHTTP" value="true"/> <setting name="communityServerName" value=“chat.server.com"/> <setting name="useCommunityCredentials" value="true" /></settingGroup></ManagedSettings>
  27. 27. Sametime Policy
  28. 28. Sametime user policies
  29. 29. Sametime policies• User must set this community as the default server community• Allow user to add multiple server communities• Allow user to add external users using Sametime Gateway communities• Allow user to save chat transcripts• Automatically save chat transcripts• Etc….
  30. 30. PluginsCheck out this link:Deploying Plug-ins and Widgets for Lotus Notes and Sametime
  31. 31. WAS install issuesCheck out this link to IBM documentation on WAS install errors
  32. 32. Using the ConsoleA good link to Console information
  33. 33. Contact detailsAndy Higginsandy@imcollaboration.com++1 (512) 426-6142www.imcollaboration.comhttp://sametimedg.blogspot.com/

×