| Oracle® iPlanet Web Server Release Notes Release 6.1 SP21 E18788-09 |
|
|
PDF · Mobi · ePub |
| Oracle® iPlanet Web Server Release Notes Release 6.1 SP21 E18788-09 |
|
|
PDF · Mobi · ePub |
This chapter contains information about the features, enhancements, and issues resolved in Oracle iPlanet Web Server Release 6.1 SP21. It also provides information about the platforms, software, technologies and protocols that the latest release supports. For information about additional documentation changes, see Chapter 3, "Product Documentation."
This chapter contains the following sections:
New Features and Enhancements in Oracle iPlanet Web Server Release 6.1 SP21
Issues Resolved in Oracle iPlanet Web Server Release 6.1 SP21
Product Patches for Oracle iPlanet Web Server Release 6.1 SP21
Oracle iPlanet Web Server 6.1 SP21 supports Network Security Services (NSS) 3.17.4.
For information about new features and enhancements in previous releases of Oracle iPlanet Web Server 6.1, see Appendix A.
Table 1-1 lists the issues resolved in Oracle iPlanet Web Server. The documentation issues are prefixed "Doc:" in the Description column of the table.
Table 1-1 Issues Resolved in 6.1 SP21
| Issue ID | Description |
|---|---|
|
20954518 |
NSS upgrade to 3.17.4. |
|
21087699 |
Version number changes for Oracle iPlanet Web Server 6.1. SP21. |
For information about issues resolved in previous releases of Oracle iPlanet Web Server 6.1, see Appendix B.
The following Oracle iPlanet Web Server Release 6.1 SP21 patches are available on the My Oracle Support site at http://support.oracle.com.
| Platform | Patch ID |
|---|---|
|
Oracle Solaris on SPARC (32-bit) |
18960052 |
|
Oracle Solaris on SPARC (64-bit) |
18960053 |
|
Oracle Solaris on x86 (32-bit) |
18960054 |
|
Linux x86 |
19025058 |
|
IBM AIX on POWER Systems (32-bit) |
18960090 |
|
HP-UX (32- bit) |
18960091 |
|
Microsoft Windows (32- bit) |
18960055 |
Table 1-2 summarizes the supported platforms for Oracle iPlanet Web Server Release 6.1 SP21.
For more information about installation requirements, see Section 1.4.1, "Required Patches" and Sun Java System Web Server 6.1 SP12 Installation and Migration Guide.
Table 1-2 Oracle iPlanet Web Server Release 6.1 SP21 Supported Platforms
| Vendor | Architecture | Operating System | Minimum Required Memory | Recommended Memory | Recommended Disk Space |
|---|---|---|---|---|---|
|
IBM |
PowerPC |
AIX * 5.2, 5.3, 6.1 |
64 MB |
192 MB |
256 MB |
|
Microsoft |
x86 (32-bit) |
Windows Server 2003 Enterprise Edition, SP1 or above Windows Server 2003 Enterprise Edition R2 or above |
64 MB |
192 MB |
256 MB |
|
Oracle |
SPARC** |
Solaris 10*** |
64 MB |
192 MB |
256 MB |
|
Oracle |
SPARC**** (64-bit) |
Solaris 10 |
64 MB |
192 MB |
256 MB |
|
Oracle |
x86 (32-bit) |
Solaris 10*** |
64 MB |
192 MB |
256 MB |
|
Red Hat |
x86 (32-bit) |
Red Hat Advanced Server 4.0 |
64 MB |
192 MB |
256 MB |
|
Novell |
x86 (32-bit) |
SUSE Linux Enterprise 9.0 |
64 MB |
192 MB |
256 MB |
* AIX 5.1 is dropped. It was deprecated in Web Server 6.1 SP5.
** The following Microsoft Windows platforms are deprecated: Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, and Windows XP Professional.
*** The following Solaris platforms are deprecated: Solaris 8, 9.
**** As of iPlanet Web Server 6.0, older SPARC CPUs are not supported. Web Server 6.1 continues to support the UltraSPARC architecture.
For better performance and support, migrate your web server to a supported operating system.
Note:
For Solaris 10 installations, Web Server 6.1 SP5 and later support Global Zone with Sparse Root Zone and Whole Root Zone.
Update your operating system with the latest applicable patches:
Base-level OS - AIX 5.2
Maintenance-level patches 5200-07 or above
JDK APAR - IY46668 must be applied
If you have deployed Java web applications on the web server, set the following environment variables to the values specified below (as per the IBM JDK documentation) before starting the server:
export AIXTHREAD_SCOPE=S
export AIXTHREAD_MUTEX_DEBUG=OFF
export AIXTHREAD_RWLOCK_DEBUG=OFF
export AIXTHREAD_COND_DEBUG=OFF
You can directly add the above code line to the web server start script.
Base-level OS - AIX 5.3
Maintenance-level patches 5300-03 or above
When you upgrade from AIX version 5.3 to AIX version 5.3 Technology Level 6 SP5, apply the following patch so that the control returns to the command-line prompt when you start the administration server/instance server.
bos.mp/bos.mp64 at 5.3.0.66
When you upgrade from AIX version 5.3 to AIX version 5.3 Technology Level 7 SP2, apply the following patch so that the control returns to the command-line prompt when you start the administration server/instance server.
bos.mp/bos.mp64 at 5.3.7.2
The following sections provide information about some of the software, technologies and protocols that Oracle iPlanet Web Server 6.1 supports:
Web Server 6.1 supports the Active Server Pages (ASP) specification through Sun Java System Active Server Pages version 4.0.1 (formerly Sun ChiliSoft ASP), version 4.0.2, and version 4.0.3. Active Server Pages software adds a secure and enterprise-grade ASP engine to the Web Server. Web Server 6.1 supports Sun Java System Active Server Pages 4.0.2 and 4.0.3 on the following platforms:
Solaris (SPARC) versions 8, 9, and 10
Solaris (x86) 9, 10
Windows 2000 Professional Edition, Server, Advanced Server, XP and 2003 Enterprise Edition
AIX 5.2, 5.3
RedHat Enterprise Linux 3.0, 4.0
A license is not required for Sun Java System Active Server Pages if you are installing it to the Web Server. The Sun Java System Active Server Pages installer is available on the companion CD if you purchase the Web Server Media Kit, or you can download it from http://www.sun.com/download/products.xml?id=420a8e72.
Note:
The Sun Java System Active Server Pages plug-in requires an additional 50 Mbytes (approximately) of disk space after Web Server 6.1 is installed.
Before you begin installation, make sure you are logged in as root.
The following browsers are supported with Web Server 6.1 Administration graphical user interface (GUI):
PUT and DELETEThis section discusses on how to disable the PUT and DELETE options.
PUT and DELETEAccess the Administration Console.
Select a server from the list of servers and click the Manage button.
Click the Restrict Access link under the Preferences tab.
Select the Edit option from the drop-down list and click the OK button.
Select The entire server option from the method A table and click the Edit Access Control button.
Click the access rights (r-x--i) link under the Rights column.
Access Rights table appears at the bottom of the screen.
Deselect the WRITE and DELETE options.
Click the Update button.
Click the Submit button.
Click the Apply link present at the top right of the screen and click the Apply Changes button to make the changes permanent.
Restart the server for changes to take effect.
Web Server 6.1 provides hardware accelerator support for Sun Crypto Accelerator 500, 1000, 4000 and 6000 boards, which enhance the performance of SSL on web server.
Note:
Initialize the Sun Crypto Accelerator card when using with web server. For more information about Sun Crypto Accelerator, see Sun Crypto Accelerator 6000 Board Version 1.1 User's Guide at:
Web Server 6.1 enables you to restrict access using flat file authentication through the Java Security Manager. Enabling the Security Manager feature can improve security by restricting the rights granted to your J2EE web applications. By default, the Security Manager feature is disabled when you install the product. To enable Security Manager, uncomment the following entries in the server.xml file:
<JVMOPTIONS>-Djava.security.manager</JVMOPTIONS>
<JVMOPTIONS>-Djava.security.policy=instance-dir/config/server.policy</JVMOPTIONS>
where instance-dir is the path to the installation directory of this server instance.
For more information about server.xml, see Sun Java System Web Server 6.1 SP12 Administrator's Configuration File Reference.
Web Server 6.1 supports content compression. This compression enables you to increase the delivery speed to clients and serve higher content volumes without incurring a corresponding increase in hardware expenses. Content compression reduces content download time, a benefit most apparent to users of dial-up and high-traffic connections.
For more information, see Sun Java System Web Server 6.1 SP12 Administrator's Guide.
Oracle iPlanet Web Server 6.1 supports Java SE 6 and J2SE 5. It does not support J2SE 1.4, which has passed its EOSL (End Of Service Life).
For the Windows, Solaris, and all Linux platforms, Web Server 6.1 includes Java SE 6. When you upgrade to or install Web Server 6.1 on these platforms, the JDK is upgraded or installed automatically. For HP-UX and AIX, you must download the JDK and install it before installing Web Server.
Oracle iPlanet Web Server 6.1 is certified with the following JDK versions:
| Platform | JDK 1.6 Version | JDK 1.5 Version |
|---|---|---|
|
Hewlett-Packard HP-UX |
1.6.0.01-jinteg_06_jun_2008_13_24-b00 |
1.5.0.16 |
|
IBM AIX |
1.6.0 pap3260sr1-20080416_01(SR1) |
1.5.0 pap32dev-20080315 (SR7) |
|
Microsoft Windows |
1.6.0_24 |
1.5.0.22 |
|
Oracle Solaris |
1.6.0_24 |
1.5.0.22 |
|
Red Hat Linux |
1.6.0_24 |
1.5.0.22 |
|
Sun Linux |
1.6.0_24 |
1.5.0.22 |
|
SUSE Linux |
1.6.0_24 |
1.5.0.22 |
Note:
A 32-bit JDK is required on all platforms except 64-bit Solaris SPARC, which requires a 64-bit JDK.
Web Server 6.1 includes a Java 2 Platform, Enterprise Edition (J2EE) compliant implementation of the Java Servlet 2.3 and JavaServer Pages ( JSP) 1.2 technology specifications. A J2EE compliant web container provides the flexibility and reliability needed to design and deploy web applications that comply with Java technology standards. Web applications can be deployed on a per virtual server basis.
For information about these technologies, see the following resources:
Java Servlets: http://www.oracle.com/technetwork/java/index-jsp-135475.html
JavaServer Pages: http://www.oracle.com/technetwork/java/javaee/jsp/index.html
For information about developing Servlets and JavaServer Pages, see Sun Java System Web Server 6.1 SP12 Programmer's Guide to Web Applications.
Web Server 6.1 includes the Java DataBase Connectivity (JDBC) software, and supports a wide range of industry-standard and customized JDBC drivers.
Web Server 6.1 supports the Java Naming and Directory Interface (JNDI) API. JNDI provides seamless connectivity to heterogeneous enterprise naming and directory services.
If you are using a localized version of Web Server 6.1x, you can take advantage of the existing localization features by installing Web Server 6.1 SP13 over the existing server. Web Server 6.1 SP13 releases are available in Japanese, Simplified and Traditional Chinese, French, Spanish, German, and Korean.
Web Server 6.1 extends the Netscape Server Application Programmer's Interface (NSAPI) to support NSAPI filters.
NSAPI filters enable the custom processing of HTTP request and response streams. This processing enabled a function to intercept and potentially modify the content presented to or generated by another function. For example, a plug-in could install a NSAPI filter to intercept a XML page generated by another plug-in's Server Application Function (SAF) and then transform that XML page into a HTML, XHTML, or WAP page appropriate for the client. Alternatively, a NSAPI filter could decompress data received from a client before presenting it to another plug-in.
For more information about NSAPI filters, see Sun Java System Web Server 6.1 SP12 NSAPI Programmer's Guide.
Oracle iPlanet Web Server 6.1 supports NSS, a set of libraries that support cross-platform development of security-enabled server applications. Oracle iPlanet Web Server 6.1 SP18 includes version 3.14.3 of NSS (for both 32-bit and 64-bit) and version 4.8.9 of NSPR.
PHP: Hypertext Preprocessor (PHP) can be used with the Web Server using one of the three supported APIs; CGI, NSAPI, and FastCGI. PHP is a page scripting language available from the PHP group. The PHP group provides instructions on its Web site (http://www.php.net) for configuring the PHP software to use any of these APIs:
CGI API is the most stable interface that can be used but will suffer from performance limitations inherent in CGI.
NSAPI uses the Web Server's native API to run the PHP software within the web server's memory. This configuration will provide the best performance, but risks crashing the server if non thread safe PHP modules are used.
FastCGI interface provides a compromise between performance and stability. FastCGI enables the PHP software to remain running after serving requests while continuing to run outside of the web server's memory. If an unstable PHP module is used, it will not crash the web server. For this reason use the FastCGI interface with the PHP software.
The FastCGI interface is supported with web server through the installation of the FastCGI add-on available at http://www.sun.com/download/products.xml?id=42d693c3.
When run as a FastCGI process, the PHP software uses the following environment variables to control the life cycle of PHP processes:
PHP_FCGI_CHILDREN determines the number of PHP processes that will be created to respond to requests.
PHP_FCGI_MAX_REQUESTS determines the number of requests a PHP process can respond to before terminating itself and being replaced with a new PHP process.
Note:
Instead of using PHP_FCGI_CHILDREN, use the FastCGI add-on configuration parameter min-procs to control the minimum number of PHP processes.
Web Server 6.1 supports a Java search engine that provides full-text search indexing and retrieval. The search feature enables you to search documents on the server and display results on a web page. Server administrators can create the indexes of documents and customize the search interface to meet user specific needs.
The default URL to access the search functionality is http://server-instance:port number/search
For example:
http://plaza:8080/search
When the user goes to this URL, the Search page, a Java web application, is launched.
For detailed information about basic and advanced search feature, see the Online Help provided with the search engine. To access Online Help, click the Help link on the Search page. For more information, see Sun Java System Web Server 6.1 SP12 Administrator's Guide.
For the Web Server SSL subsystem (NSS) to use external PKCS#11 tokens, you have to configure NSS with the modutil command to make it aware of the tokens. The Solaris libpkcs11 softtoken is a PKCS#11 compliant token which can be used with NSS. As an additional benefit on UltraSPARC-T1, systems using the Solaris 10 libpkcs11 task will make use of the platform crypto acceleration support.
Run the modutil command without any arguments for usage information. For example, to add the Solaris 10 libpkcs11 task as a PKCS11 token in NSS.
Ensure that SSL support has been initialized for the web server instances.
Run the following command:
% modutil -dbdir $ALIASDIR -dbprefix $PREFIX -add libpkcs -libfile /usr/lib/libpkcs11.so -mechanisms RSA
where
$ALIASDIR is the path to the alias directory in the install root where the NSS database files are located.
$PREFIX is the prefix used by the key3 and cer8 database files in the alias directory and is of the form https-$INSTANCENAME-.
The -mechanisms flag makes this token the preferred initial provider for the given algorithms.
Run the modutil command without any arguments for a list of all possible mechanisms.
Initialize the libpkcs11 provider's password with pktool.
% pktool setpin
For further details on configuring NSS, see the libpkcs11(3LIB), pkcs11_softtoken(5), and pktool(1) man pages. For more information about modutil, see http://www.mozilla.org/projects/security/pki/nss/tools/modutil.html.
Web Server 6.1 supports Sun Java Studio Enterprise 8. Sun Java Studio technology is Sun's powerful and extensible integrated development environment (IDE) for Java technology developers. Sun Java Studio is based on the NetBeans software and is integrated with the Sun Java platform.
Sun Java Studio support is available on all platforms supported by Web Server 6.1. The plug-in for the web server can be obtained in the following ways:
From the companion CD in the Web Server Media Kit
By using the companion AutoUpdate feature of Sun Java Studio
From the download center for Web Server
Note:
Sun Java Studio 8 plug-in for Web Server 6.1 SP13 works only with a local web server, that is, the IDE and the web server must be installed on the same machine.
For more information about Sun Java Studio 8, see http://developers.sun.com/jsenterprise/overview/previous/jse8.jsp.
Sun Java Studio Enterprise 8 can be used for remote debugging if you want to manually attach the IDE to a remote web server started in debug mode.
Restart the server instance in the debug mode by using the Web Server Administration interface (Server Manager->JVM General->Debug Enabled).
Note the JPDA port number.
Start the IDE.
Choose Debug->Start.
Select the dt_socket method.
Type the remote machine name and JPDA port number.
Any breakpoint created in the IDE on Servlet source code of a deployed application becomes active.
To complement the existing support to 32-bit Solaris SPARC, Web Server 6.1 also supports 64-bit Solaris SPARC.
The 64-bit release may be of use in certain memory-intensive deployments as it enables administrators to configure a larger file cache and Java heap than the 32-bit release. However, existing plug-ins are not compatible with the 64-bit release. These plug-ins have to be recompiled for the 64-bit release by the plug-in vendor. Java web applications that use native, and non-Java libraries should also be recompiled. Therefore, you might prefer to deploy the 32-bit release of Web Server.
Web Server 6.1 SP13 also provides 64-bit support for FastCGI, Reverse Proxy, and Java Web Services Developer Pack (JWSDP) plug-ins.
The 64-bit release is compatible with 64-bit Solaris kernels on UltraSPARC processors. The 64-bit release cannot be used on x86 processors or with 32-bit Solaris kernels. The 32-bit release continues to be compatible with both 32-bit and 64-bit Solaris kernels.
Note:
The 64-bit and 32-bit releases of Web Server are packaged and distributed separately. You cannot upgrade an existing 32-bit Web Server installation to a 64-bit installation. You can distinguish the 32-bit and 64-bit releases by the version string that is displayed in the installer, at server startup, and in the server errors log as follows:
|
Release |
Version String |
|
32-bit |
Sun ONE Web Server 6.1SP13 |
|
64-bit |
Sun ONE Web Server 6.1SP13 (64-Bit) |
Web Server 6.1 supports the Web-based Distributed Authoring and Versioning (WebDAV) protocol. WebDAV enables collaborative web publishing and has the following features:
Compliance with RFC 2518 and interoperability with RFC 2518 clients
Security and access control for web publishing
Basic publishing operations on file-system-based WebDAV collections and resources
WebDAV provides integrated support for content metadata, namespace management, and overwrite protection. These technologies combined with the many authoring tools that support WebDAV provide an ideal development platform for collaborative environments.
The following public interfaces in Web Server 6.1 may be deprecated or modified in non-compatible ways in a future web server release. These interfaces remains unchanged within the Web Server 6.1 product. Scripts that rely on these interfaces may have to be updated to function with future web server releases.
Table 1-3 Deprecated or Modified Public Interfaces
| Configuration File or Utility | Description |
|---|---|
|
|
Modified. Some functionality might be moved to other files. |
|
|
Modified. Schema and functionality might be modified. |
|
|
Deprecated. Functionality might be moved to other files. |
|
|
Deprecated. This file may be eliminated and functionality might be moved to other files. |
|
|
Deprecated. This file may be eliminated; functionality might be moved to other files. |
|
file layout |
Modified. The configuration file structure might be modified. |
|
start, stop, restart, and rotate scripts |
Modified. The names and/or locations of these utilities might change. |
|
|
Deprecated. This utility may be eliminated and functionality might be integrated with other management utilities. |
This section includes notes about installing, upgrading, and migrating your Web Server. For more information about these topics, see Sun Java System Web Server 6.1 SP12 Installation and Migration Guide. For known issues in this release of Web Server, see Chapter 2, "Known Issues."
Note the following:
Do not install Oracle iPlanet Web Server into a directory with spaces in the name.
Web server will not start if it is installed into a directory with spaces in the name, for instance, Program Files. You will not receive an error message about this problem during installation, but following installation the server will not start.
Web server cannot be set up on Red Hat Linux Advanced Server 3.0 without compat-libstdc++.
When you install Oracle iPlanet Web Server Release 6.1 SP21 over an existing installation, the installer automatically carries out the upgrade.
If you have Sun ONE Web Server 6.1 SP1 installed, point the Oracle iPlanet Web Server Release 6.1 SP21 installer to the location of the 6.1 SP1 installation and then upgrade.
Direct migration from a version of Web Server earlier than 4.1 to Oracle iPlanet Web Server Release 6.1 SP21 is not supported. You must first migrate your legacy server to Web Server 4.1, and then to Oracle iPlanet Web Server Release 6.1 SP21.
For detailed migration information, see Sun Java System Web Server 6.1 SP12 Installation and Migration Guide. This guide contains information about migrating from version 4.1 to 6.1 and from version 6.0 to 6.1.
If you have problems with Oracle iPlanet Web Server Release 6.1 SP21, contact My Oracle Support (http://support.oracle.com).
Please have the following information available prior to contacting support. This helps to ensure that our support staff can best assist you in resolving problems.
Description of the problem, including the situation where the problem occurs and its impact on your operation
Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
Detailed steps on the methods you have used to reproduce the problem
Any error logs or core dumps
|
 Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|