Portal Server on an Application Server Cluster
154
Portal Server 6 2005Q1 • Deployment Planning Guide
Running Portal Server on an application server enables you to:
•
Decouple the portal platform from the application server platform, allowing
you to choose the best combination of Portal Server and application server for
your organization
•
Call Enterprise JavaBeans™ architechture and other J2EE™ technologies that
run in the application server container
•
Use application server clustering, which provides scalability and high
availability
•
Use session failover in clustering (currently available on BEA WebLogic
Server™ and Sun Java System Application Server Enterprise Edition).
Portal Server on an Application Server Cluster
This section describes how Application Server Enterprise Edition software, BEA
WebLogic Server™, and IBM WebSphere® Application Server manage application
server clustering. Application server clustering is a loosely coupled group of
application servers that collaborate to provide shared access to the services that
each server hosts. The cluster aims to balance resource requests, high availability of
resources, and failover of application logic to provide scalability. Portal Server and
Access Manager are not pure web applications. Instead, these applications are
composed of local files residing on a machine and three web applications: portal,
amserver, and amconsole. These three web applications run in a web application
container, which runs in an application server web application container.
The Java Enterprise System installs and configures the local files, configures the
local application server, then deploys the three WAR files on the local web
application container. The WAR files themselves are not self-contained. The WAR
files depend on the local files and directories on the machine to provide their
service.
An application server cluster is a logical entity that groups many application server
instances, potentially hosted on different machines. Pure web applications are
deployed on a cluster using application server specific deployment tools. Once
deployed on the cluster, the web applications are deployed to all the server
instances that the cluster is made of, and managed in a central way.
Because of Portal Server’s dual nature, as a local application as well as a web
application, install Portal Server on an application server using the following steps:
1.
Install Portal Server on all machines using the same configuration settings.
Summary of Contents for Portal Server 6 2005Q1
Page 8: ...8 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 10: ...10 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 12: ...12 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 20: ...Sun Welcomes Your Comments 20 Portal Server Secure Remote Access 6 2005Q1 Administration Guide...
Page 36: ...A Typical Portal Server Installation 36 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 50: ...Proxylet 50 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 78: ...SRA Sizing 78 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 132: ...Identity and Directory Structure Design 132 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 142: ...Configuration Files 142 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 152: ...Tuning Parameters for etc system 152 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 178: ...Portal Design Task List 178 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 182: ...182 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 192: ...Section X 192 Portal Server 6 2005Q1 Deployment Planning Guide...