12. Domain Configuration Change
Configuration Change Management
Process
1. WhentheAdministrationServer starts, itreadsthedomain'sconfigurationfiles,
includingconfig.xml fileandany subsidiary configurationfilesreferredtoby the
config.xml fileandusesthedatatoinstantiatethefollowingMBeantreesin
Memory:
● A read-only treeof ConfigurationMBeansthatcontainsthecurrentconfigurationof
resourcesthatareontheAdministrationServer.
● Aneditabletreeof all ConfigurationMBeansfor all serversinthedomain.
13. Domain Configuration Change
Configuration Change Management
Process
2. Toinitiateaconfigurationchange, youdothefollowing:
a. Obtainalock onthecurrentconfiguration.
b. Makeany changesyoudesire, usingthetool of your choice(theAdministration
Console, WLST, the JMX APIs, and such).
c. Saveyour changestoapendingversionof theconfig.xml file, usingthe
Save buttonintheAdministrationConsole; usingtheWLST save command;
or usingthesave operationontheConfigurationManagerMBean.
14. Domain Configuration Change
Configuration Change Management
Process
TheConfigurationManager servicesavesall datafromtheeditMBeantreetoaseparate
setof configurationfilesinadirectory namedpending.
Thepending directory isimmediately below thedomain'srootdirectory. Forexample, if
your domainisnamedmydomain, thenthedefaultpathnameof thependingconfig.xml fileis
mydomain/pending/config.xml.