In this third part of a series that focuses on managing OC4J and configuring J2EE applications, we look at how to configure the OC4HJ server. It is excerpted from chapter eight of the Oracle 10g Application Server Exam Guide, written by Sam Alapati (McGraw-Hill; ISBN: 0072262710).
The OC4J server configuration files (also known as OC4J configuration files) help configure the OC4J server and are located in the following directory:
The OC4J server configuration files configure various OC4J instance-Ėrelated items such as ports, security, and basic J2EE services. These XML files are purely
exam watch: The configuration settings in the OC4J configuration files apply directly to the OC4J server, not the deployed J2EE applications.
about configuring the OC4J instance itself and arenít directly related to the deployment of the J2EE applications.
The OC4J server configuration files consist mainly of a set of Server XML configuration files and a set of Web site XML files. The server configuration files specify various properties of the OC4J server such as the listening ports, passwords, security, and related basic J2EE services as well as the data sources and Web sites. The Web site XML files are used to configure ports, Web contexts, and protocols to facilitate the functioning of the OC4J Web site.
Letís review the important OC4J server XML files.
The server.xml file is the key OC4J server configuration file; it contains references to most of the files used by the OC4J server. Besides configuring the OC4J server, the server.xml file also points to other configuration files, such as the jms.xml file for JMS support. This way, you can configure the various services in their own configuration files, but by referring to them in the server.xml file, you let it be known that these services are for the use of the OC4J instance. The server configuration files are OC4J instance specific and refer to the key J2EE configuration files. You donít usually need to modify the OC4J server configuration files when you deploy J2EE applications. Hereís how the server.xml file references other configuration files: