Running Netscape LDAP Server on a Separate Machine

I have been tasked to separate the various Netscape servers onto separate Sun machines.  Presently the Messaging (for the mail server), Enterprise (for the web server), and the Directory (for the LDAP server) are all running on the same box.  The Web server needs LDAP for the ACLs.  For mail, all mail is routed through a "relay" machine listed in the SMTP Routing Table.  Relay is set to "search by user ID" and "search using truncated domain (drop host part if local)."  I think that themail relay process uses LDAP for the "search by user ID" part.  It must be using DNS for resolving the destination server address?

This question is about moving LDAP, the Directory Server.  

We have many sites, but each has its own LDAP server.  A replication agreement keeps the user entries synchronized.  The reference is to ldap.domain.myproj.org, so for the satallite sites a simple DNS change that will make the transition to a new "Master" LDAP server.  Then the replication agreements will have to be added.  

But moving LDAP to a separate machine and turning off the LDAP process on the web/mail machine I need help with.  There is a "Referral Mode" that is used to redirect client applications to another Directory Server while the current server is unavailable: http://enterprise.netscape.com/docs/directory/61/ag/intro.htm
This will do the job but it is intended for a temporary solution and the original LDAP is still running...

Has anyone built an Netscape Server system on mulitple platforms?  How can it be done?
huffmanaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

yuzhCommented:
To minimize the impact of the server change on you whole network. I think it is a lot
easy to setup the Web/Mail server to a different box and make the new box as a
LDAP client. (the httpd.conf, sendmail.cf.... and the webpages, mailbox, aliases you
can easyly copy accross).

Then you change the DNS record to make the new box  as the webserver/mail server,
disable the web/mail service from the LDAP master server, and your don't have to
worry about the other clients.

0
huffmanaAuthor Commented:
I take it that the Netscape Web/LDAP servers are designed to run on the same machine, and the same with the Mail/LDAP servers.  Is this true?  

I guess that is accomplishes the same purpose of separating the servers into specific entities (i.e., Web server machine, LDAP server machine, and Mail server machine). At least one server failure doesn't bring down the entire Web/Mail/LDAP system.

I would like to follow your recommendation and leave the LDAP in place but it is presently running on the only good Sun server that we have (Enterprise 450). Web is going to an Ultra 10 and LDAP is going to a Sun Blade 150 :-( Mail will be staying on the Enterprise 450.  
0
yuzhCommented:
If you want to use the Sun Blade 150 for LDAP, the Sun Blade should use the same hostname and IP as the original name of Enterprise 450, and  the Enterprise 450 had to change to use
a new name and IP, to have a seperate Web/mail server is a good idea (when you have enough
boxes!).

There is a trick in here, you need to build the Sun Blade 150 first (test it and then put it back
to the network after your shultdown the E450).  

Do you have any application software license which is depand on the hostid? if you need to
move the software to a different box, you need to contact the software vendor, to get a new
license, otherwise the app will not work.
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

yuzhCommented:
You might want to "move" the E450 to the Sun Blade 150, have a look at the following
page about how: (I wrote the procedure long time ago, and it works for me):

http://www.experts-exchange.com/Operating_Systems/Solaris/Q_20537122.html

After the "move", you can then get rid of all the unwanted services/software etc, and patch it,
test, before put it alive.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
huffmanaAuthor Commented:
Turns out that the attribute copiedFrom is all that distinguishes a master slapd from a slave server.  If a ns-slapd ldif2db -f slapd.conf -i an_archived_ldif_file is run with the copiedFrom attribure in the ldif file it makes a slave server.  vi the ldif file and delete the copiedFrom line then run the ns-slapd command and it makes a master ldap server.  There are configuration switches that have to be set for address completion and stuff like that.
0
yuzhCommented:
Good to heard that you  completed the job, cheers!

yuzh
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.