Foglight Cartridge for Siebel

Size: px
Start display at page:

Download "Foglight Cartridge for Siebel"

Transcription

1 Foglight Cartridge for Siebel Reference Guide Version 1.60

2 Copyright Quest Software, Inc All rights reserved. This document contains proprietary information, which is protected by copyright. The software described in this document is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Quest Software, Inc. Warranty The information contained in this document is subject to change without notice. Quest Software makes no warranty of any kind with respect to this information. QUEST SOFTWARE SPECIFICALLY DISCLAIMS THE IMPLIED WARRANTY OF THE MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Quest Software shall not be liable for any direct, indirect, incidental, consequential, or other damage alleged in connection with the furnishing or use of this information. Trademarks Foglight is a registered trademark of Quest Software, Inc. Foglight software includes 1996 Expect software (freeware). Expect and its documentation are copyrights and trademarks of Don Libes, Associates. Foglight support of SSL includes code copyright 1997 Eric Young (eay@cryptsoft.com). All rights reserved. Portions of the code in this package were distributed by Carnegie Mellon University. 1989, 1991, 1992, Carnegie Mellon University. All rights reserved. Portions of this product were obtained from the ucd-snmp package written by Wes Hardaker at the University of California, Davis copyright 1996, Copyright , Networks Associates Technology, Inc. All rights reserved. Portions of this code are also copyright , Cambridge Broadband Ltd. All rights reserved. Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Foglight software includes Info-ZIP. Info-ZIP is provided "as is" without warranty of any kind, express or implied. In no event shall Info-ZIP or it's contributors be held liable for any direct, indirect, incidental, special or consequential damages arising out of the use of or inability to use this software. All other trademarks and registered trademarks used in this document are property of their respective owners. World Headquarters 8001 Irvine Center Drive Irvine, CA info@quest.com U.S. and Canada: Please refer to our Web site for regional and international office information. Foglight Cartridge for Siebel Reference Guide Updated - September 2004 Software Version

3 CONTENTS CHAPTER 1 FOGLIGHT CARTRIDGE FOR SIEBEL CHAPTER 2 ABOUT THE SIEBELCLIENT AGENT SIEBEL SERVER AVAILABILITY MONITORING SIEBEL DATABASE AVAILABILITY AND RESPONSE TIME MONITORING ASPS USING SIEBELCLIENT AGENT STARTUP PARAMETERS SIEBELCLIENT AGENT TABLES AGENTMSGS TABLE SIEBELCLIENTSERVERHEALTH TABLE SIEBELCLIENTSESSIONSUMMARY TABLE SIEBELCLIENTTRANSACTIONDETAIL TABLE INVESTIGATIONS INVESTIGATING SIEBEL SERVER AVAILABILITY FROM A SINGLE LOCATION INVESTIGATING SIEBEL CLIENT SESSION AVAILABILITY FROM A SINGLE LOCATION INVESTIGATING SIEBEL CLIENT TRANSACTION AVAILABILITY FROM A SINGLE LOCATION INVESTIGATING SIEBEL CLIENT SESSION RESPONSE TIME FROM A SINGLE LOCATION INVESTIGATING SIEBEL CLIENT TRANSACTION RESPONSE TIME FROM A SINGLE LOCATION INVESTIGATING SIEBEL ENTERPRISE AVAILABILITY FROM ALL LOCATIONS INVESTIGATING SIEBEL DATABASE AVAILABILITY FROM ALL LOCATIONS INVESTIGATING SIEBEL CLIENT SESSION RESPONSE TIME FROM ALL LOCATIONS INVESTIGATING SIEBEL DATABASE SERVER AVAILABILITY i

4 Contents INVESTIGATING SIEBEL DATABASE SERVER TRANSACTION PERFORMANCE VIEWS SIEB_CLIENT_SESS_RESP_TIME_OVERVIEW GRAPH SIEB_CLIENT_SESS_STATUS_OVERVIEW GRAPH SIEB_CLIENT_SRVR_AVAILABILITY_OVERVIEW GRAPH SIEB_CLIENT_STAGE_DETAIL_OVERVIEW TABLE SIEB_CLIENT_TRAN_DETAIL_OVERVIEW TABLE SIEB_CLIENT_TRAN_RESP_TIME_OVERVIEW GRAPH SIEB_CLIENT_STAGE_RESP_TIME_DIFF GRAPH SIEB_CLIENT_STAGE_RESP_TIME_PER GRAPH SIEB_CLIENT_STAGE_ROWS_RETURNED GRAPH SIEB_CLIENT_TRAN_RESP_TIME_DIFF GRAPH SIEB_CLIENT_TRAN_RESP_TIME_PER GRAPH SIEB_CLIENT_TRAN_ROWS_RETURNED GRAPH SIEB_CLIENT_TRAN_STATUS_DETAIL GRAPH SIEB_CLIENT_ALL_SESS_RESP_TIME_OVERVIEW GRAPH...57 SIEB_CLIENT_DATABASE_AVAILABILTY_OVERVIEW GRAPH...59 SIEB_CLIENT_ENTERPRISE_AVAILABILITY_OVERVIEW GRAPH.61 RULES SIEB_CLIENT_SRVR_AVAIL RULE SIEB_CLIENT_STAGE_TIME RULE SIEB_CLIENT_STAGE_PCT RULE SIEB_CLIENT_TRANS_TIME RULE SIEB_CLIENT_TRANS_PCT RULE SIEB_CLIENT_TRANS_COMP RULE SIEB_CLIENT_STAGE_COMP RULE SIEB_CLIENT_AGENT_MSG RULE SIEB_CLIENT_TRANS_SLA RULE SIEB_CLIENT_STAGE_SLA RULE DEFINING USER DEFINED TRANSACTIONS DIAGNOSING RESPONSE TIME DEGRADATION ii

5 Contents CHAPTER 3 ABOUT THE SIEBELSERVER AGENT SIEBEL SERVER AVAILABILITY MONITORING ASPS USING SIEBELSERVER AGENT STARTUP PARAMETERS SIEBELSERVER AGENT TABLES SIEBEL COMPONENT GROUPS TABLE SIEBEL COMPONENT STATISTICS TABLE SIEBEL COMPONENTS TABLE SIEBEL LOG MESSAGE TABLE SIEBEL PROCESS INFORMATION TABLE SIEBEL SERVER HEALTH TABLE SIEBEL SERVER STATISTICS TABLE SIEBEL SERVER SUMMARY TABLE SIEBEL TASKS TABLE INVESTIGATIONS INVESTIGATING SIEBEL SERVER PERFORMANCE INVESTIGATING SIEBEL COMPONENT PERFORMANCE INVESTIGATING SIEBEL SERVER LOAD INVESTIGATING SIEBEL COMPONENT LOAD INVESTIGATING SIEBEL SERVER SQL PERFORMANCE INVESTIGATING SIEBEL COMPONENT SQL PERFORMANCE INVESTIGATING SIEBEL SERVER AVAILABILITY INVESTIGATING SIEBEL ENTERPRISE PERFORMANCE INVESTIGATING SIEBEL ENTERPRISE COMPONENT PERFORMANCE INVESTIGATING SIEBEL ENTERPRISE LOAD INVESTIGATING SIEBEL ENTERPRISE SQL PERFORMANCE INVESTIGATING SIEBEL ENTERPRISE COMPONENT SQL PERFORMANCE INVESTIGATING SIEBEL ENTERPRISE AVAILABILITY VIEWS SIEB_SRVR_AVAILABILITY_OVERVIEW GRAPH iii

6 Contents SIEB_SRVR_OVERVIEW GRAPH SIEB_SRVR_UTILIZATION_OVERVIEW GRAPH SIEB_COMP_AVAILABILITY GRAPH SIEB_COMP_DETAIL GRAPH SIEB_COMP_GROUP_AVAILABILITY GRAPH SIEB_COMP_SQLEXECUTE_DETAIL GRAPH SIEB_COMP_SQLFETCH_DETAIL GRAPH SIEB_COMP_SQLPARSE_DETAIL GRAPH SIEB_COMP_SQLTIME GRAPH SIEB_COMP_STATISTICS GRAPH SIEB_COMP_TASKS GRAPH SIEB_PROC_MEMORY_DETAIL GRAPH SIEB_PROC_UTILIZATION GRAPH SIEB_SRVR_DETAIL GRAPH SIEB_SRVR_SQLTIME GRAPH SIEB_TASK_DETAIL TABLE SIEB_ENTERPRISE_AVAILABILITY_OVERVIEW GRAPH SIEB_ENTERPRISE_COMP_GROUP_AVAILABILITY GRAPH SIEB_ENTERPRISE_COMP_AVAILABILITY GRAPH SIEB_ENTERPRISE_COMP_SQLTIME GRAPH SIEB_ENTERPRISE_COMP_STATISTICS GRAPH SIEB_ENTERPRISE_OVERVIEW GRAPH SIEB_ENTERPRISE_UTILIZATION_OVERVIEW GRAPH SIEB_ENTERPRISE_DETAIL GRAPH SIEB_ENTERPRISE_SQLTIME GRAPH RULES SIEB_SRVR_AVAIL RULE SIEB_DB_CONNECT_AVAIL RULE SIEB_GW_CONNECT_AVAIL RULE SIEB_SRVR_NODBCONNRETRY RULE SIEB_SRVR_NODLRBKRETRY RULE SIEB_SRVR_NOXHAUSTRETRY RULE SIEB_SRVR_CPU_UTIL RULE iv

7 Contents SIEB_SRVR_MEMORY_UTIL RULE SIEB_SRVR_PROC_CPUTIME RULE SIEB_COMP_MTSERVERS RULE SIEB_TASK_STATUS RULE SIEB_COMP_AOMERRORS RULE SIEB_SRVR_PROC_MEMORY RULE SIEB_COMP_STATE RULE SIEB_COMP_ROUTE_AVAIL RULE SIEB_COMP_PROC_AVAIL RULE SIEB_COMP_MERGER_AVAIL RULE SIEB_COMP_ROUTE_TASK RULE SIEB_COMP_INTER_TASK RULE SIEB_LOG_MSG RULE SIEB_CRASH_LOG RULE v

8 Contents vi

9 1 Foglight Cartridge for Siebel This Reference Guide is a printable version of the Foglight online help. In instances where there is conflicting information, the online help supercedes content in this guide. The Foglight Cartridge for Siebel extends the Foglight foundation product with specialized agents designed to assure Siebel ebusiness Applications by providing application health status and capacity planning information. The Foglight solution for Siebel ebusiness Applications monitors the availability and performance of the different entities that comprise the Siebel ebusiness Application environment. Critical, important, and useful information about the Web servers, Siebel gateway server, Resonate Schedulers, Siebel servers, database and network are monitored at a configurable frequency by the different Foglight specialized agents thereby presenting the overall health and performance of the Siebel environment at any given time, current, or historical. The Foglight Cartridge for Siebel consists of the following agents: SiebelClient and SiebelServer. Refer to the Foglight Installation and Administration Guide for more information on deploying Foglight in a Siebel environment.

10 Foglight Cartridge for Siebel 2

11 2 About the SiebelClient Agent The SiebelClient agent provides two mutually exclusive pieces of value for the Siebel Administrator, which includes: Siebel Server Availability Monitoring The availability of the Siebel ebusiness Application depends upon the availability of each Siebel server in the environment. When a Siebel server is unavailable, every enabled Siebel component assigned to that Siebel server is also unavailable. Furthermore, if a Siebel component is only assigned to one Siebel server and that one Siebel server becomes unavailable, the work being performed by those components will stop. For example, if the Siebel server that is assigned the Siebel Remote components such as the Transaction Router, Transaction Merger, and Transaction Processor becomes unavailable, every Siebel Remote user assigned to that Siebel server would not be able to synchronize. The fact that a Siebel server itself is running and available, does not guarantee the Siebel users have access to the Siebel server from the geographic location where they are physically located. Therefore, it is important to monitor the Siebel server availability from all the geographic locations where the Siebel users typically reside. The SiebelClient agent provides the functionality for the Siebel Administrator and uses the Siebel Server Manager Command Line Interface to collect this data.

12 Foglight Cartridge for Siebel Siebel Database Availability and Response Time Monitoring The Siebel database is crucial to the availability of the entire Siebel environment. Therefore, monitoring the availability of the Siebel database and its ability to execute SQL is critical. In Siebel implementations where the dedicated client is utilized, the Siebel database must remain available from every geographic location where end users are located. The fact that the Siebel database itself is running and available, does not guarantee the Siebel dedicated users have access to the Siebel database from the geographic location where they are physically located. Therefore, it is important to monitor the Siebel database availability from the geographic locations where the Siebel users typically reside. The Siebel database is also a crucial component of the overall Siebel transaction response time whether it is a dedicated client request, thin/web client request, or Siebel component (EIM, Workflow, Assignment Manager) request. Thus it is important to measure the response time of the Siebel database on a constant basis. The SiebelClient agent provides for the active response time measurement for the Siebel database. Active response time measurement is simply defined as performing an action on a regular interval and measuring its success and response time. Four pre-defined transactions based on vanilla Siebel are provided out-of-the box with the SiebelClient; however, the agent provides the capability for the Siebel Administrator to define user defined transactions that are based on a customized Siebel application. Furthermore, the SiebelClient agent could be used to provide response time measurement of SQL statements that are generated by Siebel components such as Workflow, Virtual Business Components, or even non-siebel related transactions. The SiebelClient agent will provide the Siebel Administrator and the Siebel Database Administrator the ability to be alerted when different geographic locations are unable to connect to the Siebel database and execute SQL statements even if no end-users are even active, thus providing proactive notification to the Siebel Administrator. Since the SiebelClient is performing the same transactions every collection, the Siebel Database Administrator will be able to not only determine if response time varies based off of geographic location, but identify trends when the Siebel database is experiencing slower response time. ASP Using SiebelClient Agent Startup Parameters 2

13 Investigations Views Rules Investigating Siebel Server Availability from a Single Location Investigating Siebel Client Session Availability from a Single Location Investigating Siebel Client Transaction Availability from a Single Location Investigating Siebel Client Session Response Time from a Single Location Investigating Siebel Client Transaction Response Time from a Single Location Investigating Siebel Enterprise Availability from All Locations Investigating Siebel Database Availability from All Locations Sieb_Client_Sess_Resp_Time_Overview Sieb_Client_Sess_Status_Overview Sieb_Client_Srvr_Availability_Overview Sieb_Client_Stage_Detail_Overview Sieb_Client_Tran_Detail_Overview Sieb_Client_Tran_Resp_Time_Overview Sieb_Client_Stage_Resp_Time_Diff Sieb_Client_Stage_Resp_Time_Per Sieb_Client_Stage_Rows_Returned Sieb_Client_Tran_Resp_Time_Diff Sieb_Client_Tran_Resp_Time_Per Sieb_Client_Tran_Rows_Returned Sieb_Client_Tran_Status_Detail Sieb_Client_Srvr_Availability Sieb_Client_Stage Time Sieb_Client_Stage_Pct Sieb_Client_Trans_Time Sieb_Client_Trans_Pct Sieb_Client_Trans_Comp Sieb_Client_Stage_Comp 3

14 Foglight Cartridge for Siebel Sieb_Client_Agent_Msg Sieb_Client_Trans_SLA Sieb_Client_Stage_SLA Tables AgentMsgs SiebelClientServerHealth SiebelClientSessionSummary SiebelClientTransactionDetail 4

15 ASPs Using SiebelClient Agent Startup Parameters The SiebelClient agent is shipped with agent startup parameters that dictate how the agent will perform. You can change these parameters to suit your system requirements. The parameters listed in the topics below are specific to the SiebelClient agent. Topics Setting the SiebelClient Collection Rate Parameters Setting the SiebelClient Station Name Setting the SiebelClient Server Information Setting the SiebelClient Database Information Setting the SiebelClient User Defined Transaction Parameters Setting the SiebelClient SLA Parameters Setting the SiebelClient Collection Rate Parameters The collection rate, or sample frequency, is the number of seconds between the end of a collection period and the start of the next. The sample frequency can either be controlled at the agent level or set for each table; table level sampling is the preferred method. Use the Collection Rate tab on the Edit ASP dialog box to set the sample frequency. To control the growth of the Foglight database, you can eliminate records from the database by averaging data samples. This process is called weeding. Foglight keeps one record of the averaged data and purges the rest of the records, thereby reducing the size of the database. Foglight weeds only the previous week of data. The weeding frequency can be either minutes or hours. If 0 is used, no weeding will take place. To set the sample frequency 1. Right-click the SiebelClient agent icon and choose Edit, ASPs from the shortcut menu. 5

16 Foglight Cartridge for Siebel 2. Click Edit to edit the SiebelClient_Freq_List. To define the weeding parameters, enter the numerical time value in the Average Previous Week's Data To box, and select a unit of time from the drop-down list. 3. Click OK to save the entries and close the Edit ASP dialog box, or select another tab to define additional startup parameters. Editing the Sample Frequency List The SiebelClient_Freq_List allows you to define sample frequency rates on a table-by-table basis. The following tables are listed by default in the sample frequency list with the values shown below. You can edit, add, or delete tables from this list. The default Sample Frequency rate is applied to all tables not specifically listed in the Sample Frequency List. 6

17 To edit the Sample Frequency List 1. From the Foglight Operations Console right-click the SiebelClient agent icon and choose Edit, ASPs from the shortcut menu. 2. From the Edit ASP dialog box, click the Collection Rate tab. 3. Click Edit to display the SiebelClient_Freq_List dialog box. 4. Select a table from the list, and click Edit. 5. When the Sample Frequency template opens: 6. Enter the new number of seconds in the Sample Frequency box. 7. Enter the frequency that you want to purge all data from the Foglight database in the Purge Days box. 8. Click OK to save the settings. Setting the Siebel Client Station Name The Station Info tab on the SiebelClient agent's Edit ASP dialog box allows you to define the name of the geographic location where the SiebelClient agent is physically located. To define the SiebelClient Station Name 1. From the Foglight Operations Console right-click the SiebelClient agent icon and choose Edit, ASPs from the shortcut menu. 2. From the Edit ASP dialog box, select the Station Info tab. 3. In the SiebelClient Station Name box, enter the name of the geographic location where the SiebelClient agent is physically located. 4. Click OK to save the entry and close the Edit ASP dialog box, or select another tab to define additional startup parameters. 7

18 Foglight Cartridge for Siebel Setting the SiebelClient Server Information The Siebel Srvr Info tab on the SiebelClient agent's Edit ASP dialog box allows you to define Siebel Gateway and Enterprise servers, the directory path to the Siebel Server Manager, and the connection information for the Siebel server(s) that will be monitored from the SiebelClient station. Any change made to the Configuration List is a global change; it changes the Station configuration for all SiebelClient agents on all the host Foglight monitors. If you do not want to make the change global, give the Host List Configuration a new name. To define the SiebelClient Server Information 1. From the Foglight Operations Console right-click the SiebelClient agent icon and choose Edit, ASPs from the shortcut menu. 8

19 2. From the Edit ASP dialog box, select the Siebel Srvr Info tab. 3. Check the Monitor Siebel Srvr Availability box to enable SiebelClient's Siebel server availability monitoring functionality. 4. In the Gateway Server Name box, enter the name of the Siebel Gateway server. If the Gateway server uses a port other than the default 2320, use the format: GatewayServer:PortNo. 5. In the Enterprise Server Name box, enter the name of the Siebel Enterprise server. 6. In the Siebel Server Mgr Directory box, enter the full path to the directory where the Siebel Server Manager executable is located. Typically on Windows, srvrmgr resides in C:\sea\client\bin. 7. Select a Siebel server from the Siebel Server Config List drop-down list, or click Edit to open the Edit Config List dialog box. Use the configuration list dialog box to edit the connection parameters for the selected server Editing a Configuration List The Config List dialog box contains the parameters required to identify the target Siebel Database Server and to determine which predefined Siebel transactions to execute. To edit a configuration list 1. Right-click the SiebelClient agent icon and choose Edit, ASPs from the shortcut menu. 2. Select the Siebel Srvr Info tab. Select a server from the Server Config List drop-down list, and click Edit.The Config List Edit dialog box display. 9

20 Foglight Cartridge for Siebel 3. Select the AppServer for the config list, and click Edit.The Config List Edit template opens. 4. Check the Enabled box to monitor this Siebel Server for availability from the geographic location where the SiebelClient agent is physically located. 5. Enter the Siebel Server Name or Select another one by clicking Select to choose from the list. 6. If you want to edit the Siebel Administrator ID, enter the new ID in the text box, or click Select to choose from the list. 7. If you want to edit the Siebel Administrator's password, enter the new password in the text box. Setting the SiebelClient Database Information The Siebel DB Info tab on the SiebelClient agent's Edit ASP dialog box allows you to define the connection information for the Siebel database and enable which pre-defined transactions that will be executed by the SiebelClient station. To define the SiebelClient Database Information 1. From the Foglight Operations Console right-click the SiebelClient agent icon and choose Edit, ASPs from the shortcut menu. 10

21 2. From the Edit ASP dialog box, select the Siebel DB Info tab. 3. Check the Monitor Siebel Database box to enable the SiebelClient's functionality for monitoring Siebel database availability and response time. 4. In the Siebel Version list box, select the version of Siebel ebusiness Applications you are using. If the version you have is not listed, select Other. 5. Type the version number you have if it is not available in the drop down list in step 4 above. 11

22 Foglight Cartridge for Siebel 6. From the dropdown list, select the type of Relational Database Management System your Siebel database is running. 7. In the Database Alias/Name field, type the SQL*Net Alias (Oracle) or the name (DB2 or SQL Server) for the Siebel database. 8. In the ODBC DSN (SQL Server or DB2 Only) field, type the name of the ODBC data source that was created specifically for the SiebelClient. For example, if the Siebel RDBMS is DB2, a new ODBC data source will be created that utilizes the DB2 ODBC driver to connect to the Siebel database. 9. In the TNSNAMES Alias (Oracle Only) field, type the name of the SQL*Net/Net8 alias as defined in the TNSNAMES.ORA file. 10. In the Oracle Home Path (Oracle Only) field, type the path to the ORACLE_HOME directory. 11. In the TNSNAMES.ORA File Path (Oracle Only) field, type the path to the directory where the TNSNAMES.ORA file is physically located. 12. In the Siebel Schema Owner field, type the name of the table owner account, or schema that owns all of the Siebel tables, indexes, etc. inside the database. 13. In the Siebel Application User field, type the name of the Siebel ebusiness Application user name being used to run the pre-defined and user defined simulated transactions 14. In the Siebel Application User Password field, type the password for the Siebel ebusiness Application user being used to run the simulated pre-defined and user defined transactions. 15. In the Siebel Language field, type the default three letter language code used for the Siebel database. For example, ENU for English. 16. Click the checkbox next to the simulated transactions you want the SiebelClient agent to run for the defined Siebel Application user. Account Transaction runs the simulated My Accounts transaction. Contact Transaction runs the simulated My Contacts transaction. Service Request Transaction runs the simulated My Service Request transaction. Opportunity Transaction runs the simulated My Opportunities transaction. 12

23 Setting the SiebelClient User Defined Transaction Parameters The User Defined Transaction tab on the SiebelClient agent's Edit ASP dialog box allows you to define the location and name of the XML script that defines the user defined transactions that will be executed by the Siebel Client station. To define the SiebelClient User Defined Transaction parameters 1. From the Foglight Operations Console right-click the SiebelClient agent icon and choose Edit, ASPs from the shortcut menu. 2. From the Edit ASP dialog box, select the User Defined Transaction tab. 3. Check the Run User Defined Transaction box to run the user defined transaction indicated. 4. n the User Defined SQL Script Directory field, type the full path of the directory where the User Defined Transaction XML is located. 5. In the User Defined SQL Script Name field, type the name of the XML script that defines the user-defined transaction. 6. Check the Pre-defined Login box. This login is based on the basic Siebel application and includes determining the Siebel application user's responsibilities, positions, and visibility.if the Siebel application has been customized, it is recommended that the customized Login transaction be specified in the User Defined Transaction XML script. This will ensure valid response times for a customized Siebel application. 13

24 Foglight Cartridge for Siebel Setting Siebel SLA Parameters Use the SLA Info tab to enter data relating to the Siebel Client server. To set the SLA parameters 1. Right-click the SiebelClient agent icon and choose Edit, ASPs. 2. Click the SLA Info tab. 3. Select the list you want to control from the Session SLA List drop-down and click Edit. The Session SLA List details the expected time for each stage of the SiebelClient agent's session. 4. Select the list you want to control from the Pre-Defined Txn SLA List drop-down and click Edit. The Pre-Defined Txn SLA List details the expected time for each pre-defined transaction. 5. Select the list you want to control from the User Defined Txn SLA List drop-down and click Edit. 6. The User Defined Txn SLA List details the expected time for each user defined transaction defined in the User Defined Transaction XML Script. Editing Session SLA List The Session SLA List details the expected time for each stage of the SiebelClient agent s session 1. From the Foglight Operations Console right-click the SiebelClient agent icon and choose Edit, ASPs from the shortcut menu. 2. From the Edit ASP dialog box, select the SLA Info tab. 3. Click Edit to display the Session SLA List dialog box. 14

25 4. Click New to open the Add: SiebelClient_SessionsSLA_template dialog. 5. Enter the Stage and Expected Time or click Select to display an Input dialog. 6. In the Stage Input dialog, click one of the available stages and click OK to return to the Add dialog. Stage During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel application, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. This process or session is broken down into stages. The stages are Connecting, Logging In, Running Transactions, Running User Defined Txn and Completing All Stages. 15

26 Foglight Cartridge for Siebel 7. In the Expected Time Input dialog, select from the available times and click OK to return to the Add dialog. Expected Time Is the number of seconds the Siebel Administrator expects to be spent executing this stage of the session, i.e., the Service Level Agreement for this stage of the session. Float value with max 4 decimal positions. 8. Click OK in the Add dialog to return to the SLA Info tab. Editing the User Defined Transaction SLA List The User Defined Transaction SLA List details the expected time for each user defined transaction defined in the User Defined Transaction XML Script. 1. From the Foglight Operations Console right-click the SiebelClient agent icon and choose Edit, ASPs from the shortcut menu. 2. From the Edit ASP dialog box, select the SLA Info tab. 3. Click Edit to display the User Defined Txn SLA List dialog box. 16

27 4. Click New to open the Add: SiebelClient_SessionsSLA_template dialog. 5. Enter the Pre-Defined Transaction and Expected Time or click Select to display an Input dialog. 6. In the Stage Input dialog, click one of the available stages and click OK to return to the Add dialog. 7. Transaction User defined transaction name. The transaction name specified must identically match the name as defined in the XML script. 8. In the Expected Time Input dialog, select from the available times and click OK to return to the Add dialog. Expected Time Is the number of seconds the Siebel Administrator expects to be spent executing this stage of the session, i.e., the Service Level Agreement for this stage of the session. Float value with max 4 decimal positions. 17

28 Foglight Cartridge for Siebel 9. Click OK in the Add dialog to return to the SLA Info tab. Editing the Pre-Defined Transaction SLA List The Pre-Defined Transaction SLA List details the expected time for each pre-defined transaction. 1. From the Foglight Operations Console right-click the SiebelClient agent icon and choose Edit, ASPs from the shortcut menu. 2. From the Edit ASP dialog box, select the SLA Info tab. 3. Click Edit to display the Pre-Defined Txn SLA List dialog box. 4. Click New to open the Add: SiebelClient_PreDefinedSLA_template dialog. 5. Enter the Transaction and Expected Time or click Select to display an Input dialog. 18

29 6. In the Transaction Input dialog, click one of the available stages and click OK to return to the Add dialog. Transaction Pre-defined transaction name. Pre-defined transaction names are Account, Contact, Opportunity and Service Request. 7. In the Expected Time Input dialog, select from the available times and click OK to return to the Add dialog. Expected Time Is the number of seconds the Siebel Administrator expects to be spent executing this stage of the session, i.e., the Service Level Agreement for this stage of the session. Float value with max 4 decimal positions. 8. Click OK in the Add dialog to return to the SLA Info tab. 19

30 Foglight Cartridge for Siebel SiebelClient Agent Tables The SiebelClient agent stores data in the following tables in the Foglight Database. Click the hyperlinks to view field descriptions of each table. AgentMsgs SiebelClientServerHealth SiebelClientSessionSummary SiebelClientTransactionDetail AgentMsgs Table The AgentMsg table contains informational and error messages that represent the status of the SiebelClient agent. The following table describes the fields in the AgentMsg table: FIELD Message MessageID Severity DESCRIPTION Text detailing the error message generated by the SiebelClient agent Internal identifier or code assigned to the error message Severity of the error, i.e., Informational, Warning, Critical, Fatal Refer to the following table for a list of the possible messages and resolutions. MESSAGE ID MESSAGE HEADER SEVERITY CONTEXT SPECIFIC MESSAGE TEXT POSSIBLE RESOLUTION SEBL-001 GENERAL INFO Informational User Defined Transactions Loaded in Memory Informational Only User Defined Transaction Count =<transaction count> SEBL-002 VERSION INFO Informational Agent: SiebelClient Version/DCMs matched: <version> Informational Only 20

31 SEBL-004 ASPs ERROR Critical Gateway Server not defined Siebel Language not defined User Script Location not provided Modify the ASPs to correct the ASP value identified in the message text Siebel Server Manager Utility not found User and/or Password not valid for Database Siebel Schema Owner not found TNSNAMES Alias (Oracle) not found ODBC DSN (DB2) not found ODBC DSN (MSSQL) not found SEBL-005 SECONDARY ASPs ERROR Critical None of the Tables assigned a Sampling Frequency No Appserver defined for Monitoring No Session Stage SLAs defined Modify the ASPs to correct the secondary ASP value identified in the message text. No Predefined SLAs defined for DB Monitoring No UserDefined SLAs defined for DB Monitoring All Tables have zero Sampling Interval. None to populate again. Agent to die in 10 seconds. SEBL-006 SECONDARY ASPs INFO Informational Appserver <SiebelServer> not enabled for monitoring Informational Only SEBL-007 NO TABLES LEFT TO POPULATE Fatal No Tables left to populate due to exclusions. Agent to die in 30 seconds Modify the ASPs to correct the ASP value identified in the message text 21

32 Foglight Cartridge for Siebel SEBL-008 ASPs SELECTION Informational Monitor Siebel Server Availability not checked Informational Only Monitor Siebel Database not checked SEBL-009 DATABASE CLIENT LIBRARIES NOT FOUND Critical ORACLE libraries on monitored host not found! DB2 libraries on monitored host not found! SQL Server ODBC libraries on monitored host not found! One of the following may be true: Required libraries do not exist on the monitored host. Install the required database client/ ODBC libraries Database libraries/dlls can not be found in the path. Modify the path to include the directory with the libraries/dlls SEBL-010 DATABASE DOWN Critical Siebel Database is not connected at this time Oracle TNS Listener and/or Database may be unavailable. Additional messages may offer further information. Verify that the Siebel database is available SEBL-011 OCI SQLERROR Warning Context specific message Invalid SQL syntax as identified by the Oracle Call Interface. Correct the SQL query identified in the message text 22

33 SEBL-012 SEBL-019 SEBL-020 SEBL-021 SEBL-022 OCI UNDEFINED ERROR DB2 ODBC SQLERROR DB2 ODBC UNDEFINED ERROR SQL SERVER ODBC SQLERROR SQL SERVER ODBC UNDEFINED ERROR Critical None Serious unknown error from the Oracle Call Interface Warning Context specific message Invalid SQL syntax as identified by the DB2 ODBC driver. Correct the SQL query identified in the message text Critical None Serious unknown error from the DB2 ODBC driver Warning Context specific message Invalid SQL syntax as identified by the SQL Server ODBC driver. Correct the SQL query identified in the message text Critical None Serious unknown error from the SQL Server ODBC driver SEBL-101 SIEBEL APPSERVER MONITORING Critical SiebelClient agent is shutdown. No appserver(s) or database is being monitored ASPs and/or secondary ASPs are either incomplete or incorrect. Modify the ASPs to correct the ASP value identified in the message text of the related alert 23

34 Foglight Cartridge for Siebel SEBL-102 SIEBEL DATABASE LOGIN Critical Database Monitoring not turned on Required XML file <file_name> not found." Transactions' XML file not available Database Type and Library home are undefined ASPs and/or secondary ASPs are either incomplete or incorrect. Modify the ASPs to correct the ASP value identified in the message text XML File <xmlfile_name> Couldn't be loaded in Memory SEBL-103 SEBL-104 SIEBEL TRANSACTION MONITORING SIEBEL USER DEFINED TRANSACTION MONITORING Critical Context specific message These messages relate to problems with SQL statements for pre-defined transactions. Correct the SQL query identified in the message text Critical Context specific message These messages relate to problems with SQL statements for user defined transactions. Correct the SQL query identified in the message text 24

35 SEBL-105 SIEBEL APPSERVER MONITORING Warning No Appservers defined for monitoring Appservers monitoring turned off as srvrmgr utility not found Appserver name <appserver_name> is invalid. Excluded from monitoring ASPs and/or secondary ASPs are either incomplete or incorrect. Modify the ASPs to correct the ASP value identified in the message text SEBL-106 SIEBEL TRANSACTION MONITORING Warning Table <table_name> is not going to be populated Refer to underlying related messages for additional information SiebelClientServerHealth Table The following table describes the fields in the SiebelClientServerHealth table: FIELD EnterpriseServer SiebelServer SiebelServerStatus StationName DESCRIPTION Name of the Siebel Enterprise that the Siebel Server belongs to. Value retrieved from ASPs. Current run state of the Siebel Server. Name of the Siebel Server. Value retrieved from ASPs. Name of the geographic location where the SiebelClient is physically located. SiebelServerAvailability Numeric value representing run state of the Siebel Server (100 = Running or 0 = all other values). 25

36 Foglight Cartridge for Siebel SiebelClientSessionSummary Table The following table describes the fields in the SiebelClientSessionSummary table: FIELD DatabaseAlias RowsReturned StationName SessionStage DESCRIPTION Database Name/alias for the Siebel database that the SiebelClient is running transactions against. Value retrieved from ASPs. Total number of rows returned from all SQL statements for each stage. Connecting will always = 0 since there are no SQL statements for connecting to the database. Name of the geographic location where the SiebelClient is physically located. Value retrieved from ASPs. Stage of the transaction. Possible values are: Connecting Establishing a connection to Siebel Database Logging in Logging into the Siebel Database which includes determining Siebel responsibilities, position, and visibility Running Transactions Running all the enabled pre-defined transactions. Running User Defined Txn Running all the enabled user defined transactions. Completing All Stages Connecting + Logging in + Running Transactions + Running User Defined Txn StageAvgExecuteTime StageCurExecuteTime Since the SiebelClient agent was started, the average number of seconds for the SiebelClient station to complete this Stage of the transaction. During the last collection, the number of seconds the SiebelClient station spent completing this Stage of the transaction. 26

37 StageExecuteTimeDifference StageExecuteTimePercent SessionStageCompleted Difference (in seconds) between StageCurExecuteTime and StageAvgExecuteTime Difference (in percent) between StageCurExecuteTime and StageAvgExecuteTime. Numeric value representing the ability for the SiebelClient station to perform this Stage of the transaction (100 = True or 0 = False). SiebelClientTransactionDetail Table The following table describes the fields in the SiebelClientTransactionDetail table. FIELD DatabaseAlias RowsReturned StationName TransactionName TransactionAvgExecuteTime TransactionCurExecuteTime TransactionExecuteTimeDifference TransactionExecuteTimePercent TransactionCompleted DESCRIPTION Database Name/alias for the Siebel database that the SiebelClient is running transactions against. Value retrieved from ASPs. Total number of rows returned from all SQL statements for each enabled transaction. Name of the geographic location where the SiebelClient is physically located. Value retrieved from ASPs. Logical name of the Siebel Transaction whose response time the SiebelClient is measuring. Since the SiebelClient agent was started, the average number of seconds for the SiebelClient station to complete the transaction. During the last collection, the number of seconds the SiebelClient station spent completing the transaction. Difference (in seconds) between TransactionCurExecuteTime and TransactionAvgExecuteTime. Difference (in percent) between TransactionCurExecuteTime and TransactionAvgExecuteTime. Numeric value representing the ability for this SiebelClient station to complete the Siebel transaction. 27

38 Foglight Cartridge for Siebel Investigations Investigating Siebel Server Availability from a Single Location The availability of the Siebel ebusiness Application depends upon the availability of each Siebel server in the environment. When a Siebel server is unavailable, every enabled Siebel component assigned to that Siebel server is also unavailable. Furthermore, if a Siebel component is only assigned to one Siebel server and that one Siebel server becomes unavailable, the work being performed by those components stops. For example, if the Siebel server that is assigned the Siebel Remote components such as the Transaction Router, Transaction Merger, and Transaction Processor becomes unavailable, every Siebel Remote user assigned to that Siebel server would be unable to synchronize. The fact that a Siebel server itself is running and available, does not guarantee the Siebel users have access to the Siebel server from the geographic location where they are physically located. Therefore, it is important to monitor the Siebel server availability from the geographic locations where the Siebel users typically reside. Foglight s SiebelClient agent monitors the Siebel server(s) availability from the geographic location where the SiebelClient is deployed as follows: The Siebel server s availability is indicated as follows: 100% if the SiebelServerStatus = Running 0% for all other values Start with the Sieb_Client_Srvr_Availability_Overview graph The Sieb_Client_Srvr_Availability_Overview graph displays the availability percentage of the Siebel server(s) status from the geographic location where the SiebelClient agent is physically located. 28

39 Investigating Siebel Client Session Availability from a Single Location During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel application, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. This process or session is broken down into stages. The stages are Connecting, Logging In, Running Transactions, Running User Defined Txn and Completing All Stages. The SiebelClient agent stores a percentage representing the SiebelClient s ability to successfully complete each stage of the session in the SessionStageAvailability field of the SiebelClientSessionSummary table. Values < 100% represent unsuccessful completion. Connecting This stage establishes a connection to the Siebel database through the ODBC DSN for DB2 and SQL Server or SQL*Net for Oracle. Logging In This stage completes and displays the pre-defined SQL statements that the Siebel Application generates between the connection to the Siebel database and the application home screen. These SQL statements include determining the Siebel application user s responsibilities, positions, and visibility. Running Transactions This stage executes the SQL statements that the Siebel Application generates for each pre-defined transaction. "Running Transactions" does not include the SQL statements for the Login transaction. Running User Defined Txn - This stage executes the SQL statements defined in the user defined XML files. "Running User Defined Txn" does not include the SQL statement for the pre-defined Login statement. Completing All Stages This stage is the completion of Connecting, Logging In, Running Transactions and if applicable Running User Defined Txn. Start with the Sieb_Client_Sess_Status_Overview graph The Sieb_Client_Sess_Status_Overview graph is used to view the percentage that represents the SiebelClient agent s ability to successfully complete each stage of the session. 29

40 Foglight Cartridge for Siebel Investigating Siebel Client Transaction Availability from a Single Location During the configuration of the SiebelClient agent, the Siebel Administrator has the ability to enable up to four pre-defined transactions in addition to user defined transactions. During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel database, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. The SiebelClient agent stores a percentage representing the SiebelClient s ability to successfully complete each of the enabled transactions in the TransactionAvailability field of the SiebelClientTransactionDetail table. Values < 100% represent unsuccessful completion. Start with the Sieb_Client_Tran_Status_Detail graph The Sieb_Client_Tran_Status_Detail graph is used to view the percentage of completion that represents the SiebelClient agent s ability to successfully complete each enabled pre-defined and/or user defined simulated transaction.` Investigating Siebel Client Session Response Time from a Single Location During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel application, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. This process or session is broken down into stages. The stages are Connecting, Logging In, Running Transactions, Running User Defined Txn and Completing All Stages. Connecting This stage establishes a connection to the Siebel database through the ODBC DSN for DB2 and SQL Server or SQL*Net for Oracle. Logging In This stage completes the pre-defined SQL statements that the Siebel Application generates between the connection to the Siebel database and the application home screen is displayed. These SQL statements include determining the Siebel application user s responsibilities, positions, and visibility. Running Transactions This stage executes the SQL statements that the Siebel Application generates for each pre-defined transaction. "Running Transactions" does not include the SQL statements for the Login transaction. 30

41 Running User Defined Txn This stage executes the SQL statements defined in the user defined XML file. "Running User Defined Txn" does not include the SQL statement for the pre-defined Login statement. Completing All Stages This is the completion of Connecting, Logging In, Running Transactions and if applicable Running User Defined Txn. The SiebelClient agent calculates the time to execute each stage of the session and records that value as the StageCurExecuteTime in the SiebelClientSessionSummary table. From the time the SiebelClient agent starts, it calculates the average response time for each stage of the transaction and stores it as the StageAvgExecuteTime in the SiebelClientSessionSummary table. The average response time establishes a baseline for each stage of the session. Start with the Sieb_Client_Sess_Resp_Time_Overview graph: The Sieb_Client_Sess_Resp_Time_Overview graph displays the expected, current and average response time for each stage of the session at a point in time. Investigating Siebel Client Transaction Response Time from a Single Location During the configuration of the SiebelClient agent, the Siebel Administrator has the ability to enable up to four pre-defined transactions in addition to user defined transactions. During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel database, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. The SiebelClient agent calculates the time to execute each enabled pre-defined or user defined transaction and records that value as the TransactionCurExecuteTime in the SiebelClientTransactionDetail table. From the time the SiebelClient agent starts, it calculates the average response time for each enabled transaction and stores it as the TransactionAvgExecuteTime in the SiebelClientTransactionDetail table. The average response time establishes a baseline for each enabled transaction. Start with the Sieb_Client_Tran_Resp_Time_Overview graph The Sieb_Client_Tran_Resp_Time_Overview graph is used to view the expected, current and average response time for each enabled transaction at a point in time. 31

42 Foglight Cartridge for Siebel Investigating Siebel Enterprise Availability from All Locations Use the View Editor to create a Sieb_Client_Enterprise_Availability_Overview graph detailing the availability of all the Siebel servers in the enterprise. Investigating Siebel Database Availability from All Locations Use the View Editor to create a Sieb_Client_Database_Availability_Overview graph detailing the ability of all the geographic locations where the Siebel Client agent is deployed to successfully connect to the Siebel database. Investigating Siebel Client Session Response Time from All Locations Use the View Editor to create a Sieb_Client_All_Sess_Resp_Time_Overview graph detailing the session current and average response time for all the geographic locations where the SiebelClient agent is deployed. Investigating Siebel Database Server Availability The SiebelClient agent monitors the ability of a SiebelClient Station to connect, login, and execute a pre-defined Siebel transaction against the Siebel Database Server from a location within the Siebel environment. If the SiebelClient Station cannot perform one or more of the above operations, the SiebelClient agent generates an alert that notifies a Siebel Administrator. Start with the Availability Overview graph The Sieb_Client_Database_Availability_Overview graph displays the availability status of the SiebelClient Station to connect, log in, and execute a transaction against the Siebel Database Server. Drill down on the Transactions All Status bar to view the execution status of an individual transaction. The Sieb_Client_Srvr_Availability_Overview graph opens. 32

43 Investigating Siebel Database Server Transaction Performance The SiebelClient agent executes a predefined Siebel transaction to simulate a Siebel two-tier client dividing total transaction time into the following: Connect Time: The amount of time required to connect to the Siebel Database Server. Login Time: The amount of time required to log in to the Siebel application. Launch Time: The sum of Connect Time and Login Time. Transaction Time: The amount of time to execute the predefined Siebel transaction and receive the result set back to the SiebelClient Station. Due to baselining, this method of response time monitoring provides a reliable and consistent form of measurement that enables performance comparisons and correlation with other Foglight-monitored Siebel Enterprise Server components over time from known locations. Consequently, Siebel Database Server transaction performance is benchmarked. Start with the Sieb_Client_Tran_Resp_Time_Overview graph The Sieb_Client_Sess_Resp_Time_Overview graph shows average connect, login, launch, and execution time in seconds per SiebelClient Station. Drill down on the Connection Average Time bar to analyze connect time with the Connect Response Time graph. Drill down on the Login Average Time bar to investigate login time with the Login Response Time graph. Drill down on the Launch Average Time bar to analyze launch time with the Launch Response Time graph. Drill down on the Transaction All Average Time bar to analyze individual transaction time with the Transaction Response Time graph. From the Sieb_Client_Tran_Resp_Time_Overview graph Drill down on the Account Transaction Average Time bar or Account Transaction Current Time bar to isolate analysis to the Account transaction. The Account Response Time graph opens. Drill down on the Action Transaction Average Time bar or Action Transaction Current Time bar to isolate analysis to the Action transaction. The Action Response Time graph opens. 33

44 Foglight Cartridge for Siebel Drill down on the Contact Transaction Average Time bar or Contact Transaction Current Time bar to isolate analysis to the Contract transaction. The Contact Response Time graph opens. Drill down on the Opportunity Transaction Average Time bar or Opportunity Transaction Current Time bar to isolate analysis to the Opportunity transaction. The Opportunity Response Time graph opens. 34

45 Views Sieb_Client_Sess_Resp_Time_Overview Graph During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel application, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. This process or session is broken down into stages. The stages are Connecting, Logging In, Running Transactions, Running User Defined Txn and Completing All Stages. Connecting - This stage establishes a connection to the Siebel database through the ODBC DSN for DB2 and SQL Server or SQL*Net for Oracle. Logging In - This stage completes the pre-defined SQL statements that the Siebel Application generates between the connection to the Siebel database and the application home screen that is displayed. These SQL statements include determining the Siebel application user s responsibilities, positions, and visibility. Running Transactions - This stage executes the SQL statements that the Siebel Application generates for each pre-defined transaction. "Running Transactions" does not include the SQL statements for the Login transaction. Running User Defined Txn - This stage executes the SQL statements defined in the user defined XML file. "Running User Defined Txn" does not include the SQL statement for the pre-defined Login statement. Completing All Stages - This is the completion of Connecting, Logging In, Running Transactions and if applicable Running User Defined Txn. The SiebelClient agent calculates the time to execute each stage of the session and records that value as the StageCurExecuteTime in the SiebelClientSessionSummary table. From the time the SiebelClient agent starts, it calculates the average response time for each stage of the transaction and stores it as the StageAvgExecuteTime in the SiebelClientSessionSummary table. The average response time establishes a baseline for each stage of the session. The Sieb_Client_Sess_Resp_Time_Overview graph displays the expected, current and average response time for each stage of the session at a point in time. 35

46 Foglight Cartridge for Siebel To open the Sieb_Client_Sess_Resp_Time_Overview graph 1. Click the SiebelClient agent icon. The File View in the right pane displays a list of views. 2. Double-click the Sieb_Client_Sess_Resp_Time_Overview graph icon from the File View pane. The Time Range menu option in conjunction with the View/Constraints menu option can be used to show a stage s current and average response time for the last 24 hours, last week, last month, etc. This is useful in analyzing how the response time compares to the SLA or expected time. It is also useful in analyzing the response time over time and identifying response time trends. Use the Sieb_Client_Stage_Detail_Overview table view to display all the data collected for each stage at a specific time period. Refer to the Diagnosing Response Time Degradation topic for more information. To continue your investigation Drill down on the Current Time bar to the Sieb_Client_Stage_Rows_Returned graph to analyze the number of rows returned during each stage of the session for the same time range as the Sieb_Client_Sess_Resp_Time_Overview graph. Drill down on the Average Time bar to the Sieb_Client_Stage_Resp_Time_Per graph to analyze the percentage difference between the current response time and the average response time for the same time range as the Sieb_Client_Sess_Resp_Time_Overview graph. 36

47 Use the View Editor to create a Sieb_Client_All_Sess_Resp_Time_Overview graph detailing the session current and average response time for all the geographic locations where the SiebelClient agent is deployed. Sieb_Client_Sess_Status_Overview Graph During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel application, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. This process or session is broken down into stages. The stages are Connecting, Logging In, Running Transactions, Running User Defined Txn and Completing All Stages. The SiebelClient agent stores a percentage representing the SiebelClient s ability to successfully complete each stage of the session in the SessionStageAvailability field of the SiebelClientSessionSummary table. Values < 100% represent unsuccessful completion. Connecting - This stage establishes a connection to the Siebel database through the ODBC DSN for DB2 and SQL Server or SQL*Net for Oracle. Logging In - This stage completes and displays the pre-defined SQL statements that the Siebel Application generates between the connection to the Siebel database and the application home screen. These SQL statements include determining the Siebel application user s responsibilities, positions, and visibility. Running Transactions This stage executes the SQL statements that the Siebel Application generates for each pre-defined transaction. "Running Transactions" does not include the SQL statements for the Login transaction. Running User Defined Txn - This stage executes the SQL statements defined in the user defined XML file. "Running User Defined Txn" does not include the SQL statement for the pre-defined Login statement. Completing All Stages - This stage is the completion of Connecting, Logging In, Running Transactions and if applicable Running User Defined Txn. The Sieb_Client_Sess_Status_Overview graph displays the percentage of time representing SiebelClient agent s ability to successfully complete each stage of the session. To open the Sieb_Client_Sess_Status_Overview graph 1. Click the SiebelClient agent icon. The File View in the right pane displays a list of views. 37

48 Foglight Cartridge for Siebel 2. Double-click the Sieb_Client_Sess_Status_Overview graph icon from the File View pane. The Time Range menu option for the Sieb_Client_Sess_Status_Overview graph can be used to show the SiebelClient s completion statistics for the last 24 hours, last week, last month, etc. If the geographic location where the SiebelClient agent is deployed is indicating 0% completion for Connecting, this possibly indicates a network issue between the geographic location and the Siebel database. Contact the Siebel Database Administrator to diagnose any connectivity issues and ensure that the Siebel Application User being used by the SiebelClient agent still has the appropriate responsibilities and/or privileges assigned. If the SiebelClient agent is indicating 0% completion for Logging In, this possibly indicates an overall problem with the Siebel database s ability to execute SQL statements or a syntax problem in the XML file defining the SQL statements for the Login transaction. Another possibility is that the problem is specific to the Siebel Application User specified in the SiebelClient ASPs. Contact the Siebel Database Administrator to ensure that the Siebel Application User still has the appropriate responsibilities and/or privileges assigned. The Sieb_Client_Agent_Msg rule should display an alert providing more information on the source of the problem. Zero percent (0%) completion for Running Transactions possibly indicates an overall problem with the Siebel database s ability to execute SQL statements or a syntax problem in the XML file defining the SQL statements for the pre-defined transactions. Another possibility is that the problem is specific to the Siebel Application User specified in the SiebelClient ASPs. Contact the Siebel Database Administrator to ensure that the Siebel Application User still has the appropriate responsibilities and/or privileges assigned. The Sieb_Client_Agent_Msg rule should provide an alert providing more information on the source of the problem. 38

49 Zero percent (0%) completion for Running User Defined Txn, possibly indicates an overall problem with the Siebel database s ability to execute SQL statements or a syntax problem in the XML file defining the SQL statements for the user defined transactions. Another possibility is that the problem is specific to the Siebel Application User specified in the SiebelClient ASPs. Contact the Siebel Database Administrator to ensure that the Siebel Application User still has the appropriate responsibilities and/or privileges assigned. The Sieb_Client_Agent_Msg rule should provide an alert providing more information on the source of the problem. Zero percent (0%) completion for the Completing all Stages indicates that the geographic location where the SiebelClient agent is deployed is unable to connect to the database, complete the login transaction, and complete the all the pre-defined and/or user defined transactions. The Sieb_Client_Agent_Msg rule should alert providing more information on the source of the problem. To continue your investigation: Drill down to the Sieb_Client_Tran_Status_Detail graph to display the ability of the SiebelClient agent to complete each of the enabled pre-defined and/or user defined transactions during the same time range as the Sieb_Client_Sess_Status_Overview graph. Use the View Editor to create a Sieb_Client_Database_Availability_Overview graph detailing the ability for all the geographic locations where the SiebelClient agent is deployed to successfully connect to the Siebel database. Sieb_Client_Srvr_Availability_Overview Graph The availability of the Siebel ebusiness Application depends upon the availability of each Siebel server in the environment. When a Siebel server is unavailable, every enabled Siebel component assigned to that Siebel server is also unavailable. Furthermore, if a Siebel component is only assigned to one Siebel server and that one Siebel server becomes unavailable, the work being performed by those components stops. For example, if the Siebel server that is assigned the Siebel Remote components such as the Transaction Router, Transaction Merger, and Transaction Processor becomes unavailable, every Siebel Remote user assigned to that Siebel server would be unable to synchronize. The fact that a Siebel server itself is running and available does not guarantee that Siebel users have access to the Siebel server from the geographic location where they are physically located. Therefore, it is important to monitor the Siebel server availability from the geographic locations where the Siebel users typically reside. 39

50 Foglight Cartridge for Siebel Foglight s SiebelClient agent monitors the Siebel server(s) availability from the geographic location where the SiebelClient is deployed as follows: The Siebel server s availability is indicated as follows: 100% if the SiebelServerStatus = Running 0% for all other values The Sieb_Client_Srvr_Availability_Overview graph displays the availability percentage representing the Siebel server(s) status from the geographic location where the SiebelClient agent is physically located. To open the Sieb_Client_Srvr_Availability_Overview graph 1. Click the SiebelClient agent icon. The File View in the right pane displays a list of views. 2. Double-click the Sieb_Client_Srvr_Availability_Overview graph icon from the File View pane. The Time Range menu option for the Sieb_Client_Srvr_Availability_Overview graph can be used to show the Siebel server(s) availability statistics for the last 24 hours, last week, last month, etc. If the Siebel server is reported as having 0% completion, the Siebel Administrator should ensure that Siebel server is actually running and functioning correctly. There have been reported cases where the host where the Siebel server resides is still pingable on the network, but the Siebel Administrator cannot log onto the host or into the Siebel server through the Siebel Server Manager GUI or Command Line Interface. Contact Siebel Support prior to restoring the Siebel server to proper functioning to prevent any corruption that might occur without their guidance. 40

51 If the Siebel Administrator determines that the Siebel server is functioning correctly, this indicates that a network problem exits between the physical location where the SiebelClient agent is deployed and the Siebel server, thus preventing the ability for the Siebel users to access the Siebel server(s) to synchronize or perform other functions such as Workflow that utilize the Siebel server. Foglight s NetMonitor agent can be used to monitor and diagnose the network connectivity between the physical location where the SiebelClient is located and the Siebel server(s). To continue your investigation: Use the View Editor to create a Sieb_Client_Enterprise_Availability_Overview graph detailing the availability of the Siebel server(s) from all the geographic locations where the SiebelClient agent is deployed. Sieb_Client_Stage_Detail_Overview Table During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel application, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. This process or session is broken down into stages. The stages are Connecting, Logging In, Running Transactions, Running User Defined Txn and Completing All Stages. Connecting - This stage establishes a connection to the Siebel database through the ODBC DSN for DB2 and SQL Server or SQL*Net for Oracle. Logging In - This stage is completion of the pre-defined SQL statements that the Siebel Application generates between the connection to the Siebel database and the application home screen that is displayed. These SQL statements include determining the Siebel application user s responsibilities, positions, and visibility. Running Transactions - This stage executes the SQL statements that the Siebel Application generates for each pre-defined transaction. "Running Transactions" does not include the SQL statements for the Login transaction. Running User Defined Txn - This stage executes the SQL statements defined in the user-defined XML file. "Running User Defined Txn" does not include the SQL statement for the pre-defined Login statement. Completing All Stages - This stage is the completion of Connecting, Logging In, Running Transactions and if applicable Running User Defined Txn. 41

52 Foglight Cartridge for Siebel The SiebelClient agent calculates the time to execute each stage of the session and records that value as the StageCurExecuteTime in the SiebelClientSessionSummary table. From the time the SiebelClient agent starts, it calculates the average response time for each stage of the transaction and stores it as the StageAvgExecuteTime in the SiebelClientSessionSummary table. The average response time establishes a baseline for each stage of the session. For each collection, the SiebelClient agent also calculates the percentage difference between the current and average response time and stores it in the StageExecuteTimePercent field in the SiebelClientSessionSummary table while calculating the difference in seconds and storing it in the StageExecuteTimeDifference field in the SiebelClientSessionSummary table. The Sieb_Client_Stage_Detail_Overview table displays the following data for each stage of the session: Session Stage Expected Time Current Time Average Time Percentage Difference Difference in Seconds Rows Returned Percentage Completed To open the Sieb_Client_Stage_Detail_Overview table 1. Click the SiebelClient agent icon. The File View in the right pane displays a list of views. 2. Double-click the Sieb_Client_Stage_Detail_Overview table icon from the File View pane. Refer to the Diagnosing Response Time Degradation topic for more information. 42

53 To continue your investigation: Drill down on the Current Time column to the Sieb_Client_Sess_Resp_Time_Overview graph to analyze the current response time over time. Drill down on the Average Time column to the Sieb_Client_Sess_Resp_Time_Overview graph to analyze the average response time over time. Drill down on the Difference (%) column to the Sieb_Client_Stage_Resp_Time_Per graph to analyze the percentage difference between the current response time and the average response time over time. Drill down on the Difference (s) column to the Sieb_Client_Stage_Resp_Time_Diff graph to analyze the difference in seconds between the current response time and the average response time over time. Drill down on the Rows Returned column to the Sieb_Client_Stage_Rows_Returned graph to analyze the number of rows returned over time. Drill down on the Completed (%) column to the Sieb_Client_Sess_Status_Overview graph to analyze the percent completed over time. Sieb_Client_Tran_Detail_Overview Table During the configuration of the SiebelClient agent, the Siebel Administrator has the ability to enable up to four pre-defined transactions in addition to user defined transactions. During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel database, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. The SiebelClient agent calculates the time to execute each enabled pre-defined or user defined transaction and records that value as the TransactionCurExecuteTime in the SiebelClientTransactionDetail table. From the time the SiebelClient agent starts, it calculates the average response time for each enabled transaction and stores it as the TransactionAvgExecuteTime in the SiebelClientTransactionDetail table. The average response time establishes a baseline for each enabled transaction. For each collection, the SiebelClient agent also calculates the percentage difference between the current and average response time and stores it in the TransactionExecuteTimePercent field in the SiebelClientTransactionDetail table while calculating the difference in seconds and storing it in the TransactionExecuteTimeDifference field in the SiebelClientTransactionDetail table. 43

54 Foglight Cartridge for Siebel The Sieb_Client_Tran_Detail_Overview table displays a table with the following information about each stage of the session: Transaction Name Expected Time Current Time Average Time Percentage Difference Difference in Seconds Rows Returned Percentage Completed To open the Sieb_Client_Tran_Detail_Overview table 1. Click the SiebelClient agent icon. The File View in the right pane displays a list of views. 2. Double-click the Sieb_Client_Tran_Detail_Overview table icon from the File View pane. Refer to the Diagnosing Response Time Degradation topic for more information. To continue your investigation: Drill down on the Current Time column to the Sieb_Client_Tran_Resp_Time_Overview graph to analyze the current response time over time. Drill down on the Average Time column to the Sieb_Client_Tran_Resp_Time_Overview graph to analyze the average response time over time. 44

55 Drill down on the Difference (%) column to the Sieb_Client_Tran_Resp_Time_Per graph to analyze the percentage difference between the current response time and the average response time over time. Drill down on the Difference (s) column to the Sieb_Client_Tran_Resp_Time_Diff graph to analyze the difference in seconds between the current response time and the average response time over time. Drill down on the Rows Returned column to the Sieb_Client_Tran_Rows_Returned graph to analyze the number of rows returned over time. Drill down on the Completed (%) column to the Sieb_Client_Tran_Status_Detail graph to analyze the percent completed over time. Sieb_Client_Tran_Resp_Time_Overview Graph During the configuration of the SiebelClient agent, the Siebel Administrator has the ability to enable up to four pre-defined transactions in addition to user defined transactions. During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel database, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. The SiebelClient agent calculates the time to execute each enabled pre-defined or user defined transaction and records that value as the TransactionCurExecuteTime in the SiebelClientTransactionDetail table. From the time the SiebelClient agent starts, it calculates the average response time for each enabled transaction and stores it as the TransactionAvgExecuteTime in the SiebelClientTransactionDetail table. The average response time establishes a baseline for each enabled transaction. The Sieb_Client_Tran_Resp_Time_Overview graph is used to view the expected, current and average response time for each enabled transaction at a point in time. To open the Sieb_Client_Tran_Resp_Time_Overview graph 1. Click the SiebelClient agent icon. The File View in the right pane displays a list of views. 2. Double-click the Sieb_Client_Tran_Resp_Time_Overview graph icon from the File View pane. 45

56 Foglight Cartridge for Siebel The Time Range menu option in conjunction with the View/Constraints menu option can be used to show a transaction s current and average response time for the last 24 hours, last week, last month, etc. This is useful in analyzing how the response time compares to the SLA or expected time. It is also useful in analyzing the response time over time and identifying response time trends. Refer to the Diagnosing Response Time Degradation topic for more information. To continue your investigation: Drill down on the Current Time bar to the Sieb_Client_Tran_Rows_Returned graph to analyze the number of rows returned during each stage of the session during the same time range as the Sieb_Client_Tran_Resp_Time_Overview graph. Drill down on the Average Time bar to the Sieb_Client_Tran_Resp_Time_Per graph to analyze the percentage difference between the current response time and the average response time during the same time range as the Sieb_Client_Tran_Resp_Time_Overview graph. Use the Sieb_Client_Tran_Detail_Overview table to display all the data collected for each stage at a specific time period. 46

57 Sieb_Client_Stage_Resp_Time_Diff Graph During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel application, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. This process or session is broken down into stages. The stages are Connecting, Logging In, Running Transactions, Running User Defined Txn and Completing All Stages. Connecting - This stage establishes a connection to the Siebel database through the ODBC DSN for DB2 and SQL Server or SQL*Net for Oracle. Logging In - Stage is completion of the pre-defined SQL statements that the Siebel Application generates between the connection to the Siebel database and the application home screen that is displayed. These SQL statements include determining the Siebel application user s responsibilities, positions, and visibility. Running Transactions - This stage executes the SQL statements that the Siebel Application generates for each pre-defined transaction. "Running Transactions" does not include the SQL statements for the Login transaction. Running User Defined Txn - This stage executes the SQL statements defined in the user defined XML file. "Running User Defined Txn" does not include the SQL statement for the pre-defined Login statement. Completing All Stages - This is the completion of Connecting, Logging In, Running Transactions and if applicable Running User Defined Txn. The SiebelClient agent calculates the time to execute each stage of the session and records that value as the StageCurExecuteTime in the SiebelClientSessionSummary table. From the time the SiebelClient agent is started it calculates the average response time for each stage of the session and stores it as the StageAvgExecuteTime in the SiebelClientSessionSummary table. The average response time establishes a baseline for each stage of the session. For each collection, the SiebelClient agent also calculates the percentage difference between the current and average response time and stores it in the StageExecuteTimePercent field in the SiebelClientSessionSummary table. The difference in seconds provides the Siebel Administrator an insight in how far the current response time is exceeding or is below the average or baseline response time. A positive value for difference indicates the current response time is exceeding the baseline or average response time, while a negative difference indicates the current response time is below the baseline or average. 47

58 Foglight Cartridge for Siebel The Sieb_Client_Sess_Resp_Time_Diff graph is used to view the average response time and difference in seconds for each stage of the session over time. Refer to the Diagnosing Response Time Degradation topic for more information. To continue your investigation Drill down on an individual stage to isolate average response time and difference analysis to an individual session stage. Sieb_Client_Stage_Resp_Time_Per Graph During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel application, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. This process or session is broken down into stages. The stages are Connecting, Logging In, Running Transactions, Running User Defined Txn and Completing All Stages. Connecting - This stage establishes a connection to the Siebel database through the ODBC DSN for DB2 and SQL Server or SQL*Net for Oracle. Logging In - Stage is completion of the pre-defined SQL statements that the Siebel Application generates between the connection to the Siebel database and the application home screen that is displayed. These SQL statements include determining the Siebel application user s responsibilities, positions, and visibility. Running Transactions - This stage executes the SQL statements that the Siebel Application generates for each pre-defined 48

59 transaction. "Running Transactions" does not include the SQL statements for the Login transaction. Running User Defined Txn - This stage executes the SQL statements defined in the user defined XML file. "Running User Defined Txn" does not include the SQL statement for the pre-defined Login statement. Completing All Stages - This is the completion of Connecting, Logging In, Running Transactions and if applicable Running User Defined Txn. The SiebelClient agent calculates the time to execute each stage of the session and records that value as the StageCurExecuteTime in the SiebelClientSessionSummary table. From the time the SiebelClient agent is started it calculates the average response time for each stage of the session and stores it as the StageAvgExecuteTime in the SiebelClientSessionSummary table. The average response time establishes a baseline for each stage of the session. For each collection, the SiebelClient agent also calculates the percentage difference between the current and average response time and stores it in the StageExecuteTimePercent field in the SiebelClientSessionSummary table. The percentage difference provides the Siebel Administrator an insight in how far the current response time is exceeding or is below the average or baseline response time. A positive value for difference indicates the current response time is exceeding the baseline or average response time, while a negative difference indicates the current response time is below the baseline or average. The Sieb_Client_Sess_Resp_Time_Per graph is used to view the average response time and percentage difference for each stage of the session over time. To open the Sieb_Client_Stage_Resp_Time_Per graph 1. Click the SiebelClient agent icon. The File View in the right pane displays a list of views. 2. Double-click the Sieb_Client_Stage_Resp_Time_Per graph icon from the File View pane. 49

60 Foglight Cartridge for Siebel Refer to the Diagnosing Response Time Degradation topic for more information. To continue your investigation Drill down to the Sieb_Client_Stage_Resp_Time_Diff graph to analyze the difference in seconds between the current response time and the average response time. Sieb_Client_Stage_Rows_Returned Graph During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel application, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. This process or session is broken down into stages. The stages are Connecting, Logging In, Running Transactions, Running User Defined Txn and Completing All Stages. Connecting - Stage is the establishing of a connection to the Siebel database through the ODBC DSN for DB2 and SQL Server or SQL*Net for Oracle. Logging In - Stage is completion of the pre-defined SQL statements that the Siebel Application generates between the connection to the Siebel database and the application home screen that is displayed. These SQL statements include determining the Siebel application user s responsibilities, positions, and visibility. Running Transactions - This stage executes the SQL statements that the Siebel Application generates for each pre-defined transaction. "Running Transactions" does not include the SQL statements for the Login transaction. 50

61 Running User Defined Txn - This stage executes the SQL statements defined in the user defined XML file. "Running User Defined Txn" does not include the SQL statement for the pre-defined Login statement. Completing All Stages - This is the completion of Connecting, Logging In, Running Transactions and if applicable Running User Defined Txn. The SiebelClient agent calculates the total rows returned for each stage of the session and records that value as the RowsReturned in the SiebelClientSessionSummary table. Since the Connecting stage does not include the execution of SQL statements, RowsReturned for Connecting will always be 0. As the number of records in the Siebel database increases, the efficiency of the same SQL statements could decrease. The Sieb_Client_Stage_Rows_Returned graph is used to view the rows returned for each stage of the session over time. This allows the Siebel Administrator to determine if response time degradation can be contributed to an increase in the number of rows being returned. To open the Sieb_Client_Stage_Rows_Returned graph 1. Click the SiebelClient agent icon. The File View in the right pane displays a list of views. 1. Double-click the Sieb_Client_Stage_Rows_Returned graph icon from the File View pane. The Time Range menu option in conjunction with the View/Constraints menu option can be used to show the rows returned for the last 24 hours, last week, last month, etc. This is useful in analyzing rows returned over time and identifying trends. 51

62 Foglight Cartridge for Siebel Refer to the Diagnosing Response Time Degradation topic for more information. To continue your investigation Drill down on an individual stage to isolate the rows returned analysis to an individual session stage. Sieb_Client_Tran_Resp_Time_Diff Graph During the configuration of the SiebelClient agent, the Siebel Administrator has the ability to enable up to four pre-defined transactions in addition to user defined transactions. During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel database, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. The SiebelClient agent calculates the time to execute each enabled pre-defined or user defined transaction and records that value as the TransactionCurExecuteTime in the SiebelClientTransactionDetail table. From the time the SiebelClient agent starts, it calculates the average response time for each enabled transaction and stores it as the TransactionAvgExecuteTime in the SiebelClientTransactionDetail table. The average response time establishes a baseline for each enabled transaction. For each collection, the SiebelClient agent also calculates the difference in seconds between the current and average response time and stores it in the TransactionExecuteTimeDifference field in the SiebelClientTransactionDetail table. The percentage difference provides the Siebel Administrator an insight in how many seconds the current response time is exceeding or is below the average or baseline response time. A positive value for difference indicates the current response time is exceeding the baseline or average response time, while a negative difference indicates the current response time is below the baseline or average. The Sieb_Client_Tran_Resp_Time_Diff graph is used to view the average response time and difference in seconds for each stage of the session over time. The Transaction Response Time Difference graph displays the difference in time between the amount of time to complete the current transaction, and the average amount of time (during the last collection period) to complete each transaction. This graph displays the differences in both actual seconds, and as a percentage. To open the Sieb_Client_Tran_Resp_Time_Diff graph 1. Click the SiebelClient agent icon. The File View in the right pane displays a list of views. 52

63 2. Double-click the Sieb_Client_Tran_Resp_Time_Diff graph icon from the File View pane. Refer to the Diagnosing Response Time Degradation topic for more information. To continue your investigation Drill down on an individual transaction to isolate average response time and difference analysis to an individual transaction. Sieb_Client_Tran_Resp_Time_Per Graph During the configuration of the SiebelClient agent, the Siebel Administrator has the ability to enable up to four pre-defined transactions in addition to user defined transactions. During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel database, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. The SiebelClient agent calculates the time to execute each enabled pre-defined or user defined transaction and records that value as the TransactionCurExecuteTime in the SiebelClientTransactionDetail table. From the time the SiebelClient agent starts, it calculates the average response time for each enabled transaction and stores it as the TransactionAvgExecuteTime in the SiebelClientTransactionDetail table. The average response time establishes a baseline for each enabled transaction. For each collection, the SiebelClient agent also calculates the percentage difference between the current and average 53

64 Foglight Cartridge for Siebel response time and stores it in the TransactionExecuteTimePercent field in the SiebelClientTransactionDetail table. The percentage difference provides the Siebel Administrator an insight in how far the current response time is exceeding or is below the average or baseline response time. A positive value for difference indicates the current response time is exceeding the baseline or average response time, while a negative difference indicates the current response time is below the baseline or average. The Sieb_Client_Tran_Resp_Time_Per graph is used to view the average response time and percentage difference for each stage of the session over time. To open the Sieb_Client_Tran_Resp_Time_Per graph 1. Click the SiebelClient agent icon. The File View in the right pane displays a list of views. 2. Double-click the Sieb_Client_Tran_Resp_Time_Per graph icon from the File View pane. Refer to the Diagnosing Response Time Degradation topic for more information. To continue your investigation Drill down on the Sieb_Client_Tran_Resp_Time_Diff graph, to analyze the difference in seconds between the current response time and the average response time for the same time range as the Sieb_Client_Tran_Resp_Time_Per graph. 54

65 Sieb_Client_Tran_Rows_Returned Graph During the configuration of the SiebelClient agent, the Siebel Administrator has the ability to enable up to four pre-defined transactions in addition to user defined transactions. During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel database, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. The SiebelClient agent calculates the total rows returned for each enabled transaction and records that value as the RowsReturned in the SiebelClientTransactionDetail table. As the number of records in the Siebel database increases, the efficiency of the same SQL statements could decrease. The Sieb_Client_Tran_Rows_Returned graph is used to view the rows returned for each enabled transaction over time. This allows the Siebel Administrator to determine if response time degradation can be contributed to an increase in the number of rows being returned. The Sieb_Client_Tran_Rows_Returned graph displays the total number of rows returned from all SQL statements for each enabled transaction. To open the Sieb_Client_Tran_Rows_Returned graph 1. Click the SiebelClient agent icon. The File View in the right pane displays a list of views. 2. Double-click the Sieb_Client_Tran_Rows_Returned graph icon from the File View pane. 55

66 Foglight Cartridge for Siebel The Time Range menu option in conjunction with the View/Constraints menu option can be used to show the rows returned for the last 24 hours, last week, last month, etc. This is useful in analyzing rows returned over time and identifying trends. Refer to the Diagnosing Response Time Degradation topic for more information. To continue your investigation Drill down on an individual transaction to isolate the rows returned analysis to an individual transaction. Sieb_Client_Tran_Status_Detail Graph During the configuration of the SiebelClient agent, the Siebel Administrator has the ability to enable up to four pre-defined transactions in addition to user defined transactions. During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel database, and runs all the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. The SiebelClient agent stores a percentage representing the SiebelClient s ability to successfully complete each of the enabled transactions in the TransactionAvailability field of the SiebelClientTransactionDetail table. Values < 100% represent unsuccessful completion. The Sieb_Client_Tran_Status_Detail graph is used to view the percentage of completion that represents the SiebelClient agent s ability to successfully complete each enabled pre-defined and/or user defined simulated transaction. To open the Sieb_Client_Tran_Status_Detail graph 1. Click the SiebelClient agent icon. The File View in the right pane displays a list of views. 2. Double-click the Sieb_Client_Tran_Status_Detail graph icon from the File View pane. 56

67 Zero percent (0%) completion for any pre-defined or user defined transaction possibly indicates an overall problem with the Siebel database s ability to execute SQL statements or a syntax problem in the XML file defining the SQL statements for the pre-defined or user defined transactions. Another possibility is that the problem is specific to the Siebel Application User specified in the SiebelClient ASPs. Contact the Siebel Database Administrator to ensure that the Siebel Application User still has the appropriate responsibilities and/or privileges assigned. The Sieb_Client_Agent_Msg rule should alert providing more information on the source of the problem. To continue your investigation Drill down on any bar view on the Sieb_Client_Tran_Status_Detail graph for that specific transaction type. Sieb_Client_All_Sess_Resp_Time_ Overview Graph The Sieb_Client_All_Sess_Resp_Time_Overview graph displays the session current and average response time for all the geographic locations where the SiebelClient agent is deployed. Sieb_Client_All_Sess_Resp_Time_Overview View Definition Graph Type: Inverted Bar Dynamic View: Yes Subject Field: SiebelClientSessionSummary.SessionStage Header: Siebel Client Response Time Overview from All Locations 57

68 Foglight Cartridge for Siebel Footer: %D %H:%M:%S Time Range: Last 4 Hours Map Location: Siebel Enterprise Node in Siebel custom map FOGLIGHT TABLE FIELD LABEL AXIS DRILL-DOWN TARGET VIEW DRILL-DOWN SELECTION CRITERIA SiebelClientSessionSummary. SessionStageCurExecuteTime wheresessionstagecomplete d = Completing All Stages Current Time(s) Y Sieb_Client_Sess_ Resp_Time_ Overview SELECTED= SessionStage SiebelClientSessionSummary. SessionStageAvgExecuteTime wheresessionstagecomplete d = Completing All Stages Average Time(s) Y Sieb_Client_Sess_ Resp_Time_ Overview SELECTED= SessionStage 58

69 Sieb_Client_Database_Availabilty_ Overview Graph The Sieb_Client_Database_Availability_Overview graph displays the ability for all the geographic locations where the SiebelClient agent is deployed to successfully connect to the Siebel database. Sieb_Client_Database_Availabilty_Overview View Definition Graph Type: Line Graph Dynamic View: Yes Subject Field: SiebelClientSessionSummary.SessionStage Header: Siebel Client Database Availability from All Locations Footer: %D %H:%M:%S Y Axis Max: Time Range: Last 4 Hours Map Location: Siebel Enterprise Node in Siebel custom map FOGLIGHT TABLE FIELD LABEL AXI S DRILL-DOW N TARGET VIEW DRILL-DOWN SELECTION CRITERIA SiebelClientSessionSummary. SessionStageCompleted wheresessionstagecompleted = Connecting Availability % Y Sieb_Client_ Sess_Status_ Overview SELECTED= SessionStage 59

70 Foglight Cartridge for Siebel 60

71 Sieb_Client_Enterprise_Availability_ Overview Graph The Sieb_Client_Enterprise_Availability_Overview graph displays the availability of all the Siebel servers in the enterprise. Sieb_Client_Enterprise_Availability_Overview View Definition Graph Type: Line Graph Dynamic View: Yes Subject Field: SiebelClientServerHealth.SiebelServer Header: Siebel Client Enterprise Availability from All Locations Footer: %D %H:%M:%S Y Axis Max: Time Range: Last 4 Hours Map Location: Siebel Enterprise Node in Siebel custom map FOGLIGHT TABLE FIELD LABEL AXIS DRILL-DOWN TARGET VIEW DRILL-DOWN SELECTION CRITERIA SiebelClientServerHealth. SiebelServerAvailability Availability % Y Sieb_Client_ Srvr_Availability_ Overview SELECTED= SiebelServer 61

72 Foglight Cartridge for Siebel Rules Sieb_Client_Srvr_Avail Rule The Sieb_Client_Srvr_Avail rule determines when the Siebel server is unavailable from the geographic location where the SiebelClient is physically located. CODE LEVEL ACTION SiebelClient.SiebelClientServerHealth. SiebelServerAvailability == 100 SiebelClient.SiebelClientServerHealth. SiebelServerAvailability!= 100 Normal Fatal Log Message SiebelAdmin Interpreting the Rule The Sieb_Client_Srvr_Avail rule's FATAL alert level indicates that the Siebel server is unavailable from the geographic location where the SiebelClient agent is physically located. The Siebel Administrator's response to the FATAL error is dependent on the Siebel server's status and the number of geographic locations alerting with the same Siebel server status. The following information describes the server statuses associated with the FATAL error level, as well as possible solutions: Gateway Failure - This status indicates that the Siebel server is unable to connect to the Siebel gateway. Ensure that the Siebel gateway is running by checking the status of the Siebel Gateway Name Server service on Windows Siebel servers or run list_ns on Unix based Siebel servers. If the Siebel gateway process is running, ensure that the Siebel server is able to ping the Siebel gateway. The Siebel gateway could be running, but the Siebel server could have lost network connectivity between the Siebel server host and the host running the Siebel gateway. Unavailable - This status indicates that the Siebel server has been shutdown or has not completed startup. If the Siebel server has been shutdown unintentionally, use Siebel Server Manager to restart the Siebel server. Other startup options include: restarting the Siebel Server service on Windows Siebel servers or using start_server on Unix based Siebel servers. 62

73 Connect Failed - This status is a possible indication that the Siebel server is unable to make a connection to the Siebel database due to an error with the ODBC DSN, such as invalid database name. Login Failed - This status indicates that the Siebel server is unable to login to the Siebel database. To verify the Siebel server s ability to connect to the database as the Siebel Administrator, use a database utility located on the Siebel server such as SQL*Plus or ISQL to connect to the database. Contact the Siebel Database Administrator to diagnose any connectivity issues and ensure that the Siebel Administrator user id being used by the SiebelClient agent still has been assigned the Siebel Administrator responsibility inside the Siebel application. If the Siebel server is unavailable with a Gateway Failure, Connect Failed, or Login Failed status, all geographic locations should be receiving the same Sieb_Client_Srvr_Avail:FATAL alert because these statuses indicate a problem with the Siebel server itself, rather than a problem with one or a subset of the geographic locations being able to access the Siebel server. If the Siebel server status is Unavailable and all the geographic locations where the SiebelClient agent is deployed are experiencing the same alert, this indicates a Siebel server that has been shutdown or is not completely restarted. If one or more, but not all of the geographic locations where the SiebelClient agent is deployed is alerting with a status of Unavailable, this possibly indicates a network issue between the geographic location(s) where the SiebelClient agent resides and the Siebel server. Contact Siebel Support for further information on restoring the Siebel server to 100% availability. To start your investigation: Right-click or drill down to the Sieb_Client_Srvr_Availability_Overview graph. 63

74 Foglight Cartridge for Siebel Sieb_Client_Stage_Time Rule The Sieb_Client_Stage_Time rule determines whether the response time for each session stage is X seconds greater than the average response time for that stage. CODE LEVEL ACTION SiebelClient.SiebelClientSessionSummary. StageExecuteTimeDifference<#WORLD::StageTimeWarning# SiebelClient.SiebelClientSessionSummary.StageExecuteTimeD ifference >=#WORLD::StageTimeWarning# SiebelClient.SiebelClientSessionSummary. StageExecuteTimeDifference >#WORLD::StageTimeCritical# SiebelClient.SiebelClientSessionSummary. StageExecuteTimeDifference >#WORLD::StageTimeFatal# Normal Warning Critical Fatal Log Message Log Message Log Message SiebelAdmin Log Message SiebelAdmin Interpreting the Rule During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel application, and runs all of the enabled pre-defined and/or user defined transactions, then disconnects from the database. This process or session is broken down into stages. These stages are "Connecting", "Logging In", "Running Transactions", "Running User Defined Txn", and "Completing All Stages". The SiebelClient agent calculates the time to execute each stage of the session and records that value as the StageCurExecuteTime in the SiebelClientSessionSummary table. When the SiebelClient agent is started it calculates the average response time for each stage of the transaction and stores it as the StageAvgExecuteTime in the SiebelClientSessionSummary table. The average response time establishes a baseline for each stage of the session. For each collection, the SiebelClient agent also calculates the difference in seconds between the current and average response time and stores that in the StageExecuteTimeDifference field on the SiebelClientSessionSummary table. The Sieb_Client_Stage_Time rule alerts the Siebel Administrator when the current response time for a stage has exceeded the baseline or average response time by X number of seconds. The Sieb_Client_Stage_Time rule s severity increases as the difference between the stage s current and average response time grows. 64

75 The stages of the transaction include: Connecting - This stage establishes a connection to the Siebel database through the ODBC DSN. Logging In - This stage is the completion of the pre-defined SQL statements that the Siebel Application generates between the connection to the Siebel database and the application home screen that is displayed. Running Transactions - This stage is the completion of the SQL statements that the Siebel Application generates for each pre-defined transaction. Running User Defined Txn - This stage is the completion of the SQL statements that the Siebel application generates for each user defined transaction. Completing All Stages - This is the completion of the Connecting, Logging In, Running Transactions, and Running User Defined Txn stages. #WORLD::StageTimeWarning# is a Foglight Registry entry with a default value of.2500, #WORLD::StageTimeCritical# has a default value of.5000, and #WORLD::StageTimeFatal# has a default value of Use the Foglight Registry to change thresholds for rules by modifying registry entries. Refer to the Diagnosing Response Time Degradation topic for more information. To start your investigation: Right-click or drill down to the Sieb_Client_Sess_Resp_Time_Overview graph. 65

76 Foglight Cartridge for Siebel Sieb_Client_Stage_Pct Rule The Sieb_Client_Stage_Pct rule determines, for the geographic location, where the SiebelClient is physically located whether the response time for each session stage is X percent greater than the average response time for that stage. CODE LEVEL ACTION SiebelClient.SiebelClientSessionSummary. StageExecuteTimePercent<#WORLD::StagePercentWarning# SiebelClient.SiebelClientSessionSummary.StageExecuteTimePercent >=#WORLD::StagePercentWarning# SiebelClient.SiebelClientSessionSummary. StageExecuteTimePercent >#WORLD::StagePercentCritical# SiebelClient.SiebelClientSessionSummary. StageExecuteTimePercent >#WORLD::StagePercentFatal# Normal Warning Critical Fatal Log Message Log Message Siebel Admin Log Message Siebel Admin Interpreting the Rule During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel application, and runs all of the enabled pre-defined and/or user defined transactions and disconnects from the Siebel database. This process or session is broken down into stages. The stages are "Connecting", "Logging In", "Running Transactions", "Running User Defined Txn", and "Completing All Stages". The SiebelClient agent calculates the time to execute each stage of the session and records that value as the StageCurExecuteTime in the SiebelClientSessionSummary table. When the SiebelClient agent is started it calculates the average response time for each stage of the transaction and stores it as the StageAvgExecuteTime in the SiebelClientSessionSummary table. The average response time establishes a baseline for each stage of the session. For each collection, the SiebelClient agent also calculates the difference in percentage between the current and average response time and stores it in the SiebelClientSessionSummary table s StageExecuteTimePercent field. 66

77 The Sieb_Client_Stage_Per rule alerts the Siebel Administrator when the current response time for a stage has exceeded the baseline or average response time by X percent. The Sieb_Client_Stage_Pct rule s severity increases as the percentage difference between the stage s current and average response time grows. The stages of the simulated transaction include: Connecting - This stage establishes a connection to the Siebel database through the ODBC DSN. Logging In - This stage is the completion of the SQL statements that the Siebel Application generates between the connection to the Siebel database and the application home screen that is displayed. Running Transactions - This stage is the completion of the SQL statements that the Siebel Application generates for each pre-defined transaction. Running User Defined Txn - This stage is the completion of the SQL statements that the Siebel Application generates for each user defined transaction. Completing All Stages - This is the completion of the Connecting Logging In, Running Transactions, and Running User Defined Txn stages. #WORLD::StagePercentWarning# is a Foglight_Registry entry with a default value of 50.00, #WORLD::StagePercentCritical# has a default value of 75.00, and #WORLD::StagePercentFatal# has a default value of Use the Foglight Registry to change thresholds for rules by modifying registry entries. Refer to the Diagnosing Response Time Degradation topic for more information. To start your investigation: See the Sieb_Client_Sess_Resp_Time_Overview graph to begin your investigation of stage response time issues. 67

78 Foglight Cartridge for Siebel Sieb_Client_Trans_Time Rule The Sieb_Client_Trans_Time rule determines for the geographic location where the SiebelClient is physically located whether the response time for transaction is X seconds greater than the average response time for that enabled transaction. CODE LEVEL ACTION SiebelClient.SiebelClientTransactionDetail.TransactionExecuteTimePe rcent <#WORLD::TransTimeWarning# SiebelClient.SiebelClientTransactionDetail.TransactionExecuteTimePe rcent >= #WORLD::TransTimeWarning# SiebelClient.SiebelClientTransactionDetail. TransactionExecuteTimeDifference >#WORLD::TransTimeCritical# SiebelClient.SiebelClientTransactionDetail. TransactionExecuteTimeDifference >#WORLD::TransTimeFatal# Normal Warning Critical Fatal Log Message Log Message Siebel Admin Log Message Siebel Admin Interpreting the Rule The SiebelClient agent calculates the time to execute the enabled pre-defined or user defined transaction and records that value as the TransactionCurExecuteTime in the SiebelClientTransactionDetail table. When the SiebelClient agent is started it calculates the average response time for each enabled transaction and stores it as the TransactionAvgExecuteTime in the SiebelClientTransactionDetail table. The average response time establishes a baseline for each enabled transaction. For each collection, the SiebelClient agent also calculates the difference in seconds between the current and average response time and stores it in the SiebelClientTransactionDetail table s TransactionExecuteTimeDifference field. 68

79 The Sieb_Client_Trans_Time rule alerts the Siebel Administrator when the current response time for a pre-defined or user defined transaction has exceeded the baseline or average response time by X number of seconds. The Sieb_Client_Trans_Time rule s severity increases as the difference between the transaction s current and average response time grows. #WORLD::TransTimeWarning# is a Foglight_Registry entry with a default value of.2500, #WORLD::TransTimeCritical# has a default value of.5000, and #WORLD::TransTimeFatal# has a default value of Use the Foglight Registry to change thresholds for rules by modifying registry entries. Refer to the Diagnosing Response Time Degradation topic for more information. To start your investigation: See the Sieb_Client_Tran_Resp_Time_Overview graph to begin your investigation of transaction related issues. Sieb_Client_Trans_Pct Rule The Sieb_Client_Trans_Pct rule determines for the geographic location where the SiebelClient is physically located whether the response time for each enabled transaction is X seconds greater than the average response time for that enabled transaction. CODE LEVEL ACTION SiebelClient.SiebelClientTransactionDetail.TransactionExecuteTimePe rcent <#WORLD::TransTimeWarning # SiebelClient.SiebelClientTransactionDetail.TransactionExecuteTimePe rcent >= #WORLD::TransTimeWarning# SiebelClient.SiebelClientTransactionDetail.TransactionExecuteTimePe rcent >#WORLD::TransTimeCritical# SiebelClient.SiebelClientTransactionDetail.TransactionExecuteTimePe rcent >#WORLD::TransTimeFatal# Normal Warning Critical Fatal Log Message Log Message Siebel Admin Log Message Siebel Admin 69

80 Foglight Cartridge for Siebel Interpreting the Rule The SiebelClient agent calculates the time to execute the enabled pre-defined or user defined transaction and records that value as the TransactionCurExecuteTime in the SiebelClientTransactionDetail table. When the SiebelClient agent is started it calculates the average response time for each enabled transaction and stores it as the TransactionAvgExecuteTime in the SiebelClientTransactionDetail table. The average response time establishes a baseline for each enabled transaction. For each refresh interval, the SiebelClient agent also calculates the difference in percentage between the current and average response time and stores it in the SiebelClientTransactionDetail table s TransactionExecuteTimePercent field. The Sieb_Client_Trans_Time rule alerts the Siebel Administrator when the current response time for a pre-defined or user defined transaction has exceeded the baseline or average response time by X percent. The Sieb_Client_Trans_Time rule s severity increases as the difference between the transaction s current and average response time grows. #WORLD::TransPercentWarning# is a Foglight_Registry entry with a default value of 50.00, #WORLD::TransPercentCritical# has a default value of 75.00, and #WORLD::TransPercentFatal# has a default value of Use the Foglight Registry to change thresholds for rules by modifying registry entries. Refer to the Diagnosing Response Time Degradation topic for more information. To start your investigation: See the Sieb_Client_Tran_Resp_Time_Overview graph to begin your investigation of transaction response time issues. Sieb_Client_Trans_Comp Rule The Sieb_Client_Trans_Comp rule Determines whether the geographic location where the SiebelClient is physically located is able to complete each enabled transaction. CODE LEVEL ACTION SiebelClient.SiebelClientTransactionDetail. TransactionCompleted == 100 SiebelClient.SiebelClientTransactionDetail. TransactionCompleted!= 100 Normal Critical Log Message SiebelAdmin 70

81 Interpreting the Rule The Sieb_Client_Trans_Comp:CRITICAL alert level indicates that the geographic location where the SiebelClient is physically located is unable to complete one or more of the pre-defined or user defined transactions. The Siebel Administrator's response to the Critical error is dependant on the number of geographic locations alerting with the same Sieb_Client_Trans_Comp:CRITICAL alert. If all of the geographic locations where the SiebelClient agent is deployed are alerting with 0% availability for a particular transaction, this indicates a problem with the Siebel database s ability to execute SQL statements or a syntax problem in the XML file that defines the SQL statements for the pre-defined or user defined transaction indicated in the alert message. If each geographic location where the SiebelClient is deployed has ASPs configured to use a different Siebel Application User and one or more, but not all, of the geographic locations are alerting with a 0% availability for a pre-defined or user defined transaction, the problem is specific to the Siebel Application User specified in that SiebelClient's ASPs. Contact the Siebel Database Administrator to ensure that the Siebel Application User still has the appropriate assigned responsibilities and privileges. To start your investigation: See the Sieb_Client_Tran_Status_Detail graph to begin your investigation of transaction related issues. 71

82 Foglight Cartridge for Siebel Sieb_Client_Stage_Comp Rule The Sieb_Client_Stage_Comp rule determines whether the geographic location where the SiebelClient is physically located is able to complete each stage of the session. CODE LEVEL ACTION SiebelClient.SiebelClientSessionSummary. SessionStageCompleted == 100 (SiebelClient.SiebelClientSessionSummary.SessionStage!= "Connecting" && SiebelClient.SiebelClientSessionSummary.SessionStage!= "Completing All Stages") && SiebelClient.SiebelClientSessionSummary.SessionStageComplete d!= 100 SiebelClient.SiebelClientSessionSummary.SessionStage == "Connecting" && SiebelClient.SiebelClientSessionSummary.SessionStageComplete d!= 100 Normal Critical Fatal Log Message SiebelAdmin Log Message SiebelAdmin Interpreting the Rule During every collection, the Siebel Client initiates a session which includes connecting to the Siebel database, logging into the Siebel application, running the enabled transactions, and disconnecting from the Siebel database. The Sieb_Client_Stage_Comp rule alert indicates that the geographic location where the SiebelClient is physically located is unable to complete one or more of the transaction stages. The Siebel Administrator's response to the error is dependant on the stage of the transaction and the number of geographic locations alerting with the same error for the stage. The following information describes the stages associated with the errors, as well as possible solutions: Connecting - This stage establishes a connection to the Siebel database through the ODBC DSN for SQL Server and DB2 databases or SQL*Net(Net8) for Oracle databases. The percentage of completion for "Connecting" is represented as 0% and 100%. If all of the geographic locations where the SiebelClient agent is deployed are alerting with 0% availability for Connecting. This indicates the Siebel database is in an unavailable state. If one or more, but not all of the geographic locations where the SiebelClient agent is deployed are alerting with a 0% availability for Connecting, this could indicate 72

83 a network issue between the geographic location(s) where the SiebelClient agent resides and the Siebel database. Contact the Siebel Database Administrator to diagnose any connectivity issues and ensure that the Siebel Application User being used by the SiebelClient agent still has the appropriate responsibilities and or assigned privileges. Logging In - This stage is the completion of the SQL statements that the Siebel Application generates between the connection to the Siebel database and the application home screen that is displayed. These SQL statements determine the Siebel application user s responsibilities, positions, and visibility. The percentage of completion for "Logging In" represents the percentage of the number of SQL statements that were completed successfully for the Login transaction. If all of the geographic locations where the SiebelClient agent is deployed are alerting with 0% availability for Logging In, this indicates an overall problem with the Siebel database s ability to execute SQL statements. If an alert is received with a percentage between 0% and 100%, this indicates a syntax problem in the XML file defining the SQL statements for the Login transaction. If each geographic location where the SiebelClient is deployed has ASPs configured to use a different Siebel Application User and one or more, but not all, are alerting with a <100% completion for "Logging in, the problem is with the Siebel Application User specified in that SiebelClient's ASPs. Contact the Siebel Database Administrator to ensure that the Siebel Application User still has the appropriate responsibilities and assigned privileges. Running Transactions - This stage is the completion of the SQL statements that the Siebel Application generates for each pre-defined transaction. These transactions do not include the SQL statements for the pre-defined Login transaction. The percentage of completion for "Running Transactions" represents the percentage of the total number of SQL statements completed successfully for all the enabled pre-defined transactions. If all of the geographic locations where the SiebelClient agent is deployed are alerting with 0% completion for Running Transactions, this indicates a problem with the Siebel database s ability to execute SQL statements. If an alert indicating a percentage between 0% and 100% is received, this indicates a syntax problem in the XML file defining the SQL statements for the pre-defined and user defined transactions. If each geographic location where the SiebelClient is deployed has ASPs configured to use a different Siebel Application User and one or more, but not all of the geographic locations are alerting with <100% completion for Running Transactions, the problem is with the Siebel Application User specified in that SiebelClient's ASPs. Contact the Siebel Database Administrator to ensure that the Siebel Application User still has the appropriate responsibilities and assigned privileges. 73

84 Foglight Cartridge for Siebel Running User Defined Txn - This stage is the completion of the SQL statements that the Siebel Application generates for each user defined transaction. These transactions do not include the SQL statements for the user defined Login transaction. The percentage of completion for "Running User Defined Txn" represents the percentage of the total number of SQL statements completed successfully for all the enabled user defined. If all of the geographic locations where the SiebelClient agent is deployed are alerting with 0% completion for Running User Defined Txn, this indicates a problem with the Siebel database s ability to execute SQL statements. If an alert indicating a percentage between 0% and 100% is received, this indicates a syntax problem in the XML file defining the SQL statements for the pre-defined and user defined transactions. If each geographic location where the SiebelClient is deployed has ASPs configured to use a different Siebel Application User and one or more, but not all of the geographic locations are alerting with <100% completion for Running User Defined Txn, the problem is with the Siebel Application User specified in that SiebelClient's ASPs. Contact the Siebel Database Administrator to ensure that the Siebel Application User still has the appropriate responsibilities and assigned privileges. To start your investigation: Right-click or drill down to the Sieb_Client_Sess_Status_Overview graph. Sieb_Client_Agent_Msg Rule The Sieb_Client_Agent_Msg alert is generated when the SiebelClient Agent encounters an error that prevents it from properly functioning. CODE LEVEL ACTION SiebelClient.AgentMsgs.Severity == "Informational" Normal SiebelClient.AgentMsgs.Severity == "Warning" Warning Log Message SiebelClient.AgentMsgs.Severity == "Critical" Critical Log Message SiebelAdmin SiebelClient.AgentMsgs.Severity == "Fatal" Fatal Log Message SiebelAdmin 74

85 When the problem is resolved, the Sieb_Client_Agent_Msg rule will not clear automatically. It must be cleared manually. Interpreting the Rule The SiebelClient agent populates the AgentMsg table with informational and error messages that represent the status of SiebelClient agent. The messages are internally assigned a severity, (i.e., Informational, Warning, Critical, and Fatal). Refer to the following table for a list of the possible messages and resolutions. MESSAGE ID MESSAGE HEADER SEVERITY CONTEXT SPECIFIC MESSAGE TEXT POSSIBLE RESOLUTION SEBL-001 GENERAL INFO Informational User Defined Transactions Loaded in Memory Informational Only User Defined Transaction Count=<transaction count> SEBL-002 VERSION INFO Informational Agent:SiebelClient Version/DCMs matched : <version> Informational Only cont d... 75

86 Foglight Cartridge for Siebel SEBL-004 ASPs ERROR Critical Gateway Server not defined Siebel Language not defined User Script Location not provided Modify the ASPs to correct the ASP value identified in the message text. Siebel Server Manager Utility not found User and/or Password not valid for Database Siebel Schema Owner not found TNSNAMES Alias (Oracle) not found ODBC DSN (DB2) not found ODBC DSN (MSSQL) not found SEBL-005 SECONDARY ASPs ERROR Critical None of the Tables assigned a Sampling Frequency No Appserver defined for Monitoring No Session Stage SLAs defined Modify the ASPs to correct the Secondary ASP value identified in the message text No Predefined SLAs defined for DB Monitoring No UserDefined SLAs defined for DB Monitoring All Tables have zero Sampling Interval. None to populate again. Agent to die in 10 seconds. SEBL-006 SECONDARY ASPs INFO Informational Appserver <SiebelServer> not enabled for monitoring Informational Only 76

87 SEBL-007 NO TABLES LEFT TO POPULATE Fatal No Tables left to populate due to exclusions. Agent to die in 30 seconds Modify the ASPs to correct the ASP value identified in the message text SEBL-008 ASPs SELECTION Informational Monitor Siebel Server Availability not checked Informational Only Monitor Siebel Database not checked SEBL-009 DATABASE CLIENT LIBRARIES NOT FOUND Critical ORACLE libraries on monitored host not found! DB2 libraries on monitored host not found! SQL Server ODBC libraries on monitored host not found! One of the following may be true: Required libraries do not exist on the monitored host. Install the required database client/ ODBC libraries Database libraries/dlls can not be found in the path. Modify the path to include the directory with the libraries/dlls SEBL-010 DATABASE DOWN Critical Siebel Database is not connected at this time Oracle TNS Listener and/or Database may be unavailable. Additional messages may offer further information. Verify that the Siebel database is available 77

88 Foglight Cartridge for Siebel SEBL-011 OCI SQLERROR Warning Context specific message Invalid SQL syntax as identified by the Oracle Call Interface. Correct the SQL query identified in the message text SEBL-012 SEBL-019 SEBL-020 SEBL-021 SEBL-022 OCI UNDEFINED ERROR DB2 ODBC SQLERROR DB2 ODBC UNDEFINED ERROR SQL SERVER ODBC SQLERROR SQL SERVER ODBC UNDEFINED ERROR Critical None Serious unknown error from the Oracle Call Interface Warning Context specific message Invalid SQL syntax as identified by the DB2 ODBC driver. Correct the SQL query identified in the message text Critical None Serious unknown error from the DB2 ODBC driver Warning Context specific message Invalid SQL syntax as identified by the SQL Server ODBC driver. Correct the SQL query identified in the message text Critical None Serious unknown error from the SQL Server ODBC driver 78

89 SEBL-101 SIEBEL APPSERVER MONITORING Critical SiebelClient agent is shutdown. No appserver(s) or database is being monitored ASPs and/or secondary ASPs are either incomplete or incorrect. Modify the ASPs to correct the ASP value identified in the message text of the related alert SEBL-102 SIEBEL DATABASE LOGIN Critical Database Monitoring not turned on Required XML file <file_name> not found." Transactions' XML file not available Database Type and Library home are undefined ASPs and/or secondary ASPs are either incomplete or incorrect. Modify the ASPs to correct the ASP value identified in the message text XML File <xmlfile_name> Couldn't be loaded in Memory SEBL-103 SIEBEL TRANSACTION MONITORING Critical Context specific message These messages relate to problems with SQL statements for pre-defined transactions. Correct the SQL query identified in the message text 79

90 Foglight Cartridge for Siebel SEBL-104 SIEBEL USER DEFINED TRANSACTION MONITORING Critical Context specific message These messages relate to problems with SQL statements for user defined transactions. Correct the SQL query identified in the message text SEBL-105 SIEBEL APPSERVER MONITORING Warning No Appservers defined for monitoring Appservers monitoring turned off as srvrmgr utility not found Appserver name <appserver_name> is invalid. Excluded from monitoring ASPs and/or secondary ASPs are either incomplete or incorrect. Modify the ASPs to correct the ASP value identified in the message text SEBL-106 SIEBEL TRANSACTION MONITORING Warning Table <table_name> is not going to be populated Refer to underlying related messages for additional information Sieb_Client_Trans_SLA Rule The Sieb_Client_Trans_SLA rule determines whether the current response time for the transaction is greater than the expected response time. CODE LEVEL ACTION SiebelClient.SiebelClientTransactionDetail. TransactionCurExecuteTime <= Normal SiebelClient.SiebelClientTransactionDetail. TransactionExpectedTime SiebelClient.SiebelClientTransactionDetail. TransactionCurExecuteTime > SiebelClient.SiebelClientTransactionDetail. TransactionExpectedTime Critical Log Message SiebelAdmin 80

91 Interpreting the Rule The SiebelClient agent calculates the time to execute the enabled pre-defined or user defined transaction and records that value as the TransactionCurExecuteTime in the SiebelClientTransactionDetail table. The SiebelClient's ASP provides the Siebel Administrator with the ability to set the expected time (i.e., SLA), for each enabled pre-defined or user defined transaction and records that value as the TransactionExpectedTime in the SiebelCientTransactionDetail table. The Sieb_Client_Trans_SLA rule alerts the Siebel Administrator when the current response time for a pre-defined or user defined transaction has exceeded the expected value for the transaction over three collection intervals. Refer to the Diagnosing Response Time Degradation topic for more information. To start your investigation: Right-click or drill down to the Sieb_Client_Tran_Resp_Time_Overview graph. Sieb_Client_Stage_SLA Rule The Sieb_Client_Stage_SLA rule determines if current response time for a session stage is greater than the expected response time. CODE LEVEL ACTION SiebelClient.SiebelClientSessionSummary. StageCurExecuteTime <= Normal SiebelClient.SiebelClientSessionsummary. StageExpectedTime SiebelClient.SiebelClientSessionSummary. StageCurExecuteTime > SiebelClient.SiebelClientSessionsummary. StageExpectedTime Critical Log Message SiebelAdmin Interpreting the Rule During every collection, the SiebelClient agent connects to the Siebel database, logs into the Siebel application, and runs all of the enabled pre-defined and/or user defined transactions, then disconnects from the Siebel database. This process or session is broken down into stages. The stages are "Connecting", "Logging In", "Running Transactions", "Running User Defined Txn", and 81

92 Foglight Cartridge for Siebel "Completing All Stages". The SiebelClient agent calculates the time to execute each stage of the SiebelClient's session and records that value as the StageCurExecuteTime in the SiebelClientSessionSummary table. The SiebelClient's ASP provides the Siebel Administrator with the ability to set the expected time (i.e., SLA) for each stage of the SiebelClient session, and records that value as the StageExpectedTime in the SiebelClientSessionSummary table. The stages of the SiebelClient's session include: Connecting - This stage establishes a connection to the Siebel database through the ODBC DSN. Logging In - This stage is the completion of the SQL statements that the Siebel Application generates between the connection to the Siebel database and the application home screen that is displayed. Running Transactions - This stage is the completion of the SQL statements that the Siebel Application generates for each pre-defined transaction. Running User Defined Txn - This stage is the completion of the SQL statements that the Siebel Application generates for each user defined transaction. Completing All Stages - This is the completion of the Connecting, Logging In, Running Transactions, and Running User Defined Txn stages. The Sieb_Client_Stage_SLA rule alerts the Siebel Administrator when the current response time for a stage of the SiebelClient's session has exceeded the expected value for the stage over three collection intervals. Refer to the Diagnosing Response Time Degradation topic for more information. To start your investigation: Right-click or drill down to the Sieb_Client_Sess_Resp_Time_Overview graph. 82

93 Defining User Defined Transactions The SiebelClient agent provides the capability to allow the Siebel Administrator to define user defined transactions that are based on a customized Siebel Application, SQL statements generated by Siebel Workflow, Virtual Business Components, or even non-siebel related transactions. XML is the method being used to define the user defined transactions to the SiebelClient agent. The SiebelClient agent can only read one XML file; however multiple transactions can be defined in the same XML file. The XML file must be stored on the monitored host where the SiebelClient agent is located. The XML script name and location are defined to the SiebelClient agent in the ASPs. The XML file must follow defined standards that are detailed in the following sections. XML Sections - <SiebelClient> - <Transactions> <BindVariable Name="AppUser" Source="ASP\SiebelAppUser" Value="" /> <BindVariable Name="SiebLang" Source="ASP\SiebelLanguage" Value="" /> + <Transaction Name="UD_Login"> + <Transaction Name="UD_Account"> </Transactions> </SiebelClient> Note the following: "SiebelClient" cannot change and must exist. "Transactions" cannot change and must exist. "Transaction Name" must exist and include a unique name for each transaction defined in the XML file. The use of bind variables is available. BindVariable Name under the Transactions section is global in scope and can be used by any SQL query in the XML file. "Value" will be replaced by the corresponding ASP value when the bind variable references a valid ASP. Other static global bind variables can be defined in the "Transactions" section if the "Source" is eliminated but the "Value" attribute is defined. 83

94 Foglight Cartridge for Siebel Simple Transaction Example The following is an example detailing a transaction called UD_Login. The UD_Login transaction is expanded to show the single SQL query named "Login1" that comprises the transaction. - <Transaction Name="UD_Login"> - <SQLQuery Name="Login1"> <BindVariable Name="B3" Source="AppUser" Value="" /> <SQLStatement>SELECT U.LOGIN, U.ROW_ID, P.PARTY_ID FROM siebel.s_user U, siebel.s_party_per P WHERE P.PERSON_ID = U.ROW_ID (+) AND U.LOGIN = '%s' </SQLStatement> <Result Name="ROW_ID" Source="ROW_ID" Value="" /> <Result Name="PARTY_ID" Source="PARTY_ID" Value="" /> </SQLQuery> </Transaction> Note the following: Transactions are a composite made up of one of more queries. Each query may have bind and result variables but these are not mandatory. Each query must have one SQL statement defined. "SQLQuery" must have a unique name within the transaction. In the above example, "BindVariable" is local to the SQL query Login1. "SQLStatement" that defines the SQL query will be executed after the %s are replaced with the corresponding bind variable s value. SQLStatement must be defined without any imbedded carriage returns. "Result" contains the result fields that are populated by the SQL statement for use by other SQL queries. 84

95 Complex Transaction Example This example shows the interaction of the result and bind variables across the previously defined UD_Login transaction and the new UD_Account transaction which reside in the same XML file. - <Transaction Name="UD_Account"> - <SQLQuery Name="Account1"> <BindVariable Name="B1" Source="UD_Login\Login1\ROW_ID" Value="" /> <SQLStatement>SELECT T1.LAST_UPD_BY, T1.ROW_ID, T1.CONFLICT_ID, T1.CREATED_BY, T1.CREATED, T1.LAST_UPD, T1.MODIFICATION_NUM, T1.NAME, T1.QUERY_STRING, T1.DESC_TEXT, T1.CACHE_RSLT_FLG, T1.PRIV_FLG FROM siebel.s_app_query T1 WHERE (T1.CREATED_BY = '%s' OR T1.PRIV_FLG = 'N') AND (T1.NAME = 'Account') ORDER BY T1.NAME, T1.DESC_TEXT</SQLStatement> </SQLQuery> - <SQLQuery Name="Account2"> <BindVariable Name="B1" Source="Login\Login1\PARTY_ID" Value=""/> <SQLStatement>SELECT T3.LAST_UPD_BY, T3.ROW_ID, T3.CONFLICT_ID, T3.CREATED_BY, T3.CREATED, T3.LAST_UPD, T3.MODIFICATION_NUM, T5.PR_POSTN_ADDR_ID, T5.LAST_UPD_BY, T5.CONFLICT_ID, T4.END_DT, T3.PAR_PARTY_ID, T3.PARTY_TYPE_CD, T5.BL_PROD_ID, T3.ROOT_PARTY_FLG, T1.ROW_ID, T5.LAST_UPD, T5.PR_TERR_ID, T5.MODIFICATION_NUM, T5.ROW_ID, T5.NAME, T5.CREATED, T5.CREATED_BY, T2.BASE_CURCY_CD, T5.OU_ID, T5.PAR_ROW_ID, T4.ROW_ID, T4.START_DT, T5.PR_EMP_ID FROM siebel.s_party T1, siebel.s_org_ext T2, siebel.s_party T3, siebel.s_party_per T4, siebel.s_postn T5 WHERE T5.OU_ID = T2.PAR_ROW_ID AND T3.ROW_ID = T5.PAR_ROW_ID AND T5.PR_EMP_ID = T4.PERSON_ID (+) AND T5.ROW_ID = T4.PARTY_ID (+) AND T5.PR_EMP_ID = T1.ROW_ID (+) AND (T3.ROW_ID = '%s') ORDER BY T5.NAME </SQLStatement> <Result Name="T5.OU_IDî Source="T5.OU_IDî Value=""/> </SQLQuery> - <SQLQuery Name="Account3"> <BindVariable Name="B1" Source="UD_Account\Account5\T5.OU_ID" Value="" /> <SQLStatement>SELECT T1.LAST_UPD_BY, T1.ROW_ID, T1.CONFLICT_ID, T1.CREATED_BY, T1.CREATED, T1.LAST_UPD, T1.MODIFICATION_NUM, T3.NAME, T6.PAR_ROW_ID, T4.NAME, T1.PARTY_TYPE_CD, T6.ROW_ID, T6.PAR_BU_ID, T1.ROOT_PARTY_FLG, T6.CREATED_BY, T2.NAME, T6.PAR_DIVN_ID, T5.LAST_UPD_BY, T6.PR_ADDR_ID, T5.PAR_ROW_ID, T6.NAME, T6.MODIFICATION_NUM, T1.PAR_PARTY_ID, T6.LAST_UPD, T6.CONFLICT_ID, T5.NAME, T5.LAST_UPD, T6.LOC, T5.CREATED, T6.CMPT_FLG, T5.CONFLICT_ID, T6.BASE_CURCY_CD, T5.ROW_ID, T6.PRTNR_FLG, T6.CREATED, T5.MODIFICATION_NUM, T5.BU_FLG, T6.LAST_UPD_BY, T6.PR_MGR_POSTN_ID, T5.CREATED_BY FROM siebel.s_party T1, siebel.s_org_ext T2, siebel.s_postn T3, siebel.s_org_ext T4, siebel.s_bu T5, siebel.s_org_ext T6 WHERE T6.PAR_BU_ID = T4.PAR_ROW_ID (+) AND T6.PR_MGR_POSTN_ID = T3.PAR_ROW_ID (+) AND T1.PAR_PARTY_ID = T2.PAR_ROW_ID (+) AND T1.ROW_ID = T6.PAR_ROW_ID AND T1.ROW_ID = T5.PAR_ROW_ID (+) AND (T6.INT_ORG_FLG = 'Y') AND (T1.ROW_ID = '%s') ORDER BY T6.NAME 85

96 Foglight Cartridge for Siebel </SQLStatement> <Result Name="T6.PAR_BU_ID" Source="T6.PAR_BU_ID" Value="" /> </SQLQuery> + <SQLQuery Name="Account7"> + <SQLQuery Name="Account8"> + <SQLQuery Name="Account9"> </Transaction> Note the following: Account1 SQL query has a bind variable who s value is supplied by the result field from the UD_Login transaction/login1 SQL query/row_id result field. Account6 SQL query a bind variable who s value is supplied by the result field from the UD_Account transaction/account5 SQL query/t5.ou_id result field. These types of definitions allow previous result fields to be used in any of the following SQL statements, thus allowing the tailoring of SQL statements to mimic actual transactions. Diagnosing Response Time Degradation When a Siebel application is put into production, it is expected that the initial number of Accounts, Contacts, Opportunities, and Service Requests will grow over time, thus possibly influencing the response time of the simulated transactions. The three factors affect the simulated transaction s response time: Database performance Network latency between the geographic location(s) where the query is being executed (such as the location where the SiebelClient agent is deployed) and the Siebel database Efficiency of the SQL being dynamically generated by Siebel itself As the number of records in the Siebel database increases, the efficiency of the exact same SQL statements could decrease. 86

97 All databases experiencing the same level of degradation If all geographic locations where the SiebelClient agent is deployed are experiencing the same level of response time degradation, the Siebel database itself is the source of the performance degradation. Use the Foglight Database Agent or Spotlight for Oracle, DB2, or SQL Server to diagnose the root cause of the degradation. One or more, but not all databases experiencing degradation If one or more, but not all of the geographic locations where the SiebelClient agent is deployed are experiencing unacceptable response times, the degradation is isolated to a subset of the Siebel Application users. Further investigation into the network performance between the geographic location(s) where the SiebelClient agent resides and the Siebel database should be performed. Foglight s NetMonitor agent can be used to diagnose the network response time between the geographic location where the SiebelClient is physically located and the Siebel database. The only method to influence the SQL statements that are dynamically generated by Siebel is to review the configuration of the Siebel Application itself. Refer to Siebel Systems Siebel Tools Reference Guide for more information on Performance Improvement of the Siebel Application. 87

98 Foglight Cartridge for Siebel 88

99 3 About the SiebelServer Agent For most Siebel Administrators, the Siebel server is a black box with no proactive means to detect when Siebel components and tasks are unavailable, causing performance problems, or have encountered errors. The SiebelServer Agent opens that black box, allowing the Siebel Administrator to gather information to answer the following questions for the Siebel servers in the Siebel environment: Is the Siebel server up and running? Can the Siebel server connect to the Siebel database? Can the Siebel server connect to the gateway server? Do I have enough Siebel servers? Are the Siebel components properly distributed? Is an individual Siebel server process consuming too many of the host s CPU or memory resources? Are all the enabled Siebel components assigned to the Siebel server online or running? Has a Siebel task exited with error? Has a particular error occurred in one of the numerous Siebel task logs? Is a Siebel component s number of running tasks nearing the maximum number allowed? Has an application object manager encountered any errors? Are the Transaction Router, Transaction Merger, and Transaction Processor running?

100 Foglight Cartridge for Siebel The SiebelServer agent is deployed on the monitored host where the Siebel server resides and uses the Siebel Server Manager Command Line Interface combined with OS process information and file scraping to collect its data. Siebel Server Availability Monitoring The availability of the Siebel ebusiness Application depends upon the availability of each Siebel server in the environment. When a Siebel server is unavailable, every enabled Siebel component assigned to that Siebel server is also unavailable. Furthermore, if a Siebel component is only assigned to one Siebel server and that one Siebel server becomes unavailable, the work being performed by those components has stopped. For example, if the Siebel server that is assigned the Siebel Remote components such as the Transaction Router, Transaction Merger, and Transaction Processor becomes unavailable, every Siebel Remote user assigned to that Siebel server would be unable to synchronize. The fact that a Siebel server itself is running and available, does not guarantee the Siebel users have access to the Siebel server from the geographic location where they are physically located. Therefore, it is important to monitor the Siebel server availability from the geographic locations where the Siebel users typically reside. The SiebelClient agent provides the functionality for the Siebel Administrator and uses the Siebel Server Manager Command Line Interface to collect this data. ASP Using Siebel Server Agent Startup Parameters Investigations Investigating Siebel Server Performance Investigating Siebel Component Performance Investigating Siebel Server Load Investigating Siebel Component Load Investigating Siebel Server SQL Performance Investigating Siebel Component SQL Performance Investigating Siebel Server Availability Investigating Siebel Enterprise Performance Investigating Siebel Enterprise Component Performance Investigating Siebel Enterprise Load Investigating Siebel Enterprise SQL Performance 2

101 Investigating Siebel Enterprise Component SQL Performance Investigating Siebel Enterprise Availability Views Sieb_Srvr_Availability_Overview Sieb_Srvr_Overview Sieb_Srvr_Utilization_Overview Sieb_Comp_Availability Sieb_Comp_SQLExecute_Detail Sieb_Comp_SQLFetch_Detail Sieb_Comp_SQLParse_Detail Sieb_Comp_ SQLTime Sieb_Proc_Memory_Detail Sieb_Proc_Utilization Sieb_Srvr_Detail Rules Sieb_Srvr_Avail Sieb_DB_Connect_Avail Sieb_GW_Connect_Avail Sieb_SrvrNoDBConnRetry Sieb_Srvr_NoDLRbkRetry Sieb_Srvr_NoXhaustRetry Sieb_Srvr_CPU_Util Sieb_Srvr_Memory_Util Sieb_Srvr_Proc_CPUTime Sieb_Comp_MTServers Sieb_Task_Status Sieb_Comp_AOMErrors Sieb_Srvr_Proc_Memory Sieb_Comp_State Sieb_Comp_Proc_Avail Sieb_Comp_Merger_Avail Sieb_Comp_Route_Task 3

102 Foglight Cartridge for Siebel Sieb_Comp_Inter_Task Sieb_Log_MsgSieb_Crash Log Tables Siebel Component Groups Siebel Components Siebel Component Statistics Siebel Log Message Siebel Process Information 4

103 Siebel Server Health Siebel Server Statistics Siebel Server Summary Siebel Tasks 5

104 Foglight Cartridge for Siebel ASPs Using SiebelServer Agent Startup Parameters The Foglight SiebelServer agent startup parameters (ASPs) are used to define the Siebel server environment details that the SiebelServer agent will be monitoring. For more information regarding common agent startup parameters see the topic About Agent Parameters. Topics Setting the Collection Rate Setting the Database Information Setting the SiebelServer Parameters Setting the SiebelServer Log Parameters Setting the Collection Rate The collection rate, or sample frequency, is the number of seconds between the end of a collection period and the start of the next. The Siebel Server agent uses a Sample Frequency list, allowing you to set a different sample frequency for each table associated with the agent. For example, you can change the sample frequency to every five minutes to reduce Foglight server disk requirements. Use the Collection Rate tab in the Siebel Server ASP dialog to set the sample frequency. To set the sample frequency and purge days 1. Right-click the SiebelServer agent icon and choose Edit, ASPs to display the Edit ASPs dialog. 6

105 2. Enter the sample frequency in seconds in the Sample Frequency text box. 3. Enter the name of the list to be edited in the Sample Frequency List drop down list and click the Edit button to display the SiebelServer Frequency List dialog. 4. Select the table you want to use and click the Edit button to display the Edit Template dialog. Do not add or delete tables to the SiebelServer Frequency List. Only existing tables should be modified. 5. Enter a new frequency, in seconds, in the Sample Frequency text box. 6. Click OK to save your changes and close the dialog. 7. Click OK on the SiebelServer Frequency List dialog to close this dialog. 8. Click OK to save the entries and close the Edit ASP dialog, or click another tab to define additional startup parameters. 7

106 Foglight Cartridge for Siebel Setting the Purging Parameters To control the growth of the Foglight database, you may wish to purge data from tables in the Foglight Database. Use the Database tab in the Siebel Server ASP dialog to set the purging parameters. To set the purging parameters 1. Right-click the SiebelServer agent icon and choose Edit, ASPs to display the Edit ASPs dialog. 2. Click the Database tab. 3. Enter the purging rate in the Purge All Data After text box and select Days, Weeks, or Months from the drop down list. Enter 9999 if you do not want to purge data. 4. Click OK to save the entries and close the Edit ASP dialog box, or select another tab to define additional startup parameters. 8

107 Setting the SiebelServer Parameters Use the Siebel Info tab to enter data relating to the Siebel server. To set the server parameters 1. Right-click the SiebelServer agent icon and choose Edit, ASPs to display the Edit ASPs dialog. 2. Click the Siebel Info tab. 3. Enter the name of the Siebel gateway server in the Gateway Server Name text box. The gateway server name is case sensitive on Unix-based Siebel servers. If the gateway server is running on a port other than the default of 2320, enter the name of the Siebel gateway followed by the port number. For example, "Gateway Server: Port Number." 4. Enter the name of the Siebel enterprise server in the Enterprise Name text box. The Enterprise Name is case sensitive on Unix-based Siebel servers. 5. Enter the name of the Siebel server in the Siebel Server text box. The Siebel Server name is case sensitive on Unix-based Siebel servers. 6. Enter the full path to the directory where the Siebel Server Manager executable is located in the Siebel Server Manager Directory text 9

108 Foglight Cartridge for Siebel box. On Windows, srvrmgr resides in SIEBEL_HOME\siebsrvr\bin, and on UNIX it is located in SIEBEL_HOME/bin. 7. Enter the name of a Siebel application user with Siebel Administrator responsibilities in the Siebel Administrator ID text box. 8. Enter the password for the Siebel application user with Siebel Administrator responsibilities in the Siebel Administrator Password text box. 9. Enter SQL*Net Alias (Oracle) or the name (DB2 and SQL Server) of the Siebel database in the Database Alias/Name text box. 10. Enter the number of Siebel OS processes to monitor for highest memory resource utilization in the Number of Top Siebel OS Process to Monitor text box. The default value is 5 and the maximum value is 11. Click OK to save the entries and close the Edit ASP dialog. 11. Check the Enable Debug Flag to enable the ServerMgr component parameter 'debugflags=8191'. Enabling the debugflags parameter allows the agent to correlate all the Siebel OS processes to the associated Siebel component. 12. Click OK to save the entries and close the Edit ASP dialog. Click the Siebel Log Info tab to set log parameters for the Siebel server, or select another tab to define additional startup parameters. Setting the SiebelServer Log Parameters Use the Siebel Log Info tab to enter data relating to the Siebel server logs. To set the log parameters 1. Right-click the SiebelServer agent icon and choose Edit, ASPs to display the Edit ASPs dialog. 2. Click the Siebel Log Info tab. 10

109 3. Enter the full path to the directory where the Siebel Server and Component Log files are located in the Siebel Server Log Directory text box. 4. Enter the name of the list to edit in the Siebel Server Trap List drop-down list. 5. Click the Edit button to display the information about this list in the SiebelServer_Msg_List dialog. 6. Modify any of the following items: Enabled. Mark to monitor logs for the listed item. Search String. The name of the text string, or error, to search for in the Siebel server log file. 11

110 Foglight Cartridge for Siebel Message Severity. The severity of the error (i.e., Informational, Warning, Critical, or Fatal). User Message. A user defined message describing what the error means to the Siebel Administrator. 7. Click OK to close this dialog. 8. Enter the name of the list to edit in the Component Trap List drop down list. 9. Click Edit to display the information about this list in SiebelComponent_Msg_List dialog. 10. Modify any of the following items: Enabled. Mark to monitor task logs for the listed Siebel Component Alias. Component Alias. Name of the Siebel component alias that the Siebel Administrator wishes to monitor for task log errors. Match String. The name of the text string, or error, to search for in the Component task log file. Message Severity. The severity of the error (i.e., Informational, Warning, Critical, or Fatal). User Message. A user defined message describing what the error means to the Siebel Administrator. 11. Click OK to close this dialog. 12. Mark the Monitor Crash Logs (Siebel7 or above) check box to monitor the existence of new Application Object Manager Crash Logs. The 12

111 existence of a new Crash Log indicates that an Application Object Manager has crashed. 13. Enter the full path to the directory where the Application Object Manager Crash Logs are located in the Crash Log Directory text box. In Windows, the default location is SIEBEL_HOME\siebsrvr\bin. In UNIX, the default location is SIEBEL_HOME/bin. 14. Mark the Remove ServerMgr Log Files check box to remove all generated ServerMgr_TaskID.log files in the directory per sampling interval. Foglight uses the Siebel Server Manager to collect Siebel availability and performance statistics. Siebel Server Manager will generate one or more ServerMgr_TaskID.log file per sampling interval. Siebel Server Manager log files generated by other Siebel administrators are deleted during the log clean-up process. 15. Click OK to save the entries and close the Edit ASP dialog, or select another Tab to define additional startup parameters. 13

112 Foglight Cartridge for Siebel SiebelServer Agent Tables The SiebelServer agent stores data in the following tables in the Foglight Database. Click the hyperlinks to view field definitions Component Groups Component Statistics Components Log Message Process Information Server Health Server Statistics Server Summary Tasks Siebel Component Groups Table The fields included in this table are as follows: FIELD ComponentCount ComponentGroup ComponentGroupAlias ComponentGroupAvailability ComponentRunState DESCRIPTION The number of Siebel components included in the component group. The full name of the component group. A short name or alias for the component group. A numeric value (100 = online or running and 0 = all other values) that represents the component group run state. The current run state for the Siebel component group (Online, Offline, Shutdown, etc.). 14

113 Siebel Component Statistics Table The fields included in this table are as follows: FIELD AOMErrors AvgSQLExecTime AvgSQLFetchTime AvgSQLParseTime CPUTime ComponentAlias GroupAlias NumberSQLExecutes NumberSQLFetches NumberSQLParses NumberSleeps SQLExecuteTime SQLFetchTime SQLParseTime SleepTime Tasks TotalCPUTime DESCRIPTION The number of Application Object Manager (AOM) errors in the session since the last collection. Average time (seconds) the Siebel component spent performing SQL execute operations since the last collection. Average time (seconds) the Siebel component spent performing SQL fetch operations since the last collection. Average time (seconds) the Siebel component spent performing SQL parse operations since the last collection. The amount of CPU time, in seconds, for all component tasks since the last collection. A short name or alias for the Siebel component. A short name or alias for the Siebel component goup that the Siebel component belongs to. The number of SQL execution operations since the last collection. The number of SQL fetch operations since the last collection. The number of SQL parse operations since the last collection. The number of sleeps, in seconds, for component tasks since the last collection. The number of SQL execution operations since the last collection. The number of SQL fetch operations since the last collection. The number of SQL parse operations since the last collection. The amount of time, in seconds, that component tasks spent sleeping since the last collection. The number of Siebel component tasks started since the last collection. The total amount of CPU time, in seconds, for all component tasks since the Siebel server started. 15

114 Foglight Cartridge for Siebel TotalSQLExecuteTime TotalTasks The total amount of time, in seconds, the component spent performing SQL execute operations since the Siebel server started. The total number of component tasks started since the Siebel server started. Siebel Components Table The felds included in this table are as follows: FIELD ComponentAlias ComponentGroup ComponentName ComponentRunMode ComponentState ComponentStateAvailability MaxMTS MaxTasks MinMTS RunningMTS RunningTasks DESCRIPTION A short name or alias for the Siebel component. The Siebel component group associated with the component. The full name of the component. Mode the component s tasks are executed in (i.e., Background, Batch, or Interactive). Current run state for the Siebel component (Online, Shutdown, Unavailable, etc.). A numeric value (100 = online or running and 0 = all other values) that represents the component run state. The maximum number of active servers for a multithreaded service. This value indicates the maximum number of OS processes that will be spawned to support component tasks. The number of tasks that can be instantiated for the component. The minimum number of active servers for a multithreaded service. This value indicates the minimum number of OS processes that will be spawned to support component tasks. The current number of active servers for a multithreaded service. This value indicates how many OS processes are currently spawned to support component tasks. The current number of concurrent tasks that have been instantiated for the component. 16

115 Siebel Log Message Table The fields included in this table are as follows: FIELD LogFileName MsgText Severity UsrMessage DESCRIPTION The name of the log file that contains the text string (error). The actual text from the Siebel log file where the search string specified in the ASPs was found. The severity of the text string as determined by the Siebel Administrator (i.e., Informational, Warning, Critical, or Fatal). A user defined message that describes what the error means to the Siebel Administrator. Siebel Process Information Table The fields included in this table are as follows: FIELD ComponentAlias PercentCPUTime PercentMemory ProcessID ProcessImageName ProcessName ResidentSetSize VirtualSetSize DESCRIPTION A short name or alias for the Siebel component. Percentage of CPU time being used by the Siebel process at the time of collection. The percentage of resident set size in use at the time of collection. The operating system identification number assigned to the process. The name of the Siebel component or entity associated with the process. The operating system or executable name for the process. Amount of the Siebel process address space (bytes) that is currently in main memory. Main memory includes RAM plus ROM; however, it does not include cache. Amount of virtual memory used by the process in Kbytes. 17

116 Foglight Cartridge for Siebel Siebel Server Health Table The fields included in this table are as follows: FIELD DatabaseAlias DatabaseAvailability EndTime EnterpriseServer GatewayServer GatewayServerAvailability SiebelServer SiebelServerAvailability SiebelServerPID SiebelServerStatus SiebelServerUpTime StartTime DESCRIPTION Database Name/Alias for the Siebel Enterprise. Value retrieved from ASPs. Numeric value representing the Siebel server's ability to connect to the Siebel database (100 = True or 0 = False). The time that a server was shut down. This value is only available when the server is shutdown within Siebel Server Manager. Name of the Siebel enterprise that the Siebel server belongs to. Value retrieved from ASPs. Name of the gateway server for the Siebel enterprise. Value retrieved from ASPs. A value (100 = true and 0 = false) that indicates if the server can connect to the gateway server at the present time. The name of the Siebel server. A value (100 = running and 0 = all other values) that represents the run state of the server. The operating System process id (PID) for the Siebel server. The current state of the server. The possible status types include: Running, Shutdown, Unavailable, Login Failed, Handshake Failed, Not Available, Connect Failed, and Gateway Failure. The number of Days, Hours, Minutes and Seconds the Siebel Server has been running. The time that the server was started. 18

117 Siebel Server Statistics Table The fields included in this table are as follows: FIELD AvgConnectTime AvgReplySize AvgRequestSize AvgResponseTime AvgSQLExecTime AvgSQLFetchTime AvgSQLParseTime AvgThinkTime CPUTime ElapsedTime NumberDBConnRetries NumberDLRbkRetries NumberExhaustedRetries NumberReplyMessages NumberRequestMessages DESCRIPTION The average time that Object Manager sessions were connected since the last collection. The average size (bytes) of reply messages since the last connection. The average size (bytes) of request messages since the last collection. The average Object Manager response time since the last collection. The average amount of time, in seconds, that the server spent performing SQL execute operations since the last collection. The average amount of time, in seconds, that the server spent performing SQL fetch operations since the last collection. The average amount of time, in seconds, that the server spent performing SQL parse operations since the last collection. The average amount of end-user think time between requests since the last collection. The total CPU time (seconds) for all the Siebel server s tasks since the last collection. Total elapsed or running time (seconds) for all the Siebel server s tasks since the last collection. The number of retries resulting from database connection termination since the last collection. The number of retries resulting from deadlock rollbacks since the last collection. The number of times that retries have been exhausted since the last collection. The number of reply messages sent by the server since the last collection. The number of request messages sent by the server since the last collection. 19

118 Foglight Cartridge for Siebel NumberSQLExecutes NumberSQLFetches NumberSQLParses NumberSleeps SiebelServer SQLExecuteTime SQLFetchTime SQLParseTime SleepTime Tasks TotalAvgConnectTime TotalAvgRequestPerSession TotalAvgResponseTime TotalCPUTime TotalReplySize TotalRequestSize TotalResponseTime TotalSQLExecuteTime The number of SQL execute operations since the last collection. The number of SQL fetch operations since the last collection. The number of SQL parse operations since the last collection. The total number of sleeps for all tasks since the last collection. The name of the Siebel server. The amount of time, in seconds, spent performing SQL execute operations since the last collection. The amount of time, in seconds, spent performing SQL fetch operations since the last collection. The amount of time, in seconds, spent performing SQL parse operations since the last collection. The total amount of time (seconds) for all the Siebel component s tasks spent sleeping since the last collection. The total number of Siebel component tasks started since the last collection. The average time the Object Manager sessions were connected since the Siebel server started. The average number of requests per Object Manager session since the Siebel server started. The average Object Manager response time since the Siebel server started. The total CPU time (seconds) for all the Siebel Server s Tasks since the Siebel srver started. The total size, in bytes, of all reply messages since the last connection. The total size, in bytes, of all request messages since the last connection. The total response time, in seconds, for the Object Manager since the last connection. The total time (seconds) the Siebel server spent performing SQL execute operations since the Siebel server started. 20

119 TotalTasks TotalThinkTime The total number of Siebel component tasks started since the Siebel server started. The total client think time, in seconds, or the total amount of elapsed time between client requests since the Siebel server started. Siebel Server Summary Table The fields included in this table are as follows: FIELD SiebelServer TotalObjMgrSessions TotalPercentCPUTime TotalPercentMemory TotalRunningTasks DESCRIPTION The name of the Siebel server. The total number of Interactive tasks running on the Siebel server at the time of collection. The total percentage of CPU time being used by all the Siebel processes at the time of collection. The total percentage of resident set size used by all the Siebel processes at the time of collection. The total number of tasks running on the Siebel server at the time of collection. Siebel Tasks Table The fields included in this table are as follows: FIELD ComponentAlias GroupAlias OSTaskPID TaskAvailability TaskEndTime DESCRIPTION A short name or alias for the Siebel component. A short name or alias for the Siebel component group associated with the component. The Operating System process id (PID) that is running this task. A numeric value (100 = Running and 0 = all other values) that represents the current task status. The Mode the task is executed in (Background, Batch, or Interactive). 21

120 Foglight Cartridge for Siebel TaskID TaskRunMode TaskStartTime TaskStatus A numeric identification code for the Siebel component task. This field is concatenated with the ComponentAlias field to create a unique identifier for the Component Event Log. The current mode when the task is executed. The possible modes are Background, Batch, or Interactive. The time that the task started. The current status of the task. The status categories include Running, Paused, Stopping, Completed, Exited with Error, and Killed. 22

121 Investigations Investigating Siebel Server Performance When a Siebel task operation completes, task level statistics that are gathered dynamically during the operation of a task roll up to the component level. Statistics for all enabled components assigned to a Siebel server are rolled up to the server level. Siebel server statistics are cumulative (i.e., since the server started). These statistics can be used to monitor the progress and performance of a Siebel server. Start with the Sieb_Srvr_Overview graph The Sieb_Srvr_Overview graph correlates the Siebel server's cumulative response time with its cumulative, utilization and throughput. Investigating Siebel Component Performance When a Siebel task completes its operation, task level statistics, gathered dynamically during the operation of each task, roll up to the Siebel component level. These statistics can be used to monitor the performance of each enabled Siebel component. Siebel stores component statistics as cumulative statistics (i.e., since the Siebel server started). The Foglight SiebelServer agent collects both cumulative and delta Siebel component statistics. Foglight calculates Siebel component statistic deltas by determining the change in the individual statistics since the last collection, then stores the delta values in the Foglight repository along with the cumulative value for selected statistics. Start with the Sieb_Comp_Statistics graph Use the Sieb_Comp_Statistics graph to analyze the amount of throughput and resource consumption each enabled Siebel component has contributed to the Siebel server's total throughput and resource consumption since startup. 23

122 Foglight Cartridge for Siebel Investigating Siebel Server Load The Siebel ebusiness application environment is typically comprised of multiple Siebel servers with each Siebel server being assigned multiple Siebel components. It is important that all the Siebel servers that comprise the Siebel enterprise share the load and one or more Siebel servers are not overutilized while others in the enterprise remain underutilized. The Foglight SiebelServer agent collects statistics to enable the Siebel Administrator the ability to correlate the Siebel server s response time, utilization, and throughput. Start with the Sieb_Srvr_Utilization_Overview graph The Sieb_Srvr_Utilization_Overview graph provides information about object manager response time, resource utilization, and the number of running and interactive tasks. Investigating Siebel Component Load If the Siebel Administrator suspects that a Siebel server is overloaded, an analysis of each OS process that comprises the Siebel server should be performed. The Foglight SiebelServer agent calculates CPU and memory utilization statistics for each OS process that comprises the Siebel server. For Siebel 7 enterprises, this agent is able to correlate the siebmtsh executables that run multi-threaded processes or MTServers with the corresponding Siebel component. There is one siebmtsh executable for each MTServer that is currently running. Even though the Foglight SiebelServer Agent calculates CPU and memory utilization statistics for each OS process, the agent uses the Number of Top Siebel OS Process to Monitor ASP value to determine the number of top processes to store in the Foglight repository for each collection. Foglight sorts by memory percentage when determining the top processes to store in the Foglight repository. Start with the Sieb_Proc_Utilization graph The Sieb_Proc_Utilization graph monitors CPU and memory resource usage. 24

123 Investigating Siebel Server SQL Performance When a Siebel task is completed, task level statistics gathered dynamically during the operation of a task roll up to the component level. Statistics for all enabled components assigned to a Siebel server are rolled up to the Siebel server level. Siebel server statistics are cumulative (i.e., since the Siebel server started). Among the many statistics that are gathered and rolled up to the Siebel server level are statistics on the time that the Siebel server has spent parsing, executing, and fetching SQL statements. Siebel Support Web provides the following SQL time definitions: SQL Parse Time. The number of seconds spent translating the SQL statements into an execution plan. This time includes checking for proper security authorization and checks for the existence of tables, columns, and other referenced objects. SQL Execute Time. For SELECT statements, the amount of time spent identifying the rows if the statement requires a sort or uses FOR UPDATE. For INSERT, UPDATE, and DELETE statements, the amount of time spent modifying the data. SQL Fetch Time. For SELECT statements only, the amount of time spent retrieving the rows returned by the query. The Foglight SiebelServer agent collects delta SQL parse, SQL execute, and SQL fetch statistics for the Siebel server. Foglight calculates the deltas by determining the change in the individual statistic since the last collection and stores the delta value in the Foglight repository. This allows the Siebel Administrator to identify peak SQL usage time periods. Start with the Sieb_Srvr_SQLTime graph The Sieb_Srvr_SQLTime graph monitors SQL parse, fetch, and execute collection times. 25

124 Foglight Cartridge for Siebel Investigating Siebel Component SQL Performance When a Siebel task completes its operation, task level statistics gathered dynamically during the operation of each task, roll up to the component level. Among the many statistics gathered and rolled up to the Siebel component level are statistics on the time that the Siebel component spent parsing, executing, and fetching SQL statements. Siebel server statistics are cumulative (i.e., since the Siebel server started). The Foglight SiebelServer agent collects delta SQL parse, execute, and fetch statistics for each enabled Siebel component. Foglight calculates the deltas by determining the change in the individual cumulative statistic since the last collection and stores the delta value in the Foglight repository. This allows the Siebel Administrator to identify peak SQL usage time periods for each Siebel component. Start with the Sieb_Comp_SQLTime graph The Sieb_Comp_SQLTime graph tracks the amount of time spent translating, identifying, and retrieving SQL statements. Investigating Siebel Server Availability The availability of the Siebel ebusiness Application depends upon the availability of each Siebel server in the environment. When a Siebel server is unavailable, every enabled Siebel component assigned to that Siebel server is also unavailable. Furthermore, if a Siebel component is only assigned to one Siebel server and that one Siebel server becomes unavailable, the work being performed by those components stops. For example, if Assignment Manager is used to assign leads from the corporate web site to the appropriate account team, and the one Siebel server that runs the Assignment Manager component is unavailable, the new web leads are not being assigned to an account team, thus negatively impacting customer satisfaction levels. The Foglight SiebelServer agent collects availability statistics on the Siebel server, Siebel component groups, and Siebel components assigned to the Siebel server. These availability statistics not only allow the Siebel Administrator to be alerted when an availability issue is encountered, but also generate views/reports on the overall availability of the Siebel ebusiness Application environment for management. The Foglight Siebel server agent calculates the Siebel server s availability percentages as follows: 26

125 The Siebel server s availability is calculated as follows: 100% if the SiebelServerStatus = Running 0% for all other values The Siebel server s database connection availability is calculated as follows: 100% if the Siebel server is able to log into the Siebel database as the Siebel Administrator 0% for all other values The Siebel server s gateway server connection availability is calculated as follows: 100% if the Siebel server is able to connect to the Siebel gateway server. 0% for all other values Start with the Sieb_Srvr_Availability_Overview graph The Sieb_Srvr_Availability_Overview graph provides database and availability information about each Siebel server. Investigating Siebel Enterprise Performance Use the View Editor to create a Sieb_Enterprise_Overview graph to display the progress of all the Siebel servers in the enterprise. The Siebel Administrator can use this graph to analyze whether the throughput for the Siebel enterprise is balanced across all the Siebel servers in the enterprise. Use the View Editor to create a Sieb_Enterprise_Detail graph to display the interval based performance of all the Siebel servers in the enterprise. Investigating Siebel Enterprise Component Performance Use the View Editor to create a Sieb_Enterprise_Comp_Statistics graph detailing the progress of all the Siebel components in the enterprise. Investigating Siebel Enterprise Load Use the View Editor to create a Sieb_Enterprise_Utilization_Overview graph detailing the load of all the Siebel servers in the enterprise. 27

126 Foglight Cartridge for Siebel Investigating Siebel Enterprise SQL Performance Use the View Editor to create a Sieb_Enterprise_SQLTime graph detailing the interval based SQL performance of all the Siebel servers in the enterprise. Investigating Siebel Enterprise Component SQL Performance Use the View Editor to create a Sieb_Enterprise_Comp_SQLTime graph detailing the interval based SQL performance of all the enabled Siebel components in the enterprise. Investigating Siebel Enterprise Availability Use the View Editor to create a Sieb_Enterprise_Availability_Overview graph detailing the availability of all the Siebel servers in the enterprise. Use the View Editor to create a Sieb_Enterprise_Comp_Group_Availability graph detailing the availability of all the Siebel component groups in the enterprise. Use the View Editor to create a Sieb_Enterprise_Comp_Availability graph detailing the availability of all the Siebel components in the enterprise. 28

127 Views Sieb_Srvr_Availability_Overview Graph The availability of the Siebel ebusiness Application depends upon the availability of each Siebel server in the environment. When a Siebel server is unavailable, every enabled Siebel component assigned to that Siebel server is also unavailable. Furthermore, if a Siebel component is only assigned to one Siebel server and that one Siebel server becomes unavailable, the work being performed by those components has stopped. For example, if Assignment Manager is used to assigned leads from the corporate web site to the appropriate account team, and the one Siebel server that runs the Assignment Manager component is unavailable, the new web leads are not being assigned to an account team, thus negatively impacting customer satisfaction levels. The Foglight SiebelServer agent collects availability statistics on the Siebel server, Siebel component groups, and Siebel components assigned to the Siebel server. These availability statistics not only allow the Siebel Administrator to be alerted when an availability issue is encountered, but also generate views/reports on the overall availability of the Siebel ebusiness Application environment for management. Siebel server availability is calculated as follows: 100% if the SiebelServerStatus = Running. 0% for all other values. Server database connection availability is calculated as follows: 100% if the Siebel server is able to log into the Siebel database as the Siebel Administrator. 0% for all other values. Server gateway server connection availability is calculated as follows: 100% if the Siebel server is able to connect to the Siebel gateway server. 0% for all other values. The Sieb_Srvr_Availability_Overview graph is used to view the availability percentage of: Siebel server s status Siebel server s ability to connect to the Siebel database 29

128 Foglight Cartridge for Siebel Siebel server s ability to connect to the gateway server The Time Range menu option for the Sieb_Srvr_Availability_Overview graph can be used to show the Siebel server availability statistics for the last 24 hours, last week, last month, etc. If the Siebel server is reported as having 0% availability, Siebel Server Manager should be used to restart the server. Other options include restarting the Siebel Server service on Windows Siebel servers or use start_server on Unix based Siebel servers. Contact Siebel Support if restarting the server does not restore it to 100% availability. It is important for the Siebel Administrator to not only monitor the availability of the Siebel database but to monitor the ability of the Siebel server to connect to the database. If the database is available but the Siebel server is unable to login, all the enabled Siebel components assigned to the server will not be able to service user requests. To verify the Siebel server s ability to connect to the database as the Siebel Administrator, use a database utility located on the Siebel server such as SQL*Plus or ISQL to connect to the database. Contact the Siebel Database Administrator for help with diagnosing any connectivity issues. It is equally important for the Siebel server to have connectivity to the gateway server. The gateway server provides persistent backing of SiebelServer configuration information, including definitions and assignments of components, operational parameters, and connectivity information. If the gateway server becomes unavailable, new Siebel components cannot be started or added, and server administration functions become limited. However, all components and object managers currently running continue to do so. If the Siebel gateway server itself becomes unavailable, the Siebel Administrator will receive an alert that the gateway server is unavailable, but also an alert from all the Siebel servers that it has lost its connection to the gateway server. In this case, the Siebel Administrator should restart the Siebel gateway server. However, if the Siebel Administrator only receives one or more alerts that the Siebel server has lost connectivity to the Siebel gateway server, this possibly indicates that the network connectivity has been lost between the two hosts. The NetMonitor agent can be used to monitor the network connectivity between all the monitored hosts that comprise the Siebel ebusiness Application environment. 30

129 To open the Sieb_Srvr_Availability_Overview graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Srvr_Availability_Overview graph icon. You can use the Time Range menu option to show the Siebel server availability statistics for the last 24 hours, last week, last month, etc. To continue your investigation Drill down on the Siebel Server % bar to display the availability of the Siebel component groups for the Siebel server during the same time range in the Sieb_Comp_Group_Availability graph. Drill down to the Sieb_Comp_Group_Availability graph to display the availability of the Siebel component groups for the Siebel server during the same time range as the Sieb_Srvr_Availabiity_Overview graph. Use the View Editor to create a Sieb_Enterprise_Availability_Overview graph detailing the availability of all the Siebel servers in the enterprise. Sieb_Srvr_Overview Graph When a Siebel task completes its operation, task-level statistics that are gathered dynamically during the operation of a task roll up to the component level. Statistics for all enabled components assigned to a Siebel server are rolled up to the Siebel server level. Siebel stores server statistics as cumulative statistics, i.e., since the Siebel server started. These statistics can be used to monitor the progress and performance of a Siebel server. 31

130 Foglight Cartridge for Siebel The Sieb_Srvr_Overview graph correlates the Siebel server s cumulative response time with its cumulative utilization and throughput. The Sieb_Srvr_Overview correlates the following statistics: Average object manager response time since the Siebel server started. Total CPU time, in seconds, for all the server s tasks since the Siebel server started. Total time, in seconds, that the Siebel server spent performing SQL execute operations since the server started. For SELECT statements, this is the amount of time spent identifying the rows if the statement requires a sort or uses FOR UPDATE. For INSERT, UPDATE, and DELETE statements, this is the amount of time spent modifying the data. Total number of Siebel tasks started since the Siebel server started. Use the Siebel Server Overview graph as a progress indicator for the individual Siebel server. To open the Sieb_Srvr_Overview graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Srvr_Overview graph icon. To continue your investigation Drill down to the Sieb_Srvr_Detail graph to correlate the Siebel server's response time with its utilization and throughput for each refresh interval. Use the View Editor to create a Sieb_Enterprise_Overview graph detailing the progress of all the Siebel servers in the enterprise. The Siebel Administrator can use this graph to analyze whether the 32

131 throughput for the Siebel enterprise is balanced across all the Siebel servers in the enterprise. Sieb_Srvr_Utilization_Overview Graph The Siebel ebusiness application environment is typically comprised of multiple Siebel servers with each Siebel server being assigned multiple Siebel components. It is important that all the Siebel servers that comprise the Siebel enterprise share the load and one or more Siebel servers are not overutilized while others in the enterprise remain underutilized. The Foglight SiebelServer agent collects statistics to enable the Siebel Administrator to correlate the Siebel server s response time, utilization, and throughput. Use this graph to correlate the following statistics about a Siebel server: Siebel server's average object manager response time Total amount of operating system resources the Siebel server is consuming Total number of tasks the Siebel server is running Number of interactive sessions the Siebel server is running. This includes object manager sessions and other interactive tasks such as Synchronization Manager and Server Manager. High CPU consumption alone does not indicate that the Siebel server is overloaded. The server is designed to use all the CPU resources that it has available no matter the number of running tasks or object manager sessions. However, excessively high memory utilization by the Siebel server can cause the Siebel server to crash or limit the number of users who can be serviced by the object managers assigned to the Siebel server. Use the Sieb_Srvr_ Utilization_Overview graph to determine if the Siebel server is overloaded by correlating the average response time with the number of tasks or object manager sessions the Siebel server is running. To open the Sieb_Srvr_Utilization_Overview graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Srvr_Utilization_Overview graph icon. 33

132 Foglight Cartridge for Siebel Is the average response time acceptable? Does it stay within the acceptable range as the number of tasks and object manager sessions increase? As long as the average response time remains acceptable, the Siebel server is not overloaded. It becomes overloaded when its ability to service the running tasks and object manager sessions with an acceptable average response time starts to decline. A sustained decline in the average response time signals an overloaded Siebel server. To continue your investigation Drill down to the Sieb_Proc_Utilization graph to analyze the resource utilization for the individual OS process that comprises the Siebel server. Drill down to the Sieb_Srvr_Detail graph to analyze the Siebel server response time, resource utilization, and throughput since the last collection. Drill down to the Sieb_Comp_Tasks graph to analyze the number of running tasks, max tasks, running MTServers and max MTServers for each enabled component. Use the View Editor to create a Sieb_Enterprise_Utilization_Overview graph detailing the load of all the Siebel servers in the enterprise. The Siebel Administrator can use this graph to analyze whether the throughput for the Siebel enterprise is balanced across all the servers in the enterprise. 34

133 Sieb_Comp_Availability Graph The Foglight SiebelServer agent calculates the availability of the individual Siebel components as follows: If ComponentAlias = TxnRoute or TxnMerge or TxnProc and ComponentState = Running ComponentStateAvailability = 100%. For all other components, Availability = 100% if ComponentState = Online or Running. 0% for all other values. The Siebel Remote components, Transaction Router, Transaction Merger, and Transaction Processor s availability is calculated at 100% because these three components must be running at all times to ensure a continuous synchronization process. Use the Sieb_Comp_Availability graph to view the availability percentage of each enabled Siebel component group assigned to the Siebel server. To open the Sieb_Comp_Availability graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Comp_Availability graph icon. The Time Range menu option for the Sieb_Comp_Availability graph can be used to show the Siebel server availability statistics for the last 24 hours, last week, last month, etc. 35

134 Foglight Cartridge for Siebel If the Siebel Administrator determines a Siebel component is not expected to be unavailable, Siebel Server Manager should be used to restart the component. If the component does not restart as expected, the Component task logs can be used to diagnose why the Siebel component is not starting. Contact Siebel Support if restarting the Siebel component does not restore the component to 100% availability. To continue your investigation Use the View Editor to create a Sieb_Enterprise Comp_Availability graph detailing the availability of all the Siebel servers in the enterprise. The Siebel Administrator can use this graph to analyze whether the throughput for the Siebel enterprise is balanced across all the servers in the enterprise. Sieb_Comp_Detail Graph When a Siebel task completes its operation, task level statistics that are gathered dynamically during the operation of a task roll up to the Siebel component level. These statistics can be used to monitor the progress and performance of each enabled Siebel component. Siebel stores component statistics as cumulative statistics (i.e., since the Siebel server started). The Foglight SiebelServer agent calculates Siebel component statistic deltas by determining the change in the individual cumulative statistic since the last collection and stores the delta values in the Foglight repository. This allows the Siebel Administrator to analyze how the enabled Siebel components performed over time and identify peak usage time periods. Use the Sieb_Comp_Detail graph to correlate each enabled Siebel component s utilization and throughput for each refresh interval, along with the following statistics: Total CPU time, in seconds, for all the component s tasks since the last collection. Total time, in seconds, that the Siebel component spent performing SQL execute operations since the last collection. For SELECT statements, the amount of time spent identifying the rows if the statement requires a sort or uses FOR UPDATE. For INSERT, UPDATE, and DELETE statements, the amount of time spent modifying the data. Total number of Siebel tasks started since the last collection. To open the Sieb_Comp_Detail graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 36

135 2. Double-click the Sieb_Comp_Detail graph icon. The Time Range menu option in conjunction with the View/Constraints menu option can be used to show a Siebel component(s) utilization and throughput statistics for the last 24 hours, last week, last month, etc. This is useful in analyzing how the Siebel component(s) performs over time and identifying peak usage time periods. When the Siebel Administrator has identified a peak usage time period for the Siebel server, use this graph to identify which Siebel components are contributing the most to server utilization by identifying the Siebel components with the highest CPU and SQL execute times during the peak time period. When the Siebel Administrator has identified the Siebel components that have consumed the most resources or produced the most throughput since startup with the Sieb_Comp_Statistics graph, use the Sieb_Comp_Detail graph to determine if Siebel component contribution occurred at one time period or as a recurring trend. Siebel components that contribute to the server s resource utilization on a reoccurring basis should be examined more closely to determine the root cause. Then you should take corrective measures because the Siebel component will continue to contribute to the Siebel server s poor performance. If a batch component is found to be running simultaneously with a high number of interactive tasks such as object managers, the Siebel Administrator should consider running the batch component during a time period when a smaller number of interactive tasks are running. Another alternative is to move the batch component to a Siebel server dedicated to batch components or a less utilized Siebel server. 37

136 Foglight Cartridge for Siebel To continue your investigation Drill down to the Sieb_Comp_SQLTime graph to analyze the SQL execute, SQL parse, and SQL fetch times for a particular Siebel component. Drill down to the Sieb_Task_Detail table view to identify the Siebel tasks that are currently running for batch and background Siebel components. Sieb_Comp_Group_Availability Graph The Foglight SiebelServer agent calculates the availability of the Siebel component group as follows: 100% if the ComponentGroupState = Online or Running 0% for all other values Use the Sieb_Comp_Group_Availability graph to view the availability percentage of each enabled Siebel component group assigned to the Siebel server. To open the Sieb_Comp_Group_Availability graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Comp_Group_Availability graph icon. The Time Range menu option for the Sieb_Comp_Group_Availability graph can be used to show the Siebel server availability statistics for the last 24 hours, last week, last month, etc. 38

137 If the Siebel Administrator determines a Siebel component group is experiencing an unscheduled outage, the Siebel Server Manager should be used to startup the component group. To continue your investigation If a component group availability issue is identified, drill down to the Sieb_Comp_Availability graph to view the individual Siebel component availability for the particular Siebel component group. Use the View Editor to create a Sieb_Enterprise_Comp_Group_Availability graph detailing the availability of all the Siebel component groups in the enterprise. Sieb_Comp_SQLExecute_Detail Graph When a Siebel task completes its operation, task-level statistics that are gathered dynamically during the operation of a task roll up to the Siebel component level. Among the many statistics that are gathered and rolled up to the Siebel component level are statistics on the total time that the Siebel component has spent executing SQL, the average time it has spent executing and the number of execute operations. The Foglight SiebelServer agent collects delta SQL execute time, average SQL execute time and the number of SQL executions for each enabled Siebel component. Foglight calculates the deltas by determining the change in the individual cumulative statistic since the last collection and stores the delta value in the Foglight repository. This allows the Siebel Administrator to identify peak SQL execute time periods for each Siebel component. This graph correlates the following SQL statistics for each refresh interval: The number of seconds since the last collection spent identifying the rows if the statement requires a sort or uses FOR UPDATE. For INSERT, UPDATE, and DELETE statements, the amount of time spent modifying the data since the last collection. Average number of seconds since the last collection spent identifying the rows if the statement requires a sort or uses FOR UPDATE. For INSERT, UPDATE, and DELETE statements, the amount of time spent modifying the data since the last collection. Number of executes since the last collection. When the Siebel Administrator has identified a peak SQL execute time period, use this graph to determine if a small number of operations contributed to the total SQL execute time. If the number of operations is low compared to the total amount of time spent executing versus a high number of operations contributing 39

138 Foglight Cartridge for Siebel to the same execute time, this indicates that the database is spending more time identifying the rows for SELECT statements that require a sort or use FOR UPDATE or performing INSERT, UPDATE, and DELETEs. The amount of time it takes to update the Siebel database is impacted by the number of indexes that must be updated every time a record is inserted, updated, or deleted because all the indexes for the table must also be updated. Siebel Systems does not support the removal of indexes that are created during installation without guidance from Siebel Support or Siebel Expert Services. However, if the Siebel Administrator has created additional indexes to increase SELECT performance, the SQL execute time may be negatively impacted. Monitoring the SQL execute statistics after the addition of any indexes will help the Siebel Administrator determine if the additional indexes are having an unacceptable negative impact on the SQL execute times,( i.e., time to perform modifications to the data). To open the Sieb_Comp_SQLExecute_Detail graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Comp_SQLExecute_Detail graph icon. 40

139 Sieb_Comp_SQLFetch_Detail Graph When a Siebel task completes its operation, task-level statistics that are gathered dynamically during the operation of a task roll up to the Siebel component level. Among the many statistics that are gathered and rolled up to the Siebel component level are statistics on the total time that the Siebel component has spent fetching SQL, the average time it has spent fetching and the number of fetch operations. The Foglight SiebelServer agent collects delta SQL fetch time, average SQL fetch time and the number of SQL fetches for each enabled Siebel component. Foglight calculates the deltas by determining the change in the individual cumulative statistic since the last collection and stores the delta value in the Foglight repository. This allows the Siebel Administrator to identify peak SQL fetch time periods for each Siebel component. The Siebel Component SQL Fetch Detail graph correlates the following SQL statistics for each refresh interval: For SELECT statements only, the number of seconds since the last collection spent retrieving the rows returned by the query. For SELECT statements only, the average number of seconds since the last collection spent retrieving the rows returned by the query. Number of fetch operations since the last collection. When the Siebel Administrator has identified a peak SQL fetch time period, use this graph to determine if a small number of operations contributed to the total SQL fetch time. If the number of operations is low compared to the total amount of time spent fetching, this indicates the Siebel component is issuing a number of large queries that return a large number of rows such as in list applets. If the Siebel component is an object manager, the Siebel Administrator should verify that the object manager's applets are configured with the optimal join specifications and indexes. The Siebel Administrator can use the Foglight Oracle/SQL Server/DB2 agent or Quest SQLab Vision to identify the most resource intensive SQL Statements and use Quest Central for Oracle or DB2 to identify the join specification being used and prospect columns for new indexes. If the Siebel Administrator identifies a high number of operations contributing to the fetch time, this indicates that the Siebel component is performing a number of small queries that return a small number of rows such as in detail applets. Since there are a larger number of SQL statements being issued, a low SQL parse time for the same time period will indicate that the statements are being reused in the database cache. 41

140 Foglight Cartridge for Siebel To open the Sieb_Comp_SQLFetch_Detail graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Comp_SQLFetch_Detail graph icon. Sieb_Comp_SQLParse_Detail Graph When a Siebel task completes its operation, task level statistics gathered dynamically during the operation of a task roll up to the Siebel component level. These statistics include the total time that the Siebel component has spent parsing SQL, the average time it has spent parsing and the number of parse operations. The Foglight SiebelServer agent collects delta SQL parse time, average SQL parse time and the number of SQL parses for each enabled Siebel component. Foglight calculates the deltas by determining the change in the individual cumulative statistic since the last collection and stores the delta value in the Foglight repository. This allows the Siebel Administrator to identify peak SQL parse time periods for each Siebel component. This graph correlates the following SQL statistics for each refresh interval: 42 The number of seconds since the last collection spent translating the SQL statements into an execution plan. This time includes checking for proper security authorization and checks for the existence of tables, columns, and other referenced objects. Average number of seconds since the last collection spent translating the SQL statements into an execution plan. This time includes

141 checking for proper security authorization and checks for the existence of tables, columns, and other referenced objects. Number of parse operations since the last collection. When the Siebel Administrator has identified a peak SQL parse time period, use the Sieb_Comp_SQLParse_Detail graph to determine if a small number of operations contributed to the total SQL parse time. If the number of operations is low compared to the total amount of time spent parsing versus a high number of operations contributing to the same parsing time, this indicates that the database is not reusing SQL statements in the database cache but re-parsing them, thus increasing the total elapsed time for the SQL statement. Since Siebel dynamically generates SQL statements and makes use of bind variables, the Siebel Administrator is limited in being able to positively affect the SQL parse time. However, if the Siebel database is Oracle, there are two initialization parameters that can be adjusted to decrease the SQL parse time: SESSION_CACHED_CURSORS. Set this Oracle parameter to a value between 20 and 50. This causes Oracle to remember previously parsed SQL and, if the user session requests a parse of a SQL statement in the cache, then Oracle will avoid the parse. CURSOR_SHARING. Set this Oracle parameter to FORCE. This causes Oracle to substitute literals in SQL statements with bind variables, allowing otherwise unique SQL to be reused. To open the Sieb_Comp_SQLParse_Detail graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Comp_SQLParse_Detail graph icon. 43

142 Foglight Cartridge for Siebel Sieb_Comp_SQLTime Graph When a Siebel task completes its operation, task level statistics gathered dynamically during the operation of a task roll up to the component level. Among the many statistics gathered and rolled up to the Siebel component level are statistics on the time that the Siebel component spent parsing, executing, and fetching SQL statements. Siebel server statistics are cumulative (i.e., since the Siebel server started). The Foglight SiebelServer agent collects delta SQL parse, execute, and fetch statistics for each enabled Siebel component. Foglight calculates the deltas by determining the change in the individual cumulative statistic since the last collection and stores the delta value in the Foglight repository. This allows the Siebel Administrator to identify peak SQL usage time periods for each Siebel component. This graph correlates the following SQL component statistics for each refresh interval: The number of seconds spent translating the SQL statements into an execution plan since the last collection. This time includes checking for proper security authorization and checks for the existence of tables, columns, and other referenced objects. For SELECT statements, the amount of time spent since the last collection identifying the rows if the statement requires a sort or uses 44

143 FOR UPDATE. For INSERT, UPDATE, and DELETE statements, the amount of time spent modifying the data since the last collection. For SELECT statements only, the amount of time since the last collection spent retrieving the rows returned by the query. To open the Sieb_Comp_SQLTime graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Comp_SQLTime graph icon. The Time Range menu option in conjunction with the View/Constraints menu option can be used to show a Siebel component(s) SQL parse, execute, and fetch times for the last 24 hours, last week, last month, etc. This is useful in analyzing how the Siebel component(s) perform over time and identifying peak usage time periods. SQL parse time should be low, indicating a well-designed component that is parsing the SQL statement once but executing it multiple times. High SQL execute time in relation to a low SQL fetch time indicates that the component is spending more time performing INSERT, UPDATE, and DELETE statements than SELECT statements. Low SQL execute time in relation to a high SQL fetch time indicates that the component is spending more time performing SELECT statements than INSERT, UPDATE and DELETE statements. 45

144 Foglight Cartridge for Siebel Is the Siebel component s contribution to the Siebel server s SQL Time at one time period or as a reoccurring trend? Siebel components that contribute to the server s SQL Time on a reoccurring basis should be examined more closely to ensure the component is optimally configured. To continue your investigation Drill down on the SQL Parse Time bar to analyze the SQL parse time, average SQL parse time, and number of SQL parses for a particular Siebel component during the same time range in the Sieb_Comp_SQLParse_Detail graph. Drill down on the SQL Execute Time bar to analyze the SQL execute time, average SQL execute time and the number of SQL executes for a particular Siebel component during the same time range in the Sieb_Comp_SQLExecute_Detail graph. Drill down on the SQL Fetch Time bar to analyze the SQL fetch time, average SQL fetch time and the number of SQL fetches for a particular Siebel component during the same time range in the Sieb_Comp_SQLFetch_Detail graph. Use the View Editor to create a Sieb_Enterprise_SQLTime graph detailing the interval based SQL performance of all the Siebel servers in the enterprise. Sieb_Comp_Statistics Graph When a Siebel task completes its operation, task-level statistics that are gathered dynamically during the operation of a task roll up to the Siebel component level. These statistics can be used to monitor the progress and performance of each enabled Siebel component. Siebel stores component statistics as cumulative statistics, i.e., since the Siebel server started. The Foglight SiebelServer agent collects both cumulative and delta Siebel component statistics. Foglight calculates Siebel component statistic deltas by determining the change in the individual statistic since the last collection and stores the delta values in the Foglight repository along with the cumulative value for selected statistics. Use the Sieb_Comp_Statistics graph to analyze the amount of throughput and resource consumption that each enabled Siebel component has contributed to the Siebel server s total throughput and resource consumption since startup. The Sieb_Comp_Statistics graph correlates the following statistics for each enabled Siebel component: 46

145 Total CPU time (seconds) for all the component s tasks since the Siebel server started Total time (seconds) the Siebel component spent performing SQL execute operations since the Siebel server started. For SELECT statements, the amount of time spent identifying the rows if the statement requires a sort or uses FOR UPDATE. For INSERT, UPDATE, and DELETE statements, the amount of time spent modifying the data Total number of Siebel tasks started since the Siebel server started To open the Sieb_Comp_Statistics graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Comp_Statistics graph icon. To continue your investigation Drill down to the Sieb_Comp_Detail graph to analyze the Siebel component throughput and resource utilization since the last collection. Use the View Editor to create a Sieb_Enterprise_Comp_Statistics graph detailing the progress of all Siebel components in the enterprise. The Siebel Administrator can use this graph to analyze throughput and resource consumption for all enabled Siebel components across the enterprise. 47

146 Foglight Cartridge for Siebel Sieb_Comp_Tasks Graph Each Siebel component has a maximum task parameter that represents the maximum number of tasks and users that can run concurrently. The Siebel server supports both multi-process and multi-threaded components, and can operate components in background, batch, and interactive modes. Multi-process components have one OS process for each of the Siebel component s corresponding running tasks. By default, all background mode Siebel components are multi-process. Multi-threaded components, such as Siebel object managers (SOM) have multi-threaded OS processes where tasks and client sessions run as threads within the individual OS process. Each multi-threaded OS process is called an MTServer. For batch and interactive mode Siebel components that have multi-threading enabled, the Maximum MT Servers parameter represents the maximum number of multi-threaded server processes that can run concurrently. The number of tasks that can run in each server process is determined by the value of the Maximum Tasks parameter divided by Max MTServers. The Foglight SiebelServer Agent collects the task and MTServer statistics for each enabled Siebel component. Use the Siebel Component Tasks graph to correlate the following statistics for each enabled Siebel component: Current number of running tasks. Maximum number of tasks defined for the component. Current number of MTServers. Maximum number of MTServers defined for the component. To open the Sieb_Comp_Tasks graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Comp_Tasks graph icon. 48

147 Use the Time Range menu option for the Sieb_Comp_Tasks graph to show the task and MTServer values over time. This is useful in determining trends for the number of tasks/mtservers each enabled Siebel component is running. Siebel Support Web provides many resources detailing how to optimally set these parameters including: FAQ 1380: How to set Max Tasks and Max MTS Server parameters for the Siebel Object Manager. To continue your investigation Drill down to the Sieb_Task_Detail table to identify the Siebel tasks that are currently running for batch and background Siebel components. Drill down on the Max Tasks, Running MTS, or Max MTS bar to isolate the analysis to an individual Siebel component. 49

148 Foglight Cartridge for Siebel Sieb_Proc_Memory_Detail Graph If the Siebel Administrator suspects that a Siebel server is overloaded, an analysis of each OS process that comprises the Siebel server should be performed. The Foglight SiebelServer agent calculates CPU and memory utilization statistics for each OS process that comprises the Siebel server. For Siebel 7 enterprises, this agent is able to correlate the siebmtsh executables that run multi-threaded processes or MTServers with the corresponding Siebel component. There is one siebmtsh executable for each MTServer that is currently running. Even though the Foglight SiebelServer Agent calculates CPU and memory utilization statistics for each OS process, the agent uses the Number of Top Siebel OS Process to Monitor ASP value to determine the number of top processes to store in the Foglight repository for each collection. Foglight sorts by memory percentage when determining the top processes to store in the Foglight repository. If the Siebel Administrator identifies a Siebel server with high memory utilization or an individual Siebel server OS process is consuming a large percentage of memory, this graph can be used to correlate: VirtualSetSize for the individual Siebel OS processes (i.e., the amount of virtual memory used by the process in Kbytes). ResidentSetSize for the individual Siebel OS processes (i.e., the amount of Siebel process address space -Kbytes- currently in main memory). Main memory includes RAM plus ROM but does not include cache. If a Siebel object manager component is found to be consuming a large amount of memory resources and the number of running tasks is high, the Siebel Administrator should investigate whether the object manager s Max Tasks, Max MTServers, and RecycleFactor parameters are correctly set. Siebel Support Web provides many resources detailing how to optimally set these parameters including: FAQ 1380: How to set Max Tasks and Max MTS Server parameters for the Siebel Object Manager. Other options the Siebel Administrator should consider are distributing the object manager across multiple Siebel servers. This is done by assigning the Siebel component to one or more Siebel servers and using Resonate to perform load balancing between the Siebel servers. To open the Sieb_Proc_Memory_Detail graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Proc_Memory_Detail graph icon. 50

149 Sieb_Proc_Utilization Graph If the Siebel Administrator suspects that a Siebel server is overloaded, an analysis of each OS process that comprises the Siebel server should be performed. The Foglight SiebelServer agent calculates CPU and memory utilization statistics for each OS process that comprises the Siebel server. For Siebel 7 enterprises, this agent is able to correlate the siebmtsh executables that run multi-threaded processes or MTServers with the corresponding Siebel component. There is one siebmtsh executable for each MTServer that is currently running. Even though the Foglight SiebelServer Agent calculates CPU and memory utilization statistics for each OS process, the agent uses the Number of Top Siebel OS Process to Monitor ASP value to determine the number of top processes to store in the Foglight repository for each collection. Foglight sorts by memory percentage when determining the top processes to store in the Foglight repository. Use this graph to correlate the following: CPU consumption for the top OS processes that comprise the Siebel server. Memory consumption for the top OS processes that comprise the Siebel server. 51

150 Foglight Cartridge for Siebel If a Siebel object manager component is found to be consuming a large amount of memory resources and the number of running tasks is high, the Siebel Administrator should investigate whether the object manager s Max Tasks, Max MTServers, and RecycleFactor parameters are correctly set. The Siebel Support Web provides many resources detailing how to optimally set these parameters including: FAQ 1380: How to set Max Tasks and Max MTS Server parameters for the Siebel Object Manager. Other options the Siebel Administrator should consider are distributing the object manager across multiple Siebel servers. This is done by assigning the Siebel component to one or more Siebel servers and using Resonate to perform load balancing between the Siebel servers. If the Siebel component that is consuming a large amount of the CPU or memory resources is a batch or background component such as Assignment Manager, the Siebel Administrator should consider moving this component to a less utilized Siebel server by reassigning with Siebel Server Manager. If the Siebel component is a member of the Siebel Remote component group, the Siebel Administrator should investigate whether Siebel Remote can be tuned on this Siebel server or if one or more additional Siebel servers should be dedicated to the Siebel Remote component group. To open the Sieb_Proc_Utilization graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Proc_Utilization graph icon. 52

151 To continue your investigation Drill down on the CPU % bar to isolate the CPU analysis to an individual Siebel server OS process. Drill down on the Memory % bar to analyze the memory consumption for an individual Siebel server OS process in the Sieb_Proc_Memory_Detail graph. Sieb_Srvr_Detail Graph When a Siebel task is completed, task level statistics gathered dynamically during the operation of the task roll up to the component level. Statistics for all enabled components assigned to a Siebel server are rolled up to the server level. Siebel stores server statistics as cumulative statistics (i.e., since the Siebel server started). These statistics can be used to monitor the progress and performance of a Siebel server. The Foglight SiebelServer agent calculates Siebel server statistic deltas by determining the change in the individual cumulative statistic since the last collection and stores the delta values in the Foglight repository. This allows the Siebel Administrator to analyze how the Siebel server performs over time and identifying peak usage time periods. Use the Sieb_Srvr_Detail graph to correlate the Siebel server s response time with its utilization and throughput for each refresh interval. The Sieb_Srvr_Detail correlates the following statistics: Average object manager response time since the last collection. Total CPU time (seconds) for all the Siebel server s tasks since the last collection. Total time (seconds) the Siebel server spent performing SQL execute operations since the last collection. For SELECT statements, the amount of time spent identifying the rows if the statement requires a sort or uses FOR UPDATE. For INSERT, UPDATE, and DELETE statements, the amount of time spent modifying the data. Average size (bytes) of reply messages since the last connection. Average size (bytes) of request messages since the last collection. Number of Siebel tasks started since the last collection. To open the Sieb_Srvr_Detail graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Srvr_Detail graph icon. 53

152 Foglight Cartridge for Siebel The Time Range menu option for the Sieb_Srvr_Detail graph can be used to show the Siebel server s response time, utilization, and throughput statistics for the last 24 hours, last week, last month, etc. This is useful in analyzing how the Siebel server performs over time and identifying peak usage time periods. What time period does the Siebel server s response time become unacceptable? Is this a one time occurrence or does it occur on a regular basis? Did the number of tasks started increase as response time started to decline? If the response time declines as the Siebel server s throughput increases on a regular basis, the Siebel Administrator should investigate if this is related to increased user activity during the time period. For example, increase throughput between 8am and 9am due to users connecting to Siebel for the morning or increase throughput between 12pm and 1pm due to users reconnecting after lunch. Often these types of usage patterns cannot be avoided, but the Siebel Administrator should ensure that the Siebel components load is balanced to compensate for increased activity during those peak periods. Identifying what time of day the Siebel server has the lowest throughput provides the Siebel Administrator the knowledge of the optimal time to run batch components such as Enterprise Integration Manager (EIM) or Assignment Manager without impacting the majority of users. To continue your investigation Drill down to the Sieb_Srvr_SQLTime graph to analyze the Siebel server SQL execute, parse and fetch time during the same time range as the Sieb_Srvr_Detail graph. 54

153 Drill down to the Sieb_Comp_Detail graph to analyze the utilization and throughput for each enabled Siebel component during the same time range as the Sieb_Srvr_Detail graph. Use the View Editor to create a Sieb_Enterprise_Detail graph detailing the interval based performance of all the Siebel servers in the enterprise. Sieb_Srvr_SQLTime Graph When a Siebel task completes its operation, task-level statistics that are gathered dynamically during the operation of a task roll up to the component level. Statistics for all enabled components assigned to a Siebel server are rolled up to the Siebel server level. Siebel server statistics are cumulative statistics, i.e., since the Siebel server started. Among the many statistics that are gathered and rolled up to the Siebel server level are statistics on the time that the Siebel server has spent parsing, executing, and fetching SQL statements. Siebel Support Web provides the following definitions for SQL parse, SQL execute, and SQL fetch times: SQL Parse Time The number of seconds spent translating the SQL statements into an execution plan. This time includes checking for proper security authorization and checks for the existence of tables, columns, and other referenced objects. SQL Execute Time For SELECT statements, the amount of time spent identifying the rows if the statement requires a sort or uses FOR UPDATE. For INSERT, UPDATE, and DELETE statements, the amount of time spent modifying the data. SQL Fetch Time For SELECT statements only, the amount of time spent retrieving the rows returned by the query. The Foglight SiebelServer agent collects delta SQL parse, SQL execute, and SQL fetch statistics for the Siebel server. Foglight calculates the deltas by determining the change in the individual statistic since the last collection and stores the delta value in the Foglight repository. This allows the Siebel Administrator to identify peak SQL usage time periods. This graph correlates the following Siebel server statistics for each refresh interval: SQL parse time since the last collection. SQL execute time since the last collection. SQL fetch time since the last collection. 55

154 Foglight Cartridge for Siebel Use the Sieb_Srvr_SQLTime graph to analyze how efficiently the Siebel server is interfacing with the Siebel database. SQL parse time should be low indicating a well-designed application that is parsing the SQL statement once but executing it multiple times. Since Siebel dynamically generates SQL statements and makes use of bind variables, the Siebel Administrator is limited in being able to positively affect the SQL parse time. However, if the SQL parse time is high and the Siebel database is Oracle, there are two initialization parameters that can be adjusted to decrease the SQL parse time: SESSION_CACHED_CURSORS. Set this Oracle parameter to a value between 20 and 50. This causes Oracle to remember previously parsed SQL and if the user session requests a parse of a SQL statement in the cache, then Oracle will avoid the parse. CURSOR_SHARING. Set this Oracle parameter to FORCE. This causes Oracle to substitute literals in SQL statement with bind variables, which allows otherwise unique SQL to be reused. High SQL execute time in relation to a low SQL fetch time indicates that more time is being spent performing INSERT, UPDATE, and DELETE statements than SELECT statements. Low SQL execute time in relation to a high SQL fetch time indicates that more time is being spent performing SELECT statements than INSERT, UPDATE and DELETE statements. To open the Sieb_Srvr_SQLTime graph 1. Click the SiebelServer agent icon. A list of graph icons displays. 2. Double-click the Sieb_Srvr_SQL_Time graph icon. 56

155 To continue your investigation Drill down on any line to analyze the SQL execute, parse, and fetch to identify which Siebel components are contributing the most to the server s SQL times in the Sieb_Comp_SQLTime graph. Use the View Editor to create a Sieb_Enterprise_SQLTime graph detailing the interval based SQL performance of all the Siebel servers in the enterprise. Sieb_Task_Detail Table The Foglight SiebelServer Agent collects status data for each background and batch Siebel tasks that are currently running, and all Siebel tasks that have exited with error. Use the Siebel Task Detail table to identify the Siebel tasks that are currently running or have exited with error at a specified time period. This table displays the following data for each task: Component Alias Task ID Operating System process id (PID) that is running this task Task s run mode (i.e., Batch, Background, Interactive) Time the task was started Current run state for the Siebel task (Running, Paused, Stopping, etc.) If the Siebel Administrator identifies a peak usage time period for the Siebel server or an individual Siebel component, use this table view to identify all of the currently running background or batch tasks or tasks that have exited during that peak usage time period. If a Siebel task has exited with error, the task s log file should be examined to determine what error caused the Siebel task to exit. If a Siebel task exited with error, examine the task's log file to determine what error caused the Siebel task to exit. If multiple batch Siebel tasks are running during the peak usage time period and the Siebel Administrator has discretion on when the task is started, the Siebel Administrator should consider distributing the batch tasks across non-peak usage time periods. Another option available to the Siebel Administrator is to reassign the Siebel task s corresponding component to a less utilized Siebel server with Siebel Server Manager. 57

156 Foglight Cartridge for Siebel To open the Siebel_Task_Detail table 1. Click the SiebelServer agent icon. A list of graph and table icons displays. 2. Double-click the Sieb_Task_Detail table icon. 58

157 Sieb_Enterprise_Availability_Overview Graph The Sieb_Enterprise_Availability_Overview graph displays the availability of all the Siebel servers in the enterprise. Sieb_Enterprise_Availability_Overview View Definition Graph Type: Line Graph Dynamic View: Yes Subject Field: SiebelServerHealth.SiebelServer Header: Siebel Enterprise Availability Overview Footer: %D %H:%M:%S Y Axis Max: Time Range: Last 4 Hours Map Location: Siebel Enterprise Node in Siebel custom map FOGLIGHT TABLE FIELD LABEL AXIS DRILL-DOWN TARGET VIEW DRILL-DOWN SELECTION CRITERIA SiebelServerHealth. SiebelServerAvailability Siebel Server % Y Sieb_Srvr_Availability_ Overview SiebelServer SiebelServerHealth. DatabaseAvailability Database Connection % Y Sieb_Srvr_Availability _ Overview SiebelServer SiebelServerHealth. GatewayServer Availability Gateway Server Connection % Y Sieb_Comp_Group_ Availability Component Group 59

158 Foglight Cartridge for Siebel Sieb_Enterprise_Comp_Group_Availability Graph The Sieb_Enterprise_Comp_Group_Availability graph displays the availability of all the Siebel component groups in the enterprise. Sieb_Enterprise_Comp_Group_Availability View Definition Graph Type: Inverted Bar Dynamic View: Yes Subject Field: SiebelComponentGroups.ComponentGroup Header: Siebel Enterprise Component Group Availability Footer: %D %H:%M:%S Y Axis Max: Time Range: Last 4 Hours Map Location: Siebel Enterprise Node in Siebel custom map 60

159 FOGLIGHT TABLE FIELD LABEL AXIS DRILL-DOWN TARGET VIEW DRILL-DOWN SELECTION CRITERIA SiebelComponentGroups. ComponentGroup Availability Availability % Y Sieb_Comp_Group_ Availability Component Group 61

160 Foglight Cartridge for Siebel Sieb_Enterprise_Comp_Availability Graph The Sieb_Enterprise_Comp_Availability graph displays the availability of all the Siebel components in the enterprise. Sieb_Enterprise_Comp_Availability View Definition Graph Type: Inverted Bar Dynamic View: Yes Subject Field: SiebelComponents.ComponentAlias Header: Siebel Enterprise Component Availability Footer: %D %H:%M:%S Time Range: Last 4 Hours Map Location: Siebel Enterprise Node in Siebel custom map FOGLIGHT TABLE FIELD LABEL AXIS DRILL-DOWN TARGET VIEW DRILL-DO WN SELECTION CRITERIA SiebelComponents. ComponentStateAvailability Availability % Y Sieb_Comp_ Availability Component Alias 62

161 Sieb_Enterprise_Comp_SQLTime Graph The Sieb_Enterprise_Comp_SQLTime graph displays the interval based SQL performance of all the enabled Siebel components in the enterprise. Sieb_Enterprise_Comp_SQLTime View Definition Graph Type: Line Graph Dynamic View: Yes Subject Field: SiebelComponentStatistics.ComponentAlias Header: Siebel Enterprise Component SQL Time Started Since Last Collection 63

Siebel Installation Guide for Microsoft Windows. Siebel Innovation Pack 2015, Rev. D November 2015

Siebel Installation Guide for Microsoft Windows. Siebel Innovation Pack 2015, Rev. D November 2015 Siebel Installation Guide for Microsoft Windows Siebel Innovation Pack 2015, Rev. D November 2015 Copyright 2005, 2015 Oracle and/or its affiliates. All rights reserved. This software and related documentation

More information

Installing and Configuring Siebel CRM Server Software on Linux

Installing and Configuring Siebel CRM Server Software on Linux Installing and Configuring Siebel CRM Server Software on Linux In this chapter, we will explain the concepts of installing Siebel CRM server software on Linux and other UNIX-based operating systems using

More information

NextGen Meaningful Use Crystal Reports Guide

NextGen Meaningful Use Crystal Reports Guide NextGen Meaningful Use Crystal Reports Guide Version 5.6 SP1 NextGen Healthcare Information Systems, Inc. Copyright 1994-2011 NextGen Healthcare Information Systems, Inc. All Rights Reserved. NextGen is

More information

Siebel Smart Answer Guide. Siebel Innovation Pack 2013 Version 8.1/8.2 September 2013

Siebel Smart Answer Guide. Siebel Innovation Pack 2013 Version 8.1/8.2 September 2013 Siebel Smart Answer Guide Siebel Innovation Pack 2013 Version 8.1/8.2 September 2013 Copyright 2005, 2013 Oracle and/or its affiliates. All rights reserved. This software and related documentation are

More information

Site Manager Guide CMTS. Care Management Tracking System. University of Washington aims.uw.edu

Site Manager Guide CMTS. Care Management Tracking System. University of Washington aims.uw.edu Site Manager Guide CMTS Care Management Tracking System University of Washington aims.uw.edu rev. 8/13/2018 Table of Contents INTRODUCTION... 1 SITE MANAGER ACCOUNT ROLE... 1 ACCESSING CMTS... 2 SITE NAVIGATION

More information

Siebel Installation Guide for Microsoft Windows. Siebel Innovation Pack 2017 July 2017

Siebel Installation Guide for Microsoft Windows. Siebel Innovation Pack 2017 July 2017 Siebel Installation Guide for Microsoft Windows Siebel Innovation Pack 2017 July 2017 Copyright 2005, 2017 Oracle and/or its affiliates. All rights reserved. This software and related documentation are

More information

Psychiatric Consultant Guide SPIRIT CMTS. Care Management Tracking System. University of Washington aims.uw.edu

Psychiatric Consultant Guide SPIRIT CMTS. Care Management Tracking System. University of Washington aims.uw.edu Psychiatric Consultant Guide SPIRIT CMTS Care Management Tracking System University of Washington aims.uw.edu rev. 9/20/2016 Table of Contents TOP TIPS & TRICKS... 1 INTRODUCTION... 2 PSYCHIATRIC CONSULTANT

More information

Psychiatric Consultant Guide CMTS. Care Management Tracking System. University of Washington aims.uw.edu

Psychiatric Consultant Guide CMTS. Care Management Tracking System. University of Washington aims.uw.edu Psychiatric Consultant Guide CMTS Care Management Tracking System University of Washington aims.uw.edu rev. 8/13/2018 Table of Contents TOP TIPS & TRICKS... 1 INTRODUCTION... 2 PSYCHIATRIC CONSULTANT ACCOUNT

More information

Unplanned Admissions - Getting Started

Unplanned Admissions - Getting Started Vision 3 Unplanned Admissions - Getting Started Outcomes Manager Copyright INPS Ltd 2014 The Bread Factory, 1A Broughton Street, Battersea, London, SW8 3QJ T: +44 (0) 207 501700 F:+44 (0) 207 5017100 W:

More information

A Tivoli Field Guide Maximo for the Nuclear Power Industry Duty Stations (Nuc) Release 7.51

A Tivoli Field Guide Maximo for the Nuclear Power Industry Duty Stations (Nuc) Release 7.51 A Tivoli Field Guide Maximo for the Nuclear Power Industry Duty Stations (Nuc) Release 7.51 By Jean Bellefeuille Version 1.0 Copyright Notice Copyright IBM Corporation 2009. All rights reserved. May only

More information

Quick-Start Guide. Creating a Grant FOR PLAN ADMINISTRATORS. Last Updated: 2/13/15

Quick-Start Guide. Creating a Grant FOR PLAN ADMINISTRATORS. Last Updated: 2/13/15 Quick-Start Guide Creating a Grant FOR PLAN ADMINISTRATORS Last Updated: 2/13/15 This quick start guide is intended as a fingertip reference for adding a new grant into the Shareworks application. Please

More information

Oracle. Human Capital Management Cloud Using Volunteering. Release 13 (update 18A)

Oracle. Human Capital Management Cloud Using Volunteering. Release 13 (update 18A) Oracle Human Capital Management Cloud Release 13 (update 18A) Release 13 (update 18A) Part Number E92269-02 Copyright 2011-2018, Oracle and/or its affiliates. All rights reserved. Author: Lakshmi VR This

More information

Oracle. Project Portfolio Management Cloud Using Grants Management. Release 13 (update 17D) This guide also applies to on-premises implementations

Oracle. Project Portfolio Management Cloud Using Grants Management. Release 13 (update 17D) This guide also applies to on-premises implementations Oracle Project Portfolio Management Cloud Release 13 (update 17D) This guide also applies to on-premises implementations Release 13 (update 17D) Part Number E89309-01 Copyright 2011-2017, Oracle and/or

More information

Meaningful Use Hello Health v7 Guide for Eligible Professionals. Stage 2

Meaningful Use Hello Health v7 Guide for Eligible Professionals. Stage 2 Meaningful Use Hello Health v7 Guide for Eligible Professionals Stage 2 Table of Contents Introduction 3 Meaningful Use 3 Terminology 4 Computerized Provider Order Entry (CPOE) for Medication, Laboratory

More information

Banner Finance Research Accounting Training Workbook

Banner Finance Research Accounting Training Workbook Banner Finance Research Accounting Training Workbook January 2007 Release 7.3 HIGHER EDUCATION What can we help you achieve? Confidential Business Information -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

More information

Meaningful Use Hello Health v7 Guide for Eligible Professionals. Stage 1

Meaningful Use Hello Health v7 Guide for Eligible Professionals. Stage 1 Meaningful Use Hello Health v7 Guide for Eligible Professionals Stage 1 Table of Contents Introduction 3 Meaningful Use 3 Terminology 5 Computerized Provider Order Entry (CPOE) for Medication Orders [Core]

More information

DEP Documentation RSA Key Import In Keytable User Manual

DEP Documentation RSA Key Import In Keytable User Manual Haachtsesteenweg 1442 1130 Brussels Belgium DEP Documentation RSA Key Import In Keytable User Manual Version: 04.00 Atos Worldline - Technology & Products / Engineering / DEP Page: 2/16 Version Management

More information

Our Terms of Use and other areas of our Sites provide guidelines ("Guidelines") and rules and regulations ("Rules") in connection with OUEBB.

Our Terms of Use and other areas of our Sites provide guidelines (Guidelines) and rules and regulations (Rules) in connection with OUEBB. OUE Beauty Bar - Terms of Use These are the terms of use ("Terms of Use") governing the purchase of products in the vending machine(s) installed by Alkas Realty Pte Ltd at OUE Downtown Gallery, known as

More information

MONITORING PATIENTS. Responding to Readings

MONITORING PATIENTS. Responding to Readings CHAPTER 6 MONITORING PATIENTS Responding to Readings This section covers the steps required to respond to patient readings within LifeStream. You can view patient readings on the Current Status or Tabular

More information

Quick Reference. Virtual OneStop (VOS) Individual User Logging In. My Workspace* (My Dashboard ) Settings and Themes. Quick Menu*

Quick Reference. Virtual OneStop (VOS) Individual User Logging In. My Workspace* (My Dashboard ) Settings and Themes. Quick Menu* Virtual OneStop (VOS) Individual User Logging In If you don t have an account: Click the link Not Registered? on the Home page, near the Sign In button, (name may vary, but will include Register in the

More information

TranSync Compliance Monitoring Manual. Homecare Provider/Authorized Monitors

TranSync Compliance Monitoring Manual. Homecare Provider/Authorized Monitors TranSync Compliance Monitoring Manual Homecare Provider/Authorized Monitors Page ii Notices Revised Notice Trademark Copyright for Homecare Providers/Authorized Monitors 103516 Rev A Published March 21,

More information

Soarian Clinicals View Only

Soarian Clinicals View Only Soarian Clinicals View Only Participant Guide Table of Contents 1. Welcome!... 5 Course Description... 5 Learning Objectives... 5 What to Expect... 5 Evaluation... 5 Agenda... 5 2. Getting Started... 6

More information

VMware AirWatch Guide for the Apple Device Enrollment Program (DEP) Using Apple's DEP to automatically enroll new devices with AirWatch MDM

VMware AirWatch Guide for the Apple Device Enrollment Program (DEP) Using Apple's DEP to automatically enroll new devices with AirWatch MDM VMware AirWatch Guide for the Apple Device Enrollment Program (DEP) Using Apple's DEP to automatically enroll new devices with AirWatch MDM AirWatch v9.3 Have documentation feedback? Submit a Documentation

More information

VMware AirWatch Guide for the Apple Device Enrollment Program (DEP) Using Apple's DEP to automatically enroll new devices with AirWatch MDM

VMware AirWatch Guide for the Apple Device Enrollment Program (DEP) Using Apple's DEP to automatically enroll new devices with AirWatch MDM VMware AirWatch Guide for the Apple Device Enrollment Program (DEP) Using Apple's DEP to automatically enroll new devices with AirWatch MDM AirWatch v9.2 Have documentation feedback? Submit a Documentation

More information

User Guide on Jobs Bank Portal (Employers)

User Guide on Jobs Bank Portal (Employers) User Guide on Jobs Bank Portal (Employers) Table of Contents 1 INTRODUCTION... 4 2 Employer Dashboard... 5 2.1 Logging In... 5 2.2 First Time Registration... 7 2.2.1 Organisation Information Registration...

More information

Downloading Application Viewer

Downloading Application Viewer Downloading Application Viewer In order to access, complete and submit applications, you will need to download and install the PureEdge Viewer, a small, free program. PureEdge Viewer: Minimum System Requirements

More information

User Guide on Jobs Bank (Individuals)

User Guide on Jobs Bank (Individuals) User Guide on Jobs Bank (Individuals) Table of Contents 1 Individual Dashboard... 3 1.1 Logging In... 3 1.2 Logging Out... 5 2 Profile... 6 2.1 Make Selected Profile Information Not Viewable To All Employers...

More information

Outsourcer Billing User s Guide

Outsourcer Billing User s Guide Titlepage Outsourcer Billing User s Guide Document 9033597-02 Application & Gateway Copyright Notice Document 90335987-02. Copyright November 2001 by Aprisma Management Technologies, Inc. All rights reserved

More information

CLINICIAN MANUAL. LATITUDE Patient Management System

CLINICIAN MANUAL. LATITUDE Patient Management System CLINICIAN MANUAL LATITUDE Patient Management System Table of Contents LATITUDE PATIENT MANAGEMENT INTRODUCTION........................... 1 Intended Use..........................................................

More information

14: Manage Labor Exchange

14: Manage Labor Exchange 14: Manage Labor Exchange Chapter Contents Mass Job Referrals... 14-2 Assigning Referrals to Job Orders... 14-3 Finding a Candidate for the Job Order Referrals... 14-4 Referral/Notifications Details Screen...

More information

eprint MOBILE DRIVER User Guide

eprint MOBILE DRIVER User Guide eprint MOBILE DRIVER User Guide eprint Mobile Driver User Guide Copyright and License 2011 Copyright Hewlett-Packard Development Company, L.P. Reproduction, adaptation, or translation without prior written

More information

Preventative Care (Patient Reminders) Stage 2 Core Measure - 12 of 17

Preventative Care (Patient Reminders) Stage 2 Core Measure - 12 of 17 Preventative Care (Patient Reminders) Stage 2 Core Measure - 12 of 17 Objective: Use clinically relevant information to identify patients who should receive reminders for preventive/followup care and send

More information

Meaningful Use Roadmap

Meaningful Use Roadmap Meaningful Use Roadmap Copyright SOAPware, Inc. 2011 1 Introduction 1.1 2 3 Introduction 6 Registration and Attestation 2.1 1. Request the "CMS EHR Certification ID" for SOAPware 9 2.2 2. Register for

More information

Site Install Guide. Hardware Installation and Configuration

Site Install Guide. Hardware Installation and Configuration Site Install Guide Hardware Installation and Configuration The information in this document is subject to change without notice and does not represent a commitment on the part of Horizon. The software

More information

Notre Dame College Website Terms of Use

Notre Dame College Website Terms of Use Notre Dame College Website Terms of Use Agreement to Terms of Use These Terms and Conditions of Use (the Terms of Use ) apply to the Notre Dame College web site located at www.notre-dame-college.edu.hk,

More information

Downtime Viewer User Guide for All Users

Downtime Viewer User Guide for All Users Downtime Viewer User Guide for All Users Overview... 1 Logging into Downtime Viewer... 1 Opening a Patient Chart in Downtime Viewer... 2 Patient Lists... 2 Clinics... 4 Navigating in the Patient s Chart...

More information

EFIS. (Education Finance Information System) Training Guide and User s Guide

EFIS. (Education Finance Information System) Training Guide and User s Guide EFIS (Education Finance Information System) Training Guide and User s Guide January 2011 About this Guide This guide explains the basics of using the Education Finance Information System (EFIS). The intended

More information

Sentinel LDK. Migration Guide HASP HL to Sentinel LDK

Sentinel LDK. Migration Guide HASP HL to Sentinel LDK Sentinel LDK Migration Guide HASP HL to Sentinel LDK All information herein is either public information or is the property of and owned solely by Gemalto NV. and/or its subsidiaries who shall have and

More information

Proposal Gifts Guide

Proposal Gifts Guide Proposal Gifts Guide 021312 2008 Blackbaud, Inc. This publication, or any part thereof, may not be reproduced or transmitted in any form or by any means, electronic, or mechanical, including photocopying,

More information

DEVICE INTEGRATION GUIDE FOR SIEBEL FINANCIAL SERVICES TELLER

DEVICE INTEGRATION GUIDE FOR SIEBEL FINANCIAL SERVICES TELLER DEVICE INTEGRATION GUIDE FOR SIEBEL FINANCIAL SERVICES TELLER VERSION 7.0, REV. H 12-BCK97Z AUGUST 2002 Siebel Systems, Inc., 2207 Bridgepointe Parkway, San Mateo, CA 94404 Copyright 2002 Siebel Systems,

More information

Mobile App Process Guide

Mobile App Process Guide Mobile App Process Guide Agency Setup and Management Copyright 2018 Homecare Software Solutions, LLC One Court Square 44th Floor Long Island City, NY 11101 Phone: (718) 407-4633 Fax: (718) 679-9273 Document

More information

19: Manage Labor Exchange

19: Manage Labor Exchange 19: Manage Labor Exchange Chapter Contents Mass Job Referrals... 19-2 Assigning Referrals to Job Orders... 19-3 Finding a Candidate for the Job Order Referrals... 19-3 Referral/Notifications Details Screen...

More information

Grants Application Completion Report Instructions. Table of Contents

Grants Application Completion Report Instructions. Table of Contents Grants Application Completion Report Instructions Table of Contents Overview... 1 Step 1 - Logging into Grants Application Completion Report Portal... 1 Step 2 Loading a New Budget... 2 Step 3 Processing

More information

System Performance Measures:

System Performance Measures: April 2017 Version 2.0 System Performance Measures: FY 2016 (10/1/2015-9/30/2016) Data Submission Guidance CONTENTS 1. Purpose of this Guidance... 3 2. The HUD Homelessness Data Exchange (HDX)... 5 Create

More information

Moving from HASP HL to Sentinel LDK Migration Guide

Moving from HASP HL to Sentinel LDK Migration Guide Moving from HASP HL to Sentinel LDK Migration Guide Migration Guide: HASP HL to Sentinel LDK Copyrights and Trademarks Copyright 2013 SafeNet, Inc. All rights reserved. HARDLOCK, HASP, SENTINEL, SUPERPRO

More information

INTERGY MEANINGFUL USE 2014 STAGE 1 USER GUIDE Spring 2014

INTERGY MEANINGFUL USE 2014 STAGE 1 USER GUIDE Spring 2014 INTERGY MEANINGFUL USE 2014 STAGE 1 USER GUIDE Spring 2014 Intergy Meaningful Use 2014 User Guide 2 Copyright 2014 Greenway Health, LLC. All rights reserved. This document and the information it contains

More information

Effort Coordinator Training. University of Kansas Summer 2016

Effort Coordinator Training. University of Kansas Summer 2016 Effort Coordinator Training University of Kansas Summer 2016 Agenda 1. Effort Reporting Overview 2. Effort Workflow and Basic Information 3. Effort Coordinator: Pre-Review 4. PI/Self-Certifier: Certification

More information

InterQual Review Manager Guide to Conducting Reviews. McK. Change Healthcare LLC Product Support

InterQual Review Manager Guide to Conducting Reviews. McK. Change Healthcare LLC  Product Support InterQual Review Manager 17.0 Guide to Conducting Reviews McK Change Healthcare LLC www.changehealthcare.com Product Support 800.274.8374 General Terms: Change Healthcare LLC and/or one of its subsidiaries

More information

Placing a Contrast Order in PowerChart. 1 From the Online Worklist, highlight the appropriate patient, and click the PowerChart button.

Placing a Contrast Order in PowerChart. 1 From the Online Worklist, highlight the appropriate patient, and click the PowerChart button. Radiology: RadTech Contrast Processes Placing a Contrast Order in PowerChart... 1 BCMA Process... 6 Documenting Contrast Administration on the MAR... 7 Chart a Medication as Not Done... 9 Voiding a Contrast

More information

ONESOURCE FRINGE BENEFITS TAX ONESOURCE FBT INSTALLATION GUIDE 2017 STAND-ALONE INSTALLATION AND UPGRADE GUIDE. Thomson Reuters ONESOURCE Support

ONESOURCE FRINGE BENEFITS TAX ONESOURCE FBT INSTALLATION GUIDE 2017 STAND-ALONE INSTALLATION AND UPGRADE GUIDE. Thomson Reuters ONESOURCE Support ONESOURCE FRINGE BENEFITS TAX ONESOURCE FBT INSTALLATION GUIDE 2017 STAND-ALONE INSTALLATION AND UPGRADE GUIDE Thomson Reuters ONESOURCE Support Date of issue: 03 Feb 2017 Getting started: Decision tree

More information

Find & Apply. User Guide

Find & Apply. User Guide Find & Apply User Guide Version 2.0 Prepared April 9, 2008 Grants.gov Find and Apply User Guide Table of Contents Introduction....3 Find Grant Opportunities...4 Search Grant Opportunities...5 Email Subscription...8

More information

Software Requirements Specification

Software Requirements Specification Software Requirements Specification Co-op Evaluation System Senior Project 2014-2015 Team Members: Tyler Geery Maddison Hickson Casey Klimkowsky Emma Nelson Faculty Coach: Samuel Malachowsky Project Sponsors:

More information

Trigger / Timing / Frequency: When a new award is received by the University and OSP determines that the award can be accepted.

Trigger / Timing / Frequency: When a new award is received by the University and OSP determines that the award can be accepted. Kuali Research User Guide: Create a New Parent Award Version October 06 Purpose: To create a new parent award record in the system. Trigger / Timing / Frequency: When a new award is received by the University

More information

Certification of Employee Time and Effort

Certification of Employee Time and Effort Procedure: Policy: Number: Completing a Personnel Activity Report (PAR) Certification of Employee Time and Effort GP1200.3 ( ) Complete Revision Supersedes: Page: ( ) Partial Revision Page 1 of 21 ( X

More information

Building Plan Approval System

Building Plan Approval System Building Plan Approval System Citizen Copyrights reserved with EGovernments Foundation 2018 Page 1 Copyright egov Building Plan Approval User Manual March 2017 Copyright 2017 egovernments Foundation. All

More information

Working with Parameter Effectivity

Working with Parameter Effectivity Working with Parameter Effectivity HELP.LOECH Release 4.6C SAP AG Copyright Copyright 2001 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any

More information

RETRIEVAL AND CRITICAL HEALTH INFORMATION SYSTEM

RETRIEVAL AND CRITICAL HEALTH INFORMATION SYSTEM RETRIEVAL AND CRITICAL HEALTH INFORMATION SYSTEM USER GUIDE November 2014 Contents Introduction... 4 Access to REACH... 4 Homepage... 4 Roles within REACH... 5 Hospital Administrator... 5 Hospital User...

More information

Peoplesoft Effort Certification. Participant s Manual

Peoplesoft Effort Certification. Participant s Manual Peoplesoft Effort Certification Participant s Manual Version 1.3.7 Revised April, 2007 TABLE OF CONTENTS COURSE OVERVIEW... 3 INTRODUCTION... 4 LEARNING OBJECTIVES... 4 MODULE 1: WHY COMPLETE EFFORT REPORTS...

More information

Research Administration & Proposal Submission System (RAPSS) Central Office Quick Reference

Research Administration & Proposal Submission System (RAPSS) Central Office Quick Reference Research Administration & Proposal Submission System (RAPSS) Central This document is intended for Grants Specialists and Authorized Organization Representatives. Software Overview and Basic Navigation...

More information

Medical Manager v12 includes the following features and functionalities to assist you with your ICD-10 transition:

Medical Manager v12 includes the following features and functionalities to assist you with your ICD-10 transition: ICD-10 Readiness Vitera Medical Manager FAQs 1. Which version of Vitera Medical Manager supports ICD-10? Vitera Medical Manager version 12 fully supports ICD-10 and is preloaded with the full ICD-10 code

More information

AWCTS SYSTEM RELEASE NOTES

AWCTS SYSTEM RELEASE NOTES Release Date: June 2017 Release Number: v 2.8.12 Release Summary The 2.8.12 release of the Army Warrior Care & Transition System (AWCTS) consists of bug fixes and enhancements. If you have questions or

More information

12d Synergy and 12d Model

12d Synergy and 12d Model 12d Synery Getting Started Guide 12d Synergy and 12d Model Version 2.0 November 14 12d Solutions Pty Ltd ACN 101 351 991 PO Box 351 Narabeen NSW Australia 2101 (02) 9970 7117 (02) 9970 7118 support@12d.com

More information

N C MPASS. Clinical Self-Scheduling. Version 6.8

N C MPASS. Clinical Self-Scheduling. Version 6.8 N C MPASS Clinical Self-Scheduling Version 6.8 Ontario Telemedicine Network (OTN) All rights reserved. Last update: May 24, 2018 This document is the property of OTN. No part of this document may be reproduced

More information

Health Cloud Implementation Guide

Health Cloud Implementation Guide Health Cloud Implementation Guide Salesforce, Winter 18 @salesforcedocs Last updated: November 8, 2017 Copyright 2000 2017 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark

More information

Managing Online Agreements

Managing Online Agreements Quick-Start Guide Managing Online Agreements FOR PLAN ADMINISTRATORS Last Updated: 4/6/15 This quick start guide is intended as a fingertip reference for managing online grant agreements. Please consult

More information

DEFCON Authenticator. with Dual USB Port Hub

DEFCON Authenticator. with Dual USB Port Hub DEFCON Authenticator with Dual USB Port Hub DEFCON TM Authenticator 2 Introduction Thank you for purchasing the Targus DEFCON Authenticator fingerprint scanner with Dual USB Port Hub. The DEFCON Authenticator

More information

Scheduling Process Guide

Scheduling Process Guide HHAeXchange Scheduling Process Guide Scheduling and Adjusting Visits Copyright 2017 Homecare Software Solutions, LLC One Court Square 44th Floor Long Island City, NY 11101 Phone: (718) 407-4633 Fax: (718)

More information

PATIENT PORTAL USERS GUIDE

PATIENT PORTAL USERS GUIDE PATIENT PORTAL USERS GUIDE V 5.0 December 2012 eclinicalworks, 2012. All rights reserved Login and Pre-Registration Patients enter a valid Username and secure Password, then click the Sign In button to

More information

Setting Up an Award and Creating a Grant

Setting Up an Award and Creating a Grant The award is the mechanism that specifies the terms and conditions based on the sponsor agreement. There are four steps to setting up an award: 1. Create Award 2. Create Grant 3. Create Billing Schedule

More information

DTAS Mobile Application User Manual

DTAS Mobile Application User Manual Deployed Theater Accountability Software (DTAS) DTAS Mobile Application User Manual Version 3.3 Draft January 14, 2008 Submitted to LTC John Kilgallon Product Manager, AHRS PEO Enterprise Information Systems

More information

Conduent State Level Registry for Provider Incentive Payments

Conduent State Level Registry for Provider Incentive Payments Conduent State Level Registry Government Healthcare Solutions Conduent State Level Registry for Provider Incentive Payments MT User Manual Version 5.0 May 23, 2017 2017 Conduent Business Services, LLC.

More information

Care Manager Guide SPIRIT CMTS. Care Management Tracking System. University of Washington aims.uw.edu

Care Manager Guide SPIRIT CMTS. Care Management Tracking System. University of Washington aims.uw.edu Care Manager Guide SPIRIT CMTS Care Management Tracking System University of Washington aims.uw.edu rev. 12/4/2017 Table of Contents TOP TIPS & TRICKS... 1 INTRODUCTION... 2 CARE MANAGER ACCOUNT ROLE...

More information

Disaster Recovery Grant Reporting System (DRGR) Action Plan Module Draft User Guide

Disaster Recovery Grant Reporting System (DRGR) Action Plan Module Draft User Guide Disaster Recovery Grant Reporting System (DRGR) Action Plan Module Draft User Guide May 9, 2011 U.S. Department of Housing and Urban Development Office of Community Planning and Development DRGR 7.2 Release

More information

einteract User Guide July 07, 2017

einteract User Guide July 07, 2017 einteract User Guide July 07, 2017 This document covers the use of the einteract features in PointClickCare. Table of Contents einteract... 3 einteract Quick Reference Guide... 3 Overview of einteract...

More information

The Chevron-Marketer Miami-Dade Fuel Your School Promotion Miami-Dade County in Florida

The Chevron-Marketer Miami-Dade Fuel Your School Promotion Miami-Dade County in Florida The Chevron-Marketer Miami-Dade Fuel Your School Promotion Miami-Dade County in Florida 1. Agreement and Use By accessing and using the www.fuelyourschool.com/miami-dadecounty website and its contents,

More information

CSE255 Introduction to Databases - Fall 2007 Semester Project Overview and Phase I

CSE255 Introduction to Databases - Fall 2007 Semester Project Overview and Phase I SEMESTER PROJECT OVERVIEW In this term project, you are asked to design a small database system, create and populate this database by using MYSQL, and write a web-based application (with associated GUIs)

More information

12d Synergy Client Installation Guide

12d Synergy Client Installation Guide 12d Synergy Client Installation Guide Version 2.0 January 2016 12d Solutions Pty Ltd ACN 101 351 991 PO Box 351 Narabeen NSW Australia 2101 (02) 9970 7117 (02) 9970 7118 support@12d.com www.12.com 12d

More information

User Guide on Jobs Bank Portal (Employers)

User Guide on Jobs Bank Portal (Employers) User Guide on Jobs Bank Portal (Employers) Table of Contents 4 Manage Job Postings... 3 4.1 Create Job Posting... 3 4.1.1 Publish Job Posting... 10 4.2 Create Job Posting As Third Party Employer... 11

More information

CHILDREN AND YOUTH SERVICES

CHILDREN AND YOUTH SERVICES Procedural Manual for Municipalities Using the Family and Community Support Services (FCSS) On-line System CHILDREN AND YOUTH SERVICES Table of Contents TABLE OF CONTENTS 2 THE FCSS PROGRAM HANDBOOK 3

More information

Government of India Ministry of Finance Central Board of Direct Taxes Directorate of Income Tax (Systems) Notification No.

Government of India Ministry of Finance Central Board of Direct Taxes Directorate of Income Tax (Systems) Notification No. DGIT(S)/ADG(S)-2/Notification/106/2018 Government of India Ministry of Finance Central Board of Direct Taxes Directorate of Income Tax (Systems) Notification No. 4 of 2018 New Delhi, 5 th April, 2018 Procedure

More information

Optima 101: PARTICIPANT GUIDE

Optima 101: PARTICIPANT GUIDE Optima 101: Introduction to Care Operations Management (COM) PARTICIPANT GUIDE 2017 Optima Healthcare Solutions Page 1 CONTENTS CONTENTS... 2 ABOUT THIS GUIDE... 3 LEARNING OUTCOMES... 4 1. LOGGING INTO

More information

Understanding Your Meaningful Use Report

Understanding Your Meaningful Use Report Understanding Your Meaningful Use Report Distributed by Kowa Optimed EMRlogic activehr Understanding Your Meaningful Use Report, version 2.1 Publication Date: May 8, 2012 OD Professional and activehr OD

More information

Copyright 2013 GE Multilin Inc. All rights reserved. Power Management Control System (PMCS) software revision EnerVista, Integrator, Digital

Copyright 2013 GE Multilin Inc. All rights reserved. Power Management Control System (PMCS) software revision EnerVista, Integrator, Digital Copyright 2013 GE Multilin Inc. All rights reserved. Power Management Control System (PMCS) software revision 7.00. EnerVista, Integrator, Digital Energy, Multilin, and GE Multilin are trademarks or registered

More information

Effort Certification Training Guide

Effort Certification Training Guide Effort Certification Training Guide September 2010 This training guide explains the process for certifying effort reports in the University s effort reporting application, housed in the PAWS system (PeopleSoft).

More information

State of Florida. Department of Economic Opportunity. One Stop Management Information System (OSMIS) Regional Financial Management User Manual

State of Florida. Department of Economic Opportunity. One Stop Management Information System (OSMIS) Regional Financial Management User Manual State of Florida Department of Economic Opportunity One Stop Management Information System (OSMIS) Regional Financial Management User Manual Date: February 20, 2013 (Final) Version: 11.06 Table of Contents

More information

PeopleSoft 8 SP1 Financial Aid Updates to Financial Aid for SA Bundle 14 - Regulatory Release

PeopleSoft 8 SP1 Financial Aid Updates to Financial Aid for SA Bundle 14 - Regulatory Release Updates to Financial Aid for SA Bundle 14 - Regulatory Release 4 2006-2007 June 2006 Updates to Financial Aid for SA Bundle 14 - Regulatory Release 4 2006-2007 Copyright 2006, Oracle. All rights reserved.

More information

Medical Assistance Provider Incentive Repository. User Guide. For Eligible Hospitals

Medical Assistance Provider Incentive Repository. User Guide. For Eligible Hospitals Medical Assistance Provider Incentive Repository User Guide For Eligible Hospitals February 25, 2013 Contents Introduction... 3 Before You Begin... 3 Complete your R&A registration.... 3 Identify one individual

More information

NDoc Update - Release Notes (updated 04/21/2017)

NDoc Update - Release Notes (updated 04/21/2017) NDoc Version Number: 16.05.01 Important Installation Considerations: Users logged in while installing an update will lose access and any unsaved work. Installation Steps (does not apply to Hosted customers*):

More information

University of Miami Clinical Enterprise Technologies

University of Miami Clinical Enterprise Technologies Provider Manual 1 Our Mission: To design and deliver ongoing support for a network of Business and Clinical Information Management Systems which enhance the academic and research vision while implementing

More information

ecrt System 4.5 Training

ecrt System 4.5 Training ecrt System 4.5 Training The Work List The Work List is displayed immediately after you log into the system. This screen lists the tasks that require attention. The Statements Awaiting Certification list

More information

Available at :

Available at : Available at : http://servicevoter.nic.in/ Table of Contents Introduction-------------------------------------------------------------------------------------------------------5 Purpose of the System------------------------------------------------------------------------------------------5

More information

Stage 1. Meaningful Use 2014 Edition User Manual

Stage 1. Meaningful Use 2014 Edition User Manual Stage 1 Meaningful Use 2014 Edition User Manual This document, as well as the software described in it, is provided under a software license agreement with STI Computer Services, Inc. Use of this software

More information

Using Centricity Electronic Medical Record Meaningful Use Reports Version 9.5 January 2013

Using Centricity Electronic Medical Record Meaningful Use Reports Version 9.5 January 2013 GE Healthcare Using Centricity Electronic Medical Record Meaningful Use Reports Version 9.5 January 2013 Centricity Electronic Medical Record DOC0886165 Rev 13 2013 General Electric Company - All rights

More information

Care Planning User Guide June 2011

Care Planning User Guide June 2011 User Guide June 2011 2011, ADL Data Systems, Inc. All rights reserved Table of Contents Introduction... 1 About Care Plan... 1 About this Information... 1 Logon... 2 Care Planning Module Basics... 5 Starting

More information

Kansas University Medical Center ecrt Department Administrator Training. June 2008

Kansas University Medical Center ecrt Department Administrator Training. June 2008 Kansas University Medical Center ecrt Department Administrator Training June 2008 KUMC Process Timeline Effort Reporting Period 3 Week Pre-Review Period 3 Week Certification Period Post Certification Period

More information

Faculty-Led Study Abroad Application Manual for Faculty and Staff. Version /15/15. 1 P a g e

Faculty-Led Study Abroad Application Manual for Faculty and Staff. Version /15/15. 1 P a g e Faculty-Led Study Abroad Application Manual for Faculty and Staff Version 3.1 09/15/15 1 P a g e Contents Faculty-Led Study Abroad application overview... 3 How to gain access to the application... 3 Things

More information

Medicare PPS Report. Self Guided Tutorial

Medicare PPS Report. Self Guided Tutorial Medicare PPS Report Self Guided Tutorial 1 Tutorial Objectives After completing this tutorial, you will be able to: Identify the purpose of the Medicare PPS Report Access the Medicare PPS Report Customize

More information

NSF 2 Month Handbook. Effective for Reviews Performed as of 07/01/17. NSF Account Management. Updated 07/24/17

NSF 2 Month Handbook. Effective for Reviews Performed as of 07/01/17. NSF Account Management. Updated 07/24/17 Updated 07/24/17 NSF 2 Month Handbook Effective for Reviews Performed as of 07/01/17 NSF Account Management Table of Contents Contents 2 Month Rule Policy... 2 NSF Definition... 2 Sponsor/University Guidance:...

More information

Copyright. Last updated: September 28, 2017 MicroMD EMR Objective Measure Calculations Manual: Performance Year 2017

Copyright. Last updated: September 28, 2017 MicroMD EMR Objective Measure Calculations Manual: Performance Year 2017 Objective Measure Calculations Performance Year 2017 Trademarks Because of the nature of the material, numerous hardware and software products are mentioned by their trade names in this publication. All

More information

Application Notes for IgeaCare ApoloDS with Avaya IP Office Issue 1.0

Application Notes for IgeaCare ApoloDS with Avaya IP Office Issue 1.0 Avaya Solution & Interoperability Test Lab Application Notes for IgeaCare ApoloDS with Avaya IP Office Issue 1.0 Abstract These Application Notes describe the configuration steps required for IgeaCare

More information