• 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

confusion regarding config files of admin and managed servers ---HELP PLEASE !!!!!

 
Ranch Hand
Posts: 62
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I would highly appreciate if anyone can solve my question.
In the administration manual, it is given :
The administration server maintains the configuration information for all server instances that participate in the cluster. The config.xml file that resides on the administration server provides a single repository for all clustered instances (and other managed instances) in the administration server's domain.
You do not create a separate configuration file for each server in the cluster, as with previous WebLogic Server versions. !!!
What does it mean ? Of course when we have "Managed server" in individual machine, automatically the config.xml file will be created and I guess it will be used by the respective managed server when we start it in the cluster..
As per what is given in the manual, should I totally ignore the individual config file and concentrate only on the config file of admin server ? But whenever we do deploying our application to each of the managed servers, the respective config.xml files will be updated and hence I feel these config files very much have to be taken care by us.
Once again I highly appreciate if anyone can solve my confusion about the config files of managed server and config file of admin server.
thanks.
 
Ranch Hand
Posts: 113
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
As I understand it, the startup is different for the managed servers. When a managed server starts up it knows the ip address of the admin server. The managed server establishes a connection to the admin server and pulls down the configuration information from there. I don't think it ever looks at the config.xml locally.
Note: There is a feature in 7.0 and later that allows you to force the server to start up using a local config.xml, but it should only be used when the admin server is not available.
 
deepa karkala
Ranch Hand
Posts: 62
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Steve for your reply.
So, should I ignore the local config.xml files of the managed servers ?
In fact, in my current setup, I have 4 managed servers6.1 1,2,3,4 in 4 different machines. Looks like, the config file of server 2 is just copied from server 3 because throughout this config.file, I can see target as server 3 which should be logically server 2.
I thought I do the corrections in the config file of server2 to make the target as server2. But as per your opinion, I don't think I need to touch any of these local config files and leave them as they are.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic