Author Topic: What LDAP are you using with Cognos Access Manager 7.3 / 7.4 on Win 2008 R2?  (Read 4315 times)

Offline jeffowentn

  • Cognos Planning Developer and Cognos Sys Admin
  • Statesman
  • ******
  • Join Date: Jan 2009
  • Posts: 263
  • Forum Citizenship: +5/-0
  • IBM Certified Solution Designer/Expert
We currently have Cognos 8.4.1 FP4 BI and FP2 EP with Cognos Access Manager 7.3 and 7.4 on a largely Win 2003 R2 implementation sitting on SQL.  We are in the process of migrating to a Win 2008 R2 landscape and Sun One Java 5.2 LDAP does not seem to play nicely with Win 2008 R2.  So, what is the most popular option for a V3 compliant LDAP to sit under Cognos Access Manager for a mostly Cognos Enterprise Planning use of the environment (read that as nearly no Cognos BI functionality)?  Ideally, I would be able to export the current LAE from the old landscape and import it into the new landscape.

Thoughts?

It appears there are issues with users pulling through on ApacheDS 2.0 M15 through M20, although the hope was that M20 would address that issue.  So, it seems that might not be a good option.  ???

Your help is greatly appreciated.  Upgrading to Cogons 10.x is not an option.

Jeff

Offline jeffowentn

  • Cognos Planning Developer and Cognos Sys Admin
  • Statesman
  • ******
  • Join Date: Jan 2009
  • Posts: 263
  • Forum Citizenship: +5/-0
  • IBM Certified Solution Designer/Expert
It seems there are a number of options to consider:

ApacheDS
OpenLDAP
OpenDJ
AD/LDS

I am sure there are others.  Does anyone have experience leveraging one of these directory server tools or something else I should consider to replace Sun One Java 5.2 Directory Server? 

I'm in the middle of standing up the new environments, and time is of the essence.

Your help is greatly appreciated.

jeff

Offline MFGF

  • Never knowingly correct
  • Super Moderator
  • Statesman
  • ******
  • Join Date: Jul 2005
  • Posts: 10,222
  • Forum Citizenship: +620/-10
  • Cognos Software Muppet
It seems there are a number of options to consider:

ApacheDS
OpenLDAP
OpenDJ
AD/LDS

I am sure there are others.  Does anyone have experience leveraging one of these directory server tools or something else I should consider to replace Sun One Java 5.2 Directory Server? 

I'm in the middle of standing up the new environments, and time is of the essence.

Your help is greatly appreciated.

jeff

Hi,

It looks like the supported LDAP environments for use with Access Manager are

Microsoft AD
Sun
IBM (Tivoli) Directory Server

These are from the Supported Environments page:

http://www-01.ibm.com/support/docview.wss?uid=swg27038188#ds

The Access Manager Administrator Guide states that the directory server must be schema version 16 - that is the only schema version it supports. I imagine that if you can find a version of OpenLDAP or ApacheDS that uses the right schema version, it ought to work (although would be unsupported). If you have access to AD, I'd go with that :)

http://public.dhe.ibm.com/software/data/cognos/documentation/docs/en/7.5.0/accessadm.pdf

Cheers!

MF.
Meep!

Offline jeffowentn

  • Cognos Planning Developer and Cognos Sys Admin
  • Statesman
  • ******
  • Join Date: Jan 2009
  • Posts: 263
  • Forum Citizenship: +5/-0
  • IBM Certified Solution Designer/Expert
Thanks for the feedback, MFGF!  I'll have to look into that "schema version 16" bit.  I am not familiar with that.

Offline frankiet

  • Associate
  • **
  • Join Date: Feb 2016
  • Posts: 1
  • Forum Citizenship: +0/-0
I'm in the same position.  Would you please share which LDAP server you chose?

Offline jeffowentn

  • Cognos Planning Developer and Cognos Sys Admin
  • Statesman
  • ******
  • Join Date: Jan 2009
  • Posts: 263
  • Forum Citizenship: +5/-0
  • IBM Certified Solution Designer/Expert
I did not find a solution, and I got caught up with other projects.  Our plan is to stand up a separate Win 2003 box just for the LDAP and move everything else to 2008 R2.  If you find something else, let me know, but we tried a number of different things with no luck (could have been ignorance on our part).

 


       
Twittear