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 deployed in the web container directory structure.
Static web content. These include static HTML files, images, applet JAR files, and other items that can be served up directly by the web server without using the Web Server container. For Portal Server, these files are also deployed in the web container directory structure.
Static web content and dynamic web applications are all grouped together into a single WAR file.
Configuration data. These include data that is installed into the directory, that is, the Access Manager service definitions and any other data that modifies the directory at installation time. This includes modifications to the console configuration data to connect in the Portal Server extensions. Configuration data is installed only once no matter how many Portal Server nodes there are.
Software Development Kit (SDK). This is the JAR file or files that contain the Java APIs that are made available by a component. Developers need to install this package on a development system so that they can compile classes that use the API. The portal sdk files are located under the directory /opt/SUNWportal/sdk. The desktop subdirectory contains the desktopsdk.jar file required when building custom providers. The wsrp sub-directory contains the wsrpsdk.jar file.