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).
You configure the OC4J server by modifying the following elements in the server.xml file:
Global application, global Web application, and default Web site
Number of HTTP connections the OC4J server will permit
Transaction time-input settings
Referencing Other Configuration Files
You can reference other configuration XML files and directories in the server.xml file. Following are the important configuration files referenced in the server.xml file:
jms.xml and rmi.xml locations
on the job: If you’re using a standalone OC4J instance, port 8888 is used by default to access the OC4J listener. In the OracleAS environment, OPMN overrides this port setting. OracleAS by default allocates port 7777 for access via the Oracle HTTP Server when you enable the OracleAS Web Cache.