1. Configuration & Performance Management Oracle Enterprise Manager & WebLogic Server Management Pack Fumiko Yamashita Safe Harbor Statement: The views expressed on this presentation are my own and do not necessarily reflect the views of Oracle. The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making a purchasing decision. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

3. Business Transaction Management (AmberPoint)

4. Configuration Management of WebLogic

5. J2EE Performance Management (CAMM)

6. JVMDiagnostics (AD4J)

7. Provisioning of WebLogic domains/clusters/servers

8. Patch Automation for iAS

9. Coherence ManagementPerformance management For Oracle WebLogic/iAS $12K/Proc (WebLogic SE, WebLogic EE, WebLogic Suite, iAS EE)

10. Configuration ManagementConsistent Configuration by WebLogic Management Pack Compare and synchronize different WebLogic Environments Inconsistent memory settings Single view of all WebLogic configurations Synchronize configuration to follow Baseline Use out-of-the-box version controlto track all changes so systems can be restored like Windows “System Restore” Audit all configuration changes in version control

12. Accounting, Shipping, etc.SLAs Business Instrumentation Violations Track business value Track revenue, total orders, cost-per-fault Enforces agreements in real time Enables preventative and corrective actions Not just reporting violations after its too late

13. Business Challenges Hard to synchronise the configuration between multiple environments (development > UAT > production). No way to keep track how the configurations have been changed and how it affects the performance. Our application dies often. Can’t meet the SLA for uptime (i.e. 98%). Loss of business & revenue from downtime. Can’t identify the actual cause of unexpected shutdown or performance issues. Takes too long to recover from troubles. No standard method for troubleshooting. Costing IT too much. Hard to see what is up, what is down, which systems or pages are taking too long to respond. Hard to manage. Hard to see the performance issues.

14. Questions to You How are you synchronizing the configurations between NPE & Prod? How are you keeping track of all configuration changes? What is the uptime percentage of your applications & SLAs? Are you meeting the SLAs required by business? How are you identifying the actual cause of the unexpected shutdown and performance issues? Can you find the cause and proper fix with confidence every time? What is the cost to the business by experiencing the downtime? How are you monitoring the performance and configurations of your applications?