portal server deployment best practices

anyone out there knows what is the right way to deply portal server into production environment instead of manually copying all the folders and run the nessarily commands? Is there a better way to deploy portal server? Any best practices that i should follow for deploying portal server?

[301 byte] By [thaichingforum] at [2007-11-25 4:35:57]
# 1

From the above what I understood is you would like to transfer your existing portal server configuration to the new one. I don't think there is an easy method to do it.

One way You can do is by taking the "ldif " back up from the existing portal server.

For that first you have to install the portal server in the new box and then take back up of existing portal server using

# /opt/netscape/directory4/slapd-<host>/ldif2db/tmp/profile.ldif

edit the "/tmp/profile.ldif " file and modify <hostname> and <Domain name> with the new system values.

copy this file to the new server using

# /opt/netscape/directory4/slapd-<host>/ldif2db -i/tmp/backdb.ldif

and also copy the file "slapd.user_at.conf " under /opt/netscape/directory4/slapd-<hostname>/config to the new system.

Restarting the server makes you to access the portal server with the confguration of the old one.

708815 at 2007-6-29 2:48:41 > top of Java-index,Web & Directory Servers,Portal Servers...