Updates were made to the following sections. The changes are explained below.
Section 6.0, Apache HTTP Server was updated to describe key considerations for using Apache 2 on Novell Open Enterprise Server 11 and later servers.
When you install OES services on the server, Novell-ready versions of Apache 2 HTTP Server software (Prefork, 64-bit) and Tomcat 6 are automatically installed. Apache and the OES Welcome website are automatically configured for non-secure port 80 and secure port 443. The Apache HTTP Server daemon (httpd2) starts automatically on server restart.
To set up personalized websites, you must manually create a virtual host configuration file for each website. Templates for secure SSL virtual host and non-secure virtual host configuration files are available in the /etc/apache2/vhosts.d/ directory. Use a text editor to create or modify the configuration files, then gracefully restart the Apache daemon (rcapache2 graceful) to apply the changes.
WARNING:Do not install the SUSE Linux Web and Lamp Server pattern. Do not use the HTTP Server option in YaST to manage Apache or virtual host settings on an OES server. It overwrites essential OES settings for Apache and breaks the existing setup. For recovery information, see Section 6.4.1, Apache Server Errors after Using the HTTP Server Option in YaST.
Beginning with OES 11 SP2, there is no active development or enhancement to Archive and Version Services, and support will be limited to security fixes. You can continue to use AV resources with Novell Cluster Services.
Section A.0, Comparing Novell Cluster Services for Linux and NetWare was relocated to this guide from the OES 11 SP3: Novell Cluster Services for Linux Administration Guide.
Section B.0, Comparing Resources Support for Linux and NetWare was relocated to this guide from the OES 11 SP3: Novell Cluster Services for Linux Administration Guide.
|
Location |
Change |
|---|---|
|
The MySQL database format is upgraded from version 5.0 to version 5.5 in SUSE Linux Enterprise Server 11 SP3 and OES 11 SP2. For information about upgrading the database format, see |
|
Location |
Change |
|---|---|
|
You can add a sleep command of 5 or more seconds before the novcifs -add command to resolve timing issues that cause the resource to go comatose. |
|
Location |
Change |
|---|---|
|
Section 13.2.4, Editing the Load and Unload Scripts for the OES iPrint Cluster Resource |
The daemons can also be started by using the file path /etc/init.d/novell-idsd start and /etc/init.d/novell-ipsmd start. The daemons can also be stopped by using the file path /etc/init.d/novell-ipsmd stop and /etc/init.d/novell-idsd stop. |
|
Location |
Change |
|---|---|
|
Archive and Version Services in Table 2-1, Guidelines for Converting Service Cluster Resources from NetWare to Linux |
Novell Archive and Version Services is deprecated in OES 11 SP2. |
|
QuickFinder (Server Synchronization Feature) in Table 2-1, Guidelines for Converting Service Cluster Resources from NetWare to Linux |
QuickFinder is deprecated in OES 11 SP2. |
|
Location |
Change |
|---|---|
|
After the conversion is finalized, you can enable monitoring independently for each cluster resource, and configure the resource’s monitor script. You must take the resource offline and bring it online to apply the new settings. See |
Beginning with OES 11 SP2, there is no active development or enhancement to QuickFinder, and support will be limited to security fixes. You can continue to store QuickFinder information on clustered data resources with Novell Cluster Services.