Accessing J2EE Applications

By default, OC4J Standalone exposes web applications on port 8888 using their configured context paths. For example, when deploying a web application that uses the context "examples" , you can usually access it at http://localhost:8888/examples/ . If you're using Java Standard or Enterprise Edition, then you can access web-application content via port 7777 instead of 8888.

In general, dynamic pages will take a few seconds to compile and load the first time they're visited, but they should respond quickly to subsequent requests . The HTTP listener port and default web application can be easily changed with the http-web-sites.xml configuration file.

Other J2EE components can be accessed through Remote Method Invocation (RMI) and the Java Message Service (JMS) as appropriate. Within OC4J Standalone, the default RMI port is 23791 and the default JMS port is 9127. These can also be easily configured through rmi.xml and jms.xml , respectively. A full list of the ports used by Oracle 10g AS along with their recommended port ranges can be found online at http://download-uk.oracle.com/docs/cd/B10464_02/ core .904/b10376/portnums.htm#g698804 .

Later chapters will cover these settings in detail. In particular, Chapter 7 describes how to access a secured J2EE component from a client application.



Oracle Application Server 10g. J2EE Deployment and Administration
Oracle Application Server 10g: J2EE Deployment and Administration
ISBN: 1590592352
EAN: 2147483647
Year: 2004
Pages: 150

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net