image\cslogo3d1.gif

Upgrading Chili!Soft ASP for Sun Solaris

Chili!Soft ASP 3.6.0-P1 for Sun Solaris automatically upgrades many of your settings from an existing installation of Chili!Soft ASP 3.4.1. However, Chili!Soft ASP 3.6.0 does not upgrade any settings. You can determine which version you have by viewing the README file found on your Chili!Soft ASP 3.6 CD-ROM.

You can obtain Chili!Soft ASP 3.6.0-P1 for Sun Solaris from the Chili!Soft Web site at:

http://www.chilisoft.com/upgrades/solaris/

If you have already purchased Chili!Soft ASP 3.6 for Sun Solaris, you can obtain this version free of charge.

If you are upgrading from a version other than Chili!Soft ASP 3.4.1, the setup program will not preserve your existing settings. Before beginning the installation, go to the Chili!Soft Web site for information about performing an upgrade, at:

http://www.chilisoft.com/support/

To perform an upgrade from Chili!Soft ASP 3.4.1 to Chili!Soft ASP 3.6.0-P1 for Sun Solaris, you should follow the instructions provided in "Installing a Custom Configuration of Chili!Soft ASP for Sun Solaris" in this chapter. In addition, you must take the steps described in this topic.

Before you begin the upgrade, take the following steps:

·   The Chili!Soft ASP 3.6.0-P1 setup program preserves the settings from your Chili!Soft ASP 3.4.1 installation and then imports them into your new Chili!Soft ASP 3.6.0-P1 installation. However, you must take additional steps to configure the ASP Server after setup is complete. These steps are described later in this topic. Be sure to review this information prior to performing the upgrade.

·   If necessary, upgrade your Web server in order to meet the requirements listed in "Installation Requirements: Chili!Soft ASP for Sun Solaris" in this chapter.

·   It is a good idea to back up your existing installation prior to beginning the upgrade.

·   It is not a good idea to upgrade a mission-critical production server. Performing the upgrade and taking the additional configuration steps that are required might keep your server offline for an unacceptably long period of time. If possible, you should mirror the production server to a non-production server, perform the upgrade, and then test and debug the upgraded server before deploying it in your production environment.

·   The new installation will completely overwrite your existing installation. Copy to another location any items you want to preserve, such as COM components, that are contained under your current Chili!Soft ASP installation directory. Otherwise, they will be lost. If you are running SpicePack, you can obtain a free updated version of SpicePack from the Chili!Soft Web site, as described next.

·   Chili!Soft ASP 3.6 does not support multiple ASP Servers. If you are running multiple ASP Servers, e-mail Chili!Soft Customer Support at eval@chilisoft.com for instructions.

When the setup program has completed the installation, take the following steps:

·   If you were running SpicePack with your previous installation of Chili!Soft ASP 3.4.1, you need to obtain the updated version, SpicePack 1.1, from the Chili!Soft Web site and then install it. When you provide your SpicePack serial number, you can obtain a free updated version at:

http://www.chilisoft.com/upgrades/spicepack/

The README_SPICEPACK file included with SpicePack provides installation instructions.

·   Verify that any system DSNs defined for your previous installation are functioning correctly. For more information, see "Testing a DSN" in "Chapter 3: Managing Chili!Soft ASP." If they are not functioning, you can create or edit the system DSNs as needed, as described in "Configuring Data Source Names (DSNs)" in "Chapter 3: Managing Chili!Soft ASP." You can find the configuration information for the system DSNs that were defined for your previous installation in the following file:

[C-ASP_INSTALL_DIR]/casp/INSTALL/settings.import

where [C-ASP_INSTALL_DIR] is the path name of the Chili!Soft ASP 3.6 installation directory.

·   If you were running an Oracle, Sybase, or Informix database with your previous installation, you must reconfigure your database environment, as described in "Configuring the Database Environment" in "Chapter 3: Managing Chili!Soft ASP." You can find the environment settings for your previous installation under the ODBC.INI heading in the following file:

[C-ASP_INSTALL_DIR]/INSTALL/settings.import

where [C-ASP_INSTALL_DIR] is the path name of the Chili!Soft ASP 3.6 installation directory.

·   The Chili!Soft ASP 3.6 setup program sets inherit_user to "yes" by default. This setting can have important security implications for your server. Be sure to read "Setting the Security Mode" in Chapter 3: Managing Chili!Soft ASP" for more information about configuring this setting appropriately for your environment.

·   The Chili!Soft ASP 3.6 setup program sets EnableParentPaths to "no" by default. This setting can have important security implications for your server. Be sure to read "Configuring File System Access" in Chapter 3: Managing Chili!Soft ASP" for more information about configuring this setting appropriately for your environment.

·   When you choose the option to run the ASP Server in multi-process mode, the Chili!Soft ASP 3.6 setup program sets the Application Variables (AppVars) flag to Read-Only by default. When set to Read-Only, application-level variables cannot be set or modified once the global.asa file has been read. For information about changing this setting, see "Changing ASP Server Settings" in "Chapter 3: Managing Chili!Soft ASP."

Copyright 2001 Sun Microsystems, Inc. All rights reserved. Legal Notice.