Configuring File Locations

Most of the time, there's no need to change the default names and locations of the server configuration files. However, if you want to maintain two separate versions of one configuration file (for example, data-sources.xml ) without duplicating the entire config directory, then you can simply edit server.xml or application.xml to point to the correct version.

For example, if you want to be able to easily switch the configuration of the JMS topic called CustomerEvents , then you might create two versions of server.xml , each of which contained a <jms-config> element pointing to its own version of jms.xml . You can then switch between the two topics just by telling OC4J which server.xml to use at startup.

Table 4-6 shows the configuration files that can be moved or renamed by editing server.xml .

Table 4-6: Configuration Files Referenced in server.xml

Configuration File	Line in server.xml
jms.xml	<jms-config path ="./jms.xml" />
rmi.xml	<rmi-config path="./rmi.xml" />
application.xml	< global-application name ="default" path=" application.xml " />
global-web-application.xml	<global-web-app-config path=" global-web-application.xml " />
http-web-site.xml	<web-site path="./http-web-site.xml" />

Table 4-7 shows the configuration files that can be moved or renamed by editing application.xml .

Table 4-7: Configuration Files Referenced in application.xml

Configuration File	Line in application.xml
data-sources.xml	<data-sources path=" data-sources.xml " />
oc4j-connectors.xml	<connectors path="./oc4j-connectors.xml"/>
principals.xml	<principals path="./principals.xml" />
jazn-data.xml	<jazn provider="XML" location="./jazn-data.xml" />

As with log files, all paths are relative to server.xml .