Posts tagged clustering
- Pankaj Parashar, Lead Softweare Engineer @ Adobe
Adobe LiveCycle comes with pre-configured JBoss (Community Edition only) . The preconfigured JBoss has both standalone and cluster-enabled configurations. All cluster-enabled configurations are based on UDP by default. Various enterprise organizations have very restrictive network policy and don’t allow multicasting in their networks. For such organizations, TCP based clustering is recommended option. JBoss instances belonging to different subnets require TCP based clustering only. In this article, we will go through detailed instructions to configure TCP based JBoss cluster. These instructions are applicable for both preconfigured JBoss and downloaded JBoss (Version 5.1 only).
The Following are the detailed instructions for TCP Clustering:
Read the complete post at Adobe LiveCycle Blog.
- Pankaj Parashar, Lead Software Engineer @ Adobe
Sometimes while running LiveCycle on JBoss Cluster, you may see the following log messages appearing in server logs. WARN [org.jgroups.protocols.UDP] discarded message from different group “DefaultPartition” (our group is “LIVECYCLE-CLUSTER”). Sender was 10.56.78.90:54356
Read the complete post at Adobe LiveCycle Blog.
– Samartha Vashishtha, Content and Community Lead @ Adobe
We’ve added a brand new section to the Installing the Correspondence Management Developer’s Guide explaining how you can set up author-instance clustering for Correspondence Management.
When the Correspondence Management solution is deployed, the author instance runs on the same server as LiveCycle ES3. However, setting up the LiveCycle cluster doesn’t automatically configure the Correspondence Management author-instance cluster. You must set up this cluster manually.
Author-instance clustering has no dependency on LiveCycle clustering. The LiveCycle cluster acts as a backend system for author instance clustering when LiveCycle is integrated with the Correspondence Management solution. The shared nothing mode of clustering is supported for Correspondence Management.
You can read the full technical article here.
LiveCycle product blog has recently published a nice article that allows you to check if the LiveCycle scheduler has started properly in cluster mode or not.
Thanks LiveCycle team for publishing the details.
The blog entry can be found at – http://blogs.adobe.com/livecycle/2011/02/schedulerclustermode.html
Original article at http://blog.pandyaparth.com/2011/02/determining-if-the-livecycle-scheduler-has-started-in-cluster-mode/.
To configure Apache Web Server, see here.
Microsoft Windows Server 2008 R2 comes with IIS 7.5
IIS 7.0 comes with Windows Server 2008. Microsoft re-architected IIS in version 7.0 to be more modular like Apache Web Server. Metabase was removed.
As a result, configuring IIS 7.5 to load-balance a LiveCycle cluster (whether it is WebSphere, WebLogic or JBoss) is now simple and straightforward. You don’t need to make any changes on the J2EE app servers.
The following instructions assume that the IIS 7.5 instance is dedicated. For a shared IIS instance/farm, you will have to modify some of these instructions. Also, Microsoft’s AppCmd can be used to script all of these. AppCmd is a command line utility to manage IIS via commands and scripts. It is different from PowerShell.
For handling complex environments, the URL Rewrite module will be very useful.
1) Add the role “Web Server (IIS)” on Windows Server 2008 R2
– Use the menu Administrative Tools->Server Manager
– Choose Roles (there are about 17 roles defined in Windows Server 2008 R2 standard edition)
– Add Roles, then Web Server(IIS)
– Make sure “Directory Browsing” is unchecked (it is checked by default)
– Check “HTTP Redirection”
– Click Install
– Re-start the server
2) Install Application Request Routing (ARR)
You can download it here. Once downloaded, run ARRv2_setup_amd64_en-us.exe Once finished, check the install log in %USER_TEMP% and make sure that all of the components installed fine. You don’t want to see the following:
rewrite_amd64_en-us.msi Failed Status Code 1603
webfarm_amd64_en-us.msi Failed Status Code 1603
requestrouter_amd64_en-us.msi Failed Status Code 1603
ExternalDiskCache_amd64_en-us.msi Failed Status Code 1603
3) Using IIS Manager, create a new “Server Farm”
Start Internet Information Services (IIS) Manager. If the installation of Application Request Routing is successful, you should see a new node in the left pane under “Sites” called “Server Farms”.
– Create a new “Server Farm”
– Name it with something meaningful like LC_TEST_CLUSTER
– One by one, add all of the members of your LiveCycle cluster. For each, make sure that you click the ‘Advanced Settings” and provide the completely qualified DNS name (eg: server1.company.com), HTTP port (eg: 8001 for WebLogic) and HTTPS port (eg: 8002) of each of the cluster members.
– Save the “Server Farm” definition. Say “Yes” to the creation of an InBound URLRewrite Rule.
4) Configure the new “Server Farm”
– Click on the new Server Farm. On the right pane, dbl-click ‘Caching’. Make sure that for ‘Query String Support’, “Include Query String” is chosen.
– On the right pane, dbl-click ‘Load Balance’. For ‘Load Balance Algorithm’, you can choose “Weighter Round Robin” or another that makes sense to your environment (test). For ‘Load Distribution’, you can choose “Even Distribution”. If the cluster members are not all alike in their capabilities, you can choose “Custom Distribution” and assign a higher weight to a more capable cluster member so that more requests get routed to it.
– On the right pane, dbl-click ‘Routing Rules’. Make sure that the checkbox for “Use URL Rewrite to inspect incoming requests” is checked. If it is not, check it and click ‘Apply’ on the top right to save.
– On the right pane, dbl-click ‘Server Affinity’. Make sure that the checkbox for “Client Affinity” is checked.
– Exercise your application from multiple client machines (with different IP addresses)
– Verify in IIS Manager. Click on the Server Farm. On the right pane, dbl-click ‘Monitoring and Management’. Check under the column ‘Total Requests’ and make sure that all members of the cluster received requests.
Original article at http://blogs.adobe.com/livecycle/2011/03/configuring-iis-7-5-to-load-balance-a-livecycle-cluster.html.