Re: replicated LDAP on IBM i using PowerHA GlobalMirror

It turns out this other consulting company was using an OEM software
product called JXplorer to manage the LDAP entries. That product
communicates on port 389 and is completely agnostic about what LDAP it's
connecting to, UNTIL, you try and change any part of the tree. Then since
it has no idea it's talking to IBM i it clobbers the configuration file in
QUSRSYS. From IBM i's perspective the LDAP is now completely gone. With
IBM support we were able to get the configurations rebuilt and both LDAP
servers are happily running again.

I'll have to wait until the other consulting company is done with their
part of the project, then I will do as you just demonstrated and move the
libraries into the iASP, solving 90% of the problem. The other 10% is to
keep the objects in QUSRSYS sync'd up however they don't change much so a
periodic refresh is possible.

Thanks for following up.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On Sun, Jul 22, 2018 at 4:36 AM, Marc Rauzier <marc.rauzier@xxxxxxxxx>
wrote:

Le 10/07/2018 à 20:25, Jim Oberholtzer a écrit :

Marc:

I highly doubt it as the LDAP server is really a piece of Tivoli code that
runs on IBM i , with some PACE parts.

As you point out, what should be happening is the Tivoli server set up
and
then use the replication function that is built into it to push it to the
other servers. In this case I have an OEM software product and an outside
consulting company for that OEM vendor telling me that's not how they want
it done. The whole thing is very V4R5ish in my view, which becomes the
root
cause of the problem.

Sometimes you just gotta let them do what they want.

Sure.

However, and even after 12 days, I was just curious about the IBM Tivoli
Directory Server settings available through "Navigator for i" (the web
admin interface).

I created an ldap instance (TESTIASP) with its wizard and selected an IASP
as the storage disk pool for all the various objects (configuration library
and directory, change log library, database library) of the instance. The
wizard created the TESTIASPDB, TESTIASPCL, TESTIASPCF libraries in the IASP
and the /IASP/QIBM/UserData/OS400/DirSrv/idsslapd-TESTIASP directory with
all the required sub-directories and configuration files.

I did not try to reconfigure an existing one from SYSBASE to an IASP, but
at least for a new server to be created in the IASP, it works.

For the records.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD