Anand Iyer commented on Jan 5, 2009

MS Active Directory Error Resolved

This is a follow up to my previous post. Turns out that the StandAlone LDAP configuration setting does not work with IBM Mashup Center. You need to use Federated Mode repository configuration. See the following link on how to configure LDAP in a Federated Mode:

{ Link }

Anand Iyer commented on Dec 30, 2008

Getting the exact error with MS Active Directory as mentioned in one of the posts above

Has anyone been able to get MS Active Directory to work with the Mashup Center? I am also getting this error:"BMWMB0039E:Fail to load page. The error message is: Error - BMWMF0001E:Node must not be null. Please contact Lotus Mashups administrator."

Would PK63326 resolve this issue?

Hans Prummel commented on Dec 19, 2008

Unable to get it to run with MS Active Directory

Anyone got lucky with resolving this issue on MS Active Directory? I'm still having the error as mentioned, "BMWMB0039E:Fail to load page. The error message is: Error - BMWMF0001E:Node must not be null. Please contact Lotus Mashups administrator."

Stanley J Bradbury commented on Dec 7, 2008

pk63326 will impact many LDAP servers

This article states that the defect will impact all users of VMM on WAS 6.1 (which Mashup Center does). You can get the details here:

{ Link }

Run Wang commented on Dec 3, 2008

Did anyone get the same error with Sun One LDAP?

I tried to config Mashup Center with Sun one LDAP, and got the same error.

Will these steps mentioned here help?

(a) install the WAS 6.1.0.15 fixpack on to the default installation of WAS 6.1.0.13

(b) install PK63326

Judy Burkhart commented on Oct 14, 2008

Problem should be fixed

It looks like the problem was related to a DB2 password change. Should be fixed now.

Thanks

Judy

Gregory Melahn commented on Oct 8, 2008

BMWMB0039E:Fail to load page

I also see this error message on what was a working mashup server until a few minutes ago - what does this error message mean?

"BMWMB0039E:Fail to load page. The error message is: Error - BMWMF0001E:Node must not be null. Please contact Lotus Mashups administrator."

Dave Hay commented on Oct 8, 2008

Lotus Mashups and Lotus Domino LDAP

Just to close the loop. I did another clean installation of Lotus Mashups ( InfoSphere MashupHub and Lotus Mashups ) and, thanks to some excellent advice from Karen and Kris, was able to get the integration with Domino LDAP working.

I'll document this more fully when time allows but, suffice to say, the key trick was to: -

(a) install the WAS 6.1.0.15 fixpack on to the default installation of WAS 6.1.0.13

(b) install PK63326

{ Link }

Once I'd done this ( having already gone through the WAS -> Domino LDAP configuration once or 500 times ), all worked.

PS Am using Domin 8.0.1 if it helps.

Have now made some progress with the IBM Widget Portlet ( which was the original reason that I did this in the first place ), using the same Domino LDAP to provide single sign-on via LTPA to the two WAS 6.1 servers ( one running Portal, one running Mashups )

Right, that's enough for now ....

Dave Hay commented on Oct 6, 2008

Lotus Mashups and Lotus Domino LDAP

Hmmm, despite moving up to WAS 6.1.0.19 and a plethora of related fixes, I'm still seeing: -

BMWMB0039E:Fail to load page. The error message is: Error - BMWMF0001E:Node must not be null. Please contact Lotus Mashups administrator.

when I attempt to log into the Lotus Mashups server. I can, however, log into the corresponding WAS console, and also into the MashupHub.

Strange ......

Dave Hay commented on Oct 5, 2008

Broken Link ?

Hmmm, Lotus Mashups 1.0 ships with WAS 6.1.0.13, but there is no corresponding PK63326 fix for that release of WAS, as per: -

ftp://ftp.software.ibm.com/software/websphere/appserv/support/fixes/PK63326/

I'll try hooking LM up to Domino LDAP and see what happens ....

Dave Hay commented on Oct 5, 2008

Broken Link ?

I get: -

HTTP Web Server: Lotus Notes Exception - Entry not found in index

when I click on the link to the WAS fix: -

{ Link }

I'm assuming that the link should point here: -

{ Link }

which contains fixes for WAS 6.1.0.0, 6.1.0.15 and 6.1.0.17.