Presentacion SBL Customers Day 3 Ruei And Amp for Siebel
Upcoming SlideShare
Loading in...5
×
 

Presentacion SBL Customers Day 3 Ruei And Amp for Siebel

on

  • 1,964 views

 

Statistics

Views

Total Views
1,964
Views on SlideShare
1,936
Embed Views
28

Actions

Likes
1
Downloads
49
Comments
0

3 Embeds 28

http://blogs.oracle.com 21
https://blogs.oracle.com 5
http://www.slideshare.net 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Presentacion SBL Customers Day 3 Ruei And Amp for Siebel Presentacion SBL Customers Day 3 Ruei And Amp for Siebel Presentation Transcript

    • <Insert Picture Here> Gestión de Siebel
    • Siebel Lifecycle Management Install / Upgrade From Production Application • Ensure quality and performance with a comprehensive testing solution. • Monitor the health and capacity DEV utilization of your Siebel server Dev / Test Functional environment. System Testing • Monitor real end-user response time Provisioning as well as response time from synthetic service test transactions. • Diagnose performance and Oracle availability problems through PROD Enterprise TEST performance analysis. Manager • Track configuration changes to Siebel Load Application Servers and Server Testing Component parameters.
    • Soluciones • Application Testing Suite • Functional Testing • Load Testing • Test Management • Siebel Management Pack • Monitorización y Métricas • Workflow, Policies, Componentes • Diagnósticos (SARM) • Gestión de Configuración • Monitorización de Servicios (Service Tests)
    • Soluciones • Real User Experience Insight • Gestión de Actividad de Usuarios contra Siebel • Monitorización de Rendimiento, Disponibilidad, Uso, Errores Siebel • Gestión de Nivel de Servicio por Usuario, Proceso de Negocio, Componente • Análisis de Causa Raíz de Problemas
    • Siebel Management • “So after we became part of Oracle, we shipped a graphical tool (Siebel Diagnostic Tool) as part of Application Management Pack for Siebel. In fact, we have done more to the management tooling of Siebel in the past year than the 10+ years when Siebel was an independent company” • Chung Wu • Application Management Pack for Siebel PM • Original product manager for SARM
    • ¿Por Qué es Importante el Testing?. 9.0 Product Effectiveness Customer Satisfaction Software Reliability 8.5 Speed of Product Scalability of Product 8.0 7.5 7.0 6.5 6.0 No test Informal test/formal test Formal test using based on written automated tools plan/Other 1 Resultsfrom Q1 2003 Customer Satisfaction Survey. 2 Product Effectiveness is the average satisfaction ratings of the nine (9) product functionality items.
    • Testing de Entornos Siebel • User Action: Click Page Tab to Select Accounts Screen With Siebel Automation Objects Without Siebel Automation SiebApplication(“CallCenter”). Browser(“Siebel Call”). Page(“Siebel SiebPageTabs(“PageTabs”). Call_2”). Frame(“_swescrnbar”). GotoScreen “Accounts” WinObject(“Default”). Click 90,13
    • <Insert Picture Here> Jean-Pierre Garbani Forrester Research “Real life experience shows: 74% of problem alerts come from end users complaining to the service desk about performance problems, not from monitoring infrastructure components” Los clientes requieren cada vez más una visión integrada en la gestión de servicios desde el punto de vista de IT y el Usuario Final
    • <Insert Picture Here> Use Case 1 Support requests
    • Use Case 1 – Support Requests What happened, when and where for a specific user • Support desk receives a complaint from a user • Siebel performance is poor • User is Chuck Cheng, logged in as ccheng • No details known about where in Siebel he was working • No details known about what time the occurrence actually was • No details known about which Siebel component was causing this
    • Use Case 1 – Support Requests Step 1: Look up CCHENG and his activity in Siebel from RUEI • Users are shown on the dashboard • We can drill into user analysis immediately
    • Use Case 1 – Support Requests Step 1: Look up CCHENG and his activity in Siebel from RUEI • Set a filter on ccheng
    • Use Case 1 – Support Requests Step 1: Look up CCHENG and his activity in Siebel from RUEI • Review the user session • Apparently the login and logout have been slow performing • Additionally there was poor performance when going to the Sales Order Screen
    • Use Case 1 – Support Requests Step 2: Analyze his activity in Siebel Managent Pack Manual Step: Copy/Paste the username and/or time from RUEI into AMP for Siebel
    • Use Case 1 – Support Requests Step 2: Analyse his activity in Siebel Managent Pack • Check the top Server Response Time calls
    • Use Case 1 – Support Requests Step 2: Analyse his activity in Siebel Managent Pack • Review most CPU time is spent on Script execution
    • Use Case 1 – Support Requests Step 2: Analyse his activity in Siebel Managent Pack • Last action of Transform Order is taking top-CPU time with about 10 seconds
    • Use Case 1 – Support Requests Step 2: Analyse his activity in Siebel Managent Pack • This matches to the Logout action executed from Sales Order Entry
    • <Insert Picture Here> Use Case 2 Siebel Performance Analysis
    • Use Case 2 – Siebel Performance Analysis What happened, when and where • Intermittently Siebel performance is bogged down • There is no clear view on when it occurs • It is not known which Siebel components are affected • It is not known which Siebel servers are affected
    • Use Case 2 – Siebel Performance Analysis Step 1: Look up which components are slow performing • Siebel components are shown on the dashboard • You can drill down from there into Server analysis
    • Use Case 2 – Siebel Performance Analysis Step 1: Look up which components are slow performing • From there you can see • You can drill down from there into Server analysis
    • Use Case 2 – Siebel Performance Analysis Step 1: Look up which components are slow performing • Drilling down into the server analysis will give you the time at which the application was bogged down (e.g. 13:50 hrs)
    • Use Case 2 – Siebel Performance Analysis Step 1: Look up which components are slow performing • Copy/paste the time period of the event over into Enterprise Manager AMP and run a server performance report
    • Use Case 2 – Siebel Performance Analysis Step 1: Look up which components are slow performing • Lastly, drill down into the specific server components and performance to identify bottleneck Instances
    • Clientes de Calidad de Aplicaciones Financial Services e-Commerce & Media Communications and Manufacturing IT Services and Software
    • B1. Company and organizational overview Clientes de Monitorización
    • The preceding 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. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.