This content has been marked as final. Show 5 replies
I found information about those environment variables, and tried setting JDEV_USER_DIR to $HOME/.jdeveloper (which appears to be what it defaults to, anyway). That had no effect. The DOMAIN_HOME is getting created under there, but the error I'm seeing regarding the appdir persists.
I found in the WLST documentation information regarding the setOption() function and the AppDir as being one of the options that can be modified. I tried adding that to the CreateDefaultDomain.py script, closing JDev, deleting the DefaultDomain directory, then restarting and retrying the integrated server configuration, but it still fails while griping about permissions issues with the shared MH_HOME directory. As it turns out, when it tries to configure the server, it rewrites the CreateDefaultDomain.py script and overwrites my changes.
Hum... I have never used an environment like yours, so I don't have real-world experience to rely on. Here are a few pointers for further troubleshooting anyway:
- Have you tried to launch JDeveloper from the command line? If so, are you getting more specific errors when trying to start the server?
- Is SELinux enabled on your server? If yes, have you tried deactivating it?
- Have you tried to give sudo rights to a test user and launch JDeveloper under sudo?
Worst case, what you could try to do is to install a standalone WebLogic instance, then create one domain per developer. You can configure this instance as an integrated server by creating a connection in the Application Server Navigator. Your users will not see the difference (as long as they run on the same server).
Let me know how it goes.
Launched from the command line, and no further information.
No SELinux enabled.
If I ran it as sudo root (or sudo oracle) I'm sure it would work for the first user, because then the user would be able to write in the shared directory. However, then the second user would try to create the appdir in the same, shared location and would stomp on the first user.
There has to be a way to designate a non-default location for the appdir, or this won't work.
Yes, we actually do have a per-developer WLS installation, but it is not the "Integrated" one so things like right click->Run do not work (those always go to the integrated instance). We are able to deploy full apps to the per-developer instance, but some of these other features that the developers are accustomed to using do not work without the integrated server working.
Well as it turns out, there is a very elegant way of dealing with this situation as documented in this Oracle blog post:
All I had to do was define the server that I had already configured as an Integrated Server instead of a Standalone Server, then bind the application to the integrated version of the server, and voila, it worked!