Technical data

1 Overview of WebLogic System Administration
1-14 Configuring and Managing WebLogic Server
Servers
The administrative concept of a server represents an instance of WebLogic Server in
your domain. Using the system administration tools you can:
! Start and stop servers. (To start and stop servers on a remote machine, you must
have Node Manager installed on the remote machine.) For more information see
“Node Manager” on page 1-11.
! Configure a server’s connections: ports, HTTP settings, jCom settings, and time
outs.
! Configure HTTP server functionality and Virtual Hosts
! Configure logging and view logs
! Deploy applications to specific servers
! Configure WebLogic Server resources active on the server, such as JDBC
Connection Pools and startup classes.
Clusters
WebLogic Server clusters allow you to distribute the work load of your application
across multiple WebLogic Server instances. Clusters can improve performance and
provide fail-over should a server instance become unavailable. For example, clusters
provide several ways to replicate objects used in your applications so that data is not
lost in the event of hardware failure.
You can architect combinations of clusters to distribute the work load in a way that
provides the best performance for your applications.
Some services that are hosted on a single instance of WebLogic Server can be migrated
from one server to another in the event of server failure. The system administration
tools allow you to control these migrations.
For more information, see Using WebLogic Server Clusters at
http://e-docs.bea.com/wls/docs81b/cluster/index.html.