|
Home > Archive > WebSphere Portal Server > November 2006 > Sametime and Portal 6
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Sametime and Portal 6
|
|
|
| Hello,
the following message appears in my sametime contact list. The online status is not working.
My environment:
- Portal server
- Domino server 7.0.1 FP1 as ldap
- Domino server 7.0.1 FP1 with ST 7.5 FP1
- web sso is working fine
- sametime.ini has the trusted server line
- collabrorative services are configured
-------------------------------------------------------------------------------
Sametime Contact List allows users to work with Sametime Instant Messaging on a Sametime server with all Sametime users in your organization. Users can chat, display only online names in the list, sort the list, modify a status message, or modify groups.
To configure, contact your portal administrator.
Logged Out
Sametime Contact List not found.
--------------------------------------------------------------------------------
Any ideas?
Marcel
| |
|
| We got it to work with a slightly different configuration. Sametime uses native domino authentication in our situation
[b]CS_SERVER_SAMETIME.enabled=true
CS_SERVER_SAMETIME_1.hostname=yourname.yourcompany.nl
CS_SERVER_SAMETIME_1.version=7.5[/b]
# The protocol and port that the ST server uses
# to serve up HTML, CSS and JavaScript files, etc.
[b]CS_SERVER_SAMETIME_1.protocol=http
CS_SERVER_SAMETIME_1.port=80[/b]
#
# Optional advanced settings
#
# Class that provides the ST user login name, token, and whether ST is enabled for this user
[b]#CS_SERVER_SAMETIME_1.initclass=com.ibm.wkplc.people.tag.AwarenessInitLwp[/b]
# Specify whether to use the LTPA token for logging into Sametime from the browser.
# If the CS_SERVER_CUSTOM_CRED is enabled and the ssoTokenAttrib is specified,
# it will be used instead of the LTPA token.
# This option should only be turned on if your Sametime server supports tokens
# produced by the portal server.
# By default an LTPA token is enabled (preferred).
[b]#CS_SERVER_SAMETIME_1.useLTPAToken=true
[i]Yes we did comment this line out. Single signon is still working now![/i][/b]
# The following Sametime settings pertain to the server-to-server connection
# between the portal server and the ST server. This connection exists for the
# sole purpose of obtaining Sametime tokens for users. These tokens are then
# used to log users into Sametime from their web browsers.
# Port that the ST server app should connect through.
# The default connection is configured to connect through the Sametime
# mux. If you want to connect directly to the server, set the port explicitly.
[b]# CS_SERVER_SAMETIME_1.serverappPort=1516[/b]
# Sametime reconnect interval (in seconds).
# How often to attempt a reconnect to the Sametime server after being
# disconnected, or not connected.
# Use 0 to indicate that we should not attempt to reconnect.
# If not set, the internal default of 30 seconds is used.
# Lowering this value will allow the portal server to reconnect to the Sametime
# server more quickly when the Sametime server comes back online.
# However, this may increase the portal server workload and network traffic.
[b]# CS_SERVER_SAMETIME_1.reconnect=10[/b]
# Sametime timeout value (in seconds).
# The maximum amount of time to wait for a response from the Sametime server.
# If not set, the internal default of 15 seconds is used.
# Lowering this value will decrease the potential amount of time that a user
# might have to wait to login to the portal.
# However, if the Sametime server is slow to respond or the network is slow,
# increasing this value will allow portal users to have Sametime connectivity.
[b]# CS_SERVER_SAMETIME_1.timeout=50[/b]
# Specify the name format to use when resolving the WPS
# logged in user with the Sametime server. Note that use of this flag will
# force the name to be resolved even if the useLTPAToken flag is set to true.
# This resolved name will be used to login to Sametime.
# Valid values are cn/dn/loginName
[b]CS_SERVER_SAMETIME_1.nameFormatForResolve=dn[/b]
# Specify the character to use to separate distinguished names. This
# character will be used when resolving names with the Sametime server,
# and also for the name used to login to Sametime from the browser.
# Valid values are the single character comma (,) or slash (/)
[b]CS_SERVER_SAMETIME_1.dnNameSeparator=/
#CS_SERVER_SAMETIME_1.dnAuthorSeparator=/[/b]
# Tells the person tag what name format to send to Sametime.
# If the Sametime server is configured to accept only the name format email or dn,
# specify email or dn as the value. If the server is configured to accept cn, this setting is unnecessary.
# Default is to use the common name.
# Valid values are cn/dn/email.
[b]#CS_SERVER_SAMETIME_1.watchnameformat=dn[/b]
# Tells the Sametime server whether the names that the person tag sends need to be resolved.
# For better performance, set to false.
# Only set to false if you are sure that Sametime will accept the name format (the CN by default or, if specified,
# the watchnameformat setting) without having to resolve the name further.
# For greatest compatability with various LDAP setups, the default is true.
[b]CS_SERVER_SAMETIME_1.resolveNames=true[/b]
I have tested lots of settings in order to get sametime to work together with the portal and this configuration was the only way I could get it to work. Configuring Sametime to use LDAP authentication or native authentication likely results in other setti
ngs in the CSEnvironment.properties file.
One note though. Do not install IE7 because Sametime will not work with the portal anymore.
Joep Daandels -- Acuity
| |
|
| Hi Joep,
thanks, but in our environment it doesn't work.
Have you one domino server for authentication (ldap) and another domino for sametime (native directory) ?
Marcel
|
|
|
|
|