Backup and Recovery Oracle Fusion Middleware Online Documentation Library

Managing the Embedded LDAP Server 9-9

9.6 Backup and Recovery

If any of your security realms use the Default Authentication, Authorization, Credential Mapping, or Role Mapping providers, you should maintain an up-to-date backup of the following directory tree: domain_name serversadminServerdataldap In the preceding directory, domain_name is the domain root directory and adminServer is the directory in which the Administration Server stores run-time and security data. For more information backing up the embedded LDAP server data, see the following topics: ■ Back Up LDAP Repository in Managing Server Startup and Shutdown for Oracle WebLogic Server ■ Configure backups for embedded LDAP servers in Oracle WebLogic Server Administration Console Help If the embedded LDAP server file becomes corrupt or unusable, the Administration Server will generate a NumberFormatException and fail to start. This situation is rare but can occur if the disk becomes full and causes the embedded LDAP file to enter into an invalid state. To recover from an unusable embedded LDAP server file, complete the following steps: 1. Change to the following directory: domain_name serversadminServerdata 2. Rename the embedded LDAP server file, as in the following example: mv ldap ldap.old By renaming the file, and not deleting it completely, it remains available to you for analysis and potential data recovery. 3. Start the Administration Server. When the Administration Server starts, a new embedded LDAP server file is created. 4. Restore any data to the new embedded LDAP server that was added since the time the WebLogic domain was created. If you have configured a backup of the embedded LDAP server, you can restore the backed up data by importing it. For information, see Section 9.4, Exporting and Importing Information in the Embedded LDAP Server. 9-10 Securing Oracle WebLogic Server 10 Managing the RDBMS Security Store 10-1 10 Managing the RDBMS Security Store WebLogic Server provides the option of using an external RDBMS as a datastore that is used by authorization, role mapping, credential mapping, and certificate registry providers. This datastore, called the RDBMS security store, is strongly recommended for the use of SAML 2.0 services in two or more WebLogic Server instances in that domain, such as in a cluster. The following sections explain how to configure and manage the RDBMS security store: ■ Section 10.1, Security Providers that Use the RDBMS Security Store