In this article, I will show you how to create a two-node Weblogic 12c cluster using only the command line. Oracle Weblogic (formerly BEA Weblogic) is one of the most resilient, reliable and high-performance J2EE application servers that I’ve worked with. I’ve used it to host both custom applications, as well as commercial applications that required an enterprise-grade J2EE container to serve them.
The lab topology will be as follows:
|
Weblogic Server |
Hostname |
IP Address |
Port |
Cluster Name |
| AdminServer | dolan | 172.16.18.169 | 7001 | N/A |
| test_managed_server_1 | dolan | 172.16.18.169 | 7002 | TestCluster |
| test_managed_server_2 | gooby | 172.16.18.172 | 7002 | TestCluster |
As you can see, AdminServer only runs on a single node. Once the managed servers have been configured and started for the first time by way of the administration server, they can be restarted independently - thus the loss of the administration server does not impact the general running of the cluster. It will, however, prevent administration of that cluster (configuration, deployments, etc.) until such time as the administration server is back online. There are ways around this (bind the administration to a failover VIP provided by keepalived or similar) but for all but the most demanding usage, a single administration server will suffice.
Both dolan and gooby run CentOS 6.3 x86_64. All steps should be run on both nodes unless otherwise noted.