David said...Nice write up. Thank you.
Binh Nguyen said...Thanks, very helpful post
Mohamed Amin said...this point is not clear for me Add a cluster entry, This can be a comma-separated list of "IP/DNS_Name:port", a DNS name that maps to multiple IP addresses or the local machine if all servers run on one machine"
if I have 2 nodes and I need to publish Forms service to be High Available in case if one node fails, the other still works, I will put for example node1:9000,node2:9000 ?
Yes. That's fine, but I would suggest using fully qualified names, like node1.company.com:9000, node2.company.com:9000.
Mohamed Amin said...Hi
thanks for replay, but again if user was connected to node1.company.com:9000 and this server failed . how will he move to the other one without relogin to the system ,
I mean how this will be transparent to the user moving from server one to server two in case of failure in server 1 , in case we have two names ?
In the "Replication" tab of the cluster in the Admin console, you can define how sessions are managed in the cluster to allow session failover.
To cope with server failover, you must front the system with a load balancer. This might help.
Pancho said...This tutorial its excellent, but just for security, add this step as the first one enrolling the second node to the primary node: setWLSEnv.sh and also nodemanagers has to use the same port, acording to my experience. Regards!
DO NOT ask technical questions here! They will be deleted!
These comments should relate to the contents of a specific article. Constructive criticism is good. Advertising and offensive comments are bad and will be deleted!
If you post personal information (name, email address etc.) you are agreeing to them being stored and displayed. Feel free to remain anonymous.