This illustration shows the mappings from the OC4J server.xml top-level configuration file to Web site configuration files, EAR files, and the RMI and JMS configuration files. In particular:

• The <RMI> element points to the RMI configuration file, RMI.xml.
• The <JMS> element points to the JMS configuration file, JMS.xml.
• Each <web-site> element points to the Web site XML configuration file of a particular Web site that this OC4J instance recognizes. The path attribute of the <web-site> element shows the path and file name of the Web site XML file.
• Each <application> element, through its name attribute, points to the EAR file (or extracted EAR) of a J2EE application that is recognized by this OC4J instance. The path attribute has the path to the EAR file (or to the top-level directory of an extracted EAR).

The illustration has the server.xml file pointing to three EAR files--EAR1, EAR2, and EAR3--where EAR1 is the parent application of EAR2 and EAR3. (This is specified through use of the <application> element parent attribute in server.xml.) The illustration also shows how a Web site XML file binds Web modules to a Web site. In a Web site XML file, each <web-app> element specifies an EAR file name (through the application attribute), the name of a Web module that the EAR file contains (through the name attribute), and a root URL used to invoke the Web module on this Web site (through the root attribute). This "binds" the Web module to the Web site.