Sun Microsystems Portal Server 6 2005Q1, Planning Manual

Page: 31 / 192

Portal Server Software Deployment
Chapter 1 Portal Server Architecture 31
• Access Manager console SDK
• Authentication daemons that support the web applications
See the Access Manager Deployment Planning Guide for more information.
Portal Server Software Deployment
This section provides information on software deployed on Portal Server.This
section provides information on the software packaging mechanism, the software
categories within the system, and compatibility with Java software.
Software Packaging
Portal Server uses a “dynamic WAR file” approach to deploy software to the
system. Portal Server is installed using Solaris™ packages, which consist of
individual files that comprise web applications, for example, JAR, JSP, template,
and HTML files. The packages do not contain WAR or EAR files. The packages do
contain
web.xml
fragments that are used to construct the Portal Server WAR file at
installation time. This dynamically constructed file is then deployed to the web
application container. As additional packages are added to the system, for
example, for localization, the web application file is rebuilt and redeployed.
Software Categories
Portal Server distinguishes between the following kinds of software that it installs
onto the Portal Server node:
• Dynamic web applications . These include servlets running on a Java platform,
JSP files, content providers, and other items that the web container processes
when accessed by the user’s browser. For Portal Server, these files are installed
in the Web Server.
NOTE
The WAR file packaging and deployment mechanism is for use only
by Portal Server products. Customer modifications to the WAR file
or any files used to build it are currently not supported.