Note

If Hitachi Web Server is installed, first uninstall it and then install Cosminexus HTTP Server. Do not perform an overwrite installation over an older version of Hitachi Web Server.

The following table lists points to note when migrating from an older version, and indicates whether settings need to be changed.

Table G-1 Points to note when migrating from an older version

No.	Item	Cosminexus Application Server version before the migration
		V6	V7	V8
1	Specification of the ErrorDocument directive string	Y	-	-
2	Specification of a reverse proxy	Y	-	-
3	Specification of the ShmemUIDisUser directive	Y	-	-
4	If programs other than rotatelogs or rotatelogs2 are specified in the pipe format for the TransferLog, CustomLog, and ErrorLog directives (Windows version only)	Y	-	-
5	Change in behavior when a SIGXFSZ or SIGXCPU signal is received (UNIX version only)	Y	Y	-
6	Change in the update interval when the activity status is displayed (status information display)	Y	Y	-
7	GUI server manager functionality is no longer provided	Y	Y	-
8	The HTML manual is no longer provided	Y	Y	-
9	Change of program product name	Y	Y	Y
10	The program menu is no longer provided (Windows version only)	Y	Y	Y
11	Change of SSL related commands	Y	Y	Y
12	The SSLv2 protocol is not supported	Y	Y	Y
13	Change in supported encryption types	Y	Y	Y
14	Specification at SSL client authentication	Y	Y	Y

(Legend)

• V6, V7, and V8 stand for Cosminexus Application Server Version 6, Version 7, and Version 8, respectively
• Items for which settings need to be changed are as follows:
  Y: Settings need to be changed at migration
  -: No settings need to be changed
  

The following are points to note for each item. If settings need to be changed, perform the tasks from installation to startup.

1. Specification of the ErrorDocument directive textFor Cosminexus Application Server Version 6, the specification added a double quotation mark (") at the beginning of the specification string. In this version, however, enclose the string in double quotation marks ("...")
   

   (Example)

   In Cosminexus Application Server Version 6:

   ErrorDocument 500 "Server Error.

   In this version:

   ErrorDocument 500 "Server Error."

2. Specification of a reverse proxy:For Cosminexus Application Server Version 6, only mod_proxy.so (for the Windows version) or libproxy.so (for the UNXI version) was loaded. In this version, however, load both mod_proxy.so and mod_proxy_http.so.
   For the UNIX version, you must always load them in the order shown in the following example.
   

   (Example)

   For the Windows version:

   - In Cosminexus Application Server Version 6

   LoadModule proxy_module modules/mod_proxy.so

   - In this version

   LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so

   For the UNIX version:

   - In Cosminexus Application Server Version 6

   LoadModule proxy_module libexec/libproxy.so

   - In this version

   LoadModule proxy_module libexec/mod_proxy.so LoadModule proxy_http_module libexec/mod_proxy_http.so

3. Specification of the ShmemUIDisUser directive The ShmemUIDisUser directive is not needed for this version. Remove this directive specification.
4. If programs other than rotatelogs or rotatelogs2 are specified in the pipe format for the TransferLog, CustomLog, and ErrorLog directives (Windows version only)
   The code for linefeeds in the log information has been changed from LF to CRLF. So some programs might need to be revised accordingly.
   When you specify a program for a directive, you need to add the program extension (for example, .exe).
   

   (Example)

   To specify a user-created program writelogs.exe to output log information:

   - In Cosminexus Application Server Version 6

   CustomLog "|\"\"C:/proprietary/writelogs\" program argument\""

   - In this version

   CustomLog "|\"\"C:/proprietary/writelogs.exe\" program argument \""

5. Change in behavior when a SIGXFSZ or SIGXCPU signal is received (UNIX version only)
   At the reception of the SIGXFSZ signal or SIGXCPU signal, the control process now stops Web server.
   
6. Change in the update interval when the activity status is displayed (status information display)
   For the interval for updating the status information (specified in refresh=update-interval), the specifiable interval range was changed from 1 to 3,600 seconds. Also the default value was changed to 60 seconds.
   
7. The GUI server manager functionality is no longer provided.
   The GUI server manager functionality is no longer supported.
   
8. The HTML manual is no longer provided
   The shipment does not include the HTML manual.
   
9. Change of program product name
   The name of the program product has been changed from Hitachi Web Server to Cosminexus HTTP Server. Accordingly, the names used for logs or HTTP communications have changed from Hitachi Web Server to Cosminexus HTTP Server. In the Windows version, the service name created by default has also been changed, except when the service Hitachi Web Server already exists in your environment from an installation of an earlier version.
   
10. The program menu is no longer provided (Windows version only)
    The program menu of this product is no longer created in the Windows Start menu.
    
11. Change of SSL related commands
    The sslc (or sslckey) and sslccert commands have been changed to the keygen and certutil commands. Note that the following functions run by the sslc command are not included in this change.
    
    • Creating private keys and certificates for a test CA (Certification Authority), and signing at a test CA
    • Viewing the content of CRL and changing its format
    For details on the keygen and certutil commands, see 5.2 Acquiring a certificate.
    You can continue to use key and certificate files you created with the old commands. However, you cannot use new commands together with an old command (for example, the sslckey or certutil command) to create key or certificate files.
    
12. The SSLv2 protocol is not supported
    SSLv2 can no longer be specified for the SSLProtocol directive. If you send a request from a client that supports SSLv2 only, the SSL handshake will result in an error and the connection will fail.
    
13. Change in supported encryption types
    Supported encryption types have been changed. For details, see 6.2.7(20) SSLBanCipher encryption-type [encryption-type ...].
    
14. Specification at SSL client authentication
    You can no longer specify 3 for the SSLVerifyCLient directive.
    When implementing SSL client authentication, in the SSLCACertificateFile or SSLCACertificatePath directive, always specify a certificate from the CA who issued the client certificate (including the intermediate CA certificate and route CA certificate).