Enabling Automatic Configuration Backups

Monitoring and Troubleshooting 8-5 ■ you first deploy the production system ■ you add or remove deployed applications ■ the configuration is tuned for performance ■ any other permanent change is made. The domain configuration backup should contain the complete contents of the domain_nameconfig directory. For example: cd ~user_projectsdomainsmydomain tar cvf domain-backup-06-17-2007.jar config Store the new archive in a source control system, preserving earlier versions should you need to restore the domain configuration to an earlier point in time.

8.1.2.3 Backing Up Server Start Scripts

In a Oracle WebLogic Communication Services deployment, the start scripts used to boot engine and SIP data tier servers are generally customized to include domain-specific configuration information such as: ■ JVM Garbage Collection parameters required to achieve throughput targets for SIP message processing see Section 8.8, Tuning JVM Garbage Collection for Production Deployments . Different parameters and therefore, different start scripts are generally used to boot engine and SIP data tier servers. ■ Configuration parameters and startup information for the Oracle WebLogic Communication Services heartbeat mechanism. If you use the heartbeat mechanism, engine tier server start scripts should include startup options to enable and configure the heartbeat mechanism. SIP data tier server start scripts should include startup options to enable heartbeats and start the WlssEchoServer process. Backup each distinct start script used to boot engine tier, SIP data tier, or diameter relay servers in your domain.

8.1.2.4 Backing Up Logging Servlet Applications

If you use Oracle WebLogic Communication Services logging Servlets see Section 8.7, Logging SIP Requests and Responses to perform regular logging or auditing of SIP messages, backup the complete application source files so that you can easily redeploy the applications should the staging server fail or the original deployment directory becomes corrupted.

8.1.2.5 Backing Up Security Data

The WebLogic Security service stores its configuration data config.xml file, and also in an LDAP repository and other files.

8.1.2.5.1 Backing Up SerializedSystemIni.dat and Security Certificates All servers create a

file named SerializedSystemIni.dat and place it in the servers root directory. This file contains encrypted security data that must be present to boot the server. You must back up this file. If you configured a server to use SSL, also back up the security certificates and keys. The location of these files is user-configurable.

8.1.2.5.2 Backing Up the WebLogic LDAP Repository The default Authentication,

Authorization, Role Mapper, and Credential Mapper providers that are installed with