Database Reference
In-Depth Information
In most cases, configuration changes can be rolled back by simply undoing the
configuration change itself, though there are scenarios where damaging reper-
cussions have occurred. For example, modifying the number of maximum con-
nections in your connection pool typically involves zero risk. On the other hand,
in certain scenarios where a second SOA server has never yet been started and
conflicting JVM configurations are found across the servers, irrecoverable star-
tup issues may occur on that second SOA server.
We, therefore, recommend performing a backup, as a minimum, of the following
prior to making any configuration changes:
SOA domain
Database
Configuration changes that are committed to the database can usually be rolled
back by undoing them or restoring the database itself. Configuration changes
to any of the software installs (for example, files under the $MW_HOME/
Oracle_SOA1, $JAVA_HOME , and $MW_HOME/wlserver_10.3) are usually
undoable by simply restoring the configuration change to its original settings.
Before architectural changes
Examples of architectural changes include extending your domain to install ad-
ditional products or converting your single node installation to a cluster. Even
though performing these activities should not be a problem, the administrator
often has to deal with unforeseen setbacks. Some architectural changes are
simple, while others are more involved. Performing a full offline backup of the
entire infrastructure is recommended in these cases.
The database, JMS file stores, and transactions logs may not necessarily be
backed up, as the impact on transactional data due to these changes is ex-
tremely low.
Search WWH ::




Custom Search