To migrate or recover WebLogic domains in case of failures, periodically backup of the entire domain directory tree from the administration server machine. This way, you can recover from a hardware or system failure by merely restoring the domain directory and restarting the admin server.
In case of an admin server crash, the admin server retains information about all of the running managed servers in the running-managed-servers.xml file. When restarted, the admin server reads this file and tries to contact any managed servers that were previously running. Discovery mode might increase the admin server startup time if no managed servers are running, but always use the discovery mode (by default, it is on), so that the admin server reconnects with any managed servers, if they are already running.
Some important files to be watched/backed up periodically from administration server machines are:
1. config.xml - Domain configuration repository.
2. config.xml.booted - Good backup of domain configuration repository from a successful boot.
3. boot.properties - Encrypted username and password for booting administration server.
4. running-managed-servers.xml - This is a list of dependent managed servers currently running. This file is used for discovering managed servers if administration server gets restarted while the managed servers are running.
5. domain/configArchive/ - Contains the copies of the Domain Configuration Repository files. When updated using administration tools administration server copies the old config.xml to this directory.
6. domain\adminserver\ldap\ldapfiles - Embedded LDAP data files currently being used by the domain's administration server.
7. *.ldift files - These file can be used for initializing the WebLogic Domain Embedded LDAP server back to when the domain was created.
8. domain/adminserver/ldap/backup/EmbeddedLDAPBackup.zip - Backup of the WebLogic domain embedded LDAP server. Embedded LDAP is used to store users, groups, roles, policies by the default security realm, myrealm's security providers.
9. Batch/Shell Scripts - setEnv.cmd/sh, startWebLogic.cmd/sh, startManagedWebLogic.cmd/sh.
Subscribe to:
Post Comments (Atom)
2 comments:
Hi,
We are using Cognos 8.2 with Weblogic 9.1 Application Server.
We have to deploy the p2pd.war file by using the deployment from weblogic.I have all the deployment steps to ,ap the file from source location to target but my doubt is that if in case my deployment fails or the file not correctly mapped then waht are the steps to revert the changes same as befor deployment.I mean if the deployment fails is the application affected or we have an option to redeploy and make the system back in existing stage.
Will be good if someone help me with the backup steps before deployment of the p2pd file in cognos using weblogic.
Thanks,
Abhishek
Require steps for back up on this comment.
Post a Comment