which commonly translates into something like
Note that in the last realized form, the opmn-request-port is left off, so the port will default to 6003.
When its operating against Oracle Application Server, admin_client.jar uses the OPMN request port to determine what the exact network location is for the OC4J instance that is specified.
If you find you are running into an error that states "Failed at Could not get DeploymentManager", then its well worth double checking what the actual OPMN request port actually is.
This can be done in three ways I can think of:
1. From the command line using the opmnctl command
C:\oracleas\opmn\bin>opmnctl status -port
2. By looking at the $ORACLE_HOME/opmn/conf/opmn.xml and looking for the value of the defined request attribute in the port tag:
3. And finally, with the 10.1.3.1 release, you can use Application Server Control (ASC) to display the port values of the OPMN service. On the Cluster Topology page, scroll down to the bottom and click the Runtime Ports link. This will display all of the ports currently in use by the server, including the OPMN service.
Once you have the OPMN request port, if it differs from 6003 then ensure that you use the correct value with the deployer_uri so that admin_client can connect to the OPMN service.
For example, given the information above, a valid deployer URL would be:
Which can be validated as accurate:
C:\oracleas\j2ee\home>java -jar admin_client.jar
deployer:oc4j:opmn://localhost:6005/admin oc4jadmin welcome1 -validateURI
URI deployer:oc4j:opmn://localhost:6005/admin is valid and connected