- The Application Server Control (ASC) console is now mapped to the default-website with a context-root of "/em".
In the previous DP3 release, ASC was mapped to a separate website and used a context-root of "/asc".
- We've made the configurations more consistent between the standalone OC4J and the OracleAS OC4J. The most obvious change is that standalone OC4J now uses the "default-web-site.xml" file as its default website.
Previous releases of standalone have used a different file -- http-web-site.xml.
- If you download and use the installable version of Oracle Application Server, and perform the "J2EE Server" installation type, you will ultimately get an OPMN managed OC4J instance. This OC4J instance is configured out of the box to run its request listener using HTTP -- so it can be used immediately and without requiring an OHS instance to sit in front of it (although we recommend that and it can be done very easily).
The gotcha here is that the default URL to access this instance will be
Note that the port in use here is allocated at install time. It will be "8888" unless the installer detects that it in use, whereupon it will search for another free port to use instead. The end of install text will show you the port that was used.
- To see all the active ports in use, you can use the opmnctl utility
$ORACLE_HOME/opmn/bin/opmnctl status –l
Processes in Instance: test_j2ee
ias-component| process-type| status|ports
OC4J | home | Alive |http:8888,jms:12601,rmi:12401
24 August 2005
Using OracleAS 10.1.3 DP4
There are a couple of changes with the DP4 release which may catch you out .... unless you read the release notes that go along with it of course.