Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Administration Guide

- Previous: Chapter 16 Monitoring Components and Services
- Next: To configure the JVM classpath settings

## To configure the JVM general settings

The Java Virtual Machine (JVM) is included in the Java 2 Standard Edition (J2SETM) software, which is required by the Application Server. Because incorrect JVM settings will prevent the server from running, you should take care when changing these settings.

1. In tree component, select Configurations.

2. Click the JVM Setting node from the target server instance.

3. By default, the General link located below the tabs is already selected.

4. On the JVM General Settings page, you may specify the following:

   1. In the Java Home field, enter the name of the installation directory of the Java 2 Standard Edition (J2SE) software.

      The Application Server relies on the J2SE software. To verify that the J2SE version you specify is supported in this release, refer to the Release Notes. (See the link in the Further Information section.)

      Note –

      If you enter a nonexistent directory name or the installation directory name of an unsupported version of the J2SE software, then the Application Server will not start.

   2. In the Javac field, type the command-line options for the Java programming language compiler.

      The Application Server runs the compiler when EJB components are deployed.

   3. To set up debugging with the JPDA (Java Platform Debugger Architecture), you select the Debug Enabled checkbox and specify options in the Debug Options field.

      JPDA is used by application developers. For more information, see the Debugging J2EE Applications chapter of the Application Server Developer’s Guide. (For a link to the guide, see Further Information.)

   4. In the RMI Compile Options field, type the command-line options for the `rmic` compiler.

      The Application Server runs the `rmic` compiler when EJB components are deployed.

   5. In the Bytecode Preprocessor field, type a comma separated list of class names.

      Each class must implement the `com.sun.appserv.BytecodePreprocessor` interface. The classes are called in the order specified.

      Tools such as profilers might require entries in the Bytecode Preprocessor field. Profilers generate information used to analyze server performance. For more information about profiling, see the Debugging J2EE Applications chapter of the Application Server Developer’s Guide.

5. Click Save.

6. Restart the server.

- Previous: Chapter 16 Monitoring Components and Services
- Next: To configure the JVM classpath settings

- © 2010, Oracle Corporation and/or its affiliates