Technical data

10 Recovering Failed Servers
10-8 Configuring and Managing WebLogic Server
Example of Archives of config.xml During Startup
If your domain configuration is stored in config.xml, when you start the domain’s
Administration Server, the Administration Server:
1. Copies
config.xml to config.xml.original.
2. Parses
config.xml. Depending on the domain configuration, some WebLogic
subsystems add configuration information to
config.xml. For example, the
Security service adds MBeans and encrypted data for SSL communication.
3. Copies the parsed and modified
config.xml to MyConfig.xml.booted.
The Administration Server uses the parsed and modified
config.xml. When you
update the domain’s configuration, it copies the old
config.xml to
domain-name\configArchive\MyConfig.xml#2.
Backing Up Security Data
The WebLogic Security service stores its configuration data config.xml file, and also
in an LDAP repository and other files.
Backing Up the WebLogic LDAP Repository
The default Authentication, Authorization, Role Mapper, and Credential Mapper
providers that are installed with WebLogic Server store their data in an LDAP server.
Each WebLogic Server contains an embedded LDAP server. The Administration
Server contains the master LDAP server which is replicated on all Managed Servers.
If any of your security realms use these installed providers, you should maintain an
up-to-date backup of the following directory tree:
domain_name\adminServer\ldap
where domain_name is the domain’s root directory and adminServer is the directory
in which the Administration Server stores runtime and security data.
Each WebLogic Serve has an LDAP directory, but you only need to back up the LDAP
data on the Administration Server—the master LDAP server replicates the LDAP data
from each Managed Server when updates to security data are made. WebLogic security