Starting a WebLogic Server Cluster
10.2.3 Create a Clustered Domain
The are multiple methods of creating a clustered domain. For a list, see Section 4.5, Methods of Configuring Clusters. For instructions to create a cluster using the: ■ Configuration Wizard, first see Creating a WebLogic Domain in Creating Domains Using the Configuration Wizard for instructions on creating the domain, and then Select Optional Configuration for instructions on configuring a cluster. ■ Administration Console, see Create and configure clusters in Oracle WebLogic Server Administration Console Help.10.2.3.1 Starting a WebLogic Server Cluster
There are multiple methods of starting a cluster—available options include the command-line interface, scripts that contain the necessary commands, and Node Manager. Regardless of the method you use to start a cluster, start the Administration Server first, then start the Managed Servers in the cluster. Follow the instructions below to start the cluster from a command shell. Note that each server instance is started in a separate command shell. 1. Open a command shell. 2. Change directory to the domain directory that you created with the Configuration Wizard. 3. Type this command to start the Administration Server: StartWebLogic 4. Enter the user name for the domain at the Enter username to boot WebLogic Server prompt. 5. Enter the password for the domain at the Enter password to boot WebLogic Server prompt. The command shell displays messages that report the status of the startup process. 6. Open another command shell so that you can start a Managed Server. 7. Change directory to the domain directory that you created with the Configuration Wizard. 8. Type this command StartManagedWebLogic server_name address:port where: server_name is the name of the Managed Server you wish to start Note: Node Manager eases the process of starting servers, and restarting them after failure. To use Node Manager, you must first configure a Node Manager process on each machine that hosts Managed Servers in the cluster. See Section 10.2.4, Configure Node Manager. Setting up WebLogic Clusters 10-9 address is the IP address or DNS name for the Administration Server for the domain port is the listen port for the Administration Server for the domain 9. Enter the user name for the domain at the Enter username to boot WebLogic Server prompt. 10. Enter the password for the domain at the Enter password to boot WebLogic Server prompt. The command shell displays messages that report the status of the startup process. 11. To start another server instance in the cluster, return to step 6. Continue through step 10. 12. When you have started all Managed Servers in the cluster, the cluster startup process is complete.10.2.4 Configure Node Manager
Parts
» Oracle Fusion Middleware Online Documentation Library
» Document Scope and Audience Guide to this Document
» What Are the Benefits of Clustering? What Are the Key Capabilities of a Cluster?
» Servlets and JSPs EJBs and RMI Objects
» Getting Connections with Clustered JDBC Failover and Load Balancing for JDBC Connections
» Pure-Java Versus Native Socket Reader Implementations
» Client Communication via Sockets
» How WebLogic Server Creates the Cluster-Wide JNDI Tree
» How WebLogic Server Updates the JNDI Tree Client Interaction with the Cluster-Wide JNDI Tree
» Load Balancer Configuration Requirements Load Balancers and the WebLogic Session Cookie
» Related Programming Considerations How Session Connection and Failover Works with a Load Balancer
» Round-Robin Load Balancing Weight-Based Load Balancing
» Transactional Collocation Optimization for Collocated Objects
» Methods of Configuring Clusters Load Balancing for JDBC Connections
» Using Replication Groups HTTP Session State Replication
» Connection with Load Balancing Hardware Failover with Load Balancing Hardware
» Configuration Requirements for Cross-Cluster Replication
» Configuring Session State Replication Across Clusters
» Clustering Objects with Replica-Aware Stubs
» Failover and JDBC Connections Understanding Server and Service Migration
» Migration Terminology Oracle Fusion Middleware Online Documentation Library
» Features That Use Leasing Leasing Versions
» Determining Which Type of Leasing To Use High-availability Database Leasing
» Non-database Consensus Leasing Leasing
» Preparing for Automatic Whole Server Migration
» Configuring Automatic Whole Server Migration
» Startup Process in a Cluster with Migratable Servers
» Automatic Whole Server Migration Process
» Manual Whole Server Migration Process Administration Server Role in Whole Server Migration
» Migratable Server Behavior in a Cluster Node Manager Role in Whole Server Migration
» Cluster Master Role in Whole Server Migration
» JMS-related Services JTA Transaction Recovery Service
» Custom Store Availability for JMS Services Default File Store Availability for JTA
» Best Practices for Targeting JMS when Configuring Automatic Service Migration
» Architecture Web Application Tiers
» Combined Tier Architecture De-Militarized Zone DMZ Load Balancer Proxy Plug-In
» No Collocation Optimization Firewall Restrictions
» Multi-Tier Proxy Architecture Proxy Architecture Benefits Proxy Architecture Limitations
» Proxy Plug-In Versus Load Balancer
» DMZ with Two Firewall Configuration
» Dynamic Cluster Address If you do not explicitly define a cluster address
» Configuration Roadmap Install WebLogic Server
» Starting a WebLogic Server Cluster
» Configure Node Manager Configure Load Balancing Method for EJBs and RMIs
» Sample web.xml This section contains a sample deployment descriptor file
» Accessing Applications Via the Proxy Server Ensure that applications clients will
» Configure Replication Groups Configure Migratable Targets for Pinned Services
» Migrating When the Currently Active Host is Unavailable Use this migration
» Configure Multicast Time-To-Live TTL Configure Multicast Buffer Size
» Cluster-Related Configuration Options Follow Usage and Configuration Guidelines
» Manual Migration of the JTA Transaction Recovery Service State Management in a Cluster
» Naming Considerations Administration Server Considerations
» Firewall Considerations Avoiding Problems
» Check the Server Version Numbers Check the Multicast Address Check the CLASSPATH Value
Show more