Here some quick tips for Jdeveloper running on linux as it might not as convienetn as the windows version, so you do not need to check the install guide pages.
1. start jdev —
2. To access the quick start –
From quick start you can start jdev, can also go to config page to create/extend your jdev’s domain servers.
3. uninstall –
4. page to get all the jdev extenstions by manually download.
The reason you should know this – because of sometimes you can not access the jdev update site to get all the downloads for your jdev extension.
Such as SOA editor extension or webcenter extension from oracle internall site, you can go to this page to manually download zip file and to extend your jdev.
By W.ZH Jan 2009
when I migrate a sample project from 10g or 11g to my version 11g jdev, every thing looks fine and project migrated, but when you try to run it, you will see the JDBC connection error in log (password null), and also you will see that if you change or even open the DB connection and then try to save it, get an error of “unable to initialize credential store.”
Possible solutions from OTN forum:
This looks like a corrupted cwallet.sso file. It happens sometimes that this file, which holds the credentials of the connections and roles.
This file is located in the src/META-INF folder. It can be recreated if you close JDev, delete (or rename) the file and start JDev again. Then you have to add the connection to the applications again. This should recreate the cwallet.sso file.(W.Zh: I found there are two sso and
To my knowledge this should not happen in JD184.108.40.206.1 This cwallet.sso problem was first discovered in TP4 (frequently), where the file got corrupted when you interrupt starting the embedded server.
This has not happened to me since JDev 220.127.116.11.0 I just remember this when I saw you error.
I’ve figured a solution for this bug.
– Creating a new application
– Creating a new connection in the app ressources (now it’ll work : no “Unable to initialize credential store”)
– Copying Model and ViewController project from previous application
Hi. I recently got JDev 18.104.22.168.1 and when I opened my current project, it was migrated from JDev 22.214.171.124.0 and I got the same problem. I solved this checking
Hope this resolution be usefull for somebody.
W.ZH: I slove my problem by method 2 (This time OTM forum can have answers ;-)). Jdev 11g seems need some time to get mature.
By W.ZH Oct 2008
1. Download the Jdev 11g from