Sun
ONE Active Server Pages Product Home Page Developer Site Version
 

ContentsPreviousNextIndex



Enabling Chili!Beans


Chili!Beans is enabled from the Components page in the Sun ONE ASP Administration Console. To use Chili!Beans, a Java runtime environment (JRE) must be installed on the machine, and Chili!Beans must be enabled in the Administration Console. JRE 1.4 is installed with Sun ONE ASP by default, and is required for use with the product.

When Chili!Beans is enabled you have the option to enable or disable the Java virtual machine (VM) Security Manager (enabled by default). If the Java VM Security Manager is enabled, its default behavior is to prevent any access to system resources other than read-only access to the current directory. If the Java VM Security Manager is disabled, Java code executed by the Chili!Bean will run with unrestricted access to the file system and other system resources.

Note icon Note For security reasons, the Java VM Security Manager should be enabled in multi-user environments in which users supply their own Java classes.
   To selectively grant other privileges to Java code running in the Chili!Bean, with Java VM Security Manager enabled, use policytool to change the virtual machine’s security settings as specified in the Java 2 Security documentation.

To enable or disable Chili!Beans

  1. Open the Administration Console (see Accessing the Administration Console).

  2. On the ASP Server tab of the Server Management page, click Components.

  3. The Components page displays.

  4. On the Components page, click to select or clear the Chili!Beans check box.

  5. If the Chili!Beans box is selected, the Java VM Security Manager check box displays and is selected by default. Select or clear this box to enable or disable the Java VM Security Manager. The User Classpath field also displays. Use this field to specify a classpath other than the default. Paths can be separated by semicolons (;).

  6. Click Save to save your changes, or Cancel to revert to the settings that were last saved.

  7. To put your changes into effect, restart the ASP Server by clicking Restart.

Note icon Note Restarting the ASP Server resets all Session and Application variables.


ContentsPreviousNextIndex