Admin_client.jar credentials

I have created script to deploy war & ear file to OAS 10.1.3.x using admin_client.jar. I can get it to work if I use the oc4jadmin credential. However, I can not get the script to work if I use different account.
This account is member of ascontrol_admin role. I am able to deploy the application using this account through OAS Web UI but unable to do so from the command-line. We are interested in seperating oc4jadmin account from the account which will be used to deploy/undeploy application.
I get the standard error message regarding authentication shown below:
SEVERE: CoreRemoteMBeanServer.fetchMBeanServerEjbRemote Error reading application-client descriptor: Error communicating with server: Look
up error: javax.naming.AuthenticationException: Not authorized; nested exception is:
javax.naming.AuthenticationException: Not authorized; nested exception is:
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Not authorized; nested exception is:
javax.naming.AuthenticationException: Not authorized [Root exception is javax.naming.AuthenticationException: Not authorized] for
URL: ormi://orryesox.na.jmsmucker.com:12403/defaultjavax.naming.NamingException: Error reading application-client descriptor: Error commun
icating with server: Lookup error: javax.naming.AuthenticationException: Not authorized; nested exception is:
javax.naming.AuthenticationException: Not authorized; nested exception is:
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Not authorized; nested exception is:
javax.naming.AuthenticationException: Not authorized [Root exception is javax.naming.AuthenticationException: Not authorized] [Roo
t exception is java.lang.InstantiationException: Error communicating with server: Lookup error: javax.naming.AuthenticationException: Not
authorized; nested exception is:
Is there some thing special about oc4jadmin account? It seems like I should be able to create a new user wih ascontrol_admin role should be enught.... Anyone?
thanks

Okay, after reading the documentation, a thought come acrossed my mind... To use admin_client.jar, administrative account must belong to oc4j-administrator group? It looks like other out-of-box roles will not allow admin_client.jar to work..... Does any one know?
thanks

Similar Messages

Problem using admin_client.jar -addDataSourceConnectionPool

I am using admin_client.jar -addDataSourceConnectionPool to create a Connection Pool.
Below is the command i am using
java admin_client.jar deployer:oc4j:opmn://localhost:6003/home admin welcome -addDataSourceConnectionPool -applicationName default -name MySitePool -factoryClass <my application specific connection pool class> -dbUser new -dbPassword new -url <db url>
I guess the command looks good.
but when i try it out it gives me following error,
addDataSourceConnectionPool error: Can't find resource for bundle oracle.oc4j.admin.deploy.shared.util.Messages, key addDataSourceConnectionPool_failed
I am totally clueless about what could i be missing here.
Any help is highly appreciated.
Thanks
Vicky

I am using admin_client.jar
-addDataSourceConnectionPool to create a Connection
Pool.
but when i try it out it gives me following error,
addDataSourceConnectionPool error: Can't find
resource for bundle
oracle.oc4j.admin.deploy.shared.util.Messages, key
addDataSourceConnectionPool_failed
I am totally clueless about what could i be missing
here.
Same here, only that i try to add a native DataSource, resulting in:
addNativeDataSource error: Can't find resource for bundle oracle.oc4j.admin.deploy.shared.util.Messages, key addNativeDataSource_failed
i tried this with "C", "en_US.utf8" and "de_DE.utf8" locales set

Deployment Using admin_client.jar causes edit of system-jazn-data.xml

Greetings,
1. standalone OC4J version 10.1.3.3.0
2. Windows XP platform in a VM
Our automated deployment to a stand alone oc4j causes the system-jazn-data.xml file in the oc4j\j2ee\home\config folder to be overwritten. This process removes the pertinent application-specific login module information required for our JAAS security. Overwriting this file with a known working version followed by a restart of oc4j enables application login. What we would like to learn is how to control the content of the system-jazn-data.xml file during automated deployment with ant scripts using oc4j admin_client.jar. Note that when deployed with JDeveloper, the information in the orion-application.xml file is added back to the system-jazn-data.xml in the oc4j\j2ee\home\config directory and logging in is once again enabled.
THX
-Mike

Found that jar files were missing from autobuild. This continues to be an issue where libraries are added to WEB-INF\lib in JDeveloper and the individual jar files are needed for an automated build process.

Admin_client.jar with OAS 10.1.2.0.2?

I've tried unsuccessfully to use admin_client.jar with an opmn controlled OAS 10.1.2.0.2. I know this utility came out with 10.1.3, but I was hoping it is still compatible with 10.1.2. I suspect it's not, but could somebody confirm?
When I try the below, I never get confirmation that the URI is valid. It just stays at that state indefinitely. It does resolve the correct RMI port.
java -Djava.util.logging.config.file=logging.properties -jar in_client.jar deployer:oc4j:opmn://host/OC4Jinstance user pwd -validateURI
FINE: CoreRemoteMBeanServer.fetchMBeanServerEjbRemote Getting remote RMI context
for domain: ...
FINE: CoreRemoteMBeanServer.fetchMBeanServerEjbRemote CoreRemoteMBeanServer url:
ormi://<host>:<port>/default
Thanks. Brad C.

I am having the same issue.
FINE: CoreRemoteMBeanServer.fetchMBeanServerEjbRemote
Getting remote RMI context for domain: opmn-ho
me+oc4j-s2oraplt-6004-default
FINE: CoreRemoteMBeanServer.fetchMBeanServerEjbRemote
CoreRemoteMBeanServer url: ormi://servername:124
02/defaultAfter the above no response from application server, it stays indefinitely.
I am using AS 10.1.3.3.0.
Some one could help?
Edited by: Chackochen on Sep 4, 2010 1:44 AM

Using admin_client.jar from bash script

Hello,
When I make a call "java -jar admin_client.jar" from a bash script I always get 0 for $? even when there are errors reported in the console. How can I check the status correctly?
S

Greetings,
Can you see the console when running the script? I would try to test something simple like -testDatabaseConnection and you should see a result. If you cannot login the the server directly, pipe the output to a file. Next, build up your bash script with additional complexity as you go. Post the results here for the group to analyze.
THX
-Michael
Edited by: Michael F. Hardy on Dec 2, 2008 2:02 PM

Admin_client.jar and -bindAllWebApps

Hello,
The documentation says that -bindAllWebApps is an option parameter to admin_client.jar. I have app that deploys correctly with or without -bindAllWebApps however it always give me error if I don't add -bindAllWebApps Is this correct functionality? It sure is confusing.
M

Greetings,
We have experienced this same behavior. Note that when our application is deployed using -deploy or -rededploy, we found that -bindAllWebApps was necessary.
reference;
http://download-uk.oracle.com/docs/cd/B25221_04/web.1013/b14432/adminclient.htm#BABDBJAFYour application probably deploys a second time OK without the -bindAllWebApps because it was not undeployed. We found the results using -deploy and -redploy variable (ant, automated deployment) and therefore switched to a simple FTP of the war file followed by a restart of oc4j. Note that this strategy was only tested after an initial deployment of the ear file from the JDeveloper IDE.
-Michael

Admin_client.jar does not like -deploymentPlan switch

I 'm trying to deploy an app via admin client using the following command line:
java -jar $ORACLE_HOME/j2ee/home/admin_client.jar deployer:oc4j:opmn://$2.llnl.gov:6003/OpticsLoop oc4jadmin -deploy -file app.war -deploymentName $app -deploymentPlan plan.dat
It does not like the -deploymentPlan switch. Error is:
Admin command usage error: Unknown -deploy switch: plan.dat
It will deploy other apps that don't use the -deploymentPlan. With this app I need the plan so I can disable apache commons logging library that conflicts with the log4j packaged with my app.
JDK5 and Oc4J 10.1.3.3. Problem seen on Windows as well as on Linux.

hi vamsee
I was able to deploy an application, using the "-deploymentPlan" switch, like this:
D:\oracle\oc4j_101330>java -jar j2ee/home/admin_client.jar deployer:oc4j:localhost:23791 oc4jadmin welcome -deploy -file d:\temp\DPThread638837App.ear
-deploymentName DPThread638837App -deploymentPlan d:\temp\DPThread638837App-localhost-plan.datIf I change the path for the deployment plan to something that does not exist, I get the message "... Unable to find deployment plan ..." :
D:\oracle\oc4j_101330>java -jar j2ee/home/admin_client.jar deployer:oc4j:localhost:23791 oc4jadmin welcome -deploy -file d:\temp\DPThread638837App.ear
-deploymentName DPThread638837App -deploymentPlan d:\temp\unknown.dat
Deploy error: Deploy error: Unable to find deployment plan d:\temp\unknown.dat.I don't know why it doesn't work for you.
success
Jan Vervecken

Admin_client jar - add "remove-inherited" for oracle.jdbc shared library

Guys,
I am using admin_client.jar utility which comes oracle 10.1.3 to deploy our web-application on the oc4j server, everythings is working fine, except for this small issue, where i want to avoid having the shared library "oracle.jdbc" inherited by web-module (which is by default inherited by all apps apparently), since i want to use the oracle-jdbc driver bundled with the war. Now i do that the solution is to introduce a "remove-inherited" tag (for the oracle.jdbc library) under the "inherited-shared-libraries" element in the orion-application.xml file (generated on deployment by oc4j), but what i want to know is how to automate this process of adding this entry, since we dont want to have any manual intervention on deployment.
Though admin_client.jar so far has provided all the functionality required for deployment but it apprarently doesnt any way where we can specify the shared-libraries not to be inherited by the deployed war..
Any comments/suggestions ?
Thanks and Regards,
Message was edited by:
user632496
Message was edited by:
user632496

Alright that makes sense.
Yes, spot on. The suggestion I made was contingent on having an EAR file -- even though we accept a WAR file from you, we ultimately produce an EAR file from it during the deployment phase. If you don't want to produce an EAR file then its not viable for you.
Another possible solution is one that you are sort of suggesting here -- each application can be specified as a child of a parent application -- from which it will inherit various libraries and configuration settings.
What you could do is to deploy a single, dedicated application on which you configure the shared-library import to the JDBC driver you want -- and then you simply choose that application as the parent, whereupon the child application will pick up the shared-library setting.
There current, visible parent of all deployed applications is the "default" application. What you could do is to tweak the configuration of the default applicaiton so it uses a different JDBC library to the one it inherits from its actual parent (the system application). The configuration for the default application is contained within the j2ee/home/config/application.xml file -- which if you look at it, is actually an "orion-application.xml" file. So if you make the change there, it will apply to all the applications that are deployed to the container.
Just found it in the doc:
http://download.oracle.com/docs/cd/B32110_01/web.1013/b28952/classload.htm#CIHFFBCA
Even easier, what you evaluate is a simpler approach where you install and publish the Oracle JDBC driver you wish to use, with the name "oracle.jdbc" and set it with a higher version (which I assume you are doing) than the deafault one -- whereby from how the config in the application.xml is set and where the oracle.jdbc driver is imported, it should pick up the higher version -- so that way you don't even need to change the config file -- simply publish the later versioned library using the name oracle.jdbc and it should be picked up.
Currently the version in 10.1.3.3 is:
<shared-library name="oracle.jdbc" parent="api" version="10.1.0_2">
So if you published the jdbc driver you want to use with the name oracle.jdbc and a higher version, then the import of oracle.jdbc will default to the latest version, which should pick up your library.
Thus all you need to do is a one-off publishing operation of a new shared-library (oracle.jdbc: 10.1.2.3 for example) and it then should be picked up implicitly by all deployed applications.
Worth testing my theory though ... ;-)
-steve-

Admin_client.jar - connect to a remote standalone oc4j instance

Hi
I have installed a standalone instance of OC4J on a remote linux box. I am trying to connect to that running instance on a windows box using the admin client jar supplied in the oc4j_admin_client_101310.zip file but get the following error -
Failed at "Could not get DeploymentManager".
I am able to connect to a remote OPMN managed instance and a local standalone instance but not to the remote standalone instance. I know the remote instance is ok as i have logged in and validated the URI using the admin_client.jar on that box. The URI format i am using is as follows -
deployer:oc4j:host:23791
Is it possible to connect to this instance remotely?
Thanks
George

Hey George -- admin_client.jar can connect to local/remote OC4J standalone instances -- it connects to all sorts of things in 10.1.3.
The "could not get deployment manager" message is very vague, I certainly appreciate that.
What it usually comes down to is the deployer URI being incorrect in either the format being used or the host:port being incorrect.
Sounds like you have validated the URL correctly.
Just as a sanity check -- you can ping the remote server from the windows box?
The oc4j standalone instance is up and running?
The ORMI port is 23791?
What you could do if you want to see if there is an underlying problem is to enable the client side logger for admin_client.jar.
The doc describes it here:
http://download.oracle.com/docs/cd/B31017_01/web.1013/b28950/adminclient.htm#CHDHIABJ
Set it progressively to the FINE, FINER, FINEST levels and see if anything suspicious is identified in the log outputs that might be helpful.
Let me know how it goes.
-steve-

Deploying with the admin_client.jar Utility

Does anybody have an issue with deploying app to a specific OC4J instance/Instances Within a Cluster using admin_client.jar? I'm always getting same error: "Failed at: 'Could not get Deployment Manager'". When I deploy it to a local standalone OC4J it works.
Thanks in advance

Hi all.
I am using oc4j 10.1.3 standalone and am using Ant to build and deploy my project. When we were using oc4j 9, the script that I have worked fine and the project was deployed successfully. However, after we upgraded to 10.1.3, the script broke.
I tracked down the issue to oc4j 9 using "http-web-site" as the web-site name versus 10.1.3 using "default-web-site". So, I changed that and everything built and deployed ok. However, after the application deployed, I could not login. It was like some thing was not getting binded properly. Here is the deployment command I was using:
java -jar C:\oracle_10_1_3/j2ee/home/admin.jar ormi://localhost:23791 oc4jadmin admin -deploy -file ../../deploy/iemp.ear -deploymentName iemp
So, having that fail, I tried to switch over to using admin-client.jar. However, everytime I try to use it, I get an error that says "[java] Failed at "Could not get DeploymentManager". Here is the deployment command I was using:
java -jar C:\oracle_10_1_3/j2ee/home/admin_client.jar deployer:oc4j:opmn://localhost/home oc4jadmin admin -redeploy -file ../../deploy/iemp.ear -deploymentName iemp -keepSettings
I ran through the posts in this thread to try to check out the port and other issues, but I cannot seem to access opmnctl.jar. In fact, I cannot find it anywhere within the Oracle dirs. When I try to run this on the command line "$ORACLE_HOME/opmn/bin/opmnctl status -port"
I get "Unable to access jarfile C:\oracle_10_1_3/opmn/bin/opmnctl".
I am out of ideas... can anybody shed some light for me?
Thanks,
--Nate

Automated Deployment Using admin_client.jar gives 500 error

Greetings,
1. standalone OC4J version 10.1.3.3.0
2. Windows XP platform in a VM
We have a mature deployment in that the deployment from JDeveloper is routinely successful. During the course of developing continuous integration builds, the automated deployment is now failing. We had succeeded previously using admin_client.jar and the deploy command as follows:
    <target name="deploy_oc4j" depends="assembleEar"
description="deploy the enterprise archive to a standalone oc4j using admin_client.jar">
    <echo>
      In deploy_oc4j target.
    </echo>
    <java classname="${j2ee.home}/admin_client.jar" fork="true">
        <jvmarg value="-jar"/>
        <arg value="${oc4j.deploy.admin_client}"/>
        <arg value="${oc4j.deploy.username}"/>
        <arg value="${oc4j.deploy.password}"/>
        <arg value="-deploy"/>
        <arg value="-file"/>
        <arg value="${this.application.name}".ear"/>
        <arg value="-deploymentName"/>
        <arg value="${this.application.name}"/>
        <arg value="-bindAllWebApps"/>
        <arg value="${default.application.name}"/>
    </java>
    </target>We now have two issues occurring and they may be related. We have added the capability of creating a connection pool and a data source using admin_client.jar commands:
    <target name="connectionpool" depends="deploy_oc4j"
      description="create a connection pool using admin_client.jar">
    <echo>
    Adding a connection pool.
    </echo>
      <java classname="${j2ee.home}/admin_client.jar" fork="true">
        <jvmarg value="-jar"/>
        <arg value="${oc4j.deploy.admin_client}"/>
        <arg value="${oc4j.deploy.username}"/>
        <arg value="${oc4j.deploy.password}"/>
        <arg value="-addDataSourceConnectionPool"/>
        <arg value="-applicationName"/>
        <arg value="${this.application.name}"/>
        <arg value="-name"/>
        <arg value="jdev-connection-pool-name"/>
        <arg value="-factoryClass"/>
        <arg value="oracle.jdbc.pool.OracleDataSource"/>
        <arg value="-dbUser"/>
        <arg value="username"/>
        <arg value="-dbPassword"/>
        <arg value="password"/>
        <arg value="-url"/>
        <arg value="jdbc:oracle:thin:@dev:1521:ORCL"/>
      </java>
    </target>
    <target name="datasource" depends="connectionpool"
      description="create a datasource using admin_client.jar">
    <echo>
    Adding Managed Data Source.
    </echo>
      <java classname="${j2ee.home}/admin_client.jar" fork="true">
        <jvmarg value="-jar"/>
        <arg value="${oc4j.deploy.admin_client}"/>
        <arg value="${oc4j.deploy.username}"/>
        <arg value="${oc4j.deploy.password}"/>
        <arg value="-addManagedDataSource"/>
        <arg value="-applicationName"/>
        <arg value="${this.application.name}"/>
        <arg value="-name"/>
        <arg value="jdev-connection-managed-name"/>
        <arg value="-jndiLocation"/>
        <arg value="jdbc/name"/>
        <arg value="-connectionPoolName"/>
        <arg value="jdev-connection-pool-name"/>
        <arg value="-dbUser"/>
        <arg value="username"/>
        <arg value="-dbPassword"/>
        <arg value="password"/>
      </java>
    </target>We complete the automated deployment and all ant tasks succeed, including creation of the connection pool and managed data source. During this process, the existing system-jazn-data.xml file is overwritten and our Application's <login module> information has been deleted. Upon editing this file and adding back the login module data and restarting oc4j, we can login to our application. The framework of the site is present along with graphics, yet every page visited yields a 500 error (jspx +and+ HTML). Since the entire deployment is done from ant, we do not have the capability of specifying a the web-app as development configuration. We need advice on how best to debug the deployed application as well as knowledge regarding the mechanism which causes the system-jazn-data.xml file in the oc4j/j2ee/home/config folder to be modified.
THX
-Mike
Edited by: Michael F. Hardy on Sep 11, 2008 5:03 PM
Edited by: Michael F. Hardy on Sep 11, 2008 5:03 PM
Edited by: Michael F. Hardy on Sep 11, 2008 5:05 PM

Found that jar files were missing from autobuild. This continues to be an issue where libraries are added to WEB-INF\lib in JDeveloper and the individual jar files are needed for an automated build process.

Deploy using admin_client.jar to Oracle SOA suite started up with java cmd

Hey,
Someone at work asked me to create a deployer command to deploy to a locally running OC4J SOA suite. I got it working like this:
java -jar %ORACLE_HOME%\j2ee\home\admin_client.jar deployer:oc4j:opmn://localhost/home oc4jadmin oc4jadmin -deploy -file <path> -deploymentName <appname> -bindAllWebApps
However when I implemented this using Maven2 there was a problem. It seems the SOA suite OC4J instance gets started up alternatively to get debugging to work. I started it up using the startupconsole which is automatically used in the Windows XP start menu.
They start it up like this:
java -Xrs -server -XX:MaxPermSize=128M -ms512M -mx1024M -XX:AppendRatio=3 -Djava.security.policy=$ORACLE_HOME/j2ee/home/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false -Djava.net.preferIPv4Stack=true -Xdebug -Xrunjdwp:transport=dt_socket,address=5000,suspend=n,server=y -jar oc4j.jar
This causes the URI for deployment to be invalid. I tried lots of other URI forms I found online but none of them work. Maybe you guys know?
Thanks in advance

Something noteworthy it seems...
I added a few extra lines to the command to enable logging (as found here)
http://theblasfrompas.blogspot.com/2007/12/adminclientjar-giving-standard-could.html
This results in the following peculiar stacktrace:
C:\Thomas\appz\OC4JLA~1\j2ee\home>java -Djava.util.logging.config.file=logging.p
roperties -jar admin_client.jar deployer:oc4j:opnm://localhost:6003/home oc4jadm
in oc4jadmin -validateURI
SEVERE: Oc4jDeploymentFactory.getDeploymentManager For input string: "//localhos
t"java.lang.NumberFormatException: For input string: "//localhost"
at java.lang.NumberFormatException.forInputString(NumberFormatException.
java:48)
at java.lang.Integer.parseInt(Integer.java:447)
at java.lang.Integer.parseInt(Integer.java:497)
at oracle.oc4j.admin.jmx.client.Oc4jDomainFactory.getDomainFromDeployerU
rl(Oc4jDomainFactory.java:283)
at oracle.oc4j.admin.deploy.spi.factories.Oc4jDeploymentFactory.getDeplo
ymentManager(Oc4jDeploymentFactory.java:127)
at javax.enterprise.deploy.shared.factories.DeploymentFactoryManager.get
DeploymentManager(DeploymentFactoryManager.java:112)
at oracle.oc4j.admin.deploy.api.J2EEDeploymentManager.validateURI(J2EEDe
ploymentManager.java:911)
at oracle.oc4j.admin.deploy.cmdline.ValidateURICommand.execute(ValidateU
RICommand.java:61)
at oracle.oc4j.admin.deploy.cmdline.Oc4jAdminCmdline.executeCommand(Oc4j
AdminCmdline.java:96)
at oracle.oc4j.admin.deploy.cmdline.Oc4jAdminCmdline.main(Oc4jAdminCmdli
ne.java:73)
Failed at "Could not get DeploymentManager".
I find this peculiar because I use an URI format as specified in the documentation.

Using admin_client.jar

Hello,
admin_client.jar command needs oc4jadmin password. Is there a way where it can accept encrypted password or certificate? I don't want to store/send plain text password from my bash script.
Thanks
m

I think no, and I belive is a problem of this services is only for development or test purposes, if you want to implement some kind of security has to be in the OS side like encrypting or securing the file as well not printing the output in the screen.
Hope this helps
Greetings

Is there a admin_client.jar et all. for OC4J9.0.4.x.x, OC4J10.1.2.x.x ?

I want to deploy a WAR file onto these oldies in one swoop, as is possible with admin_client.jar from the command line.

There's no way to do that with releases prior to 10.1.3.
There is the j2ee\home\admin.jar utility, but it only deploys ear files.
I've seen it done by the wrapping into an ear file with ant then calling admin.jar to deploy it.
-steve-

Developer access for admin_client.jar in 10.1.3.1

I would like our developers to be able to deploy their applications to OAS 10.1.3.1 on Solaris via command line. They already have an administrator login for OAS.
It appears that the default permissions for admin_client.jar is 750 meaning that only those in the dba group have read/execute access to this jar by default.
So my question is: What is the typical supported method for allowing developers to deploy their applications via command line?
Do you simply open permissions on the jar and that's fine?
Do you install the remote client administration tool and open permissions on that?
I know that they can deploy very easily in JDeveloper, but many developers here are using eclipse instead, and we may also want to automate the deployment into our build scripts, so I'd like to know how to open the access up to do this via OAS CLI utilities.
Let me know what you all are doing out there for your developers and how this is intended to be used by those that are not DBAs.
Thanks!
Tony

OK, in case anyone else had the same issues, here is what I ended up doing to resolve the issue:
Basically I created a new unix group for those I wished to have access to admin_client.jar util and layed down the oc4j remote administration zip with that user.
In our env the steps looked like this:
1. Create Group oc4jadm
2. Create User oc4jinst (group oc4jadm)
3. Add all users that will deploy apps to the oc4jadm group
4. Unzip the remote client with oc4jinst user
5. All files are now accessible by the oc4jadm group
6. Test admin_client.jar with normal user in the oc4jadm group
7. Everything works great.
This way I could install OAS 10.1.3.1 with the oracle user and dba group like normal and not have to dig around and haphazardly grant access to the various dirs and files required by the admin_client.jar. Everything required is bundled up in the remote admin client zip and it may be installed with a user other than oracle without issue. Plus it has the added bonus of working remote servers in case you don't want your developers accessing the server on which the OAS itself resides.
HTH,
Tony

Admin_client.jar credentials

Similar Messages

Maybe you are looking for