LSF 10.0.3 ldap changes

Jimmy,
Are you on Windows? If so, this may be an issue with binding to localhost

Kwane

Just to be clear: Are you talking about the DB2 (security) database.. or the ldap that you bind to for authentication?

On Windows box I had to use the ip address for the ldaphost. I could not use server name in any form. But this was not really an ldapbind issue, as we are bound to a corporate dc not the lsf server.

On windows, your application server can not be the same as the ldap(Tivoli or ADLDS) server. The updated installation guide for 10.0.3 also lists ldap server as a seperate server.

I was upgrading my 10.0.2 test server (standalone) and ran into this error. The support was no help of course and referred me to professional service as usual. After alittle digging, I created a seperated ADLDS server and I was able to get it installed.

That's weird. I can't think of any logical reason if can't be. Hmmm....
Now I do recall there being issues when using the name 'localhost' on Windows 2008R2.

Another idea may be to bind a second IP to the server, and do it that way?

Kwane

Posted By Jimmy Chiu on 06/10/2013 02:48 PM
On windows, your application server can not be the same as the ldap(Tivoli or ADLDS) server. The updated installation guide for 10.0.3 also lists ldap server as a seperate server.

I am going to disagree. I have 10.0.0.3 running with LDS on the same server with no issues, either during the installation or during operation. This is from page 109 of the 10.0.3.0 installation guide, published May 2013: "The LDAP server is the machine where the LDAP software is installed. It can be the same machine as the Lawson server or a remote machine. Use the machine name and domain name to identify the server."

Hmm... going to redo the install again. Maybe just me.

Kwane is right. There seems to be problem with the installation program fails to resolve the DNS name when the APP server and LDS server are on the same server. (At least on mine). I used IP address instead and it works.