Databases Reference
In-Depth Information
3. Enable the following checkboxes:
Show Advanced Sections
Warn If User Holds Lock
Warn User Before Taking Lock
4. Click on the Save button.
5. Open the WLST Script Recording tab.
6. Enable the following checkboxes:
Append to File
Automatic Recording
7. Click on the Save button.
8. Obtain the configuration lock by clicking on Lock & Edit.
9. Click the PROD_DOMAIN link on the Domain Structure on the left.
10. Choose Change Log and Audit in the Configuration Audit Type drop-down menu.
11. Enable the Configuration Archive Enabled checkbox.
12. Set the number of back files in the Archive Configuration Count text field. Type 250
as the value. The default value is 50 .
13. Click on the Save button.
14. Activate the changes by clicking on the Activate Changes button.
15. You will have to restart the Administration Server for the changes to take effect.
How it works...
The Preferences section changes will enable some messages in the Administration Console
that will warn the user when the edit lock is already being used in another browser session.
This is important in a production environment to avoid the changes being made by other
administrators at the same time.
The WLST Script Recording changes will enable a Jython script to be recorded to every change
made in the Administration Console. The script is recorded by default in the $DOMAIN_HOME
root directory with a filename Script*.py .
With the backup configuration enabled, every time the domain configuration is modified,
a JAR file containing the old coniguration ($DOMAIN_HOME/config/* ) will be archived until
the limit of 250 archives as you defined in Archive Configuration Count. Change the value
so it suits your needs. JAR will be saved in the directory $DOMAIN_HOME/configArchive/
config-XXX.jar . The lesser the XXX number, the older the configuration archive is.
 
Search WWH ::




Custom Search