Track the Changes through Admin Console

In Production , some times we need  to track all admin console level changes for Audit and debug the changes.

This can be done with below step of changes

How to do it...
Carry out the following steps to protect the configuration changes:
1. Access the Administration Console with your web browser at http://prod01.domain.local:7001/console.
2. Click on the Preferences link.
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.

Thanks
Babu

Protect Chnages in Administractor Changes @ Weblogic Server 12c

This is very important as Part of Administration task . Why because we need to track all admin changes, fail over and all other users changes should be logged.


Change management in a production environment is critical and has to be done with careful
preparation and planning. WebLogic provides a way to save and later track all the changes
made in its configuration.

This recipe focuses on how to enable the embedded configuration backup, how to enable
the configuration changes audit, and how to automatically record a Jython script to all the
changes made in the Administration Console that can be used later with WLST.

Common Issues with WL @ Prod Env

Common Issues with Weblogic Server @ Production Environments

• 1.       Application URL is not accessible.
• 2.       Application responding very slowly.
• 3.       Server state is down.
• 4.       Server state is crashed.
• 5.       Server state is hanging.
• 6.       All Database Exceptions.
• 7.       Connection pool closed issues.
• 8.       Disk Space issues.
• 9.       Application Deployment Issues.
• 10.   File not found exceptions.
• 11.   Out of memory Exception.
• 12.   Heap out of memory
• 13.   Perm gen space error
• 14.   Null pointer exception.
• 15.   Struck thread in Servers
• 16.   High CPU utilization.
• 17.   Socket exceptions.
• 18.   Unable to read data from socket.
• 19.   Too many open files exception.
• 20.   Performance issues.
• 21.   Port or listen address already in used exception.
• 22.   Socket already in used exception.
• 23.   Proxy server exceptions
• 24.   Node manager bind exception.
• 25.   Authentication and Authorization. 

Thanks,

Babu