Has anyone tried using Microsoft NLB for Livecycle with JBoss clustering and get it working? Able to login to livecycle's admin ui page with the NLB IP
- 2 jboss application server (different IP address)
- Horizontal clustered
- LC ES2 installed on both servers
For those who setup successfully, hope you can share your experience.
Lionel, are you having a specific problem getting your configuration to work, or are you just looking for others using this combination?
I'm doing the same configuration but still haven't finished.
When installing, did you choose the "Partial turnkey (separated DB)" or "LiveCycle Only" and using the pre-configurated JBoss ?
I'm having problem getting it to work.. i have setup up a jboss (4.2.1) cluster and with LC on top of it. Clustering is with TCP not UDP as i have read that only TCP works for MS NLB. But after setting up the NLB, i can't access to LC admin page with NLB IP address.
I'm setting it up with pre-configured JBOSS. How about yours? i hope it's going fine
Actually I find the documentation a bit confusing. I'm trying to perform some tests and for that I have 2 Virtual machine (VMWare) and the windows NLB configured for those 2. But in the same LC documentation it says to run the installer normaly and proceed to configuration manager, whereas in another section says that we need to copy the pre-configured JBoss and do the configuration manually.
So, which should I follow? I just need to install Rights Management service.
If you are doing the LiveCycle setup manually (by this i'm referring to non-turnkey setup), then you are required to run the Configuration manager to configure LiveCycle environment, and manually configure JBOSS as an application server (E.g for Clustering, databse access & .. etc.)
The configuration manager will export the LiveCycle ES2 EAR files during the process and you will need to copy these EARs to JBOSS.
Are you reading "Configuring LiveCycle® ES2 Application Server Clusters Using JBoss" version 9?
Just a few more questions...hehehe
In the document: Configuring LiveCycle ES2 Application Server Clusters Using JBoss.
Page 35 item 3.4. Have you had to configure the Caching Locators? If yes, where did you put them, in only one machine or in all of the nodes?
On page 29, iten 2.7 (Testing the JBoss Application Server cluster) says that for testing we can run the command specifying the server, in my case is:
run.bat -c lc_sqlserver_cl -b <ipAddress>
But in the Appendix C: Configuring JBoss as a Windows Service, it says: call run.bat -c all -b <ipAddress>
So when should I start JBoss with "lc_sqlserver_cl" or "all" ?
The Caching Locators can be put anywhere (not necessary JBoss's nodes) as long as it's locatable by JBoss. It can run with 1 locator but you may put > 1 in case one locator fails to start or is dead.
If you configure with lc_sqlserver_cl then run.bat -c lc_sqlserver_cl -b <ipAddress> . LiveCycle Modified JBoss does not has the all folder which comes with orginal JBoss.
Good luck on the setup
Hey, just to let you know, I've got some problems with the Locators, and then I followed this article:
Let me know if you get succeed.
My jboss cluster is working fine with the locators.
Just wondering, did u start the locators? By default it's in %LiveCycle Root%\lib\caching\ . You will see a startlocator.bat . Run that in cmd to make sure it start successfully.
And you have to configure the run.bat as well.
Oh yes, I didn't mention that mine is working fine too. The locators are running and the 2 nodes are seeing each other.
But how did you get the MS NLB working? I can't get access to LC through NLB IP address. Did you have to include the NLB ip in somewhere in JBoss?
I suppose that as the MS NLB is already configured, once we follow the configuration (guide below) it's just a matter to turn on both nodes and should work, right? And also since the NLB is set up, we don't need to set up nothing on JBoss - e.g. section 6 of the guide below.
Is that correct?
I can't get it working too, i'm having the same situation as yours - can't access to LC admin with NLB IP.i suspect there's a clash between NLB cluster and JBoss cluster which caused the problem..
That's the reason i'm having this discussion here , hopefully anyone who has configure it correctly to provide feedback.
Any update on your side?
Yes, I got mine working after I changed to bind all address no the computer.
Go to page 30, the note in the top:
"When you start JBoss Application Server 4.2.0, to bind all addresses on the computer (including the localhost) you can specify -b 0.0.0.0 instead of the IP address of host name".
So I did this and now it's working.
I followed this thread: http://community.jboss.org/message/215486
I hope it helps.
How many NICs did you have for each servers? and for NLB what did you choose :Unicast or Multicast ?
Glad that it's working perfectly for you.
Haha, Network Interface Card (NIC), how many network adapters are you using? 1 per server?
So you have a single LC server in the NLB cluster at the moment?
I got it working too.. next step is to try getting Single Sign-On working.