what is correct procedures for doing replication in installing Portal
I have a server
OS is solairs 9
install :
Application Server 7
Directory Server 5.1
Calendar Server
Portal Server 6.1
Now I try to do load balance and Disaster Recovery , i msut install another Portal Server in other computer and useing its Directory Server by
replication of primarily Directory Server.
I need to install these different softwares; however I don't know what the procedures are for doing replication.
What is the correct procedures for doing replication?
and two different steps I try but failure ...
1. install Directory Server and replication userRoot from primarily Directory Server but failure to install Portal Server .
2. install Directory Server , Calendar Server and Portal Server then do replication userRoot from primarily Directory Server but failure in restart Portal instance in Aplication( it tell me cn't connect Portal server).
somebody have the same experience to do replication and Can tech me how to complete this problem ?
thank for your help.
# 1
FIRST of all use the current version of portal (and the other components)AND the thenWHICH component do you want to load balance or MMR- Portal - Access Manager- Directory Server?cheers/u
# 2
Portal and Directory Server components I want to load balance.
# 3
Ok, most of the time I do it the following way:
Install DS1
Install DS2
Create Replication Aggreement between the 2 Servers, both Masters.
Now, after doing this, I test the Replication by adding something e.g. an user to the replicated root on DS1 and deleting it then on DS2.
Now, I install Access Manager, which is needed by the portal on AppServer1. Then I install AM on AppServer2.
Important: Use the Loadbalancer URL to access the DS server during installation.
Restart the Appservers now and try to login to both servers using http://appserver/amconsole/ as amadmin
Please dont forget to add the second server and the LoadBalancer URL to "Organisation Aliases" and to Service Configuration -> Platform-> Server List or you cannot login on AppServer2.
Now you have to edit the fqdnMap property of the AMConfig.properties file. It should be something along:
I_dont_remember.fqdnMap[loadbalancerurl] = loadbalancerurl
Now, the AM should be accessible fully using the LB Url. Now install portal.
# 4
in open mode (without gateway component) you need to have at least one hard- or software loadbalancer (lb)
client req -> lb
-> PS/AM(1..n)
-> DS (1..m) in MMR
or
-> lb
-> PS/AM (1..n) -> DS(1..m, m<=2 or 4) in MMR
or with the current version a spilt of PS and AM is possible and allows a more complex environment, such as
client req -> lb
-> PS (1..n)
-> AM (1..m)
-> DS (1..k) in MMR
In any case SWITCH to the current version (if possible)
:-)
HTH
/u
# 5
Hi thank for helpbut Now My portal is on-line..Would it be possible to build new directory , identy and portal in other machine and replication on-line's directory data for doing load -balance ?
# 6
Yes.
Simply install the second DS, create a Multi Master replication agreement and initialize the new one from the existing one.
Now install AM and PS on the second one. Follow the steps I wrote already. First try to get DS up and running, then AM and at last PS.
hth
Chris
# 8
Sorry CRabel
have a little problem
when I simply install the second DS in b machine , create a Multi Master replication agreement
bec in my Portal Server (6.0.1) installing source , Identity Server (AM) and Portal Server are installing together.
Now I need to install second Portal Server in b machine domain is abc
in install .....it'll ask me installation summary ?
.....
What is the hostname of this server? [abc]
What is the sub-domain name for abc? (. for none) [xxx]
What is the domain name for abc? [xxx.xx]
What is the ip address of abc.xxx.xxx.xx? [123.1XXXXX.XXX]
Use an existing Directory Server? [y]/n
Use the local Directory Server? y/[n] y
--
in these item ....
what's hostname I need to Choice? is abc or Loadbalancer URL
Tks
# 9
Hi!Use the hostname of the current machine during installation of AM. Only afterwards you configure the AM for loadbalancing.This is simply done by adding the LB to the fqdnmap in AMConfig.properties and to the organisation alias(es) entry.hthChris
