• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

weblogic.Admin ... doesnt work???????

 
Ranch Hand
Posts: 136
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi
I need help to run the Admin commands. Following the cmd line interface ref pdf from bea here is what i did.
Set the wls environment as from
C:\bea\weblogic700\server\bin>setWLSEnv.cmd
my bin has the setWLS.cmd which runs the server.
In order to practice the weblogic.Admin commands like following:
java weblogic.Admin -url myserver:7001 -username weblogic
-password weblogic GETSTATE myserver

*where do i type this command. As the pdf says in the Command Line Reference i'v set the right classpath and when i go in the bin C:\bea\weblogic700\server\bin or the server directory with another cmd window i cant run a single admin command.
please help and tell where and how to practice these cmd line interfaces commands?
Also is there anywhere in the wLS pdfs a mention of the return values these Admin commands give.I just found a description of the command itself.
thanx
faiza
 
Ranch Hand
Posts: 86
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Faiza:
When you set the Environment variables in a Shell (MSDOS Prompt), it's valid only inside that shell. Your weblogic.Admin and so commands works fine only inside that shell.
Hence, if you open another cmd window, unless you do the setwlsenv.cmd again, you're going to have problems.
To avoid this, you can go to "My Computer" -> Properties and set the environment variables (almost to everything needed ), so that these variables are available system wide.
Then every cmd shell you open, will be fine with all the env. variables
[ January 07, 2003: Message edited by: Madan, Gopal ]
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic