Technical data

Backing Up Configuration and Security Data
Configuring and Managing WebLogic Server 10-7
The new file, WL_HOME\samples\server\config\medrec\config.xml,
represents the MedRec domain with the new server instance. The previous file,
WL_HOME\samples\server\config\medrec\configArchive\config.xml#2,
contains the MedRec domain configuration as it was prior to creation of the new server
instance.
The next time you change the configuration, MedRecServer saves the current
config.xml file as config.xml#3. After four changes to the domain, the
configArchive directory contains four files: config.xml#2, config.xml#3,
config.xml#4, config.xml#5. The next time you change the configuration,
MedRecServer saves the old
config.xml as config.xml#5. The previous
config.xml#5 is renamed as config.xml#4, and so on. The old config.xml#2 is
deleted.
Configuring the Number of Archived config.xml Versions
To configure how many previous versions of the domain configuration are archived:
1. In the left pane of the Administration Console, click on the name of the domain.
2. In the right pane, click the Configuration tab. Then click the General tab.
3. In the Advanced Options bar, click Show.
4. In the Archive Configuration Count box, enter the number of versions to save.
5. Click Apply.
WebLogic Server Archives config.xml during Server Startup
In addition to the files in domain-name\configArchive, the Administration Server
creates two other files that back up the domain’s configuration at key points during the
startup process:
! domain-name\config-file.xml.original—the configuration file just before
the Administration Server parses it and adds subsystem data.
! domain-name\config-file.xml.booted—the configuration file just after the
Administration Server successfully boots. If the
config.xml becomes
corrupted, you can boot the Administration Server with this file.