Filter
Top Products
Portal Server on an Application Server Cluster
156 Portal Server 6 2005Q1 • Deployment Planning Guide
See the following documentation for more information:
http://edocs.beasys.com/wls/docs61/cluster/index.html
You start the Administration Server with the following command:
install_dir
/config/domain_name/startWeblogic.sh
The local server takes its configuration from the
install_dir
/config/domain_name/config.xml
file. To start a Managed Server, use the
following command:
install_dir
/config/domain_name/startManagedWebLogic.sh
servername
admin_server_url
Instead of taking its configuration from the
install_dir
/config/domain_name/config.xml
local file, the Managed Server takes it
from the Administration Server, using HTTP.
A BEA cluster is a set of managed servers in the same domain, that are declared in
the WebLogic console as a cluster. When deploying a web application, you use the
name of the cluster, not the name of the individual servers. After the deployment,
the web application is identically deployed to all machines in the cluster.
Session failover in BEA is described in the following document:
http://edocs.beasys.com/wls/docs61/cluster/servlet.html#1009453
Using in-memory replication for HTTP session states requires the following
prerequisites:
• Portal Server supports the use of WebLogic Server clusters with in-memory
session replication. See the BEA documentation for instructions to set up these
clusters. The Java Enterprise System Installation Guide documents the load
balancer configuration for such a cluster using the HttpClusterServlet that
ships with BEA. You can also set up other load balancing hardware and
software documented by BEA in the same way.
• Session data must be serializable.
•Use the
setAttribute
to change the session state.
NOTE The default configuration supported for installing Portal Server on
BEA WebLogic Server™ is a single server that is also the
Administration Server for the domain.