|
Home > Archive > WebSphere Portal Server > May 2007 > Domino Web Access Portlet ( automatic mail detection)
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 |
Domino Web Access Portlet ( automatic mail detection)
|
|
|
| We didn't have domino ldap, we are using IBM Tivoli Directory server as the ldap. I had lot of issues doing this then finally open a PMR. Below is workaround if you are doing automatic mail detection using external LDAP:
Task 1: Set up SSO between Websphere and Domino
Task 2: Enable DIIOP on Domino
Task 3: Modify CS.Environment.properties file, following is an example:
========================================
=======================================
########################################
######################
#
# DOMINO DIRECTORY properties
# (LDAP server)
# Important:
# Should always point to a Domino Server.
# Leave enabled flag as true.
# Use the custom_ldap_* settings to point to a any LDAP Server to
# get user information.
########################################
######################
CS_SERVER_DOMINO_DIRECTORY.enabled=true
CS_SERVER_DOMINO_DIRECTORY_1.hostname=ldapHost.decisionlabs.com
CS_SERVER_DOMINO_DIRECTORY_1.port=389
CS_SERVER_DOMINO_DIRECTORY_1.ssl=false
CS_SERVER_DOMINO_DIRECTORY_1.anonymous=false
#Custom LDAP search base
CS_SERVER_DOMINO_DIRECTORY_1.custom_ldap_searchBase=o=decisionlabs.com
# custom attribute enabled for mailfile and mailserver
CS_SERVER_DOMINO_DIRECTORY_1. primary_ldap_custom_attribute_enabled=tr
ue
#Make Sure to have this line
CS_SERVER_DOMINO_DIRECTORY_1.query_user_mailserverfile=(&(objectclass=person)(|(uid=%c)(cn=%c)))
# Additional mail file attributes
CS_SERVER_DOMINO_DIRECTORY_1.mailserver_attrib=mailserver
CS_SERVER_DOMINO_DIRECTORY_1.mailfile_attrib=mailfile
########################################
###################
# Add Default IIOP/SSL Port
########################################
##################
CS_SERVER_DOMINO_DIRECTORY_1.iiopport=63148
# Optional LDAP User credential overrides
# default - uses Portal credentials or anonymous
# Use tool PropFileEncoderPassword.bat to encrypt the password and copy
# the encrypted password to this file.
CS_SERVER_DOMINO_DIRECTORY_1. userid=uid=wpsLDAPBind,cn=users,o=decisi
onlabs.com
# password for wpsbind
CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd={x}ssbm1s
########################################
######################
========================================
=======================================
Feel free to provide your feedback or any questions.
-DV
dvpunia@decisionlabs.com
| |
| Sebastian Fratini 2007-05-08, 1:19 pm |
| Hi
Did it work for you with this? I had the same problem with Domino LDAP. I wanted to configure it with the Bind User but for some reason it wasnīt working so I enabled anonymous access and then it worked.
Also I think because of this Sametime isnīt working either.
I am going to post something about my ST issue later on.
Regards,
Sebastian "Jack" Fratini
IBM Certified System Administrator
Sebastian.Fratini@e-nsx.com
NSX SA
| |
|
| If you are using domino then you can use any Admin user who has enough admin right to browse database and so on. Provide the user bind info in CS.environment file. I tried with both ( external ldap=> IBM tivoli Directory server and Domino LDAP as well).
Sametime is different, when you run LCC-configure... task on wpconfig file it uses the bind ID from WPconfig.properties file for LDAP, when you use domino web access portlet, it will use cs.environment properties file, you don't need LCC-configure-dominod
irectory task on wpconfig for DWA portlet.
If you are using wpsbind, make sure the user has enough access, in other words he should be part of admin group who can do query on ldap and browse database without any acl issues, that should fix the problem.
-DV
dvpunia@decisionlabs.com
|
|
|
|
|