• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Problem with weblogic start up

 
Ranch Hand
Posts: 79
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I am facing permission problem while starting up weblogic admin server in Linux RedHat 3.
Here is the scenario:
I have made a domain under in /opt/app/bea/user-projects/domains/dev-domain/
and the owner of this director is "weblog".

Now I want another user with a different user name to start and stop server(only one admin server is there) in this domain.
But when the user runs the ./startWebLogic.sh script he gets the error as :

<Dec 6, 2004 4:16:14 PM CST> <Info> <Management> <BEA-140013> </opt/app/bea/user_projects/domains/dev_domain/config.xml not found>
/opt/app/bea/user_projects/domains/dev_domain/config.xml not found

No config.xml was found.
Would you like the server to create a default configuration and boot? (y/n): $

What kind of permission does the user need to start/stop the admin server?
The user already has admin rights for this domain but still he is not able to start the admin server as the start script is not even asking for username.

Thanks in advance

Deepak
 
Ranch Hand
Posts: 245
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think that the problem is an O/S permission one. Generally there are not alot of O/S permission that are required to stop a server. You need to be able to read config.xml for the server and that is about it. Does the user have permission to read that file?

However, to start a server you need very different permissions unless your shell script is doing a setuid (generally considered a bad thing in Unix for a shell script). The user starting WLS will have to have write access to the files and directories under, in your case, /opt/app/bea/user_projects/domains/dev_domain. If these files are owned by someone else and they are not writeable by the current O/S user then the startup may fail in wierd and wonderful ways.
 
reply
    Bookmark Topic Watch Topic
  • New Topic