Skip Headers
Oracle® Fusion Middleware User's Guide for Oracle JRockit Virtual Edition
11g Release 1 (11.1.1.3.1)

Part Number E15206-03
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

2.2 Creating the Configuration File for the Virtual Machine

To create the configuration file for your virtual machine, perform the following steps by using the Image Tool (jrockitve-imagetool.jar).

  1. Create a sample brief configuration file by running the following command.

    java -jar jrockitve-imagetool.jar -c [config.xml] [vm_name]
    

    If you run this command from a directory other than the one that contains the Oracle JRockit Virtual Edition installation, you must specify the full path (absolute or relative) to the jrockitve-imagetool.jar file.

    This command creates a brief sample configuration file named config.xml, with vm_name as the name of the virtual machine and placeholder values for some of the elements in the configuration file, as shown in Appendix C, "Sample Brief Configuration File."

    If you do not specify the optional config.xml argument, the sample configuration file is written to stdout. You can then create the configuration file manually in a text editor, by copying the content written to stdout.

    Note:

    You can create a detailed sample configuration file containing all the possible configuration elements, by using the -create-full-config option, and then remove the elements that are not necessary for your environment.

    You can also create the configuration XML file in the following alternative ways:

    • Extract the configuration settings pertaining to an existing virtual machine by using the -r vm_cfg get config option, and use the extracted configuration settings to create the new configuration file.

    • Disassemble an existing virtual machine image by using the -d option, and use the resulting XML file as the starting point for the new configuration file.

    For more information about the -c, --create-full-config, -r, and -d options, see Appendix A, "Image Tool Command-Line Option Reference."

  2. Open the sample brief configuration file in a text editor, and do the following:

    • Verify whether the default values for elements in the sample configuration file are appropriate for your environment, and change them if required.

    • The sample brief configuration file does not include the following elements, but the Image Tool assumes certain default values for them when it assembles the virtual machine image. If the default values (described below) are not appropriate for your environment, add the elements explicitly in the configuration file and specify the required value.

      • <jrockitve-binary-url>: Location of the Oracle JRockit Virtual Edition binary file (jrockitve.bin)

        The default value for <jrockitve-binary-url> is assumed to be the directory that contains the configuration file. To specify a different location for the jrockitve.bin file, add the <jrockitve-binary-url> element.

      • <java-filesystem-imports>: Location of the Java application to be virtualized

        The default location of the Java application to be virtualized is assumed to be a subdirectory named root within the directory that contains the configuration XML file. For example, if the configuration XML file is in a directory named myconfig, the Java application to be virtualized is assumed to be in the myconfig/root directory. To change the location, add the <java-filesystem-imports> element.

        While creating a virtual machine image, the Image Tool copies, recursively, everything under the directories specified in the <java-filesystem-imports> element (if it is specified) or under the default root directory.

    • Make sure that all the mandatory elements are specified in the configuration file.

    For more information about the configuration elements and their attributes, see Appendix B, "Configuration File Element Reference."

  3. After making the required changes in the configuration file, save it.