Siebel agent Reference - IBM

IBM Tivoli Composite Application Manager Agent for SiebelCRMVersion 7.1.1

Reference

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 269.

This edition applies to version 7.1.1 of IBM Tivoli Composite Application Manager Agent for Siebel CRM (productnumber 5724-V09) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2010, 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . vii

Chapter 1. Workspaces reference . . . . 1Predefined workspaces . . . . . . . . . . . 1Workspace descriptions . . . . . . . . . . . 2

Siebel Navigator item . . . . . . . . . . 2Availability Navigator item . . . . . . . . 2Components Navigator item . . . . . . . . 3File System Navigator item . . . . . . . . 4Logs Navigator item . . . . . . . . . . . 4Logs Pre77 Navigator item. . . . . . . . . 4Statistics Navigator item . . . . . . . . . 5Tasks Navigator item . . . . . . . . . . 6

Chapter 2. Attributes reference . . . . . 9Attribute groups for the monitoring agent . . . . 9Attributes in each attribute group . . . . . . . 12

Availability attribute group . . . . . . . . 13Comp Counts attribute group . . . . . . . 18Comp CPU Util Rollup attribute group . . . . 19Comp Detail attribute group. . . . . . . . 20Comp Logs attribute group . . . . . . . . 22Comp Logs Pre77 attribute group . . . . . . 23Comp Name attribute group. . . . . . . . 25Component Resource attribute group . . . . . 25Component Statistics attribute group . . . . . 31Database File System attribute group . . . . . 33Database Files attribute group . . . . . . . 35DLA Input attribute group . . . . . . . . 38Enterprise attribute group . . . . . . . . 42File System attribute group . . . . . . . . 43Files attribute group . . . . . . . . . . 45Gate Log attribute group . . . . . . . . . 49Gate Log Pre77 attribute group . . . . . . . 50Managed URLs attribute group. . . . . . . 51Marketing Statistics attribute group . . . . . 54Performance Object Status attribute group . . . 56Server Log attribute group . . . . . . . . 61Server Log Pre77 attribute group . . . . . . 62Siebel Server attribute group . . . . . . . 64Siebel Statistics attribute group . . . . . . . 66Statistic Details attribute group . . . . . . . 68Statistics AsgnSubsys attribute group . . . . . 91Statistics CommInboundProcessor attribute group 92Statistics EAISubsys attribute group . . . . . 93Statistics FlightDataRecorder attribute group . . 95Statistics InfraCore attribute group . . . . . 96Statistics InfraDatabase attribute group . . . . 101Statistics InfraMultiThread attribute group . . 104Statistics InfraObjMgr attribute group . . . . 106Statistics InfraRecovery attribute group . . . . 116Statistics PIMSIENG attribute group . . . . . 118Statistics PSPEngine attribute group . . . . . 120

Statistics SearchDataProcessor attribute group 121Statistics ServerQueryTime attribute group . . 122Statistics TestSubsys attribute group . . . . . 123Statistics XMLCnv attribute group . . . . . 125Task CPU Util Rollup attribute group . . . . 126Task Detail attribute group . . . . . . . . 128Task Resource attribute group . . . . . . . 131Task Summary attribute group . . . . . . 138User Session attribute group . . . . . . . 141User Session Summary attribute group . . . . 143

Disk capacity planning for historical data . . . . 145

Chapter 3. Situations reference. . . . 149Predefined situations . . . . . . . . . . . 149Situation descriptions. . . . . . . . . . . 151

Siebel Navigator item . . . . . . . . . 151Availability Navigator item . . . . . . . . 151Components Navigator item . . . . . . . 155File System Navigator item. . . . . . . . 158Logs Navigator item . . . . . . . . . . 164Logs Pre77 Navigator item . . . . . . . . 166Statistics Navigator item. . . . . . . . . 166Tasks Navigator item . . . . . . . . . . 170

Chapter 4. Take Action commandsreference . . . . . . . . . . . . . 173Predefined Take Action commands . . . . . . 173Take Action command descriptions . . . . . . 174

Delete Archived Logs action . . . . . . . 174Http URL Add action . . . . . . . . . 175Http URL Remove action . . . . . . . . 176Pause Siebel Server Task action . . . . . . 177Put Component Group Online action . . . . 179Resume Siebel Server Task action. . . . . . 181Run Srvrmgr Command action . . . . . . 182Shutdown Siebel_Server_Component action . . 184Start Gateway Name Server action . . . . . 186Start Siebel Server action . . . . . . . . 187Start Siebel Server Task action . . . . . . . 188Startup Siebel_Server_Component action . . . 190Stop Gateway Name Server action . . . . . 191Stop Siebel Server action . . . . . . . . 193Stop Siebel Server Task action . . . . . . . 194Take Component Group Offline action . . . . 195

Chapter 5. Event mapping . . . . . . 199

Chapter 6. Tivoli Common Reportingfor the Siebel agent. . . . . . . . . 221Cognos-based report packages. . . . . . . . 221Prerequisites. . . . . . . . . . . . . . 222Running Cognos reports. . . . . . . . . . 223Working with Cognos reports . . . . . . . . 223Creating or customizing reports . . . . . . . 251

© Copyright IBM Corp. 2010, 2013 iii

Ad-hoc querying . . . . . . . . . . . . 252Debugging . . . . . . . . . . . . . . 252

Chapter 7. Discovery Library Adapterfor the Siebel agent. . . . . . . . . 257DLA data model class types represented in CDM 257DLA data model classes for Siebel agent . . . . 257

Chapter 8. Integration with TivoliBusiness Service Manager . . . . . 263Components for integrating with Tivoli BusinessService Manager . . . . . . . . . . . . 263Tasks to integrate the agent with Tivoli BusinessService Manager . . . . . . . . . . . . 264

Installing the Discovery Library Toolkit on theTivoli Business Service Manager . . . . . . 264Configuring the Tivoli Event Integration Facility(EIF) probe to enrich events . . . . . . . 264Creating a service in Tivoli Business ServiceManager . . . . . . . . . . . . . . 264

Creating a data source mapping for each datasource . . . . . . . . . . . . . . . 265Configuring additional IBM Tivoli Monitoringweb services. . . . . . . . . . . . . 265Viewing data in the Tivoli Enterprise Portal . . 265

Appendix. ITCAM for Applicationsdocumentation library. . . . . . . . 267Prerequisite publications. . . . . . . . . . 267Related publications . . . . . . . . . . . 267Other sources of documentation . . . . . . . 268

Notices . . . . . . . . . . . . . . 269Trademarks . . . . . . . . . . . . . . 271Privacy policy considerations . . . . . . . . 271

Index . . . . . . . . . . . . . . . 273

iv Siebel agent Reference

Figures

1. Arithmetic Overflow Errors in Ad-HocQuerying . . . . . . . . . . . . . 253

2. Properties panel. . . . . . . . . . . 2543. Publish packages . . . . . . . . . . 255

© Copyright IBM Corp. 2010, 2013 v

vi Siebel agent Reference

Tables

1. Capacity planning for historical data loggedby the Siebel agent. . . . . . . . . . 145

2. Siebel Application Server Availability Report 2243. Siebel Top N CPU & Memory Details by

Server Type Report . . . . . . . . . 2264. Siebel Bottom N CPU & Memory Details by

Server Type Report . . . . . . . . . 2285. Siebel CPU & Memory Details by Server Type

Report . . . . . . . . . . . . . . 2306. Siebel Component Overview Report . . . . 2327. Siebel Peak Memory Usage Report . . . . 233

8. Siebel Retry Summary Report . . . . . . 2359. Siebel SQL Details Report . . . . . . . 237

10. Siebel Top N Components By Running TasksAcross Enterprises . . . . . . . . . . 239

11. Siebel Top N Components By Running TasksAcross Servers . . . . . . . . . . . 242

12. Siebel Top N Components By Running TasksOn One Server . . . . . . . . . . . 244

13. Siebel Task Details Report . . . . . . . 24514. Siebel Test Details Report . . . . . . . 24715. Siebel Transaction Overview Report . . . . 249

© Copyright IBM Corp. 2010, 2013 vii

viii Siebel agent Reference

Chapter 1. Workspaces reference

A workspace is the working area of the Tivoli® Enterprise Portal application window. The Navigator treecontains a list of the workspaces provided by the agent.

About workspaces

Use the Navigator tree to select the workspace you want to see. As part of the application window, thestatus bar shows the Tivoli Enterprise Portal Server name and port number to which the displayedinformation applies and the ID of the current user.

When you select an item in the Navigator tree, a default workspace is displayed. When you right-click aNavigator item, a menu that includes a Workspace item is displayed. The Workspace item contains a listof workspaces for that Navigator item. Each workspace has at least one view. Some views have links toother workspaces. You can also use the Workspace Gallery tool as described in the Tivoli Enterprise PortalUser's Guide to open workspaces.

The workspaces in the Navigator are displayed in a Physical view that shows your enterprise as aphysical mapping or a dynamically populated logical view that is agent-specific. You can also create aLogical view. The Physical view is the default view.

This monitoring agent provides predefined workspaces. You cannot modify or delete the predefinedworkspaces, but you can create new workspaces by editing them and saving the changes with a differentname.

Workspace views can be any combination of query-based views, event views, and special purpose views.

Additional information about workspaces

For more information about creating, customizing, and working with workspaces, see "Using workspaces"in the Tivoli Enterprise Portal User's Guide.

For a list of the predefined workspaces for this monitoring agent and a description of each workspace,see Predefined workspaces and the information about each individual workspace.

Some attribute groups for this monitoring agent might not be represented in the predefined workspacesor views for this agent. For a full list of the attribute groups, see “Attribute groups for the monitoringagent” on page 9.

If you are using remote management to navigate to your systems in the Tivoli Enterprise Portal, navigatefrom the host name of the computer where you installed the agent.

Predefined workspacesThe Siebel agent provides predefined workspaces, which are organized by Navigator item.v Siebel Navigator item

– Siebel workspacev Availability Navigator item

– Agent Health workspace– Availability workspace

v Components Navigator item

© Copyright IBM Corp. 2010, 2013 1

– Component Counts workspace– Components workspace– Components (Superseded) workspace

v File System Navigator item– File System workspace

v Logs Navigator item– Logs workspace– Siebel Gateway Name Server Log workspace

v Logs Pre77 Navigator item– Gateway Name Server Log Pre 77 workspace– Logs Pre77 workspace

v Statistics Navigator item– InfraCore,InfraMultithread and InfraRecovery Statistics workspace– Other Siebel Statistics workspace– Siebel Statistics (Superseded) workspace– Statistics workspace

v Tasks Navigator item– Task CPU Details workspace– Tasks workspace– Tasks Summary workspace– User Sessions workspace

Workspace descriptionsEach workspace description provides information about the workspace such as the purpose and a list ofviews in the workspace.

Workspaces are listed under Navigator items.

Siebel Navigator itemThe workspace descriptions are organized by the Navigator item to which the workspaces are relevant.Siebel workspace

This is the top-level workspace for the Monitoring Agent for Siebel CRM.

This workspace contains the following views:Enterprise Server Status

Displays the output of the 'list servers' command for this enterprise.Server CPU Utilization

Displays the CPU utilization for the monitored Siebel Server and Gateway Name Serverprocesses.

Application Server Connection StatusDisplays the connection status of the Siebel application server.

Siebel ComponentsDisplays output of the srvrmgr list components command for this Siebel ApplicationServer.

Task SummaryDisplays a summary of task information for this Siebel Application Server.

Availability Navigator itemThe workspace descriptions are organized by the Navigator item to which the workspaces are relevant.

2 Siebel agent Reference

Agent Health workspaceDisplays the status of the performance objects used for this agent's data collection.

This workspace contains the following views:Performance Object Status

Displays the data collection status for each agent attribute group. The status reflects thelast attempt to collect data.

Application Server Connection StatusDisplays the connection status of the Siebel agent.

Availability workspaceThe Availability workspace displays the overall health of the application.

This workspace contains the following views:Availability

This view displays the overall health of the application.Memory

This view displays the memory utilization of the applications.Processor

This view displays the processor utilization of the applications.

Components Navigator itemThe workspace descriptions are organized by the Navigator item to which the workspaces are relevant.Component Counts workspace

Provides the number of running interactive Tasks per Siebel Component

This workspace contains the following views:Number of Running Interactive Tasks per Component

Displays the list of Siebel Components along with the number of running interactiveTasks, computed from the cached output of the srvrmgr tasks command for this SiebelApplication Server. The default refresh or sampling interval for this cached data is 15minutes. This default sampling interval has been chosen so the agent does not put asignificant load on the system or the Siebel server as it gathers the data. To modify thedefault refresh interval, set the KUB_SRVRMGR_POLL_MINUTES environment variable.The minimum allowable setting is 1 minute. Note that because this view displays cacheddata, the active components that it reports may differ slightly from those displayed in theTasks workspace views.

Component Task CountsBar Chart of Siebel Components displaying the number of running interactive Tasks,computed from the cached output of the srvrmgr tasks command for this SiebelApplication Server. The default refresh or sampling interval for this cached data is 15minutes. This default sampling interval has been chosen so the agent does not put asignificant load on the system or the Siebel server as it gathers the data. To modify thedefault refresh interval, set the KUB_SRVRMGR_POLL_MINUTES environment variable.The minimum allowable setting is 1 minute. Note that because this view displays cacheddata, the active components that it reports may differ slightly from those displayed in theTasks workspace views.

Components workspaceProvides component information for the Siebel Application Server

This workspace contains the following views:Siebel Components

Displays cached output of the srvrmgr list components command for this SiebelApplication Server. The default refresh or sampling interval for this cached data is 15minutes. This default sampling interval has been chosen so the agent does not put asignificant load on the system or the Siebel server as it gathers the data. To modify thedefault refresh interval, set the KUB_SRVRMGR_POLL_MINUTES environment variable.

Chapter 1. Workspaces reference 3

The minimum allowable setting is 1 minute. Note that because this view displays cacheddata, the active components that it reports may differ slightly from those displayed in theComponents workspace views.

Component CPU UtilizationThis view displays the CPU utilization per component.

Components (Superseded) workspaceSiebel Server components CPU overview.

This workspace contains the following views:Component CPU Utilization

A graph of CPU utilization for each Siebel Server component. This view displaysavailability data updated at minute intervals.

Component CPU Utilization SummaryA graph summarizing the CPU utilization for all Siebel Server components. This viewdisplays availability data for up to the past five minutes.

File System Navigator itemThe workspace descriptions are organized by the Navigator item to which the workspaces are relevant.File System workspace

Provides Siebel installation directory and Siebel File System information about the Siebel Server.

This workspace contains the following views:Siebel Installation Volume

Displays the Siebel installation volume usage by the Siebel Server.Siebel Installation Files and Directories

Displays the detailed information about the files and directories usage of the SiebelServer.

Siebel File System VolumeDisplays an overview of Siebel File System usage by the Siebel Server.

Siebel File System DirectoryDisplays the detailed information about the Siebel File System usage by the Siebel Server.

Siebel File System Cleanup StatisticsDisplays information about the Siebel File System cleanup statistics.

Logs Navigator itemThe workspace descriptions are organized by the Navigator item to which the workspaces are relevant.Logs workspace

Provides monitoring information for Siebel log files.

This workspace contains the following views:Application Server Log

Displays Siebel Server log file information.Component Logs

Displays Siebel Server component log file information.Siebel Gateway Name Server Log workspace

Displays entries from the Gateway Name Server log.

This workspace contains the following view:Gateway Name Server Log

Displays entries from the Gateway Name Server log.

Logs Pre77 Navigator itemThe workspace descriptions are organized by the Navigator item to which the workspaces are relevant.Gateway Name Server Log Pre 77 workspace

Displays entries from the Gateway Name Server log prior to version 7.7.

This workspace contains the following view:


Gateway Name Server Log (Prior to Siebel Version 7.7)Displays entries from the Gateway Name Server log.

Logs Pre77 workspaceProvides monitoring information for Siebel log files prior to version 7.7.

This workspace contains the following views:Application Server Log (Prior to Siebel Version 7.7)

Displays Siebel Server log file information.Component Logs (Prior to Siebel Version 7.7)

Displays Siebel Server component log file information.

Statistics Navigator itemThe workspace descriptions are organized by the Navigator item to which the workspaces are relevant.InfraCore,InfraMultithread and InfraRecovery Statistics workspace

Detailed statistics for the InfraCore, InfraMultithread and InfraRecovery Siebel subsystems.

This workspace contains the following views:InfraCore Performance Measurements

A summary of the InfraCore performance measurements.InfraCore Statistics

A summary of the InfraCore Statistics.InfraMultithread Statistics

A summary of the InfraMultithread Statistics.InfraRecovery Statistics

A summary of the InfraRecovery Statistics.Other Siebel Statistics workspace

Detailed statistics for the PIMSIEng, PSPEng, Test Subsystem, XMLCnv, AsgnSubsys,CommInboundProcessor, EAISubsystem and FlightDataRecorder Siebel subsystems.

This workspace contains the following views:Test Subsystem Performance Measurements

A summary of the Test Subsystem performance measurements.PIMSIEngPerformance Measurements

A summary of the PIMSIEng performance measurements.PSP Eng Statistics

A summary of the PSP Eng statistics.AsgnSubsys Statistics

A summary of the AsgnSubsys statistics.Test Subsystem Statistics

A summary of the Test Subsystem Statistics.CommInboundProcessor Statistics

A summary of the CommInboundProcessor Statistics.PIMSIEng Statistics

A summary of the PIMSIEng Statistics.EAISubsys Statistics

A summary of the EAISubsys Statistics.XMLCnv Statistics

A summary of the XMLCnv Statistics.FlightDataRecorder Statistics

A summary of the FightDataRecorder Statistics.Siebel Statistics (Superseded) workspace

Displays cached information gathered through execution of the Siebel srvrmgr 'list statistics' CLI.

This workspace contains the following view:Siebel Statistics

Displays information gathered through execution of the Siebel srvrmgr 'list statistics' CLI.


Statistics workspaceDetailed statistics of the Object Manager and Database Manager Siebel subsystem

This workspace contains the following views:Object Manager Performance Measurements

A summary of the Object Manager performance measurements.Database Manager Performance Measurements

A summary of the Database Manager performance measurements.Object Manager Statistics

A summary of the Object Manager statistics.Additional Object Manager Statistics

A summary of the Additional Object Manager statistics.Database Manager Statistics

A summary of the Database Manager Statistics.

Tasks Navigator itemThe workspace descriptions are organized by the Navigator item to which the workspaces are relevant.Task CPU Details workspace

Siebel Server tasks CPU overview.

This workspace contains the following views:Tasks CPU Utilization

A graph of CPU utilization for Siebel Server tasks. This view displays availability dataupdated at minute intervals.

Tasks CPU Utilization SummaryA graph summarizing the CPU utilization for all Siebel Server tasks. This view displaysavailability data for up to the past five minutes.

Tasks workspaceA report of task information for this Siebel Application Server.

This workspace contains the following views:Siebel Tasks

Displays cached output from the srvrmgr list tasks command for the Siebel ApplicationServer. The default refresh or sampling interval for this cached data is 15 minutes. Thisdefault sampling interval has been chosen so the agent does not put a significant load onthe system or the Siebel server as it gathers the data. To modify the default refreshinterval, set the KUB_SRVRMGR_POLL_MINUTES environment variable. The minimumallowable setting is 1 minute. Note that because this view displays cached data, the activetasks that it reports may differ slightly from those displayed in the Task workspaceviews.

Siebel Tasks SummaryDisplays a summary of Siebel task counts by run status, run mode, and task type.

Tasks Summary workspaceA report of task information for this Siebel Application Server.

This workspace contains the following views:Tasks by Runstate - Graphical

Graphical display of task counts by run status from the srvrmgr list tasks command forthe Siebel Application Server.

Tasks by RunstateSummarizes task counts by run status from the srvrmgr list tasks command for the SiebelApplication Server.

Tasks by Runmode - GraphicalGraphical display of task counts by run mode from the srvrmgr list tasks command forthe Siebel Application Server.


Tasks by RunmodeSummarizes task counts by run mode from the srvrmgr list tasks command for the SiebelApplication Server.

Tasks by Type - GraphicalGraphical display of task counts by type from the srvrmgr list tasks command for theSiebel Application Server.

Tasks by TypeSummarizes task counts by type from the srvrmgr list tasks command for the SiebelApplication Server.

User Sessions workspaceA report of user session information for this Siebel Application Server.

This workspace contains the following views:User Sessions

Displays user session task information from the srvrmgr list tasks command for the SiebelApplication Server, such as the task ID and run status of the user session task.

User Sessions Summary - GraphicalGraphical display of summarized task counts of user sessions by run status from thesrvrmgr list tasks command for the Siebel Application Server.

User Sessions SummarySummarizes task counts of user sessions by run status from the srvrmgr list taskscommand for the Siebel Application Server.


Chapter 2. Attributes reference

Attributes are the application properties that are being measured and reported by the IBM® TivoliComposite Application Manager Agent for Siebel CRM.

About attributes

Attributes are organized into attribute groups. Attributes in an attribute group relate to a single objectsuch as an application, or to a single kind of data such as status information.

Attributes in a group can be used in queries, query-based views, situations, policy workflows, take actiondefinitions, and launch application definitions. Chart or table views and situations are two examples ofhow attributes in a group can be used:v Chart or table views

Attributes are displayed in chart and table views. The chart and table views use queries to specifywhich attribute values to request from a monitoring agent. You use the Properties editor to apply filtersand set styles to define the content and appearance of a view based on an existing query.

v SituationsYou use attributes to create situations that monitor the state of your operating system, database, orapplication. A situation describes a condition you want to test. When you start a situation, the valuesyou assign to the situation attributes are compared with the values collected by the Siebel agent andregisters an event if the condition is met. You are alerted to events by indicator icons that are displayedin the Navigator.

Additional information about attributes

For more information about using attributes and attribute groups, see the Tivoli Enterprise Portal User'sGuide.

For a list of the attribute groups, a list of the attributes in each attribute group, and descriptions of theattributes for this monitoring agent, see “Attribute groups for the monitoring agent” and “Attributes ineach attribute group” on page 12.

Attribute groups for the monitoring agentThe Siebel agent contains the following attribute groups. The table name depends on the maximum tablename limits of the target database being used for the Tivoli Data Warehouse. If the maximum name is 30characters, any warehouse table name longer than 30 characters is shortened to 30 characters.v Attribute group name: Availability

– Table name: KUBAVAIL– Warehouse table name: KUB_AVAILABILITY or KUBAVAIL

v Attribute group name: Comp Counts– Table name: KUBCOMPCOU

v Attribute group name: Comp CPU Util Rollup– Table name: KUBCUTLRLU– Warehouse table name: KUB_COMP_CPU_UTIL_ROLLUP or KUBCUTLRLU

v Attribute group name: Comp Detail– Table name: KUBCOMPDET– Warehouse table name: KUB_COMP_DETAIL or KUBCOMPDET


v Attribute group name: Comp Logs– Table name: KUBCOMPLOG

v Attribute group name: Comp Logs Pre77– Table name: KUBCMPLOGP

v Attribute group name: Comp Name– Table name: KUBCOMPNAM

v Attribute group name: Component Resource– Table name: KUBCPUCOMP– Warehouse table name: KUB_COMPONENT_RESOURCE or KUBCPUCOMP

v Attribute group name: Component Statistics– Table name: KUBCOMPSTA– Warehouse table name: KUB_COMPONENT_STATISTICS or KUBCOMPSTA

v Attribute group name: Database File System– Table name: KUBDBFILSY– Warehouse table name: KUB_DATABASE_FILE_SYSTEM or KUBDBFILSY

v Attribute group name: Database Files– Table name: KUBDBFIL– Warehouse table name: KUB_DATABASE_FILES or KUBDBFIL

v Attribute group name: DLA Input– Table name: KUBDLAINP– Warehouse table name: KUB_DLA_INPUT or KUBDLAINP

v Attribute group name: Enterprise– Table name: KUBENTERPI– Warehouse table name: KUB_ENTERPRISE or KUBENTERPI

v Attribute group name: File System– Table name: KUBFILESYS– Warehouse table name: KUB_FILE_SYSTEM or KUBFILESYS

v Attribute group name: Files– Table name: KUBFILES– Warehouse table name: KUB_FILES

v Attribute group name: Gate Log– Table name: KUBGNSLOG

v Attribute group name: Gate Log Pre77– Table name: KUBGNSLOGP

v Attribute group name: Managed URLs– Table name: KUBMANAGED– Warehouse table name: KUB_MANAGED_URLS or KUBMANAGED

v Attribute group name: Marketing Statistics– Table name: KUBMKTST– Warehouse table name: KUB_MARKETING_STATISTICS or KUBMKTST

v Attribute group name: Performance Object Status– Table name: KUBPOBJST– Warehouse table name: KUB_PERFORMANCE_OBJECT_STATUS or KUBPOBJST

v Attribute group name: Server Log– Table name: KUBSRVLOG


v Attribute group name: Server Log Pre77– Table name: KUBSRVLOGP

v Attribute group name: Siebel Server– Table name: KUBSIEBSRV– Warehouse table name: KUB_SIEBEL_SERVER or KUBSIEBSRV

v Attribute group name: Siebel Statistics– Table name: KUBSIEBSTA– Warehouse table name: KUB_SIEBEL_STATISTICS or KUBSIEBSTA

v Attribute group name: Statistic Details– Table name: KUBDETSTA– Warehouse table name: KUB_STATISTIC_DETAILS or KUBDETSTA

v Attribute group name: Statistics AsgnSubsys– Table name: KUBSTATASG– Warehouse table name: KUB_STATISTICS_ASGNSUBSYS or KUBSTATASG

v Attribute group name: Statistics CommInboundProcessor– Table name: KUBSTATCOM– Warehouse table name: KUB_STATISTICS_COMMINBOUNDPROCESSOR or KUBSTATCOM

v Attribute group name: Statistics EAISubsys– Table name: KUBSTATEAI– Warehouse table name: KUB_STATISTICS_EAISUBSYS or KUBSTATEAI

v Attribute group name: Statistics FlightDataRecorder– Table name: KUBSTATFLT– Warehouse table name: KUB_STATISTICS_FLIGHTDATARECORDER or KUBSTATFLT

v Attribute group name: Statistics InfraCore– Table name: KUBSTATCOR– Warehouse table name: KUB_STATISTICS_INFRACORE or KUBSTATCOR

v Attribute group name: Statistics InfraDatabase– Table name: KUBSTATDAT– Warehouse table name: KUB_STATISTICS_INFRADATABASE or KUBSTATDAT

v Attribute group name: Statistics InfraMultiThread– Table name: KUBSTATMUL– Warehouse table name: KUB_STATISTICS_INFRAMULTITHREAD or KUBSTATMUL

v Attribute group name: Statistics InfraObjMgr– Table name: KUBSTATOBJ– Warehouse table name: KUB_STATISTICS_INFRAOBJMGR or KUBSTATOBJ

v Attribute group name: Statistics InfraRecovery– Table name: KUBSTATREC– Warehouse table name: KUB_STATISTICS_INFRARECOVERY or KUBSTATREC

v Attribute group name: Statistics PIMSIENG– Table name: KUBSTATPIM– Warehouse table name: KUB_STATISTICS_PIMSIENG or KUBSTATPIM

v Attribute group name: Statistics PSPEngine– Table name: KUBSTATENG– Warehouse table name: KUB_STATISTICS_PSPENGINE or KUBSTATENG

v Attribute group name: Statistics SearchDataProcessor

Chapter 2. Attributes reference 11

– Table name: KUBSTATSEA– Warehouse table name: KUB_STATISTICS_SEARCHDATAPROCESSOR or KUBSTATSEA

v Attribute group name: Statistics ServerQueryTime– Table name: KUBSTATSQT– Warehouse table name: KUB_STATISTICS_SERVERQUERYTIME or KUBSTATSQT

v Attribute group name: Statistics TestSubsys– Table name: KUBSTATSUB– Warehouse table name: KUB_STATISTICS_TESTSUBSYS or KUBSTATSUB

v Attribute group name: Statistics XMLCnv– Table name: KUBSTATXML– Warehouse table name: KUB_STATISTICS_XMLCNV or KUBSTATXML

v Attribute group name: Task CPU Util Rollup– Table name: KUBTUTLRLU– Warehouse table name: KUB_TASK_CPU_UTIL_ROLLUP or KUBTUTLRLU

v Attribute group name: Task Detail– Table name: KUBTASKDET– Warehouse table name: KUB_TASK_DETAIL or KUBTASKDET

v Attribute group name: Task Resource– Table name: KUBCPUTASK– Warehouse table name: KUB_TASK_RESOURCE or KUBCPUTASK

v Attribute group name: Task Summary– Table name: KUBTASKSUM– Warehouse table name: KUB_TASK_SUMMARY or KUBTASKSUM

v Attribute group name: User Session– Table name: KUBUSERSES– Warehouse table name: KUB_USER_SESSION or KUBUSERSES

v Attribute group name: User Session Summary– Table name: KUBUSERSE2– Warehouse table name: KUB_USER_SESSION_SUMMARY or KUBUSERSE2

Attributes in each attribute groupAttributes in each Siebel agent attribute group collect data that the agent uses for monitoring.

The descriptions of the attribute groups contain the following information:

Historical groupWhether the attribute group is a historical type that you can roll off to a data warehouse.

Attribute descriptionsInformation such as description, type, source, and warehouse name, as applicable, for eachattribute in the attribute group.

Some attributes are designated as key attributes. A key attribute is an attribute that is used inwarehouse aggregation to identify rows of data that represent the same object.

The Source information sometimes uses C programming code syntax for if-then-else clauses todescribe how an attribute is derived, for example:(CPU_Pct < 0 ) || (Memory_Pct < 0 )? 0 : 1


This example means that if the CPU_Pct attribute is less than 0 or if the Memory_Pct attribute isless than 0, then the attribute is set to 0. Otherwise, the attribute is set to 1.

Availability attribute groupThe Availability attribute group contains the availability data for all processes and services that make upthis application.Historical group

This attribute group is eligible for use with Tivoli Data Warehouse.Attribute descriptions

The following list contains information about each attribute in the Availability attribute group:Node attribute: This attribute is a key attribute.

DescriptionThe managed system name of the agent.

TypeString

SourceThe source for this attribute is the agent.

Warehouse nameNODE

Timestamp attributeDescription

The local time at the agent when the data was collected.Type

StringSource

The source for this attribute is the agent.Warehouse name

TIMESTAMPApplication Component attribute: This attribute is a key attribute.

DescriptionThe descriptive name of a part of the application.

TypeString


Warehouse nameAPPLICATION_COMPONENT or COMPONENT

Name attributeDescription

The name of the process, service, or functionality test. This name matches theexecutable name of the process, the service short name or the name of the processused to test the application.

TypeString with enumerated values. The strings are displayed in the Tivoli EnterprisePortal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v N/A (N/A)

Any other value is the value that is returned by the agent in the Tivoli EnterprisePortal.


Warehouse nameNAME

Status attribute


DescriptionThe status of the application component.v For processes 'UP', 'DOWN', 'WARNING', or

'PROCESS_DATA_NOT_AVAILABLE': 'PROCESS_DATA_NOT_AVAILABLE' isdisplayed for a process when the matching process is running but the resourceuse information cannot be collected for that process.

v For services 'UP', 'DOWN', or 'UNKNOWN': 'UNKNOWN' is displayed whenthe service is not installed.

v For functionality tests: 'PASSED' or 'FAILED' is displayed.Type

Integer with enumerated values. The strings are displayed in the Tivoli EnterprisePortal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v DOWN (0)v UP (1)v WARNING (2)v UNKNOWN (3)v PASSED (4)v FAILED (5)v PROCESS DATA NOT AVAILABLE (6)



Warehouse nameSTATUS

Full Name attributeDescription

The full name of the process including the path.Type

String with enumerated values. The strings are displayed in the Tivoli EnterprisePortal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v N/A (N/A)


SourceThe source for this attribute is collected from the operating system. On Windowsthe data is gathered from the Windows process. The data is limited to 256 bytes.On UNIX the data is gathered from ????. The data is limited to 2048 bytes. OnLinux the data is gathered from the /proc/pid/cmdline information. The data islimited to 2048 bytes.

Warehouse nameFULL_NAME or FULLNAME

Type attributeDescription

The type of the application component. Components are processes, services, orfunctionality tests.

TypeInteger with enumerated values. The strings are displayed in the Tivoli EnterprisePortal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v PROCESS (0)v SERVICE (1)v FUNCTIONALITY TEST (2)




Warehouse nameTYPE

Virtual Size attributeDescription

The virtual size (in MB) of the process.Type

Integer (32-bit gauge)Source

The source for this attribute is Collected from the operating system. On Windowsit is gathered from the Perfmon counter Process - Private Bytes. On Unix it isgathered from getproc64 on AIX, from /proc/name/psinfo on Solaris or frompstat_getproc on HP-UX. On Linux it is gathered from the /proc/pid information..

Warehouse nameVIRTUAL_SIZE or VIRTSIZE

Page Faults per Sec attributeDescription

The rate of page faults for the process measured in faults per second. Thisattribute only contains valid data for processes.

TypeInteger (32-bit gauge)

SourceThe source for this attribute is Collected from the operating system. On Windowsit is gathered from the Perfmon counter Process - Page Faults/sec. On Unix it isgathered from getproc64 on AIX, from /proc/name/psinfo on Solaris or frompstat_getproc on HP-UX. On Linux it is gathered from the /proc/pid information..

Warehouse namePAGE_FAULTS_PER_SEC or PAGEFAULTS

Working Set Size attributeDescription

The working set size of the process in MB. This attribute only contains valid datafor processes.


SourceThe source for this attribute is Collected from the operating system. On Windowsit is gathered from the Perfmon counter Process - Working Set. On Unix it isgathered from getproc64 on AIX, from /proc/name/psinfo on Solaris or frompstat_getproc on HP-UX. On Linux it is gathered from the /proc/pid information..

Warehouse nameWORKING_SET_SIZE or WORKSET

Thread Count attributeDescription

The number of threads currently allocated by this process. This attribute onlycontains valid data for processes.


SourceThe source for this attribute is Collected from the operating system. On Windowsit is gathered from the Perfmon counter Process - Thread Count. On Unix it is


gathered from getproc64 on AIX, from /proc/name/psinfo on Solaris or frompstat_getproc on HP-UX. On Linux it is gathered from the /proc/pid information..

Warehouse nameTHREAD_COUNT or THREADS

PID attributeDescription

The process ID associated with the process. This attribute only contains valid datafor processes.


SourceThe source for this attribute is Collected from the operating system. On Windowsit is gathered from the Perfmon counter Process - ID Process. On Unix it isgathered from getproc64 on AIX, from /proc/name/psinfo on Solaris or frompstat_getproc on HP-UX. On Linux it is gathered from the /proc/pid information..

Warehouse namePID

Percent Privileged Time attributeDescription

The percentage of the available CPU time that is being used by this process forprivileged operation.


SourceThe source for this attribute is Collected from the operating system. On Windowsit is gathered from the Perfmon counter Process - % Privileged Time. On Unix itis gathered from getproc64 on AIX, from /proc/name/psinfo on Solaris or frompstat_getproc on HP-UX. On Linux it is gathered from the /proc/pid information..

Warehouse namePERCENT_PRIVILEGED_TIME or PERCPRIV

Percent User Mode Time attributeDescription

The percentage of the available CPU time that is being used by this process foruser mode operation.


SourceThe source for this attribute is Collected from the operating system. On Windowsit is gathered from the Perfmon counter Process - % User Time. On Unix it isgathered from getproc64 on AIX, from /proc/name/psinfo on Solaris or frompstat_getproc on HP-UX. On Linux it is gathered from the /proc/pid information..

Warehouse namePERCENT_USER_MODE_TIME or PERCUSER

Percent Processor Time attributeDescription

The percentage of the elapsed time that this process used the processor to executeinstructions.


SourceThe source for this attribute is Collected from the operating system. On Windowsit is gathered from the Perfmon counter Process - % Processor Time. On Unix it is



Warehouse namePERCENT_PROCESSOR_TIME or PERCPROC

Command Line attributeDescription

The program name and any arguments specified on the command line when theprocess was started. This has the value N/A if this is a Service, or Functionalitytest.



SourceThe source for this attribute is Collected from the operating system. On Windowsit is gathered from the process. On Unix it is gathered from ????. On Linux it isgathered from the /proc/pid/cmdline information. It is limited to 2048 bytes. .

Warehouse nameCOMMAND_LINE or CMDLINE

Functionality Test Status attributeDescription

The return code of the functionality test. When the monitored application isrunning correctly, 'SUCCESS' is displayed. 'NOT_RUNNING' is displayed when itis not running correctly. 'N/A' is displayed when the row does not represent afunctionality test.

TypeInteger with enumerated values. The strings are displayed in the Tivoli EnterprisePortal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v SUCCESS (0)v N/A (1)v GENERAL ERROR (2)v WARNING (3)v NOT RUNNING (4)v DEPENDENT NOT RUNNING (5)v ALREADY RUNNING (6)v PREREQ NOT RUNNING (7)v TIMED OUT (8)v DOESNT EXIST (9)v UNKNOWN (10)v DEPENDENT STILL RUNNING (11)v INSUFFICIENT USER AUTHORITY (12)



Warehouse nameFUNCTIONALITY_TEST_STATUS or FUNCSTATUS

Functionality Test Message attribute


DescriptionThe text message that corresponds to the Functionality Test Status. This is onlyvalid for functionality tests.




Warehouse nameFUNCTIONALITY_TEST_MESSAGE or FUNCMSG

Comp Counts attribute groupThis attribute group contains a list of Siebel Components along with the number of running interactiveTasks per ComponentHistorical group

This attribute group is not eligible for use with Tivoli Data Warehouse.Attribute descriptions

The following list contains information about each attribute in the Comp Counts attribute group:Node attribute: This attribute is a key attribute.


TypeString




StringSource

The source for this attribute is the agent.Component Name attribute: This attribute is a key attribute.

DescriptionThe name of the Siebel Component.

TypeString

SourceThe source for this attribute is Script data.

Running Interactive Task Count attributeDescription

The current number of running interactive Tasks for the ComponentType

Integer (32-bit gauge) with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return the values that areshown in parentheses. The following values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)



SourceThe source for this attribute is Script data.

Comp CPU Util Rollup attribute groupThis attribute group comprises a summary of CPU utilization for the active components on the SiebelServer.Historical group


The following list contains information about each attribute in the Comp CPU Util Rollupattribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPMaximum attribute: This attribute is a key attribute.

DescriptionThe maximum amount of percent processor time used by a component.

TypeInteger (32-bit counter) with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return the values that areshown in parentheses. The following values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)


SourceThe source for this attribute is WMI - nullmax.

Warehouse nameMAXIMUM

Minimum attributeDescription

The minimum amount of percent processor time used by a component.Type

Integer (32-bit counter) with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return the values that areshown in parentheses. The following values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)



SourceThe source for this attribute is WMI - nullmin.

Warehouse nameMINIMUM

Average attributeDescription

The average percent processor time used by all active components.Type

Integer (32-bit counter) with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return the values that areshown in parentheses. The following values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)


SourceThe source for this attribute is WMI - nullave.

Warehouse nameAVERAGE

Total attributeDescription

The sum of percent processor time used by all active components.Type



SourceThe source for this attribute is WMI - nulltot.

Warehouse nameTOTAL

Comp Detail attribute groupThis attribute group consists of detailed information for components on the Siebel Server.Historical group


The following list contains information about each attribute in the Comp Detail attribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE

Timestamp attribute


DescriptionThe local time at the agent when the data was collected.

TypeString


Warehouse nameTIMESTAMP

Server Name attributeDescription

The Siebel Application Server name.Type

StringWarehouse name

SERVER_NAME or SNComp Alias attribute: This attribute is a key attribute.

DescriptionThe component alias.

TypeString

Warehouse nameCOMP_ALIAS

Comp Name attribute: This attribute is a key attribute.Description

The component name.Type


COMP_NAMEComp Grp Alias attribute

DescriptionThe component group alias.

TypeString

Warehouse nameCOMP_GRP_ALIAS or CGA

Run Mode attributeDescription

The run mode of the component.Type


RUN_MODERun State attribute

DescriptionThe run state of the component.

TypeString

Warehouse nameRUN_STATE

Running Tasks attributeDescription

Number of running tasks for the component.Type

Integer (32-bit gauge) with enumerated values. The strings are displayed in the


Tivoli Enterprise Portal. The warehouse and queries return the values that areshown in parentheses. The following values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)


Warehouse nameRUNNING_TASKS or RT

Gateway Name attributeDescription

The name of the Siebel Gateway.Type

StringSource

The source for this attribute is derived: getenv("KUB_SIEBEL_GATEWAY").Warehouse name

GATEWAY_NAME or GNEnterprise Name attribute

DescriptionThe name of the Siebel Enterpise.

TypeString

SourceThe source for this attribute is derived: getenv("KUB_SIEBEL_ENTERPRISE").

Warehouse nameENTERPRISE_NAME or EN

Comp Logs attribute groupThis attribute group comprises information from the logs of the Siebel Server components. It is used onlyfor Siebel version 7.7 or later.Historical group


The following list contains information about each attribute in the Comp Logs attribute group:Node attribute: This attribute is a key attribute.


TypeString




StringSource

The source for this attribute is the agent.Source Name attribute: This attribute is a key attribute.

DescriptionThe file name for this log record.

TypeString

SourceThe source for this attribute is Log File Data.


Event Type Alias attributeDescription

The event type alias for this log record.Type

StringSource

The source for this attribute is Log File Data.Type attribute

DescriptionThe event sub type for this log record.

TypeString


Severity attributeDescription

The event severity for this log record.Type

StringSource

The source for this attribute is Log File Data.SARMID attribute

DescriptionThe Siebel Application Response Measurement ID.

TypeString


Logs Timestamp attributeDescription

The time stamp for this log record.Type

StringSource

The source for this attribute is Log File Data.Log Message attribute

DescriptionThe log message field for this log record.

TypeString




StringSource

The source for this attribute is derived: getenv("KUB_SIEBEL_GATEWAY").

Comp Logs Pre77 attribute groupThis attribute group comprises information from the logs of the Siebel Server components. It is used onlyfor versions prior to Siebel version 7.7.Historical group

This attribute group is not eligible for use with Tivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the Comp Logs Pre77 attributegroup:Node attribute: This attribute is a key attribute.


TypeString




StringSource



TypeString



The event type alias for this log record.Type

StringSource


DescriptionThe event sub type for this log record.

TypeString



The event severity for this log record.Type

StringSource

The source for this attribute is Log File Data.Logs Timestamp attribute

DescriptionThe time stamp for this log record.

TypeString


Log Message attributeDescription

The log message field for this log record.


TypeString


Comp Name attribute groupThis attribute group lists the names of components on the Siebel Server.Historical group


The following list contains information about each attribute in the Comp Name attribute group:Node attribute: This attribute is a key attribute.


TypeString




StringSource

The source for this attribute is the agent.Comp Log Name attribute: This attribute is a key attribute.

DescriptionComponent Log Name

TypeString

SourceThe source for this attribute is derived: Comp_Log_Name_Source.

Comp PID attributeDescription

PID of the ComponentType



SourceThe source for this attribute is derived: atoi(Comp_PID_Source).

Component Resource attribute groupThis attribute group contains Availability metrics for active Siebel Server components.Historical group


The following list contains information about each attribute in the Component Resource attributegroup:Node attribute: This attribute is a key attribute.



TypeString


Warehouse nameNODE



StringSource




TypeString








Warehouse nameNAME

Status attributeDescription

The status of the application component.v For processes 'UP', 'DOWN', 'WARNING', or

'PROCESS_DATA_NOT_AVAILABLE': 'PROCESS_DATA_NOT_AVAILABLE' isdisplayed for a process when the matching process is running but the resourceuse information cannot be collected for that process.



Integer with enumerated values. The strings are displayed in the Tivoli Enterprise


Portal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v DOWN (0)v UP (1)v WARNING (2)v UNKNOWN (3)v PASSED (4)v FAILED (5)v PROCESS DATA NOT AVAILABLE (6)















Warehouse nameTYPE


The virtual size (in MB) of the process.



SourceThe source for this attribute is Collected from the operating system. On Windowsit is gathered from the Perfmon counter Process - Private Bytes. On Unix it isgathered from getproc64 on AIX, from /proc/name/psinfo on Solaris or frompstat_getproc on HP-UX. On Linux it is gathered from the /proc/pid information..















SourceThe source for this attribute is Collected from the operating system. On Windowsit is gathered from the Perfmon counter Process - Thread Count. On Unix it isgathered from getproc64 on AIX, from /proc/name/psinfo on Solaris or frompstat_getproc on HP-UX. On Linux it is gathered from the /proc/pid information..







Warehouse namePID














SourceThe source for this attribute is Collected from the operating system. On Windowsit is gathered from the Perfmon counter Process - % Processor Time. On Unix it isgathered from getproc64 on AIX, from /proc/name/psinfo on Solaris or frompstat_getproc on HP-UX. On Linux it is gathered from the /proc/pid information..


Command Line attribute


DescriptionThe program name and any arguments specified on the command line when theprocess was started. This has the value N/A if this is a Service, or Functionalitytest.











Functionality Test Message attributeDescription

The text message that corresponds to the Functionality Test Status. This is onlyvalid for functionality tests.






Comp Log Name attribute: This attribute is a key attribute.Description

Component Log NameType

StringSource

The source for this attribute is Join - Comp_Log_Name.Warehouse name

COMP_LOG_NAME or CLNComp PID attribute

DescriptionPID of the Component

TypeInteger (32-bit gauge) with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return the values that areshown in parentheses. The following values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)


SourceThe source for this attribute is Join - Comp_PID.

Warehouse nameCOMP_PID

Component Statistics attribute groupThis attribute group consists of detailed information gathered through execution of the Siebel srvrmgr'list statistics for component' CLI.Historical group


The following list contains information about each attribute in the Component Statistics attributegroup:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource

The source for this attribute is the agent.



Component Name attribute: This attribute is a key attribute.Description

The name of the Siebel component.Type


COMPONENT_NAME or CNStatistic attribute: This attribute is a key attribute.

DescriptionThe name of the Siebel component statistic.

TypeString

Warehouse nameSTATISTIC

Statistic Alias attributeDescription

The alias name of the Siebel component statistic.Type


STATISTIC_ALIAS or SASubsystem attribute

DescriptionThe Siebel subsystem that the Siebel component statistic applies to.

TypeString

Warehouse nameSD_SUBSYSTEM or SS

Siebel Server Name attribute: This attribute is a key attribute.Description

The Siebel Server name that the Siebel component statistic applies to.Type


SERVER_NAME or SNCurrent Value attribute

DescriptionThe current value of the Siebel component statistic.

TypeReal number (64-bit gauge) with eight decimal places of precision withenumerated values. The strings are displayed in the Tivoli Enterprise Portal. Thewarehouse and queries return the values that are shown in parentheses. Thefollowing values are defined:v Value Exceeds Maximum (9223372036854775807)v Value Exceeds Minimum (-9223372036854775808)


Warehouse nameCURRENT_VALUE or CV

Description attributeDescription

The description of the Siebel component statistic.


TypeString

Warehouse nameSD_DESCRIPTION or SD

Database File System attribute groupThis attribute group consists of information about the volume on which the Siebel File System isinstalled.Historical group


The following list contains information about each attribute in the Database File System attributegroup:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPName attribute: This attribute is a key attribute.

DescriptionThe path to the root of the Siebel File System.

TypeString

Warehouse nameNAME

Free Space in MB attributeDescription

The amount of free space in megabytes (MB) on the volume.Type



Warehouse nameFREE_SPACE_IN_MB or FSIM

Percent Used attributeDescription

The percentage of volume space that is used.




Warehouse namePERCENT_USED or PU

Percent Free attributeDescription

The percentage of the volume that is free.Type



Warehouse namePERCENT_FREE or PF

Hours Until Full attributeDescription

This attribute has been deprecated.Type

Integer with enumerated values. The strings are displayed in the Tivoli EnterprisePortal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v Value exceeds maximum (2147483647)


Warehouse nameHOURS_UNTIL_FULL or HUF

Total Size in MB attributeDescription

The total size in megabytes (MB) of the volume.Type



Warehouse nameTOTAL_SIZE_IN_MB or TSIM

Mount Point attributeDescription

The name of the volume on which the Siebel File System mounted.Type

String


Warehouse nameMOUNT_POINT or MP



StringSource


GATEWAY_NAME or GN

Database Files attribute groupThis attribute group consists of information about various directories and files in the Siebel File System.Historical group


The following list contains information about each attribute in the Database Files attribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPDirectory Name attribute: This attribute is a key attribute.

DescriptionThe name of the directory being monitored.

TypeString

Warehouse nameDIRECTORY_NAME or DN

File Name attribute: This attribute is a key attribute.Description

The name of the file being monitored.Type


FILE_NAMECurrent Size in MB attribute

DescriptionThe size in megabytes (MB) of the directory or file; if it is a directory, it includesthe size of all subdirectory contents.


TypeInteger (32-bit gauge) with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return the values that areshown in parentheses. The following values are defined:v N/A (-1)


Warehouse nameCURRENT_SIZE_IN_MB or CSIM

Percent of File System Used attributeDescription

The percent of file system space used by the directory.Type

Integer (32-bit gauge) with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return the values that areshown in parentheses. The following values are defined:v N/A (-1)


Warehouse namePERCENT_OF_FILE_SYSTEM_USED or POFSU

Size Change Last Hour attributeDescription

The change in size in megabytes (MB) during the past hour; value is extrapolatedfrom the difference between the size at the current time and the size at the timeinterval closest to an hour ago. It is valid after the monitoring agent has beenrunning for one agent polling interval.



Warehouse nameSIZE_CHANGE_LAST_HOUR or SCLH

Percent Change Last Hour attributeDescription

The percent change in size during the last hour; value is extrapolated from thedifference between the size at the current time and the size at the time intervalclosest to an hour ago. It is valid after the monitoring agent has been running forone agent polling interval.



Warehouse namePERCENT_CHANGE_LAST_HOUR or PCLH

Size Change Average attribute


DescriptionThe average change in size per hour, in megabytes (MB), since the monitoringagent was started.



Warehouse nameSIZE_CHANGE_AVERAGE or SCA

Percent Change Average attributeDescription

The average percent change in size per hour since the monitoring agent wasstarted.



Warehouse namePERCENT_CHANGE_AVERAGE or PCA

Size Change Total attributeDescription

The change in size in megabytes (MB) since the monitoring agent was started.Type



Warehouse nameSIZE_CHANGE_TOTAL or SCT

Percent Change Total attributeDescription

The percent change in size since the monitoring agent was started.Type



Warehouse namePERCENT_CHANGE_TOTAL or PCT



Integer with enumerated values. The strings are displayed in the Tivoli Enterprise


Portal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v Value exceeds maximum (2147483647)



Type attribute: This attribute is a key attribute.Description

The Siebel role of the directory.Type

Integer with enumerated values. The strings are displayed in the Tivoli EnterprisePortal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v Siebel File System (0)v Non Orphaned File (1)v Orphaned File (2)


Warehouse nameTYPE

DLA Input attribute groupThis attribute group contains data that is used by the Discovery Library Adapter for the Siebel agent.Historical group


The following list contains information about each attribute in the DLA Input attribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPEnterprise Name attribute: This attribute is a key attribute.

DescriptionThe name of the Siebel Enterprise.

TypeString

SourceThe source for this attribute is Join - Enterprise_Name.



Gateway Bind Address attributeDescription

The IPv4 bind address in ip:port format of the Siebel Gateway serverType

StringSource

The source for this attribute is Join - Gateway_Bind_Address.Warehouse name

GATEWAY_BIND_ADDRESS or GBAGateway IP Address attribute

DescriptionThe IPv4 address of the Siebel Gateway server

TypeString

SourceThe source for this attribute is Join - Gateway_IP_Address.

Warehouse nameGATEWAY_IP_ADDRESS or GIA

Gateway Port attributeDescription

The port of the Siebel Gateway serverType

Integer (32-bit numeric property) with enumerated values. The strings aredisplayed in the Tivoli Enterprise Portal. The warehouse and queries return thevalues that are shown in parentheses. The following values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)


SourceThe source for this attribute is Join - Gateway_Port.

Warehouse nameGATEWAY_PORT or GP

Gateway Hostname attributeDescription

The Hostname of the Siebel Gateway serverType

StringSource

The source for this attribute is Join - Gateway_Hostname.Warehouse name

GATEWAY_HOSTNAME or GHServer Type attribute

DescriptionThe Siebel server type.

TypeString

SourceThe source for this attribute is Join - Server_Type.

Warehouse nameSERVER_TYPE or ST

Server Name attribute: This attribute is a key attribute.


DescriptionThe Siebel Server name.

TypeString

SourceThe source for this attribute is Join - Server_Name.

Warehouse nameSERVER_NAME or SN

Host name attributeDescription

The host name or IP address of the workstation where the server is running.Type

StringSource

The source for this attribute is Join - Host_name.Warehouse name

HOST_NAMEInstall Dir attribute

DescriptionThe name of the directory where this server is installed.

TypeString

SourceThe source for this attribute is Join - Install_Dir.

Warehouse nameINSTALL_DIR or ID

Server State attributeDescription

The Siebel Application Server state. (Starting Up, Running, Shutting Down,Shutdown, Not Available, Connect Failed, Handshake Failed, Login Failed,Disconnected.)

TypeString

SourceThe source for this attribute is Join - Server_State.

Warehouse nameSERVER_STATE or SS

Start Time attributeDescription

The time when the server was started.Type

StringSource

The source for this attribute is Join - Start_Time.Warehouse name

START_TIMEEnd Time attribute

DescriptionThe time when the server was stopped.

TypeString

SourceThe source for this attribute is Join - End_Time.

Warehouse nameEND_TIME

Server Status attribute


DescriptionThe status of the server.

TypeString

SourceThe source for this attribute is Join - Server_Status.

Warehouse nameSERVER_STATUS or SS0

Running Task Count attribute: This attribute is a key attribute.Description

The number of running tasks in this Siebel Application Server.Type



SourceThe source for this attribute is Join - Active_Task_Count.

Warehouse nameACTIVE_TASK_COUNT or ATC

Application Server Connection Status attribute: This attribute is a key attribute.Description

Indicates whether the Siebel agent has successfully queried Siebel CRM. If thevalue is False, the Siebel CRM might be down or the Siebel agent is notconfigured correctly.

TypeString

SourceThe source for this attribute is Join - Connection_Status.

Warehouse nameCONNECTION_STATUS or CS

Updated Start Time attributeDescription


TimestampSource

The source for this attribute is Join - Updated_Start_Time.Warehouse name

UPDATED_START_TIME or USTUpdated End Time attribute


TypeTimestamp

SourceThe source for this attribute is Join - Updated_End_Time.

Warehouse nameUPDATED_END_TIME or UET


The name of the Siebel Gateway.


TypeString

SourceThe source for this attribute is Join - Gateway_Name.

Warehouse nameGATEWAY_NAME or GN

Enterprise Name0 attributeDescription

The name of the Siebel Enterpise.Type

StringSource

The source for this attribute is Join - Enterprise_Name.Warehouse name

ENTERPRISE_NAME0 or EN0

Enterprise attribute groupThe Siebel Enterprise name and the IPv4 bind address of the Siebel Gateway server.Historical group


The following list contains information about each attribute in the Enterprise attribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPEnterprise Name attribute: This attribute is a key attribute.

DescriptionThe name of the Siebel Enterprise.

TypeString


Gateway Bind Address attributeDescription

The IPv4 bind address in ip:port format of the Siebel Gateway serverType


GATEWAY_BIND_ADDRESS or GBAGateway IP Address attribute


DescriptionThe IPv4 address of the Siebel Gateway server

TypeString

Warehouse nameGATEWAY_IP_ADDRESS or GIA

Gateway Port attributeDescription

The port of the Siebel Gateway serverType

Integer (32-bit numeric property) with enumerated values. The strings aredisplayed in the Tivoli Enterprise Portal. The warehouse and queries return thevalues that are shown in parentheses. The following values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)


Warehouse nameGATEWAY_PORT or GP

Gateway Hostname attributeDescription

The Hostname of the Siebel Gateway serverType


GATEWAY_HOSTNAME or GHServer Type attribute

DescriptionThe Siebel server type.

TypeString

SourceThe source for this attribute is derived: getenv("SERVER_TYPE").

Warehouse nameSERVER_TYPE or ST

File System attribute groupThis attribute group consists of information about the volume on which the Siebel Server is installed.Historical group


The following list contains information about each attribute in the File System attribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE


The local time at the agent when the data was collected.


TypeString



Name attribute: This attribute is a key attribute.Description

The path to the Siebel installation.Type


NAMEFree Space in MB attribute

DescriptionThe amount of free space in megabytes (MB) on the volume.



Warehouse nameFREE_SPACE_IN_MB or FSIM

Percent Used attributeDescription

The percentage of volume space that is used.Type



Warehouse namePERCENT_USED or PU

Percent Free attributeDescription

The percentage of volume space that is free.Type



Warehouse namePERCENT_FREE or PF

Hours Until Full attribute


DescriptionThis attribute has been deprecated.

TypeInteger with enumerated values. The strings are displayed in the Tivoli EnterprisePortal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v Value exceeds maximum (2147483647)



Total Size in MB attributeDescription

The total size in megabytes (MB) of the volume.Type



Warehouse nameTOTAL_SIZE_IN_MB or TSIM

Mount Point attributeDescription

The name of the volume on which the Siebel installation is mounted.Type


MOUNT_POINT or MPGateway Name attribute

DescriptionThe name of the Siebel Gateway.

TypeString

SourceThe source for this attribute is derived: getenv("KUB_SIEBEL_GATEWAY").


Files attribute groupThis attribute group consists of information about various directories and files in the installed SiebelServer.Historical group


The following list contains information about each attribute in the Files attribute group:Node attribute: This attribute is a key attribute.


TypeString



Warehouse nameNODE



StringSource


TIMESTAMPDirectory Name attribute: This attribute is a key attribute.

DescriptionThe name of the directory being monitored.

TypeString

Warehouse nameDIRECTORY_NAME or DN

Filename attribute: This attribute is a key attribute.Description

The name of the file being monitored.Type


FILENAMECurrent Size in MB attribute

DescriptionThe size in megabytes (MB) of the directory or file; if it is a directory, it includesthe size of all subdirectory contents.



Warehouse nameCURRENT_SIZE_IN_MB or CSIM

Percent of File System Used attributeDescription

The percent of file system space used by the directory.Type



Warehouse namePERCENT_OF_FILE_SYSTEM_USED or POFSU

Size Change Last Hour attributeDescription

The change in size in megabytes (MB) during the past hour; value is extrapolated


from the difference between the size at the current time and the size at the timeinterval closest to an hour ago. It is valid after the monitoring agent has beenrunning for one agent polling interval.



Warehouse nameSIZE_CHANGE_LAST_HOUR or SCLH

Percent Change Last Hour attributeDescription

The percent change in size during the last hour; value is extrapolated from thedifference between the size at the current time and the size at the time intervalclosest to an hour ago. It is valid after the monitoring agent has been running forone agent polling interval.



Warehouse namePERCENT_CHANGE_LAST_HOUR or PCLH

Size Change Average attributeDescription

The average change in size per hour, in megabytes (MB), since the monitoringagent was started.



Warehouse nameSIZE_CHANGE_AVERAGE or SCA

Percent Change Average attributeDescription

The average percent change in size per hour since the monitoring agent wasstarted.



Warehouse namePERCENT_CHANGE_AVERAGE or PCA

Size Change Total attribute


DescriptionThe change in size in megabytes (MB) since the monitoring agent was started.



Warehouse nameSIZE_CHANGE_TOTAL or SCT

Percent Change Total attributeDescription

The percent change in size since the monitoring agent was started.Type



Warehouse namePERCENT_CHANGE_TOTAL or PCT



Integer with enumerated values. The strings are displayed in the Tivoli EnterprisePortal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v Value exceeds maximum (2147483647)



Name attribute: This attribute is a key attribute.Description

The Siebel role of the directory.Type

Integer with enumerated values. The strings are displayed in the Tivoli EnterprisePortal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v Siebel Server (1)v Siebel Server Logs (2)v Log Archive (3)v Docking (4)v Transaction Processing (5)v Gateway Name Server (6)v Gateway Name Server Logs (7)v Component Logs (8)v Component Log Archive (9)v Component Docking (10)v Component Transaction Processing (11)



Warehouse nameTYPE



StringSource


GATEWAY_NAME or GN

Gate Log attribute groupThis attribute group comprises information from the log of the Siebel Gateway Name Server. It is usedonly for Siebel version 7.7 or later.Historical group


The following list contains information about each attribute in the Gate Log attribute group:Node attribute: This attribute is a key attribute.


TypeString




StringSource



TypeString



The event type alias.Type

StringSource


DescriptionThe event sub type.

TypeString




The event severity.Type

StringSource



TypeString



The Siebel log time stamp.Type

StringSource


DescriptionThe log message field.

TypeString




StringSource

The source for this attribute is derived: getenv("KUB_SIEBEL_GATEWAY").

Gate Log Pre77 attribute groupThis attribute group comprises information from the log of the Siebel Gateway Name Server. It is usedonly for versions prior to Siebel version 7.7.Historical group


The following list contains information about each attribute in the Gate Log Pre77 attributegroup:Node attribute: This attribute is a key attribute.


TypeString


Timestamp attribute



TypeString


Source Name attribute: This attribute is a key attribute.Description

The file name for this log record.Type

StringSource

The source for this attribute is Log File Data.Event Type Alias attribute

DescriptionThe event type alias.

TypeString



The event sub type.Type

StringSource

The source for this attribute is Log File Data.Severity attribute

DescriptionThe event severity.

TypeString




StringSource



TypeString


Managed URLs attribute groupThis attribute group contains data that is gathered from URL monitoring by using HTTP.Historical group

This attribute group is eligible for use with Tivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the Managed URLs attributegroup:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPURL attribute: This attribute is a key attribute.

DescriptionThe URL that is monitored.

TypeString

Warehouse nameURL or HTTPURL

Response Time attributeDescription

The amount of time in milliseconds it takes to download the response.Type

Integer (32-bit gauge) with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return the values that areshown in parentheses. The following values are defined:v TIMEOUT (-1)


Warehouse nameRESPONSE_TIME or HTTPRSP

Page Size attributeDescription

The size of the page that is returned (in bytes) by the HTTP request.Type

Integer (32-bit gauge) with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return the values that areshown in parentheses. The following values are defined:v NO RESPONSE RECEIVED (-1)


Warehouse namePAGE_SIZE or PAGESZ

Page Objects attribute


DescriptionThe total number of additional objects that are associated with the monitoredpage.

TypeInteger (32-bit gauge) with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return the values that areshown in parentheses. The following values are defined:v NOT COLLECTED (-1)


Warehouse namePAGE_OBJECTS or PGOBJS

Total Object Size attributeDescription

The total number of bytes that are downloaded for the related page objects.Type

Integer (32-bit gauge) with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return the values that areshown in parentheses. The following values are defined:v NOT COLLECTED (-1)


Warehouse nameTOTAL_OBJECT_SIZE or TOTOSZ

Page Title attributeDescription

The title of the received URL page.Type


PAGE_TITLE or PAGETTLServer Type attribute

DescriptionThe type of server that is used at the target URL website.

TypeString

Warehouse nameSERVER_TYPE or SRVTYP

Response Code attributeDescription

The response code for the HTTP request.Type

Integer (32-bit numeric property) with enumerated values. The strings aredisplayed in the Tivoli Enterprise Portal. The warehouse and queries return thevalues that are shown in parentheses. The following values are defined:v NO RESPONSE RECEIVED (-1)


Warehouse nameRESPONSE_CODE or CODE


The current managed URL status, for example, OK or a status description.


TypeString


URL Alias attributeDescription

The alias that the user specified for the URL.Type


URL_ALIAS or ALIASUser Data attribute

DescriptionThe data that the user specified for the URL.

TypeString

Warehouse nameUSER_DATA or USER

Marketing Statistics attribute groupSiebel File System StatisticsHistorical group


The following list contains information about each attribute in the Marketing Statistics attributegroup:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPCurrent attribute: This attribute is a key attribute.

DescriptionThe number of files that have a corresponding record in the file attachmentdatabase table.




Warehouse nameMARKETING_STATISTICS_CURRENT or MSC

Orphaned attribute: This attribute is a key attribute.Description

The number of files that do not have a corresponding record in the fileattachment database table.



Warehouse nameMARKETING_STATISTICS_ORPHANED or MSO

Invalid attribute: This attribute is a key attribute.Description

The number of files (or directories) that are not file attachments. If sfscleanup.exeis attempting to delete a subdirectory that is not empty, the operation errors out.This gives you an opportunity to review the files contained within the directorybefore deletion.



Warehouse nameMARKETING_STATISTICS_INVALID or MSI

Ancient attribute: This attribute is a key attribute.Description

The number of files that have an associated record in the database with adifferent revision number.



Warehouse nameMARKETING_STATISTICS_ANCIENT or MSA

Total attribute: This attribute is a key attribute.Description

The total number of Current, Orphaned, Invalid and Ancient files in the SiebelFile System.

TypeInteger (32-bit gauge) with enumerated values. The strings are displayed in the




Warehouse nameMARKETING_STATISTICS_TOTAL or MST

Duration attribute: This attribute is a key attribute.Description




Warehouse nameMARKETING_STATISTICS_DURATION or MSD



StringSource




TypeString




The name of the Siebel Server.Type

StringSource

The source for this attribute is derived: getenv("KUB_SIEBEL_SERVERNAME").Warehouse name

SERVER_NAME or SN

Performance Object Status attribute groupThe Performance Object Status attribute group contains information that reflects the status of otherattribute groups so you can see the status of all of the performance objects that make up this applicationall at once. Each of these other performance attribute groups is represented by a row in this table (orother type of view). The status for an attribute group reflects the result of the last attempt to collect data


for that attribute group, which allows you to see whether the agent is performing correctly. Unlike otherattribute groups, the Performance Object Status attribute group does not reflect the state of the monitoredapplication. This attribute group is most often used to determine why data is not available for one of theperformance attribute groups.Historical group


The following list contains information about each attribute in the Performance Object Statusattribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPQuery Name attribute: This attribute is a key attribute.

DescriptionThe name of the attribute group.

TypeString

Warehouse nameQUERY_NAME or ATTRGRP

Object Name attributeDescription

The name of the performance object.Type


OBJECT_NAME or OBJNAMEObject Type attribute

DescriptionThe type of the performance object.

TypeInteger with enumerated values. The strings are displayed in the Tivoli EnterprisePortal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v WMI (0)v PERFMON (1)v WMI ASSOCIATION GROUP (2)v JMX (3)v SNMP (4)v SHELL COMMAND (5)v JOINED GROUPS (6)v CIMOM (7)


v CUSTOM (8)v ROLLUP DATA (9)v WMI REMOTE DATA (10)v LOG FILE (11)v JDBC (12)v CONFIG DISCOVERY (13)v NT EVENT LOG (14)v FILTER (15)v SNMP EVENT (16)v PING (17)v DIRECTOR DATA (18)v DIRECTOR EVENT (19)v SSH REMOTE SHELL COMMAND (20)


Warehouse nameOBJECT_TYPE or OBJTYPE

Object Status attributeDescription

The status of the performance object.Type

Integer with enumerated values. The strings are displayed in the Tivoli EnterprisePortal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v ACTIVE (0)v INACTIVE (1)


Warehouse nameOBJECT_STATUS or OBJSTTS

Error Code attributeDescription

The error code that is associated with the query.Type

Integer with enumerated values. The strings are displayed in the Tivoli EnterprisePortal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v NO ERROR (0)v GENERAL ERROR (1)v OBJECT NOT FOUND (2)v COUNTER NOT FOUND (3)v NAMESPACE ERROR (4)v OBJECT CURRENTLY UNAVAILABLE (5)v COM LIBRARY INIT FAILURE (6)v SECURITY INIT FAILURE (7)v PROXY SECURITY FAILURE (9)v NO INSTANCES RETURNED (10)v ASSOCIATOR QUERY FAILED (11)v REFERENCE QUERY FAILED (12)v NO RESPONSE RECEIVED (13)v CANNOT FIND JOINED QUERY (14)v CANNOT FIND JOIN ATTRIBUTE IN QUERY 1 RESULTS (15)v CANNOT FIND JOIN ATTRIBUTE IN QUERY 2 RESULTS (16)v QUERY 1 NOT A SINGLETON (17)v QUERY 2 NOT A SINGLETON (18)


v NO INSTANCES RETURNED IN QUERY 1 (19)v NO INSTANCES RETURNED IN QUERY 2 (20)v CANNOT FIND ROLLUP QUERY (21)v CANNOT FIND ROLLUP ATTRIBUTE (22)v FILE OFFLINE (23)v NO HOSTNAME (24)v MISSING LIBRARY (25)v ATTRIBUTE COUNT MISMATCH (26)v ATTRIBUTE NAME MISMATCH (27)v COMMON DATA PROVIDER NOT STARTED (28)v CALLBACK REGISTRATION ERROR (29)v MDL LOAD ERROR (30)v AUTHENTICATION FAILED (31)v CANNOT RESOLVE HOST NAME (32)v SUBNODE UNAVAILABLE (33)v SUBNODE NOT FOUND IN CONFIG (34)v ATTRIBUTE ERROR (35)v CLASSPATH ERROR (36)v CONNECTION FAILURE (37)v FILTER SYNTAX ERROR (38)v FILE NAME MISSING (39)v SQL QUERY ERROR (40)v SQL FILTER QUERY ERROR (41)v SQL DB QUERY ERROR (42)v SQL DB FILTER QUERY ERROR (43)v PORT OPEN FAILED (44)v ACCESS DENIED (45)v TIMEOUT (46)v NOT IMPLEMENTED (47)v REQUESTED A BAD VALUE (48)v RESPONSE TOO BIG (49)v GENERAL RESPONSE ERROR (50)v SCRIPT NONZERO RETURN (51)v SCRIPT NOT FOUND (52)v SCRIPT LAUNCH ERROR (53)v CONF FILE DOES NOT EXIST (54)v CONF FILE ACCESS DENIED (55)v INVALID CONF FILE (56)v EIF INITIALIZATION FAILED (57)v CANNOT OPEN FORMAT FILE (58)v FORMAT FILE SYNTAX ERROR (59)v REMOTE HOST UNAVAILABLE (60)v EVENT LOG DOES NOT EXIST (61)v PING FILE DOES NOT EXIST (62)v NO PING DEVICE FILES (63)v PING DEVICE LIST FILE MISSING (64)v SNMP MISSING PASSWORD (65)v DISABLED (66)v URLS FILE NOT FOUND (67)v XML PARSE ERROR (68)v NOT INITIALIZED (69)v ICMP SOCKETS FAILED (70)v DUPLICATE CONF FILE (71)v KUB SIEBEL VERSION NOT DEFINED (1001)v KUB SIEBEL GATEWAY NOT DEFINED (1002)v KUB SIEBEL ADMINID NOT DEFINED (1003)


v KUB SIEBEL ADMINPASSWORD NOT DEFINED (1004)v KUB SIEBEL ENTERPRISE NOT DEFINED (1005)v KUB SIEBEL SERVERNAME NOT DEFINED (1006)v KUB SIEBEL INSTALL ROOT OR KUB SIEBEL GATEWAY NS ROOT OR

BOTH MUST BE DEFINED (1007)v DEFINE ALL OR NONE KUB SIEBEL INSTALL ROOT KUB SIEBEL

ENTERPRISE KUB SIEBEL SERVER NAME (1008)v KUB SIEBEL INSTALL ROOT MUST SPECIFY DISK LETTER (1009)v KUB SIEBEL GATEWAY NS ROOT MUST SPECIFY DISK LETTER (1010)v KUB SIEBEL INSTALL ROOT DOES NOT EXIST (1011)v KUB SIEBEL GATEWAY NS ROOT DOES NOT EXIST (1012)v KUB SIEBEL SERVER MONITORING DISABLED (1013)v KUB SIEBEL GATEWAY NS MONITORING DISABLED (1014)v KUB NOT APPLICABLE FOR GATEWAY ONLY CONFIGURATION (1015)v KUB NOT APPLICABLE FOR SIEBEL SERVER ONLY CONFIGURATION

(1016)v KUB MISSING VARIABLE (1017)v KUB DISABLED STATE (1018)v KUB PATH NOT DEFINED (1019)v UNABLE TO OPEN FILE (1020)v UNABLE TO PARSE FILE (1021)v UNABLE TO PROCESS DATA FOR THE AG (1022)v HANDLE NOT RECOGNIZED (1023)v DIRECTORY STRUCTURE COULD NOT BE CREATED (1024)v SIEBEL ERROR CODE SBL DBC 00101 (10101)v SIEBEL ERROR CODE SBL DBC 00103 (10103)v SIEBEL ERROR CODE SBL DBC 00104 (10104)v SIEBEL ERROR CODE SBL DBC 00105 (10105)v SIEBEL ERROR CODE SBL DBC 00106 (10106)v SIEBEL ERROR CODE SBL DBC 00107 (10107)v SIEBEL ERROR CODE SBL DBC 00108 (10108)v SIEBEL ERROR CODE SBL DBC 00111 (10111)v SIEBEL ERROR CODE SBL DBC 00112 (10112)v SIEBEL ERROR CODE SBL DAT 00477 (20477)v SIEBEL ERROR CODE SBL ADM 05006 (35006)v SIEBEL ERROR CODE SBL ADM 08102 (38102)v SIEBEL ERROR CODE SBL ADM 08300 (38300)v SIEBEL ERROR CODE SBL ADM 09050 (39050)v SIEBEL ERROR CODE SBL ADM 09051 (39051)v SIEBEL ERROR CODE SBL ADM 09052 (39052)v SIEBEL ERROR CODE SBL ADM 09053 (39053)v SIEBEL ERROR CODE SBL ADM 09054 (39054)v SIEBEL ERROR CODE SBL ADM 09153 (39153)v SIEBEL ERROR CODE SBL ADM 09204 (39204)v SIEBEL ERROR CODE SBL ADM 09205 (39205)v SIEBEL ERROR CODE SBL ADM 09210 (39210)v SIEBEL ERROR CODE SBL ADM 09211 (39211)v SIEBEL ERROR CODE SBL ADM 09350 (39350)v SIEBEL ERROR CODE SBL ADM 09351 (39351)v SIEBEL ERROR CODE SBL ADM 09352 (39352)v SIEBEL ERROR CODE SBL ADM 09354 (39354)v SIEBEL ERROR CODE SBL SVR 00026 (40026)v SIEBEL ERROR CODE SBL SVR 00028 (40028)v SIEBEL ERROR CODE SBL SVR 00051 (40051)v SIEBEL ERROR CODE SBL SVR 00052 (40052)v SIEBEL ERROR CODE SBL SVR 01014 (41014)


v SIEBEL ERROR CODE SBL SVR 01015 (41015)v SIEBEL ERROR CODE SBL SVR 01031 (41031)v SIEBEL ERROR CODE SBL SVR 01042 (41042)v SIEBEL ERROR CODE SBL SVR 01045 (41045)v SIEBEL ERROR CODE SBL SVR 01051 (41051)v SIEBEL ERROR CODE SBL SVR 09127 (49127)v SIEBEL ERROR CODE SBL SVR 09124 (49124)v SIEBEL ERROR CODE SBL SVR 09149 (49149)v SIEBEL ERROR CODE SBL SVR 00107 (40107)


Warehouse nameERROR_CODE or ERRCODE

Server Log attribute groupThis attribute group comprises information from the log of the Siebel Server. It is used only for Siebelversion 7.7 or later.Historical group


The following list contains information about each attribute in the Server Log attribute group:Node attribute: This attribute is a key attribute.


TypeString




StringSource



TypeString




StringSource


DescriptionThe event subtype.

TypeString





StringSource



TypeString




StringSource



TypeString




StringSource

The source for this attribute is derived: getenv("KUB_SIEBEL_GATEWAY").Enterprise Name attribute


TypeString




StringSource

The source for this attribute is derived: getenv("KUB_SIEBEL_SERVERNAME").

Server Log Pre77 attribute groupThis attribute group comprises information from the log of the Siebel Server. It is used only for versionsprior to Siebel version 7.7.


Historical groupThis attribute group is not eligible for use with Tivoli Data Warehouse.

Attribute descriptionsThe following list contains information about each attribute in the Server Log Pre77 attributegroup:Node attribute: This attribute is a key attribute.


TypeString




StringSource



TypeString




StringSource


DescriptionThe event sub type.

TypeString




StringSource

The source for this attribute is Log File Data.Logs Timestamp attribute

DescriptionThe Siebel log time stamp.

TypeString


Log Message attribute



TypeString


Siebel Server attribute groupThis attribute group contains general information about the Siebel Server.Historical group


The following list contains information about each attribute in the Siebel Server attribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPServer Name attribute: This attribute is a key attribute.

DescriptionThe Siebel Server name.

TypeString


Host name attributeDescription

The host name or IP address of the workstation where the server is running.Type


HOST_NAMEInstall Dir attribute

DescriptionThe name of the directory where this server is installed.

TypeString

Warehouse nameINSTALL_DIR or ID

Server State attribute


DescriptionThe Siebel Application Server state. (Starting Up, Running, Shutting Down,Shutdown, Not Available, Connect Failed, Handshake Failed, Login Failed,Disconnected.)

TypeString

Warehouse nameSERVER_STATE or SS

Start Time attributeDescription



START_TIMEEnd Time attribute


TypeString

Warehouse nameEND_TIME

Server Status attributeDescription

The status of the server.Type


SERVER_STATUS or SS0Running Task Count attribute: This attribute is a key attribute.

DescriptionThe number of running tasks in this Siebel Application Server.



Warehouse nameACTIVE_TASK_COUNT or ATC

Application Server Connection Status attribute: This attribute is a key attribute.Description

Indicates whether the Siebel agent has successfully queried Siebel CRM. If thevalue is False, the Siebel CRM might be down or the Siebel agent is notconfigured correctly.

TypeString

Warehouse nameCONNECTION_STATUS or CS

Updated Start Time attributeDescription

The time when the server was started.


TypeTimestamp

Warehouse nameUPDATED_START_TIME or UST

Updated End Time attributeDescription

The time when the server was stopped.Type

TimestampWarehouse name

UPDATED_END_TIME or UETGateway Name attribute

DescriptionThe name of the Siebel Gateway.

TypeString

SourceThe source for this attribute is derived: getenv("KUB_SIEBEL_GATEWAY").


Enterprise Name attributeDescription

The name of the Siebel Enterpise.Type

StringSource

The source for this attribute is derived: getenv("KUB_SIEBEL_ENTERPRISE").Warehouse name

ENTERPRISE_NAME or EN

Siebel Statistics attribute groupThis attribute group consists of detailed information gathered through execution of the Siebel srvrmgr'list statistics' CLI. Additional information can be found in the Siebel System Monitoring and DiagnosticGuide.Historical group


The following list contains information about each attribute in the Siebel Statistics attribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource

The source for this attribute is the agent.



Statistic attribute: This attribute is a key attribute.Description

The name of the Siebel statistic.Type


STATISTICStatistic Alias attribute

DescriptionThe alias name of the Siebel statistic.

TypeString

Warehouse nameSTATISTIC_ALIAS or SA

Subsystem attributeDescription

The Siebel subsystem that the Siebel statistic applies to.Type


SD_SUBSYSTEM or SSSiebel Server Name attribute: This attribute is a key attribute.

DescriptionThe Siebel Server name that the statistic applies to.

TypeString


Current Value attributeDescription

The current value of the Siebel statistic.Type

Real number (64-bit gauge) with eight decimal places of precision withenumerated values. The strings are displayed in the Tivoli Enterprise Portal. Thewarehouse and queries return the values that are shown in parentheses. Thefollowing values are defined:v Value Exceeds Maximum (9223372036854775807)v Value Exceeds Minimum (-9223372036854775808)


Warehouse nameCURRENT_VALUE or CV

Description attributeDescription

The description of the Siebel statistic.Type


SD_DESCRIPTION or SD


Statistic Details attribute groupThis attribute group contains detailed information gathered through execution of the Siebel srvrmgr 'liststatistics' command. Additional information can be found in the Siebel System Monitoring and DiagnosticGuide.Historical group


The following list contains information about each attribute in the Statistic Details attributegroup:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPAverage Connect Time attribute

DescriptionAverage connect time for Object Manager sessions (in seconds).

TypeReal number (32-bit gauge) with two decimal places of precision withenumerated values. The strings are displayed in the Tivoli Enterprise Portal. Thewarehouse and queries return the values that are shown in parentheses. Thefollowing values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)


Warehouse nameAVERAGE_CONNECT_TIME or SDTL2

Average OOB Component Time attributeDescription

Average component time for Object Manager sessions (in seconds).Type

Real number (32-bit gauge) with two decimal places of precision withenumerated values. The strings are displayed in the Tivoli Enterprise Portal. Thewarehouse and queries return the values that are shown in parentheses. Thefollowing values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)



Warehouse nameAVERAGE_OOB_COMPONENT_TIME or SDTL3

Average OOB Queue Size attributeDescription

Average size of queues for Object Manager sessions (in bytes).Type



Warehouse nameAVERAGE_OOB_QUEUE_SIZE or SDTL4

Average Reply Size attributeDescription

Average size of reply messages (in bytes).Type



Warehouse nameAVERAGE_REPLY_SIZE or SDTL5

Average Request Size attributeDescription

Average size of request messages (in bytes).Type



Warehouse nameAVERAGE_REQUEST_SIZE or SDTL6

Average Requests Per Session attributeDescription

Average number of requests per Object Manager session.Type




Warehouse nameAVERAGE_REQUESTS_PER_SESSION or SDTL7

Average Response Time attributeDescription

Average response time of Object Manager sessions (in milliseconds).Type



Warehouse nameAVERAGE_RESPONSE_TIME or SDTL8

Average Think Time attributeDescription

Average end-user think time between requests (in seconds).Type



Warehouse nameAVERAGE_THINK_TIME or SDTL9

Avg SQL Execute Time attributeDescription

Average time for SQL execute operations (in seconds).Type



Warehouse nameAVG_SQL_EXECUTE_TIME or SDTL10

Avg SQL Fetch Time attributeDescription

Average time for SQL fetch operations (in seconds).Type

Real number (32-bit gauge) with two decimal places of precision withenumerated values. The strings are displayed in the Tivoli Enterprise Portal. Thewarehouse and queries return the values that are shown in parentheses. Thefollowing values are defined:


v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)


Warehouse nameAVG_SQL_FETCH_TIME or SDTL11

Avg SQL Parse Time attributeDescription

Average time for SQL parse operations (in seconds).Type



Warehouse nameAVG_SQL_PARSE_TIME or SDTL12

CPU Time attributeDescription

Total CPU time for component tasks (in seconds).Type



Warehouse nameCPU_TIME or SDTL13

Completed Transactions from PIM attributeDescription

Number of completed transactions from the PIM Server.Type



Warehouse nameCOMPLETED_TRANSACTIONS_FROM_PIM or SDTL14

Completed Transactions from Siebel attributeDescription

Number of completed transactions from the Siebel Server.Type

Real number (32-bit gauge) with two decimal places of precision with


enumerated values. The strings are displayed in the Tivoli Enterprise Portal. Thewarehouse and queries return the values that are shown in parentheses. Thefollowing values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)


Warehouse nameCOMPLETED_TRANSACTIONS_FROM_SIEBEL or SDTL15

Data Cursor Cache CPU attributeDescription

Total CPU time spent on creating data cursor objects in cache (in seconds).Type



Warehouse nameDATA_CURSOR_CACHE_CPU or SDTL16

Data Cursor Cache Hits attributeDescription

Number of SQL data cursor cache hits.Type



Warehouse nameDATA_CURSOR_CACHE_HITS or SDTL17

Data Cursor Cache Memory attributeDescription

Total memory used for creating data cursor objects in cache (in bytes).Type



Warehouse nameDATA_CURSOR_CACHE_MEMORY or SDTL18

Data Cursor Cache Misses attributeDescription

Number of SQL data cursor cache misses.




Warehouse nameDATA_CURSOR_CACHE_MISSES or SDTL19

Data Cursor Cache Objects attributeDescription

Number of objects that are currently in the data cursor cache.Type



Warehouse nameDATA_CURSOR_CACHE_OBJECTS or SDTL20

EAI Receiver Total Messages Processed attributeDescription

Total number of messages processed by the EAI Receiver.Type



Warehouse nameEAI_RECEIVER_TOTAL_MESSAGES_PROCESSED or SDTL21

Elapsed Time attributeDescription

Total elapsed (running) time for component tasks (in seconds).Type



Warehouse nameELAPSED_TIME or SDTL22

Events Processed attribute


DescriptionTotal number of events processed.



Warehouse nameEVENTS_PROCESSED or SDTL23

Events Processed Rate attributeDescription

Rate of processing the events.Type



Warehouse nameEVENTS_PROCESSED_RATE or SDTL24

FDR Avg time between aging attributeDescription

Average amount of time elapsed between Flight Data Recorder statistics update(in seconds).



Warehouse nameFDR_AVG_TIME_BETWEEN_AGING or SDTL25

FDR Buffer Life in seconds attributeDescription

Amount of time that has elapsed since buffer was created (in seconds).Type




Warehouse nameFDR_BUFFER_LIFE_IN_SECONDS or SDTL26

FDR Buffer Wraps attributeDescription

Number of buffer wraps.Type



Warehouse nameFDR_BUFFER_WRAPS or SDTL27

Failed Transactions from PIM attributeDescription

Number of failed transactions from the PIM server.Type



Warehouse nameFAILED_TRANSACTIONS_FROM_PIM or SDTL28

Failed Transactions from Siebel attributeDescription

Number of failed transactions from the Siebel Server.Type



Warehouse nameFAILED_TRANSACTIONS_FROM_SIEBEL or SDTL29

Global Data Cursor Cache CPU attributeDescription

Total CPU time spent on creating global data cursor objects in cache (in seconds).Type




Warehouse nameGLOBAL_DATA_CURSOR_CACHE_CPU or SDTL30

Global Data Cursor Cache Hits attributeDescription

Number of global data cursor cache hits.Type



Warehouse nameGLOBAL_DATA_CURSOR_CACHE_HITS or SDTL31

Global Data Cursor Cache Memory attributeDescription

Total memory used for creating global data cursor objects in cache (in bytes).Type



Warehouse nameGLOBAL_DATA_CURSOR_CACHE_MEMORY or SDTL32

Global Data Cursor Cache Misses attributeDescription

Number of global data cursor cache misses.Type



Warehouse nameGLOBAL_DATA_CURSOR_CACHE_MISSES or SDTL33

Global Data Cursor Cache Objects attributeDescription

Number of objects that are currently in the global data cursor cache.Type

Real number (32-bit gauge) with two decimal places of precision withenumerated values. The strings are displayed in the Tivoli Enterprise Portal. Thewarehouse and queries return the values that are shown in parentheses. Thefollowing values are defined:


v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)


Warehouse nameGLOBAL_DATA_CURSOR_CACHE_OBJECTS or SDTL34

Maximum OOB Component Time attributeDescription

Maximum time used by the Object Manager component.Type



Warehouse nameMAXIMUM_OOB_COMPONENT_TIME or SDTL35

Maximum Peak Memory Usage attributeDescription

Maximum amount of memory used by task. Rolls up differently fromMinPeakMemory.



Warehouse nameMAXIMUM_PEAK_MEMORY_USAGE or SDTL36

Minimum Peak Memory Usage attributeDescription

Minimum amount of memory used by task. Rolls up differently fromMaxPeakMemory.



Warehouse nameMINIMUM_PEAK_MEMORY_USAGE or SDTL37

Num of DBConn Retries attributeDescription

Number of retries because of loss of database connections.




Warehouse nameNUM_OF_DBCONN_RETRIES or SDTL38

Num of DLRbk Retries attributeDescription

Number of retries because of deadlock rollbacks.Type



Warehouse nameNUM_OF_DLRBK_RETRIES or SDTL39

Num of Exhausted Retries attributeDescription

Number of times that all retries are exhausted.Type



Warehouse nameNUM_OF_EXHAUSTED_RETRIES or SDTL40

Number of Component Crashes attributeDescription

Number of times that a process of the component has failed.Type



Warehouse nameNUMBER_OF_COMPONENT_CRASHES or SDTL41

Number of Component Restarts attribute


DescriptionNumber of times that a process of the component has restarted.



Warehouse nameNUMBER_OF_COMPONENT_RESTARTS or SDTL42

Number of Errors attributeDescription

Total number of level 0 and level 1 errors.Type



Warehouse nameNUMBER_OF_ERRORS or SDTL43

Number of SQL Executes attributeDescription

Total number of SQL execute operations.Type



Warehouse nameNUMBER_OF_SQL_EXECUTES or SDTL44

Number of SQL Fetches attributeDescription

Total number of SQL fetch operations.Type




Warehouse nameNUMBER_OF_SQL_FETCHES or SDTL45

Number of SQL Parses attributeDescription

Total number of SQL parse operations.Type



Warehouse nameNUMBER_OF_SQL_PARSES or SDTL46

Number of Sleeps attributeDescription

Total number of sleeps for component tasks.Type



Warehouse nameNUMBER_OF_SLEEPS or SDTL47

Number of object rows assigned attributeDescription

The cumulative number of records assigned by this component since the serverwas started.



Warehouse nameNUMBER_OF_OBJECT_ROWS_ASSIGNED or SDTL48

Object Manager Errors attributeDescription

Number of errors encountered during the Object Manager session.Type

Real number (32-bit gauge) with two decimal places of precision withenumerated values. The strings are displayed in the Tivoli Enterprise Portal. Thewarehouse and queries return the values that are shown in parentheses. Thefollowing values are defined:v Value Exceeds Maximum (2147483647)


v Value Exceeds Minimum (-2147483648)


Warehouse nameOBJECT_MANAGER_ERRORS or SDTL49

PSP Cache Hit Total attributeDescription

Total PSP (Product Selection and Pricing) cached query results used.Type



Warehouse namePSP_CACHE_HIT_TOTAL or SDTL50

PSP Cache Miss Total attributeDescription

Total PSP (Product Selection and Pricing) database queries that are not found incache.



Warehouse namePSP_CACHE_MISS_TOTAL or SDTL51

Reply Messages attributeDescription

Number of reply messages sent by the server.Type



Warehouse nameREPLY_MESSAGES or SDTL52

Request Messages attributeDescription

Number of request messages received by the server.Type





Warehouse nameREQUEST_MESSAGES or SDTL53

SQL Cursor Cache Hits attributeDescription

Number of SQL cursor cache hits.Type



Warehouse nameSQL_CURSOR_CACHE_HITS or SDTL54

SQL Cursor Cache Misses attributeDescription

Number of SQL cursor cache misses.Type



Warehouse nameSQL_CURSOR_CACHE_MISSES or SDTL55

SQL Cursor Total Cpu attributeDescription

Total CPU time spent on creating SQL cursor objects in cache (in seconds).Type



Warehouse nameSQL_CURSOR_TOTAL_CPU or SDTL56

SQL Cursor Total Mem attributeDescription

Total memory used for creating SQL cursor objects in cache (in bytes).




Warehouse nameSQL_CURSOR_TOTAL_MEM or SDTL57

SQL Cursor Total Objects attributeDescription

Total number of SQL cursor objects in cache.Type



Warehouse nameSQL_CURSOR_TOTAL_OBJECTS or SDTL58

SQL Execute Time attributeDescription

Total elapsed time for SQL execute operations (in seconds).Type



Warehouse nameSQL_EXECUTE_TIME or SDTL59

SQL Fetch Time attributeDescription

Total elapsed time for SQL fetch operations (in seconds).Type



Warehouse nameSQL_FETCH_TIME or SDTL60

SQL Object Cache CPU attribute


DescriptionTotal CPU time spent on creating SQL objects in cache (in seconds).



Warehouse nameSQL_OBJECT_CACHE_CPU or SDTL61

SQL Object Cache Hits attributeDescription

Number of SQL object cache hits.Type



Warehouse nameSQL_OBJECT_CACHE_HITS or SDTL62

SQL Object Cache Memory attributeDescription

Total memory used for creating SQL objects in cache (in bytes).Type



Warehouse nameSQL_OBJECT_CACHE_MEMORY or SDTL63

SQL Object Cache Misses attributeDescription

Number of SQL object cache misses.Type




Warehouse nameSQL_OBJECT_CACHE_MISSES or SDTL64

SQL Object Cache Objects attributeDescription

Number of objects currently in the SQL object cache.Type



Warehouse nameSQL_OBJECT_CACHE_OBJECTS or SDTL65

SQL Parse Time attributeDescription

Total elapsed time for SQL parse operations (in seconds).Type



Warehouse nameSQL_PARSE_TIME or SDTL66

SearchEvents Processed attributeDescription

Total number of records processed during indexing.Type



Warehouse nameSEARCHEVENTS_PROCESSED or SDTL67

SearchEvents Processed Rate attributeDescription

Rate at which records are processed during indexing.Type




Warehouse nameSEARCHEVENTS_PROCESSED_RATE or SDTL68

Siebel Adapter Total Query Calls attributeDescription

Total number of query calls made to the Siebel Adapter.Type



Warehouse nameSIEBEL_ADAPTER_TOTAL_QUERY_CALLS or SDTL69

Siebel Adapter Total Query Size attributeDescription

Total cumulative size of output property sets (in KB) for all queries.Type



Warehouse nameSIEBEL_ADAPTER_TOTAL_QUERY_SIZE or SDTL70

Siebel Adapter Total Sync Size attributeDescription

Total cumulative size of input property sets (in KB) for all non-query calls (suchas synchronize, upsert, update, or insert)



Warehouse nameSIEBEL_ADAPTER_TOTAL_SYNC_SIZE or SDTL71

Siebel Adapter Total Sync/Upsert Calls attributeDescription

Total Number of non-query calls (such as synchronize, upsert, update, or insert)made to the Siebel Adapter.

TypeReal number (32-bit gauge) with two decimal places of precision with




Warehouse nameSIEBEL_ADAPTER_TOTAL_SYNC_UPSERT_CALLS or SDTL72

Sleep Time attributeDescription

Total amount of sleep time for component tasks (in seconds).Type



Warehouse nameSLEEP_TIME or SDTL73

Tasks Exceeding Configured Capacity attributeDescription

Number of tasks that exceeded configured capacity.Type



Warehouse nameTASKS_EXCEEDING_CONFIGURED_CAPACITY or SDTL74

Tests Attempted attributeDescription

Number of tests that were started.Type



Warehouse nameTESTS_ATTEMPTED or SDTL75

Tests Failed attributeDescription

Number of tests that failed.




Warehouse nameTESTS_FAILED or SDTL76

Tests Successful attributeDescription

Number of tests that were successful.Type



Warehouse nameTESTS_SUCCESSFUL or SDTL77

Total Database Response Time attributeDescription

Total Database Response/Processing Time (milliseconds)Type



Warehouse nameTOTAL_DATABASE_RESPONSE_TIME or SDTL78

Total Reply Size attributeDescription

Total size of reply messages (in bytes).Type



Warehouse nameTOTAL_REPLY_SIZE or SDTL79

Total Request Size attribute


DescriptionTotal size of request messages (in bytes).



Warehouse nameTOTAL_REQUEST_SIZE or SDTL80

Total Response Time attributeDescription

Total response time of the Object Manager (in milliseconds).Type



Warehouse nameTOTAL_RESPONSE_TIME or SDTL81

Total Tasks attributeDescription

Total number of tasks completed for server components.Type



Warehouse nameTOTAL_TASKS or SDTL82

Total Think Time attributeDescription

Total end-user think time (in seconds).Type




Warehouse nameTOTAL_THINK_TIME or SDTL83

Total XML Converter Size of Input Buffer attributeDescription

Total cumulative size of input buffer (in KB).Type



Warehouse nameTOTAL_XML_CONVERTER_SIZE_OF_INPUT_BUFFER or SDTL84

Total XML Converter Size of Output Buffer attributeDescription

Total cumulative size of output buffer (in KB).Type



Warehouse nameTOTAL_XML_CONVERTER_SIZE_OF_OUTPUT_BUFFER or SDTL85

Total XML Generator Calls attributeDescription

Total number of XML Generator Calls.Type



Warehouse nameTOTAL_XML_GENERATOR_CALLS or SDTL86

Total XML Parser Calls attributeDescription

Total number of XML Parser Calls.Type




Warehouse nameTOTAL_XML_PARSER_CALLS or SDTL87

Transactions form Siebel in Progress attributeDescription

Number of in process transactions from Siebel.Type



Warehouse nameTRANSACTIONS_FORM_SIEBEL_IN_PROGRESS or SDTL88

Transactions from PIM in Progress attributeDescription

Number of in process transactions from PIM.Type



Warehouse nameTRANSACTIONS_FROM_PIM_IN_PROGRESS or SDTL89

Statistics AsgnSubsys attribute groupThis attribute group contains detailed information that is gathered on AsgnSubsys through execution ofthe Siebel srvrmgr 'list statistics' command. Additional information can be found in the Siebel SystemMonitoring and Diagnostic Guide.Historical group


The following list contains information about each attribute in the Statistics AsgnSubsys attributegroup:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE


The local time at the agent when the data was collected.


TypeString



Number of object rows assigned attributeDescription

Cumulative number of records assigned by this component since the server wasstarted.



SourceThe source for this attribute is Filtered data - Number_of_object_rows_assigned.

Warehouse nameNUMBER_OF_OBJECT_ROWS_ASSIGNED or SIEBDTL48

Statistics CommInboundProcessor attribute groupThis attribute group contains detailed information gathered on CommInboundProcessor throughexecution of the Siebel srvrmgr 'list statistics' command. Additional information can be found in theSiebel System Monitoring and Diagnostic Guide.Historical group


The following list contains information about each attribute in the StatisticsCommInboundProcessor attribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPEvents Processed attribute

DescriptionTotal number of events processed.





SourceThe source for this attribute is Filtered data - Events_Processed.

Warehouse nameEVENTS_PROCESSED or SIEBDTL23

Events Processed Rate attributeDescription

Rate of processing the events.Type



SourceThe source for this attribute is Filtered data - Events_Processed_Rate.

Warehouse nameEVENTS_PROCESSED_RATE or SIEBDTL24

Statistics EAISubsys attribute groupThis attribute group contains detailed information that is gathered on EAISubsys through execution ofthe Siebel srvrmgr 'list statistics' command. Additional information can be found in the Siebel SystemMonitoring and Diagnostic Guide.Historical group


The following list contains information about each attribute in the Statistics EAISubsys attributegroup:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPEAI Receiver Total Messages Processed attribute


DescriptionTotal number of messages processed by the EAI Receiver.



SourceThe source for this attribute is Filtered data -EAI_Receiver_Total_Messages_Processed.

Warehouse nameEAI_RECEIVER_TOTAL_MESSAGES_PROCESSED or SIEBDTL21

Siebel Adapter Total Query Calls attributeDescription

Total number of query calls made to the Siebel Adapter.Type



SourceThe source for this attribute is Filtered data - Siebel_Adapter_Total_Query_Calls.

Warehouse nameSIEBEL_ADAPTER_TOTAL_QUERY_CALLS or SIEBDTL69

Siebel Adapter Total Query Size attributeDescription

Total cumulative size of output property sets (in KB) for all queries.Type



SourceThe source for this attribute is Filtered data - Siebel_Adapter_Total_Query_Size.

Warehouse nameSIEBEL_ADAPTER_TOTAL_QUERY_SIZE or SIEBDTL70

Siebel Adapter Total Sync Size attributeDescription

Total cumulative size of input property sets (in KB) for all non-query calls(synchronize, upsert, update, or insert).

TypeInteger (32-bit gauge) with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return the values that areshown in parentheses. The following values are defined:v Value Exceeds Maximum (2147483647)




SourceThe source for this attribute is Filtered data - Siebel_Adapter_Total_Sync_Size.

Warehouse nameSIEBEL_ADAPTER_TOTAL_SYNC_SIZE or SIEBDTL71

Siebel Adapter Total Sync/Upsert Calls attributeDescription

Total number of non-query calls (synchronize, upsert, update or insert) made tothe Siebel Adapter.



SourceThe source for this attribute is Filtered data -Siebel_Adapter_Total_Sync_Upsert_Calls.

Warehouse nameSIEBEL_ADAPTER_TOTAL_SYNC_UPSERT_CALLS or SIEBDTL72

Statistics FlightDataRecorder attribute groupThis attribute group contains detailed information that is gathered on FlightDataRecorder throughexecution of the Siebel srvrmgr 'list statistics' command. Additional information can be found in theSiebel System Monitoring and Diagnostic Guide.Historical group


The following list contains information about each attribute in the Statistics FlightDataRecorderattribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPFDR Avg time between aging attribute


DescriptionAverage amount of time elapsed between Flight Data Recorder statistics update(in seconds).



SourceThe source for this attribute is Filtered data - FDR_Avg_time_between_aging.

Warehouse nameFDR_AVG_TIME_BETWEEN_AGING or SIEBDTL25

FDR Buffer Life in seconds attributeDescription

Amount of time that has elapsed since the buffer was created (in seconds).Type



SourceThe source for this attribute is Filtered data - FDR_Buffer_Life_in_seconds.

Warehouse nameFDR_BUFFER_LIFE_IN_SECONDS or SIEBDTL26

FDR Buffer Wraps attributeDescription

Number of buffer wraps.Type



SourceThe source for this attribute is Filtered data - FDR_Buffer_Wraps.

Warehouse nameFDR_BUFFER_WRAPS or SIEBDTL27

Statistics InfraCore attribute groupThis attribute group contains detailed information that is gathered on InfraCore through execution of theSiebel srvrmgr 'list statistics' command. Additional information can be found in the Siebel SystemMonitoring and Diagnostic Guide.Historical group



Attribute descriptionsThe following list contains information about each attribute in the Statistics InfraCore attributegroup:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPCPU Time attribute

DescriptionTotal CPU time for component tasks (in seconds).



SourceThe source for this attribute is Filtered data - CPU_Time.

Warehouse nameCPU_TIME or SIEBDTL13


Total elapsed (running) time for component tasks (in seconds).Type



SourceThe source for this attribute is Filtered data - Elapsed_Time.

Warehouse nameELAPSED_TIME or SIEBDTL22

Maximum Peak Memory Usage attribute


DescriptionMaximum amount of peak memory that is used by task.



SourceThe source for this attribute is Filtered data - Maximum_Peak_Memory_Usage.

Warehouse nameMAXIMUM_PEAK_MEMORY_USAGE or SIEBDTL36

Minimum Peak Memory Usage attributeDescription

Minimum amount of peak memory that is used by task.Type



SourceThe source for this attribute is Filtered data - Minimum_Peak_Memory_Usage.

Warehouse nameMINIMUM_PEAK_MEMORY_USAGE or SIEBDTL37

Number of Component Crashes attributeDescription

Number of times that a process of the component has failed.Type



SourceThe source for this attribute is Filtered data - Number_of_Component_Crashes.

Warehouse nameNUMBER_OF_COMPONENT_CRASHES or SIEBDTL41

Number of Component Restarts attributeDescription

Number of times that a process of the component has restarted.Type




SourceThe source for this attribute is Filtered data - Number_of_Component_Restarts.

Warehouse nameNUMBER_OF_COMPONENT_RESTARTS or SIEBDTL42

Number of Errors attributeDescription

Total number of level 0 and level 1 errors.Type



SourceThe source for this attribute is Filtered data - Number_of_Errors.

Warehouse nameNUMBER_OF_ERRORS or SIEBDTL43

Number of Sleeps attributeDescription

Total number of sleeps for component tasks.Type



SourceThe source for this attribute is Filtered data - Number_of_Sleeps.

Warehouse nameNUMBER_OF_SLEEPS or SIEBDTL47

Sleep Time attributeDescription

Total amount of sleep time for component tasks (in seconds).Type



SourceThe source for this attribute is Filtered data - Sleep_Time.

Warehouse nameSLEEP_TIME or SIEBDTL73

Tasks Exceeding Configured Capacity attributeDescription

Number of tasks stated that exceeded configured capacity.




SourceThe source for this attribute is Filtered data -Tasks_Exceeding_Configured_Capacity.

Warehouse nameTASKS_EXCEEDING_CONFIGURED_CAPACITY or SIEBDTL74

Total Tasks attributeDescription

Total number of tasks completed for server components.Type



SourceThe source for this attribute is Filtered data - Total_Tasks.

Warehouse nameTOTAL_TASKS or SIEBDTL82



StringSource




TypeString





StringSource


SERVER_NAME or SN


Statistics InfraDatabase attribute groupThis attribute group contains detailed information that is gathered on InfraDatabase through execution ofthe Siebel srvrmgr 'list statistics' command. Additional information can be found in the Siebel SystemMonitoring and Diagnostic Guide.Historical group


The following list contains information about each attribute in the Statistics InfraDatabaseattribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPAvg SQL Execute Time attribute

DescriptionAverage time for SQL execute operations (in seconds).



SourceThe source for this attribute is Filtered data - Avg_SQL_Execute_Time.

Warehouse nameAVG_SQL_EXECUTE_TIME or SIEBDTL10

Avg SQL Fetch Time attributeDescription

Average time for SQL fetch operations (in seconds).Type




SourceThe source for this attribute is Filtered data - Avg_SQL_Fetch_Time.

Warehouse nameAVG_SQL_FETCH_TIME or SIEBDTL11

Avg SQL Parse Time attributeDescription

Average time for SQL parse operations (in seconds).Type



SourceThe source for this attribute is Filtered data - Avg_SQL_Parse_Time.

Warehouse nameAVG_SQL_PARSE_TIME or SIEBDTL12

SQL Parse Time attributeDescription

Total elapsed time for SQL parse operations (in seconds).Type



SourceThe source for this attribute is Filtered data - SQL_Parse_Time.

Warehouse nameSQL_PARSE_TIME or SIEBDTL66

Number of SQL Executes attributeDescription

Total number of SQL execute operations.Type



SourceThe source for this attribute is Filtered data - Number_of_SQL_Executes.

Warehouse nameNUMBER_OF_SQL_EXECUTES or SIEBDTL44

Number of SQL Fetches attribute


DescriptionTotal number of SQL fetch operations.



SourceThe source for this attribute is Filtered data - Number_of_SQL_Fetches.

Warehouse nameNUMBER_OF_SQL_FETCHES or SIEBDTL45

Number of SQL Parses attributeDescription

Total number of SQL parse operations.Type



SourceThe source for this attribute is Filtered data - Number_of_SQL_Parses.

Warehouse nameNUMBER_OF_SQL_PARSES or SIEBDTL46

SQL Execute Time attributeDescription

Total elapsed time for SQL execute operations (in seconds).Type



SourceThe source for this attribute is Filtered data - SQL_Execute_Time.

Warehouse nameSQL_EXECUTE_TIME or SIEBDTL59

SQL Fetch Time attributeDescription

Total elapsed time for SQL fetch operations (in seconds).Type

Real number (32-bit gauge) with two decimal places of precision withenumerated values. The strings are displayed in the Tivoli Enterprise Portal. Thewarehouse and queries return the values that are shown in parentheses. Thefollowing values are defined:v Value Exceeds Maximum (2147483647)




SourceThe source for this attribute is Filtered data - SQL_Fetch_Time.

Warehouse nameSQL_FETCH_TIME or SIEBDTL60



StringSource




TypeString





StringSource


SERVER_NAME or SN

Statistics InfraMultiThread attribute groupThis attribute group contains detailed information that is gathered on InfraMultiThread throughexecution of the Siebel srvrmgr 'list statistics' command. Additional information can be found in theSiebel System Monitoring and Diagnostic Guide.Historical group


The following list contains information about each attribute in the Statistics InfraMultiThreadattribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE

Timestamp attribute



TypeString



Average OOB Component Time attributeDescription

Average OOB Component TimeType



SourceThe source for this attribute is Filtered data - Average_OOB_Component_Time.

Warehouse nameAVERAGE_OOB_COMPONENT_TIME or SIEBDTL3

Average OOB Queue Size attributeDescription

Average OOB Queue SizeType



SourceThe source for this attribute is Filtered data - Average_OOB_Queue_Size.

Warehouse nameAVERAGE_OOB_QUEUE_SIZE or SIEBDTL4

Maximum OOB Component Time attributeDescription

Maximum OOB Component TimeType



SourceThe source for this attribute is Filtered data - Maximum_OOB_Component_Time.


Warehouse nameMAXIMUM_OOB_COMPONENT_TIME or SIEBDTL35

Statistics InfraObjMgr attribute groupThis attribute group contains detailed information that is gathered on InfraObjMgr through execution ofthe Siebel srvrmgr 'list statistics' command. Additional information can be found in the Siebel SystemMonitoring and Diagnostic Guide.Historical group


The following list contains information about each attribute in the Statistics InfraObjMgr attributegroup:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPAverage Connect Time attribute

DescriptionAverage connect time for Object Manager sessions (in seconds).



SourceThe source for this attribute is Filtered data - Average_Connect_Time.

Warehouse nameAVERAGE_CONNECT_TIME or SIEBDTL2

Average Reply Size attributeDescription

Average size of reply messages (in bytes).Type




SourceThe source for this attribute is Filtered data - Average_Reply_Size.

Warehouse nameAVERAGE_REPLY_SIZE or SIEBDTL5

Average Requests Per Session attributeDescription

Average number of requests per Object Manager session.Type



SourceThe source for this attribute is Filtered data - Average_Requests_Per_Session.

Warehouse nameAVERAGE_REQUESTS_PER_SESSION or SIEBDTL7

Average Request Size attributeDescription

Average size of request messages (in bytes).Type



SourceThe source for this attribute is Filtered data - Average_Request_Size.

Warehouse nameAVERAGE_REQUEST_SIZE or SIEBDTL6

Average Response Time attributeDescription

Average response time of the Object Manager (in milliseconds).Type



SourceThe source for this attribute is Filtered data - Average_Response_Time.

Warehouse nameAVERAGE_RESPONSE_TIME or SIEBDTL8

Average Think Time attribute


DescriptionAverage end-user think time between requests (in seconds).



SourceThe source for this attribute is Filtered data - Average_Think_Time.

Warehouse nameAVERAGE_THINK_TIME or SIEBDTL9

Data Cursor Cache CPU attributeDescription

Total CPU time spent on creating data cursor objects in cache (in seconds).Type



SourceThe source for this attribute is Filtered data - Data_Cursor_Cache_CPU.

Warehouse nameDATA_CURSOR_CACHE_CPU or SIEBDTL16

Data Cursor Cache Hits attributeDescription

Number of SQL data cursor cache hits.Type



SourceThe source for this attribute is Filtered data - Data_Cursor_Cache_Hits.

Warehouse nameDATA_CURSOR_CACHE_HITS or SIEBDTL17

Data Cursor Cache Memory attributeDescription

Total memory used for creating data cursor objects in cache (in bytes).Type




SourceThe source for this attribute is Filtered data - Data_Cursor_Cache_Memory.

Warehouse nameDATA_CURSOR_CACHE_MEMORY or SIEBDTL18

Data Cursor Cache Misses attributeDescription

Number of SQL data cursor cache misses.Type



SourceThe source for this attribute is Filtered data - Data_Cursor_Cache_Misses.

Warehouse nameDATA_CURSOR_CACHE_MISSES or SIEBDTL19

Data Cursor Cache Objects attributeDescription

Number of objects currently in the data cursor cache.Type



SourceThe source for this attribute is Filtered data - Data_Cursor_Cache_Objects.

Warehouse nameDATA_CURSOR_CACHE_OBJECTS or SIEBDTL20

Total Database Response Time attributeDescription

Total Database Response/Processing Time (in milliseconds).Type



SourceThe source for this attribute is Filtered data - Total_Database_Response_Time.

Warehouse nameTOTAL_DATABASE_RESPONSE_TIME or SIEBDTL78

Object Manager Errors attribute


DescriptionNumber of errors encountered during Object Manager session.



SourceThe source for this attribute is Filtered data - Object_Manager_Errors.

Warehouse nameOBJECT_MANAGER_ERRORS or SIEBDTL49

Global Data Cursor Cache CPU attributeDescription

Total CPU time spent on creating global data cursor objects in cache (in seconds).Type



SourceThe source for this attribute is Filtered data - Global_Data_Cursor_Cache_CPU.

Warehouse nameGLOBAL_DATA_CURSOR_CACHE_CPU or SIEBDTL30

Global Data Cursor Cache Hits attributeDescription

Number of global data cursor cache hits.Type




Warehouse nameGLOBAL_DATA_CURSOR_CACHE_HITS or SIEBDTL31

Global Data Cursor Cache Memory attributeDescription

Total memory used for creating global data cursor objects in cache (in bytes).Type





Warehouse nameGLOBAL_DATA_CURSOR_CACHE_MEMORY or SIEBDTL32

Global Data Cursor Cache Misses attributeDescription

Number of global data cursor cache misses.Type




Warehouse nameGLOBAL_DATA_CURSOR_CACHE_MISSES or SIEBDTL33

Global Data Cursor Cache Objects attributeDescription

Number of objects currently in the global data cursor cache.Type




Warehouse nameGLOBAL_DATA_CURSOR_CACHE_OBJECTS or SIEBDTL34

Reply Messages attributeDescription

Number of reply messages sent by the server.Type



SourceThe source for this attribute is Filtered data - Reply_Messages.

Warehouse nameREPLY_MESSAGES or SIEBDTL52

Total Reply Size attributeDescription

Total size of reply messages (in bytes).




SourceThe source for this attribute is Filtered data - Total_Reply_Size.

Warehouse nameTOTAL_REPLY_SIZE or SIEBDTL79

Request Messages attributeDescription

Number of request messages received by the server.Type



SourceThe source for this attribute is Filtered data - Request_Messages.

Warehouse nameREQUEST_MESSAGES or SIEBDTL53

Total Response Time attributeDescription

Total response time of the Object Manager (in milliseconds).Type



SourceThe source for this attribute is Filtered data - Total_Response_Time.

Warehouse nameTOTAL_RESPONSE_TIME or SIEBDTL81

Total Request Size attributeDescription

Total size of request messages (in bytes).Type




SourceThe source for this attribute is Filtered data - Total_Request_Size.

Warehouse nameTOTAL_REQUEST_SIZE or SIEBDTL80

SQL Cursor Cache Hits attributeDescription

Number of SQL cursor cache hits.Type



SourceThe source for this attribute is Filtered data - SQL_Cursor_Cache_Hits.

Warehouse nameSQL_CURSOR_CACHE_HITS or SIEBDTL54

SQL Cursor Cache Misses attributeDescription

Number of SQL cursor cache misses.Type



SourceThe source for this attribute is Filtered data - SQL_Cursor_Cache_Misses.

Warehouse nameSQL_CURSOR_CACHE_MISSES or SIEBDTL55

SQL Cursor Total Cpu attributeDescription

Total CPU time spent on creating SQL cursor objects in cache (in seconds).Type



SourceThe source for this attribute is Filtered data - SQL_Cursor_Total_Cpu.

Warehouse nameSQL_CURSOR_TOTAL_CPU or SIEBDTL56

SQL Cursor Total Mem attributeDescription

Total memory used for creating SQL cursor objects in cache (in bytes).Type





SourceThe source for this attribute is Filtered data - SQL_Cursor_Total_Mem.

Warehouse nameSQL_CURSOR_TOTAL_MEM or SIEBDTL57

SQL Cursor Total Objects attributeDescription

Total number of SQL cursor objects in cache.Type



SourceThe source for this attribute is Filtered data - SQL_Cursor_Total_Objects.

Warehouse nameSQL_CURSOR_TOTAL_OBJECTS or SIEBDTL58

SQL Object Cache CPU attributeDescription

Total CPU time spent on creating SQL objects in cache (in seconds).Type



SourceThe source for this attribute is Filtered data - SQL_Object_Cache_CPU.

Warehouse nameSQL_OBJECT_CACHE_CPU or SIEBDTL61

SQL Object Cache Hits attributeDescription

Number of SQL object cache hits.Type



SourceThe source for this attribute is Filtered data - SQL_Object_Cache_Hits.


Warehouse nameSQL_OBJECT_CACHE_HITS or SIEBDTL62

SQL Object Cache Memory attributeDescription

Total memory used for creating SQL objects in cache (in bytes).Type



SourceThe source for this attribute is Filtered data - SQL_Object_Cache_Memory.

Warehouse nameSQL_OBJECT_CACHE_MEMORY or SIEBDTL63

SQL Object Cache Misses attributeDescription

Number of SQL object cache misses.Type



SourceThe source for this attribute is Filtered data - SQL_Object_Cache_Misses.

Warehouse nameSQL_OBJECT_CACHE_MISSES or SIEBDTL64

SQL Object Cache Objects attributeDescription

Number of objects currently in the SQL object cache.Type



SourceThe source for this attribute is Filtered data - SQL_Object_Cache_Objects.

Warehouse nameSQL_OBJECT_CACHE_OBJECTS or SIEBDTL65

Total Think Time attributeDescription

Total end-user think time (in seconds).Type





SourceThe source for this attribute is Filtered data - Total_Think_Time.

Warehouse nameTOTAL_THINK_TIME or SIEBDTL83



StringSource




TypeString





StringSource


SERVER_NAME or SN

Statistics InfraRecovery attribute groupThis attribute group contains detailed information that is gathered on InfraRecovery through execution ofthe Siebel srvrmgr 'list statistics' command. Additional information can be found in the Siebel SystemMonitoring and Diagnostic Guide.Historical group


The following list contains information about each attribute in the Statistics InfraRecoveryattribute group:Node attribute: This attribute is a key attribute.


TypeString



Warehouse nameNODE



StringSource


TIMESTAMPNum of DBConn Retries attribute

DescriptionNumber of retries because of loss of database connections.



SourceThe source for this attribute is Filtered data - Num_of_DBConn_Retries.

Warehouse nameNUM_OF_DBCONN_RETRIES or SIEBDTL38

Num of DLRbk Retries attributeDescription

Number of retries because of deadlock rollbacks.Type



SourceThe source for this attribute is Filtered data - Num_of_DLRbk_Retries.

Warehouse nameNUM_OF_DLRBK_RETRIES or SIEBDTL39

Num of Exhausted Retries attributeDescription

Number of times that all retries are exhausted.Type



SourceThe source for this attribute is Filtered data - Num_of_Exhausted_Retries.


Warehouse nameNUM_OF_EXHAUSTED_RETRIES or SIEBDTL40

Statistics PIMSIENG attribute groupThis attribute group contains detailed information that is gathered on PIMSIENG through execution ofthe Siebel srvrmgr 'list statistics' command. Additional information can be found in the Siebel SystemMonitoring and Diagnostic Guide.Historical group


The following list contains information about each attribute in the Statistics PIMSIENG attributegroup:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPTransactions form Siebel in Progress attribute

DescriptionNumber of in process transactions from Siebel



SourceThe source for this attribute is Filtered data -Transactions_form_Siebel_in_Progress.

Warehouse nameTRANSACTIONS_FORM_SIEBEL_IN_PROGRESS or SIEBDTL88

Transactions from PIM in Progress attributeDescription

Number of in process transactions from PIM.Type




SourceThe source for this attribute is Filtered data - Transactions_from_PIM_in_Progress.

Warehouse nameTRANSACTIONS_FROM_PIM_IN_PROGRESS or SIEBDTL89

Completed Transactions from PIM attributeDescription

Number of completed transactions from the PIM Server.Type



SourceThe source for this attribute is Filtered data - Completed_Transactions_from_PIM.

Warehouse nameCOMPLETED_TRANSACTIONS_FROM_PIM or SIEBDTL14

Completed Transactions from Siebel attributeDescription

Number of completed transactions from the Siebel Server.Type



SourceThe source for this attribute is Filtered data -Completed_Transactions_from_Siebel.

Warehouse nameCOMPLETED_TRANSACTIONS_FROM_SIEBEL or SIEBDTL15

Failed Transactions from PIM attributeDescription

Number of failed transactions from the PIM.Type



SourceThe source for this attribute is Filtered data - Failed_Transactions_from_PIM.

Warehouse nameFAILED_TRANSACTIONS_FROM_PIM or SIEBDTL28

Failed Transactions from Siebel attribute


DescriptionNumber of failed transactions from the Siebel Server.



SourceThe source for this attribute is Filtered data - Failed_Transactions_from_Siebel.

Warehouse nameFAILED_TRANSACTIONS_FROM_SIEBEL or SIEBDTL29



StringSource




TypeString





StringSource


SERVER_NAME or SN

Statistics PSPEngine attribute groupThis attribute group contains detailed information that is gathered on PSPEngine through execution ofthe Siebel srvrmgr 'list statistics' command. Additional information can be found in the Siebel SystemMonitoring and Diagnostic Guide.Historical group


The following list contains information about each attribute in the Statistics PSPEngine attributegroup:Node attribute: This attribute is a key attribute.



TypeString


Warehouse nameNODE



StringSource


TIMESTAMPPSP Cache Hit Total attribute

DescriptionTotal PSP Cache Hit Number



SourceThe source for this attribute is Filtered data - PSP_Cache_Hit_Total.

Warehouse namePSP_CACHE_HIT_TOTAL or SIEBDTL50

PSP Cache Miss Total attributeDescription

Total PSP Cache Miss NumberType



SourceThe source for this attribute is Filtered data - PSP_Cache_Miss_Total.

Warehouse namePSP_CACHE_MISS_TOTAL or SIEBDTL51

Statistics SearchDataProcessor attribute groupThis attribute group contains detailed information that is gathered on SearchDataProcessor throughexecution of the Siebel srvrmgr 'list statistics' command. Additional information can be found in theSiebel System Monitoring and Diagnostic Guide.Historical group



Attribute descriptionsThe following list contains information about each attribute in the Statistics SearchDataProcessorattribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPSearchEvents Processed attribute

DescriptionTotal number of records processed during indexing.



SourceThe source for this attribute is Filtered data - SearchEvents_Processed.

Warehouse nameSEARCHEVENTS_PROCESSED or SIEBDTL67

SearchEvents Processed Rate attributeDescription

Rate of processing the records during indexing.Type



SourceThe source for this attribute is Filtered data - SearchEvents_Processed_Rate.

Warehouse nameSEARCHEVENTS_PROCESSED_RATE or SIEBDTL68

Statistics ServerQueryTime attribute groupThis attribute group contains query times for collecting data using the Siebel Server Manager.


Historical groupThis attribute group is eligible for use with Tivoli Data Warehouse.

Attribute descriptionsThe following list contains information about each attribute in the Statistics ServerQueryTimeattribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPServer Manager Query Name attribute: This attribute is a key attribute.

DescriptionName of the Siebel Server Manager query.

TypeString

Warehouse nameQUERY_NAME

Query Execution Time attributeDescription

Amount of time to execute Siebel Server Manager query.Type



Warehouse nameEXECUTION_TIME or ET

Statistics TestSubsys attribute groupThis attribute group contains detailed information that is gathered on TestSubsys through execution ofthe Siebel srvrmgr 'list statistics' command. Additional information can be found in the Siebel SystemMonitoring and Diagnostic Guide.Historical group


The following list contains information about each attribute in the Statistics TestSubsys attributegroup:Node attribute: This attribute is a key attribute.



TypeString


Warehouse nameNODE



StringSource


TIMESTAMPTests Attempted attribute

DescriptionNumber of tests that were started.



SourceThe source for this attribute is Filtered data - Tests_Attempted.

Warehouse nameTESTS_ATTEMPTED or SIEBDTL75

Tests Failed attributeDescription

Number of tests that failed.Type



SourceThe source for this attribute is Filtered data - Tests_Failed.

Warehouse nameTESTS_FAILED or SIEBDTL76

Tests Successful attributeDescription

Number of tests that were successful.Type

Integer (32-bit gauge) with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return the values that areshown in parentheses. The following values are defined:v Value Exceeds Maximum (2147483647)




SourceThe source for this attribute is Filtered data - Tests_Successful.

Warehouse nameTESTS_SUCCESSFUL or SIEBDTL77

Statistics XMLCnv attribute groupThis attribute group contains detailed information that is gathered on XMLCnv through execution of theSiebel srvrmgr 'list statistics' command. Additional information can be found in the Siebel SystemMonitoring and Diagnostic Guide.Historical group


The following list contains information about each attribute in the Statistics XMLCnv attributegroup:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPTotal XML Converter Size of Input Buffer attribute

DescriptionTotal cumulative size of input buffer (in KB).



SourceThe source for this attribute is Filtered data -Total_XML_Converter_Size_of_Input_Buffer.

Warehouse nameTOTAL_XML_CONVERTER_SIZE_OF_INPUT_BUFFER or SIEBDTL84

Total XML Converter Size of Output Buffer attributeDescription

Total cumulative size of output buffer (in KB).




SourceThe source for this attribute is Filtered data -Total_XML_Converter_Size_of_Output_Buffer.

Warehouse nameTOTAL_XML_CONVERTER_SIZE_OF_OUTPUT_BUFFER or SIEBDTL85

Total XML Generator Calls attributeDescription

Total number of XML Generator Calls.Type



SourceThe source for this attribute is Filtered data - Total_XML_Generator_Calls.

Warehouse nameTOTAL_XML_GENERATOR_CALLS or SIEBDTL86

Total XML Parser Calls attributeDescription

Total number of XML Parser Calls.Type



SourceThe source for this attribute is Filtered data - Total_XML_Parser_Calls.

Warehouse nameTOTAL_XML_PARSER_CALLS or SIEBDTL87

Task CPU Util Rollup attribute groupThis attribute group comprises a summary of CPU utilization for the active Siebel Server componentsrunning a task.Historical group


The following list contains information about each attribute in the Task CPU Util Rollup attributegroup:Node attribute: This attribute is a key attribute.



TypeString


Warehouse nameNODE



StringSource


TIMESTAMPMaximum attribute: This attribute is a key attribute.

DescriptionThe maximum amount of percent processor time used by a component running atask.



SourceThe source for this attribute is WMI - nullmax.

Warehouse nameMAXIMUM

Minimum attributeDescription

The minimum amount of percent processor time used by a component running atask.



SourceThe source for this attribute is WMI - nullmin.

Warehouse nameMINIMUM

Average attributeDescription

The average percent processor time used by all active components running a task.Type

Integer (32-bit counter) with enumerated values. The strings are displayed in the




SourceThe source for this attribute is WMI - nullave.

Warehouse nameAVERAGE

Total attributeDescription

The sum of percent processor time used by all active components running a task.Type



SourceThe source for this attribute is WMI - nulltot.

Warehouse nameTOTAL

Task Detail attribute groupThis attribute group consists of detailed information about the tasks on this Siebel Server.Historical group


The following list contains information about each attribute in the Task Detail attribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPServer Name attribute

DescriptionThe name of the Siebel Server.


TypeString


Comp Alias attributeDescription

The component alias.Type


COMP_ALIASComp Group Alias attribute

DescriptionThe component group alias.

TypeString

Warehouse nameCOMP_GROUP_ALIAS or CGA

Task ID attribute: This attribute is a key attribute.Description

The internal Siebel task ID.Type


TASK_IDTask PID attribute

DescriptionThe operating system process ID of the task.



Warehouse nameTASK_PID

Run State attributeDescription

The run state of the task.Type


RUN_STATETask Label attribute

DescriptionThe task label.

TypeString

Warehouse nameTASK_LABEL

Parent Task Id attributeDescription

The task ID of the parent task.


TypeString

Warehouse namePARENT_TASK_ID or PTI

Task Ping Time attributeDescription

The last ping time for task.Type


TASK_PING_TIME or TPTPID Group TID attribute

DescriptionThe task PID, component group alias and task ID. If the task PID is missing, thetask process is no longer running.

TypeString

Warehouse namePID_ALIAS_TID or PAT

Task Status attributeDescription

The status of the task.Type


TASK_STATUS or TSTask Start Time attribute

DescriptionThe time when this task starts.

TypeTimestamp

Warehouse nameTASK_START_TIME or TST

Task End Time attributeDescription

The time when this task ends.Type

TimestampWarehouse name

TASK_END_TIME or TETTask Elapsed Time attribute

DescriptionThe number of minutes that have elapsed since this task started.



Warehouse nameTASK_ELAPSED_TIME or TET0


Task Resource attribute groupThis attribute group contains Availability metrics for active Siebel Server tasks.Historical group


The following list contains information about each attribute in the Task Resource attribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource




TypeString








Warehouse nameNAME


The status of the application component.v For processes 'UP', 'DOWN', 'WARNING', or

'PROCESS_DATA_NOT_AVAILABLE': 'PROCESS_DATA_NOT_AVAILABLE' is


displayed for a process when the matching process is running but the resourceuse information cannot be collected for that process.



Integer with enumerated values. The strings are displayed in the Tivoli EnterprisePortal. The warehouse and queries return the values that are shown inparentheses. The following values are defined:v DOWN (0)v UP (1)v WARNING (2)v UNKNOWN (3)v PASSED (4)v FAILED (5)v PROCESS DATA NOT AVAILABLE (6)
















Warehouse nameTYPE


The virtual size (in MB) of the process.Type

Integer (32-bit gauge)Source

The source for this attribute is Collected from the operating system. On Windowsit is gathered from the Perfmon counter Process - Private Bytes. On Unix it isgathered from getproc64 on AIX, from /proc/name/psinfo on Solaris or frompstat_getproc on HP-UX. On Linux it is gathered from the /proc/pid information..















SourceThe source for this attribute is Collected from the operating system. On Windowsit is gathered from the Perfmon counter Process - Thread Count. On Unix it is








Warehouse namePID














SourceThe source for this attribute is Collected from the operating system. On Windowsit is gathered from the Perfmon counter Process - % Processor Time. On Unix it is




Command Line attributeDescription

The program name and any arguments specified on the command line when theprocess was started. This has the value N/A if this is a Service, or Functionalitytest.











Functionality Test Message attribute


DescriptionThe text message that corresponds to the Functionality Test Status. This is onlyvalid for functionality tests.







StringSource

The source for this attribute is Join - Server_Name.Warehouse name

SERVER_NAME or SNComp Alias attribute

DescriptionThe component alias.

TypeString

SourceThe source for this attribute is Join - Comp_Alias.

Warehouse nameCOMP_ALIAS

Comp Group Alias attributeDescription

The component group alias.Type

StringSource

The source for this attribute is Join - Comp_Group_Alias.Warehouse name

COMP_GROUP_ALIAS or CGATask ID attribute: This attribute is a key attribute.

DescriptionThe internal Siebel task ID.

TypeString

SourceThe source for this attribute is Join - Task_ID.

Warehouse nameTASK_ID

Task PID attributeDescription

The operating system process ID of the task.Type





SourceThe source for this attribute is Join - Task_PID.


Run State attributeDescription

The run state of the task.Type

StringSource

The source for this attribute is Join - Run_State.Warehouse name

RUN_STATETask Label attribute

DescriptionThe task label.

TypeString

SourceThe source for this attribute is Join - Task_Label.

Warehouse nameTASK_LABEL

Parent Task Id attributeDescription

The task ID of the parent task.Type

StringSource

The source for this attribute is Join - Parent_Task_Id.Warehouse name

PARENT_TASK_ID or PTITask Ping Time attribute

DescriptionThe last ping time for task.

TypeString

SourceThe source for this attribute is Join - Task_Ping_Time.

Warehouse nameTASK_PING_TIME or TPT

PID Group TID attributeDescription

The task PID, component group alias and task ID. If the task PID is missing, thetask process is no longer running.

TypeString

SourceThe source for this attribute is Join - PID_Alias_TID.


Warehouse namePID_ALIAS_TID or PAT

Task Status attributeDescription

The status of the task.Type

StringSource

The source for this attribute is Join - Task_Status.Warehouse name

TASK_STATUS or TSTask Start Time attribute

DescriptionThe time when this task starts.

TypeTimestamp

SourceThe source for this attribute is Join - Task_Start_Time.


Task End Time attributeDescription

The time when this task ends.Type

TimestampSource

The source for this attribute is Join - Task_End_Time.Warehouse name

TASK_END_TIME or TETTask Elapsed Time attribute

DescriptionThe number of minutes that have elapsed since this task started.



SourceThe source for this attribute is Join - Task_Elapsed_Time.

Warehouse nameTASK_ELAPSED_TIME or TET0

Task Summary attribute groupThis attribute group consists of summary information about the tasks on this Siebel Server.Historical group


The following list contains information about each attribute in the Task Summary attribute group:Node attribute: This attribute is a key attribute.



TypeString


Warehouse nameNODE



StringSource


TIMESTAMPRunning Count attribute

DescriptionThe number of tasks that are currently running on the Siebel Server.



Warehouse nameRUNNING_COUNT or RC

Completed Count attributeDescription

The number of completed tasks on the Siebel Server.Type



Warehouse nameCOMPLETED_COUNT or CC

Error Count attributeDescription

The number of tasks that exit with error on the Siebel Server.Type



Warehouse nameERROR_COUNT or EC


Other Count attributeDescription

The number of tasks that are in an unrecognized state on the Siebel Server.Type



Warehouse nameOTHER_COUNT or OC

Interactive Count attributeDescription

The number of interactive tasks on the Siebel Server.Type



Warehouse nameINTERACTIVE_COUNT or IC

Background Count attributeDescription

The number of background tasks on the Siebel Server.Type



Warehouse nameBACKGROUND_COUNT or BC

Batch Count attributeDescription

The number of batch tasks on the Siebel Server.Type



Warehouse nameBATCH_COUNT or BC0

Normal Count attribute


DescriptionThe number of normal tasks on the Siebel Server.



Warehouse nameNORMAL_COUNT or NC

Worker Count attributeDescription

The number of worker tasks on the Siebel Server.Type



Warehouse nameWORKER_COUNT or WC

User Session attribute groupThis attribute group consists of detailed information about the user session tasks on this Siebel Server.Historical group


The following list contains information about each attribute in the User Session attribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE



StringSource


TIMESTAMPServer Name attribute

DescriptionThe name of the Siebel Server.


TypeString


Task ID attribute: This attribute is a key attribute.Description

The internal Siebel task ID for the user session.Type


TASK_IDTask PID attribute

DescriptionThe operating system process ID of the user session.

TypeString


Run Mode attributeDescription

The component run mode of the user session. For a user session, this value isInteractive.

TypeString

Warehouse nameRUN_MODE

Task Type attributeDescription

The Siebel task type of the user session. For a user session, this value is Normal.Type


TASK_TYPEUser ID attribute

DescriptionThe user ID for this user session.

TypeString

Warehouse nameUSER_ID

Task Runstate attributeDescription

The current state of the Siebel user session.Type


TASK_RUNSTATE or TRTask Start Time attribute

DescriptionThe time when this user session starts.

TypeTimestamp


Task End Time attribute


DescriptionThe time when this user session ends.

TypeTimestamp

Warehouse nameTASK_END_TIME or TET


The number of minutes that have elapsed since this user session started.Type



Warehouse nameELAPSED_TIME or ET



StringSource




TypeString



User Session Summary attribute groupThis attribute group consists of summary information about the user session tasks on this Siebel Server.Historical group


The following list contains information about each attribute in the User Session Summaryattribute group:Node attribute: This attribute is a key attribute.


TypeString


Warehouse nameNODE

Timestamp attribute



TypeString



Running Count attributeDescription

The number of user sessions that are currently running on the Siebel Server.Type



Warehouse nameRUNNING_COUNT or RC

Completed Count attributeDescription

The number of completed user sessions on the Siebel Server.Type



Warehouse nameCOMPLETED_COUNT or CC

Error Count attributeDescription

The number of user sessions that exit with error on the Siebel Server.Type



Warehouse nameERROR_COUNT or EC

Other Count attributeDescription

The number of user sessions that are in an unrecognized state on the SiebelServer.





Warehouse nameOTHER_COUNT or OC

Disk capacity planning for historical dataDisk capacity planning for a monitoring agent is a prediction of the amount of disk space to beconsumed for each attribute group with historical data that is being collected. Required disk storage is animportant factor when you are defining data collection rules and your strategy for historical datacollection.

The Capacity planning for historical data table provides the following information required to calculatedisk space for this monitoring agent:

Table Table name as it is displayed in the warehouse database, if the attribute group is configured to bewritten to the warehouse. The table name listed here corresponds to the table name in “Attributegroups for the monitoring agent” on page 9.

Attribute groupName of the attribute group used to create the table in the warehouse database if it is shortenough to fit in the table naming constraints of the database being used for the warehouse. Theattribute group name listed here corresponds to the Warehouse table name in “Attribute groupsfor the monitoring agent” on page 9.

Bytes per row (agent)Estimate of the record length for each row or instance written to the agent disk for historical datacollection. This estimate can be used for agent disk space planning purposes.

Database bytes per row (warehouse)Estimate of the record length for detailed records written to the warehouse database, if theattribute group is configured to be written to the warehouse. Detailed records are records thathave been uploaded from the agent for long-term historical data collection. This estimate can beused for warehouse disk-space planning purposes.

Aggregate bytes per row (warehouse)Estimate of the record length for aggregate records written to the warehouse database, if theattribute group is configured to be written to the warehouse. Aggregate records are created by theSummarization agent for attribute groups that have been configured for summarization. Thisestimate can be used for warehouse disk-space planning purposes.

In addition to the information in the tables, you must know the number of rows of data that you plan tocollect. An attribute group can have single or multiple rows of data depending on the applicationenvironment that is being monitored. For example, if your attribute group is monitoring each processorin your computer and you have a dual processor computer, the number of rows is two.

Table 1. Capacity planning for historical data logged by the Siebel agent

Table Attribute group

Bytes perrow(agent)

Databasebytes perrow(warehouse)

Aggregatebytes perrow(warehouse)

KUBAVAIL KUB_AVAILABILITY 3272 3296 3606

KUBCPUCOMP KUB_COMPONENT_RESOURCE 3376 3402 3751


Table 1. Capacity planning for historical data logged by the Siebel agent (continued)


Bytes perrow(agent)



KUBCOMPSTA KUB_COMPONENT_STATISTICS 852 863 951

KUBCOMPCOU KUB_COMP_COUNTS 208 206 282

KUBCUTLRLU KUB_COMP_CPU_UTIL_ROLLUP 92 92 198

KUBCOMPDET KUB_COMP_DETAIL 590 595 671

KUBCOMPLOG KUB_COMP_LOGS 1392 1400 1437

KUBCMPLOGP KUB_COMP_LOGS_PRE77 1291 1297 1334

KUBCOMPNAM KUB_COMP_NAME 180 178 254

KUBDBFIL KUB_DATABASE_FILES 316 324 673

KUBDBFILSY KUB_DATABASE_FILE_SYSTEM 396 400 593

KUBDLAINP KUB_DLA_INPUT 1028 1047 1084

KUBENTERPI KUB_ENTERPRISE 508 514 551

KUBFILES KUB_FILES 416 425 774

KUBFILESYS KUB_FILE_SYSTEM 396 400 593

KUBGNSLOG KUB_GATE_LOG 1392 1400 1437

KUBGNSLOGP KUB_GATE_LOG_PRE77 1291 1297 1334

KUBMKTST KUB_MARKETING_STATISTICS 400 405 442

KUBPOBJST KUB_PERFORMANCE_OBJECT_STATUS 288 289 326

KUBSRVLOG KUB_SERVER_LOG 2486 2500 2537

KUBSRVLOGP KUB_SERVER_LOG_PRE77 1291 1297 1334

KUBSIEBSRV KUB_SIEBEL_SERVER 596 605 642

KUBSIEBSTA KUB_SIEBEL_STATISTICS 724 734 822

KUBSTATASG KUB_STATISTICS_ASGNSUBSYS 80 77 153

KUBSTATCOM KUB_STATISTICS_COMMINBOUNDPROCESSOR 84 82 197

KUBSTATEAI KUB_STATISTICS_EAISUBSYS 96 97 329

KUBSTATFLT KUB_STATISTICS_FLIGHTDATARECORDER 88 87 241

KUBSTATCOR KUB_STATISTICS_INFRACORE 420 454 944

KUBSTATDAT KUB_STATISTICS_INFRADATABASE 412 492 952

KUBSTATMUL KUB_STATISTICS_INFRAMULTITHREAD 88 111 289

KUBSTATOBJ KUB_STATISTICS_INFRAOBJMGR 512 605 2028

KUBSTATREC KUB_STATISTICS_INFRARECOVERY 88 87 241

KUBSTATPIM KUB_STATISTICS_PIMSIENG 400 405 676

KUBSTATENG KUB_STATISTICS_PSPENGINE 84 82 197

KUBSTATSEA KUB_STATISTICS_SEARCHDATAPROCESSOR 84 82 197

KUBSTATSUB KUB_STATISTICS_TESTSUBSYS 88 87 241

KUBSTATXML KUB_STATISTICS_XMLCNV 92 92 285

KUBDETSTA KUB_STATISTIC_DETAILS 428 1568 6093

KUBTUTLRLU KUB_TASK_CPU_UTIL_ROLLUP 92 92 198

KUBTASKDET KUB_TASK_DETAIL 1116 1126 1241


Table 1. Capacity planning for historical data logged by the Siebel agent (continued)


Bytes perrow(agent)



KUBCPUTASK KUB_TASK_RESOURCE 4312 4350 4738

KUBTASKSUM KUB_TASK_SUMMARY 112 117 505

KUBUSERSES KUB_USER_SESSION 976 984 1060

KUBUSERSE2 KUB_USER_SESSION_SUMMARY 92 92 285

For more information about historical data collection, see "Managing historical data" in the IBM TivoliMonitoring Administrator's Guide.


Chapter 3. Situations reference

A situation is a logical expression involving one or more system conditions. Situations are used tomonitor the condition of systems in your network. You can manage situations from the Tivoli EnterprisePortal by using the Situation Editor or from the command-line interface using the tacmd commands forsituations. You can manage private situations in the private configuration XML file.

About situations

The monitoring agents that you use to monitor your system environment include a set of predefinedsituations that you can use as-is. You can also create new situations to meet your requirements.

Predefined situations contain attributes that check for system conditions common to many enterprises.Using predefined situations can improve the speed with which you can begin using the IBM TivoliComposite Application Manager Agent for Siebel CRM. You can change the conditions or values beingmonitored by a predefined situation to the conditions or values best suited to your enterprise.

You can display predefined situations and create your own situations using the Situation editor. TheSituation editor initially lists the situations associated with the Navigator item that you selected. Whenyou click a situation name or create a situation, a panel opens with the following tabs:

FormulaFormula describing the condition being tested.

DistributionList of managed systems (operating systems, subsystems, or applications) to which the situationcan be distributed. All the Siebel agent managed systems are assigned by default.

Expert adviceComments and instructions to be read in the event workspace.

ActionCommand to be sent to the system.

EIF Customize forwarding of the event to an Event Integration Facility receiver. (Available when theTivoli Enterprise Monitoring Server is configured to forward events.)

Until Options to close the event after a period of time, or when another situation becomes true.

Additional information about situations

The Tivoli Enterprise Portal User's Guide contains more information about predefined and customsituations and how to use them to respond to alerts.

For a list of the predefined situations and information about each individual situation for this monitoringagent, see “Predefined situations.”

Predefined situationsThe monitoring agent contains predefined situations, which are organized by Navigator item.v Siebel

– Not applicablev Availability

– KUB_Server_Down


– KUB_Gateway_Name_Server_Down– KUB_Object_Problem– KUB_Server_Degraded– KUB_Comp_CPU_Crit– KUB_Comp_CPU_Warn– KUB_Server_CPU_Crit– KUB_Server_CPU_Warn– KUB_Server_Process_Size

v Components– KUB_Connection_Failure– KUB_Comp_Offline– KUB_Comp_Shutdown– KUB_Comp_Unavailable– KUB_Active_Task_Count_High– KUB_Active_Task_Count_Low

v File System– KUB_FileSys_Space_Avail_Crit– KUB_FileSys_Space_Avail_Warn– KUB_DBFileSys_Space_Avail_Crit– KUB_DBFileSys_Space_Avail_Warn– KUB_Server_Space_Used– KUB_Log_Dir_Space_Used– KUB_Log_File_Size– KUB_Log_File_Rate– KUB_Gateway_NS_Log_Space_Used– KUB_Log_Archive_Space_Used– KUB_Docking_Space_Used– KUB_TxnProc_Space_Used– KUB_Ancient_Files_More_Than_10– KUB_Invalid_Files_More_Than_10– KUB_Orphan_Files_More_Than_10

v Logs– KUB_Component_Exit_With_Error– KUB_Incorrect_Password_Config– KUB_Oracle_Database_Down– KUB_Configuration_Store_Error– KUB_GtwySrvr_Not_Connected

v Logs Pre77– Not applicable

v Statistics– KUB_Error_Amount_High– KUB_Component_Restarts_Number– KUB_Component_Failed_Number– KUB_Tasks_Exceed_Configuration– KUB_Connect_Time_High


– KUB_Response_Time_High– KUB_Data_Cursor_Cache_Misses– KUB_SQL_execute_Time_High– KUB_SQL_Fetch_Time_High– KUB_Failed_Transactions_Siebel

v Tasks– KUB_Long_Running_Session

Situation descriptionsEach situation description provides information about the situation that you can use to monitor thecondition of systems in your network.

The situation descriptions provide the following information:

DescriptionInformation about the conditions that the situation tests.

FormulaSyntax that contains one or more logical expressions that describe the conditions for the situationto monitor.

DistributionWhether the situation is automatically distributed to instances of the agent or is available formanual distribution.

Run at startupWhether the situation starts monitoring when the agent starts.

Sampling intervalNumber of seconds that elapse between one sample of data that the monitoring agent collects forthe server and the next sample.

Situation persistenceWhether the conditions specified in the situation evaluate to "true" for the defined number ofoccurrences in a row before the situation is raised. The default of one means that nopersistence-checking takes place.

SeveritySeverity of the predefined events: Warning, Informational, or Critical.

Clearing conditionsControls when a true situation closes: after a period, when another situation is true, or whicheveroccurs first if both are selected.

Siebel Navigator itemNo predefined situations are included for this Navigator item.

Availability Navigator itemThe situation descriptions are organized by the Navigator item to which the situations are relevant.KUB_Server_Down situation

DescriptionThe Siebel Server process is not running.

The situation is evaluated for each distinct value of the COMPONENT attribute.Formula

*IF *VALUE KUB_AVAILABILITY.Status *EQ ’DOWN’ *AND *VALUEKUB_AVAILABILITY.Application_Component *EQ ’Siebel Application Server’

Chapter 3. Situations reference 151

See “Attributes in each attribute group” on page 12 for descriptions of the attributes inthis formula.

DistributionThis situation is automatically distributed to instances of this agent.

Run at startupYes

Sampling interval5 minutes

Situation persistenceThe number of times the conditions of the situation must occur for the situation to betrue is 1.

Error conditionsCritical

Clearing conditionsThe situation clears when the condition becomes false.

KUB_Gateway_Name_Server_Down situationDescription

The Siebel Gateway Name Server process is not running.


*IF *VALUE KUB_AVAILABILITY.Status *EQ ’DOWN’ *AND *VALUEKUB_AVAILABILITY.Application_Component *EQ ’Gateway Name Server’



Run at startupYes





KUB_Object_Problem situationDescription

The agent is unable to gather data, it may be mis-configured.


*IF ( *VALUE KUB_PERFORMANCE_OBJECT_STATUS.Error_Code *EQ ’OBJECT_NOT_FOUND’ )*OR ( *VALUE KUB_PERFORMANCE_OBJECT_STATUS.Error_Code *EQ’OBJECT_CURRENTLY_UNAVAILABLE’ ) *OR ( *VALUEKUB_PERFORMANCE_OBJECT_STATUS.Error_Code *EQ ’GENERAL_ERROR’ )



Run at startupYes




Error conditionsInformational


KUB_Server_Degraded situationDescription

Srvrmgr process is unresponsive or the agent is mis-configured.


*IF ( ( *VALUE KUB_PERFORMANCE_OBJECT_STATUS.Object_Name *EQ ’Comp_Detail’ *AND*VALUE KUB_PERFORMANCE_OBJECT_STATUS.Error_Code *NE NO_ERROR *AND *VALUEKUB_PERFORMANCE_OBJECT_STATUS.Error_Code *NEKUB_NOT_APPLICABLE_FOR_GATEWAY_ONLY_CONFIGURATION ) *OR ( *VALUEKUB_PERFORMANCE_OBJECT_STATUS.Object_Name *EQ ’Siebel_Server’ *AND *VALUEKUB_PERFORMANCE_OBJECT_STATUS.Error_Code *NE NO_ERROR *AND *VALUEKUB_PERFORMANCE_OBJECT_STATUS.Error_Code *NEKUB_NOT_APPLICABLE_FOR_GATEWAY_ONLY_CONFIGURATION ) *OR ( *VALUEKUB_PERFORMANCE_OBJECT_STATUS.Object_Name *EQ ’Task_Detail’ *AND *VALUEKUB_PERFORMANCE_OBJECT_STATUS.Error_Code *NE NO_ERROR *AND *VALUEKUB_PERFORMANCE_OBJECT_STATUS.Error_Code *NEKUB_NOT_APPLICABLE_FOR_GATEWAY_ONLY_CONFIGURATION ) )


DistributionThis situation is available for distribution.

Run at startupNo



Error conditionsWarning


KUB_Comp_CPU_Crit situationDescription

The CPU utilization for a Siebel Server component is very high.


*IF *SCAN KUB_AVAILABILITY.Name *EQ ’siebmtsh’ *AND *VALUEKUB_AVAILABILITY.Percent_Processor_Time *GE ’80’



Run at startupYes






KUB_Comp_CPU_Warn situationDescription

The CPU utilization for a Siebel Server component is high.


*IF *SCAN KUB_AVAILABILITY.Name *EQ ’siebmtsh’ *AND *VALUEKUB_AVAILABILITY.Percent_Processor_Time *GE ’70’ *AND *VALUEKUB_AVAILABILITY.Percent_Processor_Time *LT ’80’



Run at startupYes





KUB_Server_CPU_Crit situationDescription

The CPU utilization for the Siebel Server is very high.


*IF *SCAN KUB_AVAILABILITY.Command_Line *EQ ’-s siebsrvr’ *AND *SCANKUB_AVAILABILITY.Command_Line *EQ ’siebsvc’ *AND *VALUEKUB_AVAILABILITY.Percent_Processor_Time *GE ’80’



Run at startupYes





KUB_Server_CPU_Warn situation


DescriptionThe CPU utilization for the Siebel Server is high.


*IF *SCAN KUB_AVAILABILITY.Command_Line *EQ ’-s siebsrvr’ *AND *SCANKUB_AVAILABILITY.Command_Line *EQ ’siebsvc’ *AND *VALUEKUB_AVAILABILITY.Percent_Processor_Time *GE ’70’ *AND *VALUEKUB_AVAILABILITY.Percent_Processor_Time *LT ’80’



Run at startupYes





KUB_Server_Process_Size situationDescription

The virtual memory (MB) used by the server process is large.


*IF *SCAN KUB_AVAILABILITY.Command_Line *EQ ’-s siebsrvr’ *AND *VALUEKUB_AVAILABILITY.Virtual_Size *GE ’2000’



Run at startupNo





Components Navigator itemThe situation descriptions are organized by the Navigator item to which the situations are relevant.KUB_Connection_Failure situation

DescriptionThere is a problem with the connection to the Siebel CRM.

The situation is evaluated for each distinct value of the SN attribute.


Formula*IF *VALUE KUB_SIEBEL_SERVER.Connection_Status *EQ ’No’



Run at startupYes





KUB_Comp_Offline situationDescription

The specified Siebel Server component is not online.

The situation is evaluated for each distinct value of the COMP_ALIAS attribute.Formula

*IF *VALUE KUB_COMP_DETAIL.Run_State *EQ ’Not Online’



Run at startupNo





KUB_Comp_Shutdown situationDescription

The specified Siebel Server component is shut down.


*IF *VALUE KUB_COMP_DETAIL.Run_State *EQ ’Shutdown’



Run at startupNo






KUB_Comp_Unavailable situationDescription

The specified Siebel Server component is not available.


*IF *VALUE KUB_COMP_DETAIL.Run_State *EQ ’Unavailable’



Run at startupNo





KUB_Active_Task_Count_High situationDescription

The number of tasks running in the Siebel Server is too high.


*IF *VALUE KUB_SIEBEL_SERVER.Active_Task_Count *GE ’5’



Run at startupNo





KUB_Active_Task_Count_Low situationDescription

The number of tasks running in the Siebel Server is too low.

The situation is evaluated for each distinct value of the COMP_ALIAS attribute.


Formula*IF *VALUE KUB_SIEBEL_SERVER.Active_Task_Count *LE ’0’



Run at startupNo





File System Navigator itemThe situation descriptions are organized by the Navigator item to which the situations are relevant.KUB_FileSys_Space_Avail_Crit situation

DescriptionThe volume space available to the Siebel Server is very low.

The situation is evaluated for each distinct value of the NAME attribute.Formula

*IF *VALUE KUB_FILE_SYSTEM.Percent_Free *LT ’5’



Run at startupYes





KUB_FileSys_Space_Avail_Warn situationDescription

The volume space available to the Siebel Server is low.


*IF *VALUE KUB_FILE_SYSTEM.Percent_Free *LT ’10’ *AND *VALUEKUB_FILE_SYSTEM.Percent_Free *GE ’5’




Run at startupYes





KUB_DBFileSys_Space_Avail_Crit situationDescription

The volume space available to the Siebel File System is low.


*IF *VALUE KUB_DATABASE_FILE_SYSTEM.Percent_Free *LT 5



Run at startupYes





KUB_DBFileSys_Space_Avail_Warn situationDescription

The volume space available to the Siebel File System is low.


*IF *VALUE KUB_DATABASE_FILE_SYSTEM.Percent_Free *LT 10 *AND *VALUEKUB_DATABASE_FILE_SYSTEM.Percent_Free *GE 5



Run at startupYes






KUB_Server_Space_Used situationDescription

The space occupied by the files for this Siebel Server is large.

The situation is evaluated for each distinct value of the DN attribute.Formula

*IF *VALUE KUB_FILES.Type *EQ ’1’ *AND *VALUEKUB_FILES.Percent_of_File_System_Used *GT ’80’



Run at startupYes





KUB_Log_Dir_Space_Used situationDescription

The space occupied by the Siebel Server log directory is large.


*IF *VALUE KUB_FILES.Type *EQ ’2’ *AND *VALUEKUB_FILES.Percent_of_File_System_Used *GT ’25’ *AND *VALUE KUB_FILES.Filename *EQ’’



Run at startupYes





KUB_Log_File_Size situationDescription

The Siebel Server main log file is too large.


*IF *VALUE KUB_FILES.Type *EQ ’2’ *AND *SCAN KUB_FILES.Filename *EQ ’.log’ *AND*VALUE KUB_FILES.Percent_of_File_System_Used *GT ’5’




Run at startupNo





KUB_Log_File_Rate situationDescription

The Siebel Server main log file is filling too quickly.


*IF *VALUE KUB_FILES.Type *EQ ’2’ *AND *SCAN KUB_FILES.Filename *EQ ’.log’ *AND*VALUE KUB_FILES.Size_Change_Last_Hour *GT ’256’



Run at startupNo





KUB_Gateway_NS_Log_Space_Used situationDescription

The Siebel Gateway Name Server log directory is large.





Run at startupYes






KUB_Log_Archive_Space_Used situationDescription

The Siebel log archive directory is large.





Run at startupYes





KUB_Docking_Space_Used situationDescription

The space occupied by the files for this sub-directory is large.





Run at startupYes





KUB_TxnProc_Space_Used situationDescription

Space occupied by files in this TXNPROC sub-directory is large.






Run at startupYes





KUB_Ancient_Files_More_Than_10 situationDescription

More than 10 ancient files were found.

The situation is evaluated for each distinct value of the MSC attribute.Formula

*IF *VALUE KUB_MARKETING_STATISTICS.Marketing_Statistics_Ancient *GT ’10’



Run at startupNo

Sampling interval30 seconds




KUB_Invalid_Files_More_Than_10 situationDescription

More than 10 invalid files were found.


*IF *VALUE KUB_MARKETING_STATISTICS.Marketing_Statistics_Invalid *GT ’10’



Run at startupNo






KUB_Orphan_Files_More_Than_10 situationDescription

More than 10 orphan files were found.


*IF *VALUE KUB_MARKETING_STATISTICS.Marketing_Statistics_Orphaned *GT ’10’



Run at startupNo





Logs Navigator itemThe situation descriptions are organized by the Navigator item to which the situations are relevant.KUB_Component_Exit_With_Error situation

DescriptionA component has exited with an error

The situation is evaluated for each distinct value of the SN attribute.Formula

*IF *SCAN KUB_SERVER_LOG.Log_Message *EQ ’exited with error’ *AND *VALUEKUB_SERVER_LOG.Type *EQ ’ProcessExit’



Run at startupNo

Sampling intervalNone. Data is analyzed when it becomes available.

Situation persistenceNot Applicable



Clearing conditionsThe situation does not clear automatically.

KUB_Incorrect_Password_Config situationDescription

Incorrect password configuration


*IF ( ( *SCAN KUB_SERVER_LOG.Log_Message *EQ ’SBL-ADM-01042’ *AND *VALUEKUB_SERVER_LOG.Type *EQ ’ProcessExit’ ) *OR ( *SCAN KUB_SERVER_LOG.Log_Message*EQ ’SBL-SEC-10007’ *AND *VALUE KUB_SERVER_LOG.Type *EQ ’ProcessExit’ ) )



Run at startupNo





KUB_Oracle_Database_Down situationDescription

The Oracle database is currently down


*IF *SCAN KUB_GATE_LOG.Log_Message *EQ ’listener’ *AND *VALUE KUB_GATE_LOG.Type*EQ ’DBCLogError’



Run at startupNo





KUB_Configuration_Store_Error situationDescription

Unable to open connection to Siebel Gateway configuration store.


*IF *SCAN KUB_SERVER_LOG.Log_Message *EQ ’SBL-SCM-00018’




Run at startupNo





KUB_GtwySrvr_Not_Connected situationDescription

The gateway server is not connected.


*IF *SCAN KUB_COMP_LOGS.Log_Message *EQ ’Unable to connect to the gateway server’



Run at startupNo





Logs Pre77 Navigator itemNo predefined situations are included for this Navigator item.

Statistics Navigator itemThe situation descriptions are organized by the Navigator item to which the situations are relevant.KUB_Error_Amount_High situation

DescriptionThe Total number of level 0 and 1 errors is high.

The situation is evaluated for each distinct value of the SIEBDTL41 attribute.Formula

*IF *CHANGE KUB_STATISTICS_INFRACORE.Number_of_Errors *GT 2.00



Run at startupNo






KUB_Component_Restarts_Number situationDescription

The number of times a component process has restarted is high.


*IF *CHANGE KUB_STATISTICS_INFRACORE.Number_of_Component_Restarts *GT 2.00



Run at startupNo





KUB_Component_Failed_Number situationDescription

The number of times a component process has failed is high.


*IF *CHANGE KUB_STATISTICS_INFRACORE.Number_of_Component_Crashes *GT 2.00



Run at startupNo





KUB_Tasks_Exceed_Configuration situationDescription

The tasks stated that exceed configured capacity is high.

The situation is evaluated for each distinct value of the SIEBDTL41 attribute.


Formula*IF *CHANGE KUB_STATISTICS_INFRACORE.Tasks_Exceeding_Configured_Capacity *GT 2.00



Run at startupNo





KUB_Connect_Time_High situationDescription

The average connect time for Object Manager sessions is high.


*IF *VALUE KUB_STATISTICS_INFRAOBJMGR.Average_Connect_Time *GT 28800.00



Run at startupNo





KUB_Response_Time_High situationDescription

The Object Manager response time between requests is high.


*IF *VALUE KUB_STATISTICS_INFRAOBJMGR.Average_Response_Time *GT 5.00



Run at startupNo






KUB_Data_Cursor_Cache_Misses situationDescription

The number of SQL data cursor cache misses is high.


*IF *CHANGE KUB_STATISTICS_INFRAOBJMGR.Data_Cursor_Cache_Misses *GT 5



Run at startupNo





KUB_SQL_execute_Time_High situationDescription

The Average time for SQL execute operations is high.


*IF *VALUE KUB_STATISTICS_INFRADATABASE.Avg_SQL_Execute_Time *GT 10.00



Run at startupNo





KUB_SQL_Fetch_Time_High situationDescription

The Average time for SQL fetch operations is high.

The situation is evaluated for each distinct value of the SIEBDTL10 attribute.


Formula*IF *VALUE KUB_STATISTICS_INFRADATABASE.Avg_SQL_Fetch_Time *GT 5.00



Run at startupNo





KUB_Failed_Transactions_Siebel situationDescription

The Number of failed transactions from Siebel high.


*IF *CHANGE KUB_STATISTICS_PIMSIENG.Failed_Transactions_from_Siebel *GT 5.00



Run at startupNo





Tasks Navigator itemThe situation descriptions are organized by the Navigator item to which the situations are relevant.KUB_Long_Running_Session situation

DescriptionA long running user session is detected. Default > 24 hours.

The situation is evaluated for each distinct value of the TASK_ID attribute.Formula

*IF *VALUE KUB_USER_SESSION.Elapsed_Time *GE 1440 *AND *VALUEKUB_USER_SESSION.Task_Runstate *EQ ’Running’




Run at startupNo

Sampling interval1 hour





Chapter 4. Take Action commands reference

Take Action commands can be run from the portal client or included in a situation or a policy.

About Take Action commands

When included in a situation, the command runs when the situation becomes true. A Take Actioncommand in a situation is also referred to as reflex automation. When you enable a Take Action commandin a situation, you automate a response to system conditions. For example, you can use a Take Actioncommand to send a command to restart a process on the managed system or to send a text message to acell phone.

In advanced automation, policies are used to take actions, schedule work, and automate manual tasks. Apolicy comprises a series of automated steps called activities that are connected to create a workflow.After an activity is completed, the Tivoli Enterprise Portal receives return-code feedback, and advancedautomation logic responds with subsequent activities that are prescribed by the feedback.

A basic Take Action command shows the return code of the operation in a message box that is displayedafter the action is completed or in a log file. After you close this window, no further information isavailable for this action.

Additional information about Take Action commands

For more information about working with Take Action commands, see “Take Action commands” in theTivoli Enterprise Portal User's Guide.

For a list of the Take Action commands for this monitoring agent and a description of each command, see“Predefined Take Action commands” and the information for each individual command.

Predefined Take Action commandsNot all agents have predefined Take Action commands. But you can create Take Action commands forany agent.

This monitoring agent contains the following Take Action commands:v Delete Archived Logsv Http URL Addv Http URL Removev Pause Siebel Server Taskv Put Component Group Onlinev Resume Siebel Server Taskv Run Srvrmgr Commandv Shutdown Siebel_Server_Componentv Start Gateway Name Serverv Start Siebel Serverv Start Siebel Server Taskv Startup Siebel_Server_Componentv Stop Gateway Name Serverv Stop Siebel Server


v Stop Siebel Server Taskv Take Component Group Offline

Take Action command descriptionsEach Take Action command description provides information you can use to decide whether to run theTake Action command or whether to include the Take Action command in a situation or a policy.

The descriptions of the Take Action commands provide the following information:

DescriptionActions the command performs on the system to which it is sent, and the permissions requiredfor the Take Action command to function.

Return codesInformation that the Take Action command returns.

Delete Archived Logs actionDeletes the archived log or logs. Specify the archive by subdirectory name, e.g., archive_54.System command

To include the Take Action command in a situation or workflow policy, use the following syntaxfor the system command:DELETE_ARCHIVED_LOGS \

[Log_Archive_Subdirectory]

You can use attribute substitution to supply the Take Action command arguments from thesituation, for example:DELETE_ARCHIVED_LOGS \

[&{Log_Archive_Subdirectory}]

You can also use attribute substitution in a workflow policy though the format is slightlydifferent:DELETE_ARCHIVED_LOGS \

[&WaitOnSituation:Log_Archive_Subdirectory]Command arguments

v Name: Log_Archive_Subdirectory– Description: The directory of the archive log to be deleted, for example, archive_54.– Default: *

Return codesv Return Code: 8

– Return Code Type: TIMED_OUT– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB1003– Message: The requested take action timed out.

v Return Code: 1– Return Code Type: DOESNT_EXIST– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB4025I– Message: No archived Siebel logs exist to be deleted.

v Return Code: 0– Return Code Type: OK


– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bitx86), Solaris (64-bit SPARC)

– Message ID: KUB4026I– Message: The archived Siebel log files were deleted.

v Return Code: 14– Return Code Type: GENERAL_ERROR– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB4047E– Message: The requested command failed. The script or program used to issue the requested

command was not found.v Return Code: 13

– Return Code Type: GENERAL_ERROR– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB4048E– Message: The requested command failed. A parameter is not correctly defined.


x86), Solaris (64-bit SPARC)– Message ID: KUB4049E– Message: The requested command failed. The user ID used to run the command has

insufficient authority.v Return Code: 11


x86), Solaris (64-bit SPARC)– Message ID: KUB4050E– Message: The requested command failed. A required environment variable is not correctly

defined.v Return Code: 2


x86), Solaris (64-bit SPARC)– Message ID: KUB4053E– Message: Some or all of the archived logs cannot be deleted.

v Return Code: 15– Return Code Type: INSUFFICIENT_USER_AUTHORITY– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB4056E– Message: The command failed because the Monitoring Agent for Siebel CRM ran out of

memory.

Http URL Add actionAdd a HTTP URL to be monitored.System command

To include the Take Action command in a situation or workflow policy, use the following syntaxfor the system command:HTTP_URL_ADD \

[URL]

Chapter 4. Take Action commands reference 175

[User_Data]

[Alias]

You can use attribute substitution to supply the Take Action command arguments from thesituation, for example:HTTP_URL_ADD \

[&{URL}] \

[&{User_Data}] \

[&{Alias}]

You can also use attribute substitution in a workflow policy though the format is slightlydifferent:HTTP_URL_ADD \

[&WaitOnSituation:URL] \

[&WaitOnSituation:User_Data] \

[&WaitOnSituation:Alias]Command arguments

v Name: URL– Description: The URL to monitor.– Default: None

v Name: User_Data– Description: The user data to associate with this URL– Default: None

v Name: Alias– Description: An optional alias name for the URL.– Default: None


– Return Code Type: GENERAL_ERROR– Operating systems: AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit x86), Solaris (64-bit SPARC),

Windows, Windows (64-bit)– Message ID: KQZ3011E– Message: Action Failed. See the agent log file for more information.

v Return Code: 0– Return Code Type: SUCCESS– Operating systems: AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit x86), Solaris (64-bit SPARC),

Windows, Windows (64-bit)– Message ID: KQZ3012I– Message: Action successfully completed.

Usage A URL to monitor must be specified. If it does not contain a protocol, http:// is used.

Http URL Remove actionRemove a URL from the list of monitored URLs.System command

To include the Take Action command in a situation or workflow policy, use the following syntaxfor the system command:HTTP_URL_REMOVE \

[URL]

[User_Data]


You can use attribute substitution to supply the Take Action command arguments from thesituation, for example:HTTP_URL_REMOVE \

[&{URL}] \

[&{User_Data}]

You can also use attribute substitution in a workflow policy though the format is slightlydifferent:HTTP_URL_REMOVE \

[&WaitOnSituation:URL] \

[&WaitOnSituation:User_Data]Command arguments

v Name: URL– Description: The URL to be removed.– Default: None

v Name: User_Data– Description: The user data associated with this URL– Default: None


– Return Code Type: GENERAL_ERROR– Operating systems: AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit x86), Solaris (64-bit SPARC),

Windows, Windows (64-bit)– Message ID: KQZ3011E– Message: Action Failed. See the agent log file for more information.

v Return Code: 0– Return Code Type: SUCCESS– Operating systems: AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit x86), Solaris (64-bit SPARC),

Windows, Windows (64-bit)– Message ID: KQZ3012I– Message: Action successfully completed.

Usage The URL and the User_Data arguments must be specified as shown in the Tivoli EnterprisePortal.

Pause Siebel Server Task actionPauses a Siebel Server task by specifying the task ID.System command

To include the Take Action command in a situation or workflow policy, use the following syntaxfor the system command:PAUSE_SIEBEL_SERVER_TASK \

[KUB_Task_Detail.Task_ID]

You can use attribute substitution to supply the Take Action command arguments from thesituation, for example:PAUSE_SIEBEL_SERVER_TASK \

[&{KUB_Task_Detail.Task_ID}]

You can also use attribute substitution in a workflow policy though the format is slightlydifferent:PAUSE_SIEBEL_SERVER_TASK \

[&WaitOnSituation:KUB_Task_Detail.Task_ID]


Command argumentsv Name: KUB_Task_Detail.Task_ID

– Description: The ID of the task to be paused.– Default: ""




v Return Code: 1– Return Code Type: NOT_RUNNING– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB4019I– Message: The specified Siebel Server task is already paused.

v Return Code: 0– Return Code Type: OK– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB4020I– Message: The Siebel Server task was paused.


x86), Solaris (64-bit SPARC)– Message ID: KUB4044E– Message: An error occurred in pausing the Siebel Server task.











defined.


v Return Code: 3– Return Code Type: PREREQ_NOT_RUNNING– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB4051E– Message: The take action failed because the application server is not running.



memory.v Return Code: 4


x86), Solaris (64-bit SPARC)– Message ID: KUB4075E– Message: The Siebel Server task cannot be paused, since it is not running.

Put Component Group Online actionPuts the component group online.System command

To include the Take Action command in a situation or workflow policy, use the following syntaxfor the system command:PUT_COMPONENT_GROUP_ONLINE \

[KUB_Comp_Detail.Comp_Grp_Alias]

You can use attribute substitution to supply the Take Action command arguments from thesituation, for example:PUT_COMPONENT_GROUP_ONLINE \

[&{KUB_Comp_Detail.Comp_Grp_Alias}]

You can also use attribute substitution in a workflow policy though the format is slightlydifferent:PUT_COMPONENT_GROUP_ONLINE \

[&WaitOnSituation:KUB_Comp_Detail.Comp_Grp_Alias]Command arguments

v Name: KUB_Comp_Detail.Comp_Grp_Alias– Description: The alias of the component group to be put online.– Default: ""




v Return Code: 1– Return Code Type: ALREADY_RUNNING– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB4015I


– Message: The component group is already online.v Return Code: 0

– Return Code Type: OK– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB4016I– Message: The component group was put online.


x86), Solaris (64-bit SPARC)– Message ID: KUB4028E– Message: The component group does not exist.


x86), Solaris (64-bit SPARC)– Message ID: KUB4041E– Message: An error occurred putting the component group online.










– Return Code Type: PREREQ_NOT_RUNNING– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit




memory.


Resume Siebel Server Task actionResumes a Siebel Server task by specifying the task ID.System command

To include the Take Action command in a situation or workflow policy, use the following syntaxfor the system command:RESUME_SIEBEL_SERVER_TASK \


You can use attribute substitution to supply the Take Action command arguments from thesituation, for example:RESUME_SIEBEL_SERVER_TASK \


You can also use attribute substitution in a workflow policy though the format is slightlydifferent:RESUME_SIEBEL_SERVER_TASK \

[&WaitOnSituation:KUB_Task_Detail.Task_ID]Command arguments

v Name: KUB_Task_Detail.Task_ID– Description: The ID of the task to be resumed.– Default: ""





x86), Solaris (64-bit SPARC)– Message ID: KUB4021I– Message: The specified Siebel Server task is already running.


x86), Solaris (64-bit SPARC)– Message ID: KUB4022I– Message: The Siebel Server task was resumed.


x86), Solaris (64-bit SPARC)– Message ID: KUB4045E– Message: An error occurred in resuming the Siebel Server task.



command was not found.
















x86), Solaris (64-bit SPARC)– Message ID: KUB4076E– Message: The Siebel Server task cannot be resumed, since it is not paused.

Run Srvrmgr Command actionRuns a srvrmgr command. Specify the command to be issued, e.g., /s SiebelServer4 /c "start server forcomponent WorkActn".System command

To include the Take Action command in a situation or workflow policy, use the following syntaxfor the system command:RUN_SRVRMGR_COMMAND \

[Parameters]

You can use attribute substitution to supply the Take Action command arguments from thesituation, for example:RUN_SRVRMGR_COMMAND \

[&{Parameters}]


You can also use attribute substitution in a workflow policy though the format is slightlydifferent:RUN_SRVRMGR_COMMAND \

[&WaitOnSituation:Parameters]Command arguments

v Name: Parameters– Description: The parameters for the srvrmgr command, for example, /s mySiebelServer /c

"start server for component WorkActn". It is not necessary to provide these flags and valuesunless overriding the defaults: /e (enterprise), /g (gateway ns), /p (password), /u (user ID).

– Default: ""Return codes

v Return Code: 8– Return Code Type: TIMED_OUT– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit



x86), Solaris (64-bit SPARC)– Message ID: KUB4027I– Message: The specified srvrmgr command was issued. For results, see the take action log

file.v Return Code: 14













x86), Solaris (64-bit SPARC)


– Message ID: KUB4051E– Message: The take action failed because the application server is not running.


x86), Solaris (64-bit SPARC)– Message ID: KUB4054E– Message: The specified srvrmgr command failed.





x86), Solaris (64-bit SPARC)– Message ID: KUB4077E– Message: The command parameter is missing.

Shutdown Siebel_Server_Component actionShuts down the Siebel Server component.System command

To include the Take Action command in a situation or workflow policy, use the following syntaxfor the system command:SHUTDOWN_SIEBEL_SERVER_COMPONENT \

[KUB_Comp_Detail.Comp_Alias]

You can use attribute substitution to supply the Take Action command arguments from thesituation, for example:SHUTDOWN_SIEBEL_SERVER_COMPONENT \

[&{KUB_Comp_Detail.Comp_Alias}]

You can also use attribute substitution in a workflow policy though the format is slightlydifferent:SHUTDOWN_SIEBEL_SERVER_COMPONENT \

[&WaitOnSituation:KUB_Comp_Detail.Comp_Alias]Command arguments

v Name: KUB_Comp_Detail.Comp_Alias– Description: The alias of the Siebel Server component to be shut down.– Default: ""




v Return Code: 13– Return Code Type: GENERAL_ERROR



– Message ID: KUB4028E– Message: The component group does not exist.















– Return Code Type: NOT_RUNNING– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB4080I– Message: The Siebel Server component was not shut down because it is not started.


x86), Solaris (64-bit SPARC)– Message ID: KUB4081I– Message: The Siebel Server component was shut down.


x86), Solaris (64-bit SPARC)– Message ID: KUB4083E– Message: An error occurred when shutting down the Siebel Server component.


Start Gateway Name Server actionStarts the Siebel Gateway Name Server.Return codes




x86), Solaris (64-bit SPARC)– Message ID: KUB4001I– Message: The Siebel Gateway Name Server is already started.


x86), Solaris (64-bit SPARC)– Message ID: KUB4002I– Message: The Siebel Gateway Name Server was started.


x86), Solaris (64-bit SPARC)– Message ID: KUB4035E– Message: An error occurred starting the Siebel Gateway Name Server.










– Return Code Type: INSUFFICIENT_USER_AUTHORITY– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit


memory.


Start Siebel Server actionStarts the Siebel Application Server.Return codes




x86), Solaris (64-bit SPARC)– Message ID: KUB4009I– Message: The Siebel Server is already started.


x86), Solaris (64-bit SPARC)– Message ID: KUB4010I– Message: The Siebel Server was started.

v Return Code: 2– Return Code Type: WARNING– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB4029W– Message: The Siebel Server was started and is in the WARNING state.


x86), Solaris (64-bit SPARC)– Message ID: KUB4039E– Message: An error occurred starting the Siebel Server.












x86), Solaris (64-bit SPARC)– Message ID: KUB4052E– Message: The requested command failed because the Gateway Name Server is not running.



memory.

Start Siebel Server Task actionStarts a Siebel Server task, which is an instance of a component. Specify the component name.System command

To include the Take Action command in a situation or workflow policy, use the following syntaxfor the system command:START_SIEBEL_SERVER_TASK \


[Parameters]

You can use attribute substitution to supply the Take Action command arguments from thesituation, for example:START_SIEBEL_SERVER_TASK \

[&{KUB_Comp_Detail.Comp_Alias}] \

[&{Parameters}]

You can also use attribute substitution in a workflow policy though the format is slightlydifferent:START_SIEBEL_SERVER_TASK \

[&WaitOnSituation:KUB_Comp_Detail.Comp_Alias] \

[&WaitOnSituation:Parameters]Command arguments

v Name: KUB_Comp_Detail.Comp_Alias– Description: The alias of the component instance to be started.– Default: ""

v Name: Parameters– Description: The parameters, if any, of the component instance to be started.– Default: ""





x86), Solaris (64-bit SPARC)


– Message ID: KUB4018I– Message: The Siebel Server task was started.


x86), Solaris (64-bit SPARC)– Message ID: KUB4043E– Message: An error occurred in starting the Siebel Server task.


















x86), Solaris (64-bit SPARC)– Message ID: KUB4071E– Message: No more tasks available for this component.

v Return Code: 4– Return Code Type: GENERAL_ERROR



– Message ID: KUB4072E– Message: Undefined parameter for the task or component.


x86), Solaris (64-bit SPARC)– Message ID: KUB4073E– Message: The specified component is not active on this server.

Startup Siebel_Server_Component actionStarts up the Siebel Server component.System command

To include the Take Action command in a situation or workflow policy, use the following syntaxfor the system command:STARTUP_SIEBEL_SERVER_COMPONENT \


You can use attribute substitution to supply the Take Action command arguments from thesituation, for example:STARTUP_SIEBEL_SERVER_COMPONENT \

[&{KUB_Comp_Detail.Comp_Alias}]

You can also use attribute substitution in a workflow policy though the format is slightlydifferent:STARTUP_SIEBEL_SERVER_COMPONENT \

[&WaitOnSituation:KUB_Comp_Detail.Comp_Alias]Command arguments

v Name: KUB_Comp_Detail.Comp_Alias– Description: The alias of the Siebel Server component to be started.– Default: ""





















– Return Code Type: ALREADY_RUNNING– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB4078I– Message: The Siebel Server component is already started.


x86), Solaris (64-bit SPARC)– Message ID: KUB4079I– Message: The Siebel Server component was started.


x86), Solaris (64-bit SPARC)– Message ID: KUB4082E– Message: An error occurred when starting up the Siebel Server component.

Stop Gateway Name Server actionStops the Siebel Gateway Name Server.Return codes



v Return Code: 1


– Return Code Type: NOT_RUNNING– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB4003I– Message: The Siebel Gateway Name Server was not stopped since it is not running.


x86), Solaris (64-bit SPARC)– Message ID: KUB4004I– Message: The Siebel Gateway Name Server was stopped.


x86), Solaris (64-bit SPARC)– Message ID: KUB4036E– Message: An error occurred stopping the Siebel Gateway Name Server.










– Return Code Type: DEPENDENT_STILL_RUNNING– Operating systems: Windows, Windows (64-bit), AIX (64-bit), Linux 2.6 (Intel), Linux (64-bit

x86), Solaris (64-bit SPARC)– Message ID: KUB4055E– Message: The Siebel Gateway Name Server was not stopped. A Siebel Application Server is

still running.v Return Code: 15



memory.


Stop Siebel Server actionStops the Siebel Application Server.Return codes




x86), Solaris (64-bit SPARC)– Message ID: KUB4011I– Message: The Siebel Server was not stopped since it is not running.


x86), Solaris (64-bit SPARC)– Message ID: KUB4012I– Message: The Siebel Server was stopped.


x86), Solaris (64-bit SPARC)– Message ID: KUB4040E– Message: An error occurred stopping the Siebel Server.












memory.


Stop Siebel Server Task actionStops a Siebel Server task by specifying the task ID.System command

To include the Take Action command in a situation or workflow policy, use the following syntaxfor the system command:STOP_SIEBEL_SERVER_TASK \


You can use attribute substitution to supply the Take Action command arguments from thesituation, for example:STOP_SIEBEL_SERVER_TASK \


You can also use attribute substitution in a workflow policy though the format is slightlydifferent:STOP_SIEBEL_SERVER_TASK \

[&WaitOnSituation:KUB_Task_Detail.Task_ID]Command arguments

v Name: KUB_Task_Detail.Task_ID– Description: The ID of the task to be stopped.– Default: ""





x86), Solaris (64-bit SPARC)– Message ID: KUB4023I– Message: The specified Siebel Server task was not stopped since it is not running.


x86), Solaris (64-bit SPARC)– Message ID: KUB4024I– Message: The Siebel Server task was stopped.


x86), Solaris (64-bit SPARC)– Message ID: KUB4030I– Message: The Siebel Server task is stopping.


x86), Solaris (64-bit SPARC)– Message ID: KUB4046E– Message: An error occurred in stopping the Siebel Server task.

v Return Code: 14

















memory.

Take Component Group Offline actionTakes the component group offline.System command

To include the Take Action command in a situation or workflow policy, use the following syntaxfor the system command:TAKE_COMPONENT_GROUP_OFFLINE \

[KUB_Comp_Detail.Comp_Grp_Alias]

You can use attribute substitution to supply the Take Action command arguments from thesituation, for example:TAKE_COMPONENT_GROUP_OFFLINE \

[&{KUB_Comp_Detail.Comp_Grp_Alias}]


You can also use attribute substitution in a workflow policy though the format is slightlydifferent:TAKE_COMPONENT_GROUP_OFFLINE \

[&WaitOnSituation:KUB_Comp_Detail.Comp_Grp_Alias]Command arguments

v Name: KUB_Comp_Detail.Comp_Grp_Alias– Description: The alias of the component group to be taken offline.– Default: ""





x86), Solaris (64-bit SPARC)– Message ID: KUB4013I– Message: The component group was not taken offline since it is not online.


x86), Solaris (64-bit SPARC)– Message ID: KUB4014I– Message: The component group was taken offline.




x86), Solaris (64-bit SPARC)– Message ID: KUB4042E– Message: An error occurred taking the component group offline.







– Return Code Type: GENERAL_ERROR



– Message ID: KUB4050E– Message: The requested command failed. A required environment variable is not correctly






memory.


Chapter 5. Event mapping

The Tivoli Event Integration Facility (EIF) interface is used to forward situation events to TivoliNetcool/OMNIbus or Tivoli Enterprise Console®.

EIF events specify an event class, and the event data is specified as name-value pairs that identify thename of an event slot and the value for the slot. An event class can have subclasses. IBM TivoliMonitoring provides the base event class definitions and a set of base slots that are included in allmonitoring events. Agents extend the base event classes to define subclasses that include agent-specificslots. For Siebel agent events, the event classes correspond to the agent attribute groups, and theagent-specific slots correspond to the attributes in the attribute group.

The situation editor in the Tivoli Enterprise Portal can be used to perform custom mapping of data to EIFslots instead of using the default mapping described in this topic. For more information about EIF slotcustomization, see the Tivoli Enterprise Portal User's Guide.

Tivoli Enterprise Console requires that event classes and their slots are defined in BAROC (Basic Recorderof Objects in C) files. Each agent provides a BAROC file that contains event class definitions for the agentand is installed on the Tivoli Enterprise Monitoring Server in the TECLIB directory (install_dir/cms/TECLIB for Windows systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems) whenapplication support for the agent is installed. The BAROC file for the agent and the base BAROC filesprovided with Tivoli Monitoring must also be installed onto the Tivoli Enterprise Console. For details, see“Setting up event forwarding to Tivoli Enterprise Console” in the IBM Tivoli Monitoring Installation andSetup Guide.

Each of the event classes is a child of KUB_Base and is defined in the kub.baroc (version 07.01.01) file.The KUB_Base event class can be used for generic rules processing for any event from the IBM TivoliComposite Application Manager Agent for Siebel CRM.

For events that are generated by situations in the Availability attribute group, events are sent by using theITM_KUB_AVAILABILITY event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv application_component: STRINGv name: STRINGv name_enum: STRINGv kub_status: INTEGERv kub_status_enum: STRINGv full_name: STRINGv full_name_enum: STRINGv type: INTEGERv type_enum: STRINGv virtual_size: INTEGERv page_faults_per_sec: INTEGERv working_set_size: INTEGERv thread_count: INTEGERv pid: INTEGERv percent_privileged_time: INTEGER


v percent_user_mode_time: INTEGERv percent_processor_time: INTEGERv command_line: STRINGv command_line_enum: STRINGv functionality_test_status: INTEGERv functionality_test_status_enum: STRINGv functionality_test_message: STRINGv functionality_test_message_enum: STRING

For events that are generated by situations in the Comp Counts attribute group, events are sent by usingthe ITM_KUB_COMP_COUNTS event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv comp_name: STRINGv task_count: INTEGERv task_count_enum: STRING

For events that are generated by situations in the Comp CPU Util Rollup attribute group, events are sentby using the ITM_KUB_COMP_CPU_UTIL_ROLLUP event class. This event class contains the followingslots:v node: STRINGv timestamp: STRINGv maximum: INTEGERv maximum_enum: STRINGv minimum: INTEGERv minimum_enum: STRINGv average: INTEGERv average_enum: STRINGv total: INTEGERv total_enum: STRING

For events that are generated by situations in the Comp Detail attribute group, events are sent by usingthe ITM_KUB_COMP_DETAIL event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv comp_alias: STRINGv comp_name: STRINGv comp_grp_alias: STRINGv run_mode: STRINGv run_state: STRINGv running_tasks: INTEGERv running_tasks_enum: STRINGv gateway_name: STRINGv enterprise_name: STRING


For events that are generated by situations in the Comp Logs attribute group, events are sent by usingthe ITM_KUB_COMP_LOGS event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv source_name: STRINGv event_type_alias: STRINGv type: STRINGv kub_severity: STRINGv sarmid: STRINGv logs_timestamp: STRINGv log_message: STRINGv gateway_name: STRING

For events that are generated by situations in the Comp Logs Pre77 attribute group, events are sent byusing the ITM_KUB_COMP_LOGS_PRE77 event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv source_name: STRINGv event_type_alias: STRINGv type: STRINGv kub_severity: STRINGv logs_timestamp: STRINGv log_message: STRING

For events that are generated by situations in the Comp Name attribute group, events are sent by usingthe ITM_KUB_COMP_NAME event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv comp_log_name: STRINGv comp_pid: INTEGERv comp_pid_enum: STRING

For events that are generated by situations in the Component Resource attribute group, events are sent byusing the ITM_KUB_COMPONENT_RESOURCE event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv application_component: STRINGv name: STRINGv name_enum: STRINGv kub_status: INTEGERv kub_status_enum: STRINGv full_name: STRINGv full_name_enum: STRINGv type: INTEGERv type_enum: STRINGv virtual_size: INTEGERv page_faults_per_sec: INTEGER

Chapter 5. Event mapping 201

v working_set_size: INTEGERv thread_count: INTEGERv pid: INTEGERv percent_privileged_time: INTEGERv percent_user_mode_time: INTEGERv percent_processor_time: INTEGERv command_line: STRINGv command_line_enum: STRINGv functionality_test_status: INTEGERv functionality_test_status_enum: STRINGv functionality_test_message: STRINGv functionality_test_message_enum: STRINGv comp_log_name: STRINGv comp_pid: INTEGERv comp_pid_enum: STRING

For events that are generated by situations in the Component Statistics attribute group, events are sent byusing the ITM_KUB_COMPONENT_STATISTICS event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv component_name: STRINGv statistic: STRINGv statistic_alias: STRINGv sd_subsystem: STRINGv server_name: STRINGv current_value: REALv current_value_enum: STRINGv sd_description: STRING

For events that are generated by situations in the Database File System attribute group, events are sent byusing the ITM_KUB_DATABASE_FILE_SYSTEM event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv name: STRINGv free_space_in_mb: INTEGERv free_space_in_mb_enum: STRINGv percent_used: INTEGERv percent_used_enum: STRINGv percent_free: INTEGERv percent_free_enum: STRINGv hours_until_full: INTEGERv hours_until_full_enum: STRINGv total_size_in_mb: INTEGERv total_size_in_mb_enum: STRINGv mount_point: STRINGv gateway_name: STRING


For events that are generated by situations in the Database Files attribute group, events are sent by usingthe ITM_KUB_DATABASE_FILES event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv directory_name: STRINGv file_name: STRINGv current_size_in_mb: INTEGERv current_size_in_mb_enum: STRINGv percent_of_file_system_used: INTEGERv percent_of_file_system_used_enum: STRINGv size_change_last_hour: INTEGERv size_change_last_hour_enum: STRINGv percent_change_last_hour: INTEGERv percent_change_last_hour_enum: STRINGv size_change_average: INTEGERv size_change_average_enum: STRINGv percent_change_average: INTEGERv percent_change_average_enum: STRINGv size_change_total: INTEGERv size_change_total_enum: STRINGv percent_change_total: INTEGERv percent_change_total_enum: STRINGv hours_until_full: INTEGERv hours_until_full_enum: STRINGv type: INTEGERv type_enum: STRING

For events that are generated by situations in the DLA Input attribute group, events are sent by using theITM_KUB_DLA_INPUT event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv enterprise_name: STRINGv gateway_bind_address: STRINGv gateway_ip_address: STRINGv gateway_port: INTEGERv gateway_port_enum: STRINGv gateway_hostname: STRINGv server_type: STRINGv server_name: STRINGv host_name: STRINGv install_dir: STRINGv server_state: STRINGv start_time: STRINGv end_time: STRINGv server_status: STRINGv active_task_count: INTEGER


v active_task_count_enum: STRINGv connection_status: STRINGv updated_start_time: STRINGv updated_end_time: STRINGv gateway_name: STRINGv enterprise_name0: STRING

For events that are generated by situations in the Enterprise attribute group, events are sent by using theITM_KUB_ENTERPRISE event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv enterprise_name: STRINGv gateway_bind_address: STRINGv gateway_ip_address: STRINGv gateway_port: INTEGERv gateway_port_enum: STRINGv gateway_hostname: STRINGv server_type: STRING

For events that are generated by situations in the File System attribute group, events are sent by usingthe ITM_KUB_FILE_SYSTEM event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv name: STRINGv free_space_in_mb: INTEGERv free_space_in_mb_enum: STRINGv percent_used: INTEGERv percent_used_enum: STRINGv percent_free: INTEGERv percent_free_enum: STRINGv hours_until_full: INTEGERv hours_until_full_enum: STRINGv total_size_in_mb: INTEGERv total_size_in_mb_enum: STRINGv mount_point: STRINGv gateway_name: STRING

For events that are generated by situations in the Files attribute group, events are sent by using theITM_KUB_FILES event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv directory_name: STRINGv filename: STRINGv current_size_in_mb: INTEGERv current_size_in_mb_enum: STRINGv percent_of_file_system_used: INTEGERv percent_of_file_system_used_enum: STRING


v size_change_last_hour: INTEGERv size_change_last_hour_enum: STRINGv percent_change_last_hour: INTEGERv percent_change_last_hour_enum: STRINGv size_change_average: INTEGERv size_change_average_enum: STRINGv percent_change_average: INTEGERv percent_change_average_enum: STRINGv size_change_total: INTEGERv size_change_total_enum: STRINGv percent_change_total: INTEGERv percent_change_total_enum: STRINGv hours_until_full: INTEGERv hours_until_full_enum: STRINGv type: INTEGERv type_enum: STRINGv gateway_name: STRING

For events that are generated by situations in the Gate Log attribute group, events are sent by using theITM_KUB_GATE_LOG event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv source_name: STRINGv event_type_alias: STRINGv type: STRINGv kub_severity: STRINGv sarmid: STRINGv logs_timestamp: STRINGv log_message: STRINGv gateway_name: STRING

For events that are generated by situations in the Gate Log Pre77 attribute group, events are sent byusing the ITM_KUB_GATE_LOG_PRE77 event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv source_name: STRINGv event_type_alias: STRINGv type: STRINGv kub_severity: STRINGv logs_timestamp: STRINGv log_message: STRING

For events that are generated by situations in the Marketing Statistics attribute group, events are sent byusing the ITM_KUB_MARKETING_STATISTICS event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv marketing_statistics_current: INTEGER


v marketing_statistics_current_enum: STRINGv marketing_statistics_orphaned: INTEGERv marketing_statistics_orphaned_enum: STRINGv marketing_statistics_invalid: INTEGERv marketing_statistics_invalid_enum: STRINGv marketing_statistics_ancient: INTEGERv marketing_statistics_ancient_enum: STRINGv marketing_statistics_total: INTEGERv marketing_statistics_total_enum: STRINGv marketing_statistics_duration: INTEGERv marketing_statistics_duration_enum: STRINGv gateway_name: STRINGv enterprise_name: STRINGv server_name: STRING

For events that are generated by situations in the Performance Object Status attribute group, events aresent by using the ITM_KUB_PERFORMANCE_OBJECT_STATUS event class. This event class contains thefollowing slots:v node: STRINGv timestamp: STRINGv query_name: STRINGv object_name: STRINGv object_type: INTEGERv object_type_enum: STRINGv object_status: INTEGERv object_status_enum: STRINGv error_code: INTEGERv error_code_enum: STRING

For events that are generated by situations in the Server Log attribute group, events are sent by using theITM_KUB_SERVER_LOG event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv source_name: STRINGv event_type_alias: STRINGv type: STRINGv kub_severity: STRINGv sarmid: STRINGv logs_timestamp: STRINGv log_message: STRINGv gateway_name: STRINGv enterprise_name: STRINGv server_name: STRING

For events that are generated by situations in the Server Log Pre77 attribute group, events are sent byusing the ITM_KUB_SERVER_LOG_PRE77 event class. This event class contains the following slots:v node: STRING


v timestamp: STRINGv source_name: STRINGv event_type_alias: STRINGv type: STRINGv kub_severity: STRINGv logs_timestamp: STRINGv log_message: STRING

For events that are generated by situations in the Siebel Server attribute group, events are sent by usingthe ITM_KUB_SIEBEL_SERVER event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv host_name: STRINGv install_dir: STRINGv server_state: STRINGv start_time: STRINGv end_time: STRINGv server_status: STRINGv active_task_count: INTEGERv active_task_count_enum: STRINGv connection_status: STRINGv updated_start_time: STRINGv updated_end_time: STRINGv gateway_name: STRINGv enterprise_name: STRING

For events that are generated by situations in the Siebel Statistics attribute group, events are sent by usingthe ITM_KUB_SIEBEL_STATISTICS event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv statistic: STRINGv statistic_alias: STRINGv sd_subsystem: STRINGv server_name: STRINGv current_value: REALv current_value_enum: STRINGv sd_description: STRING

For events that are generated by situations in the Statistic Details attribute group, events are sent byusing the ITM_KUB_STATISTIC_DETAILS event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv average_connect_time: REALv average_connect_time_enum: STRINGv average_oob_component_time: REALv average_oob_component_time_enum: STRING


v average_oob_queue_size: REALv average_oob_queue_size_enum: STRINGv average_reply_size: REALv average_reply_size_enum: STRINGv average_request_size: REALv average_request_size_enum: STRINGv average_requests_per_session: REALv average_requests_per_session_enum: STRINGv average_response_time: REALv average_response_time_enum: STRINGv average_think_time: REALv average_think_time_enum: STRINGv avg_sql_execute_time: REALv avg_sql_execute_time_enum: STRINGv avg_sql_fetch_time: REALv avg_sql_fetch_time_enum: STRINGv avg_sql_parse_time: REALv avg_sql_parse_time_enum: STRINGv cpu_time: REALv cpu_time_enum: STRINGv completed_transactions_from_pim: REALv completed_transactions_from_pim_enum: STRINGv completed_transactions_from_siebel: REALv completed_transactions_from_siebel_enum: STRINGv data_cursor_cache_cpu: REALv data_cursor_cache_cpu_enum: STRINGv data_cursor_cache_hits: REALv data_cursor_cache_hits_enum: STRINGv data_cursor_cache_memory: REALv data_cursor_cache_memory_enum: STRINGv data_cursor_cache_misses: REALv data_cursor_cache_misses_enum: STRINGv data_cursor_cache_objects: REALv data_cursor_cache_objects_enum: STRINGv eai_receiver_total_messages_processed: REALv eai_receiver_total_messages_processed_enum: STRINGv elapsed_time: REALv elapsed_time_enum: STRINGv events_processed: REALv events_processed_enum: STRINGv events_processed_rate: REALv events_processed_rate_enum: STRINGv fdr_avg_time_between_aging: REALv fdr_avg_time_between_aging_enum: STRINGv fdr_buffer_life_in_seconds: REAL


v fdr_buffer_life_in_seconds_enum: STRINGv fdr_buffer_wraps: REALv fdr_buffer_wraps_enum: STRINGv failed_transactions_from_pim: REALv failed_transactions_from_pim_enum: STRINGv failed_transactions_from_siebel: REALv failed_transactions_from_siebel_enum: STRINGv global_data_cursor_cache_cpu: REALv global_data_cursor_cache_cpu_enum: STRINGv global_data_cursor_cache_hits: REALv global_data_cursor_cache_hits_enum: STRINGv global_data_cursor_cache_memory: REALv global_data_cursor_cache_memory_enum: STRINGv global_data_cursor_cache_misses: REALv global_data_cursor_cache_misses_enum: STRINGv global_data_cursor_cache_objects: REALv global_data_cursor_cache_objects_enum: STRINGv maximum_oob_component_time: REALv maximum_oob_component_time_enum: STRINGv maximum_peak_memory_usage: REALv maximum_peak_memory_usage_enum: STRINGv minimum_peak_memory_usage: REALv minimum_peak_memory_usage_enum: STRINGv num_of_dbconn_retries: REALv num_of_dbconn_retries_enum: STRINGv num_of_dlrbk_retries: REALv num_of_dlrbk_retries_enum: STRINGv num_of_exhausted_retries: REALv num_of_exhausted_retries_enum: STRINGv number_of_component_crashes: REALv number_of_component_crashes_enum: STRINGv number_of_component_restarts: REALv number_of_component_restarts_enum: STRINGv number_of_errors: REALv number_of_errors_enum: STRINGv number_of_sql_executes: REALv number_of_sql_executes_enum: STRINGv number_of_sql_fetches: REALv number_of_sql_fetches_enum: STRINGv number_of_sql_parses: REALv number_of_sql_parses_enum: STRINGv number_of_sleeps: REALv number_of_sleeps_enum: STRINGv number_of_object_rows_assigned: REALv number_of_object_rows_assigned_enum: STRING


v object_manager_errors: REALv object_manager_errors_enum: STRINGv psp_cache_hit_total: REALv psp_cache_hit_total_enum: STRINGv psp_cache_miss_total: REALv psp_cache_miss_total_enum: STRINGv reply_messages: REALv reply_messages_enum: STRINGv request_messages: REALv request_messages_enum: STRINGv sql_cursor_cache_hits: REALv sql_cursor_cache_hits_enum: STRINGv sql_cursor_cache_misses: REALv sql_cursor_cache_misses_enum: STRINGv sql_cursor_total_cpu: REALv sql_cursor_total_cpu_enum: STRINGv sql_cursor_total_mem: REALv sql_cursor_total_mem_enum: STRINGv sql_cursor_total_objects: REALv sql_cursor_total_objects_enum: STRINGv sql_execute_time: REALv sql_execute_time_enum: STRINGv sql_fetch_time: REALv sql_fetch_time_enum: STRINGv sql_object_cache_cpu: REALv sql_object_cache_cpu_enum: STRINGv sql_object_cache_hits: REALv sql_object_cache_hits_enum: STRINGv sql_object_cache_memory: REALv sql_object_cache_memory_enum: STRINGv sql_object_cache_misses: REALv sql_object_cache_misses_enum: STRINGv sql_object_cache_objects: REALv sql_object_cache_objects_enum: STRINGv sql_parse_time: REALv sql_parse_time_enum: STRINGv searchevents_processed: REALv searchevents_processed_enum: STRINGv searchevents_processed_rate: REALv searchevents_processed_rate_enum: STRINGv siebel_adapter_total_query_calls: REALv siebel_adapter_total_query_calls_enum: STRINGv siebel_adapter_total_query_size: REALv siebel_adapter_total_query_size_enum: STRINGv siebel_adapter_total_sync_size: REAL


v siebel_adapter_total_sync_size_enum: STRINGv siebel_adapter_total_sync_upsert_calls: REALv siebel_adapter_total_sync_upsert_calls_enum: STRINGv sleep_time: REALv sleep_time_enum: STRINGv tasks_exceeding_configured_capacity: REALv tasks_exceeding_configured_capacity_enum: STRINGv tests_attempted: REALv tests_attempted_enum: STRINGv tests_failed: REALv tests_failed_enum: STRINGv tests_successful: REALv tests_successful_enum: STRINGv total_database_response_time: REALv total_database_response_time_enum: STRINGv total_reply_size: REALv total_reply_size_enum: STRINGv total_request_size: REALv total_request_size_enum: STRINGv total_response_time: REALv total_response_time_enum: STRINGv total_tasks: REALv total_tasks_enum: STRINGv total_think_time: REALv total_think_time_enum: STRINGv total_xml_converter_size_of_input_buffer: REALv total_xml_converter_size_of_input_buffer_enum: STRINGv total_xml_converter_size_of_output_buffer: REALv total_xml_converter_size_of_output_buffer_enum: STRINGv total_xml_generator_calls: REALv total_xml_generator_calls_enum: STRINGv total_xml_parser_calls: REALv total_xml_parser_calls_enum: STRINGv transactions_form_siebel_in_progress: REALv transactions_form_siebel_in_progress_enum: STRINGv transactions_from_pim_in_progress: REALv transactions_from_pim_in_progress_enum: STRING

For events that are generated by situations in the Statistics AsgnSubsys attribute group, events are sent byusing the ITM_KUB_STATISTICS_ASGNSUBSYS event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv number_of_object_rows_assigned: INTEGERv number_of_object_rows_assigned_enum: STRING


For events that are generated by situations in the Statistics CommInboundProcessor attribute group,events are sent by using the ITM_KUB_STATISTICS_COMMINBOUNDPROCESSOR event class. Thisevent class contains the following slots:v node: STRINGv timestamp: STRINGv events_processed: INTEGERv events_processed_enum: STRINGv events_processed_rate: INTEGERv events_processed_rate_enum: STRING

For events that are generated by situations in the Statistics EAISubsys attribute group, events are sent byusing the ITM_KUB_STATISTICS_EAISUBSYS event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv eai_receiver_total_messages_processed: INTEGERv eai_receiver_total_messages_processed_enum: STRINGv siebel_adapter_total_query_calls: INTEGERv siebel_adapter_total_query_calls_enum: STRINGv siebel_adapter_total_query_size: INTEGERv siebel_adapter_total_query_size_enum: STRINGv siebel_adapter_total_sync_size: INTEGERv siebel_adapter_total_sync_size_enum: STRINGv siebel_adapter_total_sync_upsert_calls: INTEGERv siebel_adapter_total_sync_upsert_calls_enum: STRING

For events that are generated by situations in the Statistics FlightDataRecorder attribute group, events aresent by using the ITM_KUB_STATISTICS_FLIGHTDATARECORDER event class. This event class containsthe following slots:v node: STRINGv timestamp: STRINGv fdr_avg_time_between_aging: INTEGERv fdr_avg_time_between_aging_enum: STRINGv fdr_buffer_life_in_seconds: INTEGERv fdr_buffer_life_in_seconds_enum: STRINGv fdr_buffer_wraps: INTEGERv fdr_buffer_wraps_enum: STRING

For events that are generated by situations in the Statistics InfraCore attribute group, events are sent byusing the ITM_KUB_STATISTICS_INFRACORE event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv cpu_time: REALv cpu_time_enum: STRINGv elapsed_time: REALv elapsed_time_enum: STRINGv maximum_peak_memory_usage: INTEGERv maximum_peak_memory_usage_enum: STRING


v minimum_peak_memory_usage: INTEGERv minimum_peak_memory_usage_enum: STRINGv number_of_component_crashes: INTEGERv number_of_component_crashes_enum: STRINGv number_of_component_restarts: INTEGERv number_of_component_restarts_enum: STRINGv number_of_errors: INTEGERv number_of_errors_enum: STRINGv number_of_sleeps: INTEGERv number_of_sleeps_enum: STRINGv sleep_time: INTEGERv sleep_time_enum: STRINGv tasks_exceeding_configured_capacity: INTEGERv tasks_exceeding_configured_capacity_enum: STRINGv total_tasks: INTEGERv total_tasks_enum: STRINGv gateway_name: STRINGv enterprise_name: STRINGv server_name: STRING

For events that are generated by situations in the Statistics InfraDatabase attribute group, events are sentby using the ITM_KUB_STATISTICS_INFRADATABASE event class. This event class contains thefollowing slots:v node: STRINGv timestamp: STRINGv avg_sql_execute_time: REALv avg_sql_execute_time_enum: STRINGv avg_sql_fetch_time: REALv avg_sql_fetch_time_enum: STRINGv avg_sql_parse_time: REALv avg_sql_parse_time_enum: STRINGv sql_parse_time: REALv sql_parse_time_enum: STRINGv number_of_sql_executes: INTEGERv number_of_sql_executes_enum: STRINGv number_of_sql_fetches: INTEGERv number_of_sql_fetches_enum: STRINGv number_of_sql_parses: INTEGERv number_of_sql_parses_enum: STRINGv sql_execute_time: REALv sql_execute_time_enum: STRINGv sql_fetch_time: REALv sql_fetch_time_enum: STRINGv gateway_name: STRINGv enterprise_name: STRINGv server_name: STRING


For events that are generated by situations in the Statistics InfraMultiThread attribute group, events aresent by using the ITM_KUB_STATISTICS_INFRAMULTITHREAD event class. This event class containsthe following slots:v node: STRINGv timestamp: STRINGv average_oob_component_time: REALv average_oob_component_time_enum: STRINGv average_oob_queue_size: INTEGERv average_oob_queue_size_enum: STRINGv maximum_oob_component_time: REALv maximum_oob_component_time_enum: STRING

For events that are generated by situations in the Statistics InfraObjMgr attribute group, events are sentby using the ITM_KUB_STATISTICS_INFRAOBJMGR event class. This event class contains the followingslots:v node: STRINGv timestamp: STRINGv average_connect_time: REALv average_connect_time_enum: STRINGv average_reply_size: INTEGERv average_reply_size_enum: STRINGv average_requests_per_session: INTEGERv average_requests_per_session_enum: STRINGv average_request_size: INTEGERv average_request_size_enum: STRINGv average_response_time: REALv average_response_time_enum: STRINGv average_think_time: INTEGERv average_think_time_enum: STRINGv data_cursor_cache_cpu: INTEGERv data_cursor_cache_cpu_enum: STRINGv data_cursor_cache_hits: INTEGERv data_cursor_cache_hits_enum: STRINGv data_cursor_cache_memory: INTEGERv data_cursor_cache_memory_enum: STRINGv data_cursor_cache_misses: INTEGERv data_cursor_cache_misses_enum: STRINGv data_cursor_cache_objects: INTEGERv data_cursor_cache_objects_enum: STRINGv total_database_response_time: REALv total_database_response_time_enum: STRINGv object_manager_errors: INTEGERv object_manager_errors_enum: STRINGv global_data_cursor_cache_cpu: INTEGERv global_data_cursor_cache_cpu_enum: STRINGv global_data_cursor_cache_hits: INTEGER


v global_data_cursor_cache_hits_enum: STRINGv global_data_cursor_cache_memory: INTEGERv global_data_cursor_cache_memory_enum: STRINGv global_data_cursor_cache_misses: INTEGERv global_data_cursor_cache_misses_enum: STRINGv global_data_cursor_cache_objects: INTEGERv global_data_cursor_cache_objects_enum: STRINGv reply_messages: INTEGERv reply_messages_enum: STRINGv total_reply_size: INTEGERv total_reply_size_enum: STRINGv request_messages: INTEGERv request_messages_enum: STRINGv total_response_time: REALv total_response_time_enum: STRINGv total_request_size: INTEGERv total_request_size_enum: STRINGv sql_cursor_cache_hits: INTEGERv sql_cursor_cache_hits_enum: STRINGv sql_cursor_cache_misses: INTEGERv sql_cursor_cache_misses_enum: STRINGv sql_cursor_total_cpu: INTEGERv sql_cursor_total_cpu_enum: STRINGv sql_cursor_total_mem: INTEGERv sql_cursor_total_mem_enum: STRINGv sql_cursor_total_objects: INTEGERv sql_cursor_total_objects_enum: STRINGv sql_object_cache_cpu: INTEGERv sql_object_cache_cpu_enum: STRINGv sql_object_cache_hits: INTEGERv sql_object_cache_hits_enum: STRINGv sql_object_cache_memory: INTEGERv sql_object_cache_memory_enum: STRINGv sql_object_cache_misses: INTEGERv sql_object_cache_misses_enum: STRINGv sql_object_cache_objects: INTEGERv sql_object_cache_objects_enum: STRINGv total_think_time: REALv total_think_time_enum: STRINGv gateway_name: STRINGv enterprise_name: STRINGv server_name: STRING

For events that are generated by situations in the Statistics InfraRecovery attribute group, events are sentby using the ITM_KUB_STATISTICS_INFRARECOVERY event class. This event class contains thefollowing slots:


v node: STRINGv timestamp: STRINGv num_of_dbconn_retries: INTEGERv num_of_dbconn_retries_enum: STRINGv num_of_dlrbk_retries: INTEGERv num_of_dlrbk_retries_enum: STRINGv num_of_exhausted_retries: INTEGERv num_of_exhausted_retries_enum: STRING

For events that are generated by situations in the Statistics PIMSIENG attribute group, events are sent byusing the ITM_KUB_STATISTICS_PIMSIENG event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv transactions_form_siebel_in_progress: INTEGERv transactions_form_siebel_in_progress_enum: STRINGv transactions_from_pim_in_progress: INTEGERv transactions_from_pim_in_progress_enum: STRINGv completed_transactions_from_pim: INTEGERv completed_transactions_from_pim_enum: STRINGv completed_transactions_from_siebel: INTEGERv completed_transactions_from_siebel_enum: STRINGv failed_transactions_from_pim: INTEGERv failed_transactions_from_pim_enum: STRINGv failed_transactions_from_siebel: INTEGERv failed_transactions_from_siebel_enum: STRINGv gateway_name: STRINGv enterprise_name: STRINGv server_name: STRING

For events that are generated by situations in the Statistics PSPEngine attribute group, events are sent byusing the ITM_KUB_STATISTICS_PSPENGINE event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv psp_cache_hit_total: INTEGERv psp_cache_hit_total_enum: STRINGv psp_cache_miss_total: INTEGERv psp_cache_miss_total_enum: STRING

For events that are generated by situations in the Statistics SearchDataProcessor attribute group, eventsare sent by using the ITM_KUB_STATISTICS_SEARCHDATAPROCESSOR event class. This event classcontains the following slots:v node: STRINGv timestamp: STRINGv searchevents_processed: INTEGERv searchevents_processed_enum: STRINGv searchevents_processed_rate: INTEGERv searchevents_processed_rate_enum: STRING


For events that are generated by situations in the Statistics TestSubsys attribute group, events are sent byusing the ITM_KUB_STATISTICS_TESTSUBSYS event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv tests_attempted: INTEGERv tests_attempted_enum: STRINGv tests_failed: INTEGERv tests_failed_enum: STRINGv tests_successful: INTEGERv tests_successful_enum: STRING

For events that are generated by situations in the Statistics XMLCnv attribute group, events are sent byusing the ITM_KUB_STATISTICS_XMLCNV event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv total_xml_converter_size_of_input_buffer: INTEGERv total_xml_converter_size_of_input_buffer_enum: STRINGv total_xml_converter_size_of_output_buffer: INTEGERv total_xml_converter_size_of_output_buffer_enum: STRINGv total_xml_generator_calls: INTEGERv total_xml_generator_calls_enum: STRINGv total_xml_parser_calls: INTEGERv total_xml_parser_calls_enum: STRING

For events that are generated by situations in the Task CPU Util Rollup attribute group, events are sentby using the ITM_KUB_TASK_CPU_UTIL_ROLLUP event class. This event class contains the followingslots:v node: STRINGv timestamp: STRINGv maximum: INTEGERv maximum_enum: STRINGv minimum: INTEGERv minimum_enum: STRINGv average: INTEGERv average_enum: STRINGv total: INTEGERv total_enum: STRING

For events that are generated by situations in the Task Detail attribute group, events are sent by using theITM_KUB_TASK_DETAIL event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv comp_alias: STRINGv comp_group_alias: STRINGv task_id: STRINGv task_pid: INTEGER


v task_pid_enum: STRINGv run_state: STRINGv task_label: STRINGv parent_task_id: STRINGv task_ping_time: STRINGv pid_alias_tid: STRINGv task_status: STRINGv task_start_time: STRINGv task_end_time: STRINGv task_elapsed_time: INTEGERv task_elapsed_time_enum: STRING

For events that are generated by situations in the Task Resource attribute group, events are sent by usingthe ITM_KUB_TASK_RESOURCE event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv application_component: STRINGv name: STRINGv name_enum: STRINGv kub_status: INTEGERv kub_status_enum: STRINGv full_name: STRINGv full_name_enum: STRINGv type: INTEGERv type_enum: STRINGv virtual_size: INTEGERv page_faults_per_sec: INTEGERv working_set_size: INTEGERv thread_count: INTEGERv pid: INTEGERv percent_privileged_time: INTEGERv percent_user_mode_time: INTEGERv percent_processor_time: INTEGERv command_line: STRINGv command_line_enum: STRINGv functionality_test_status: INTEGERv functionality_test_status_enum: STRINGv functionality_test_message: STRINGv functionality_test_message_enum: STRINGv server_name: STRINGv comp_alias: STRINGv comp_group_alias: STRINGv task_id: STRINGv task_pid: INTEGERv task_pid_enum: STRING


v run_state: STRINGv task_label: STRINGv parent_task_id: STRINGv task_ping_time: STRINGv pid_alias_tid: STRINGv task_status: STRINGv task_start_time: STRINGv task_end_time: STRINGv task_elapsed_time: INTEGERv task_elapsed_time_enum: STRING

For events that are generated by situations in the Task Summary attribute group, events are sent by usingthe ITM_KUB_TASK_SUMMARY event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv running_count: INTEGERv running_count_enum: STRINGv completed_count: INTEGERv completed_count_enum: STRINGv error_count: INTEGERv error_count_enum: STRINGv other_count: INTEGERv other_count_enum: STRINGv interactive_count: INTEGERv interactive_count_enum: STRINGv background_count: INTEGERv background_count_enum: STRINGv batch_count: INTEGERv batch_count_enum: STRINGv normal_count: INTEGERv normal_count_enum: STRINGv worker_count: INTEGERv worker_count_enum: STRING

For events that are generated by situations in the User Session attribute group, events are sent by usingthe ITM_KUB_USER_SESSION event class. This event class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv task_id: STRINGv task_pid: STRINGv run_mode: STRINGv task_type: STRINGv user_id: STRINGv task_runstate: STRINGv task_start_time: STRING


v task_end_time: STRINGv elapsed_time: INTEGERv elapsed_time_enum: STRINGv gateway_name: STRINGv enterprise_name: STRING

For events that are generated by situations in the User Session Summary attribute group, events are sentby using the ITM_KUB_USER_SESSION_SUMMARY event class. This event class contains the followingslots:v node: STRINGv timestamp: STRINGv running_count: INTEGERv running_count_enum: STRINGv completed_count: INTEGERv completed_count_enum: STRINGv error_count: INTEGERv error_count_enum: STRINGv other_count: INTEGERv other_count_enum: STRING


Chapter 6. Tivoli Common Reporting for the Siebel agent

This chapter contains agent-specific information about Tivoli Common Reporting for the Siebel agent. Usethis chapter in conjunction with the Tivoli Common Reporting chapter in the IBM Tivoli MonitoringAdministrator's Guide V6.2.3 for complete information about prerequisites, importing reports, and runningreports.

The ITCAM agent for Siebel CRM Data Model and Reports are historical reports, reporting against rawand summarized data collected in Tivoli Data Warehouse. These reports are built to run against ITCAMfor Applications 7.1 only.

The following databases are supported:v DB2 V8.1 FP10 and higher, V8.2 FP3 and higher, V9.1 and fixpacks, or V9.5v Oracle v9.2, 10g Release 1 and 10g Release 2v MS SQL 2000 SP4 or 2005

This set of data model and reports is primarily focused on Siebel agent. The report is a set of samplereports and is intended to guide you to customize your own reports on the data model.

The reports can be administered and run on Tivoli Common Reporting V2.1, which is shipped withITCAM for Applications 7.1.

For more information about Tivoli Common Reporting, see http://www.ibm.com/developerworks/spaces/tcr.

Cognos-based report packagesThe Cognos-based Tivoli Common Reporting tool is used to create, view, and manage reports for theTivoli group of products.

You can use the Cognos reports to analyze resource information such as availability, utilization,performance, and so on. With Cognos reports, you can evaluate the key metrics of the computers that areon the managed environment of your organization.

By using the Tivoli Common Reporting tool, you can:v Create custom reports by using the drag-and-drop feature integrated with the web-based editor.v Schedule, share, secure, and administer reports in a single interface.v Save the report in HTML, PDF, Excel, XML, or CSV file formats.v Share reports by e-mail or save the reports in a file system for later use.

The following databases are supported for all reports:v DB2v Oraclev SQL Server

You can use Tivoli Common Reporting V2.1 software that is shipped with IBM Tivoli Monitoring V6.2.3 ora later version to administer, run, and edit Cognos reports. For more information about Tivoli CommonReporting, see the Tivoli Common Reporting Information Center (http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_21/ic-home.html).


http://www.ibm.com/developerworks/spaces/tcr

http://www.ibm.com/developerworks/spaces/tcr

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_21/ic-home.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_21/ic-home.html

PrerequisitesThis topic describes the prerequisite components for installing and running Tivoli Common Reportingpackages in Tivoli Monitoring products. You must ensure that all prerequisites are met before running theCognos reports.1. Install Tivoli Common Reporting.

To install and configure Tivoli Common Reporting , see the documentation in the IBM Tivoli CommonReporting information center (http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_21/ttcr_install.html).To ensure that Tivoli Common Reporting is running, go to: https://machine_name:16311/ibm/console/.

2. Configure historical collection for the Siebel agent and the IBM Tivoli Warehouse Summarization andPruning Agent. Ensure that historical data collection is turned on and started, summarized tables andviews are created and populated in the Tivoli Data Warehouse. After IBM Tivoli Monitoring V6.2.3 isinstalled and the Siebel agent is installed and configured, configure historical collection. Also,configure the Warehouse Summarization and Pruning agent with or without shifts enabled. For moreinformation about how to enable historical collection and configure the Warehouse Summarizationand Pruning agent in IBM Tivoli Monitoring, see the following documentation:v http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3/

history_manage_intro.htmv http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3/

itm623_install632.htm?path=3_0_2_0_8#historical_data_storagev http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3/

history_configureintro_tep.htmHistorical collection and yearly, quarterly, monthly, weekly, daily, and hourly summarization must beenabled for the following attribute groups:v KUB_AVAILABILITYv KUB_COMP_DETAILv KUB_DLA_INPUTv KUB_STATISTICS_INFRACOREv KUB_STATISTICS_INFRADATABASEv KUB_STATISTICS_INFRAOBJMGRv KUB_STATISTICS_INFRARECOVERYv KUB_STATISTICS_PIMSIENGv KUB_STATISTICS_TESTSUBSYSv KUB_TASK_SUMMARY

To ensure that the required views are present, run the following query against the Tivoli DataWarehouse:v DB2: Select distinct "TABNAME" from SYSCAT.TABLES where "TABSCHEMA" = 'ITMUSER'v Oracle: Select distinct "TABLE_NAME" from USER_TABLES

Attention: You must first log on as ITMUSER.v MS SQL Server: Select TABLE_NAME "VIEWNAME" from INFORMATION_SCHEMA.TABLES

If set up correctly, the result set contains the following views:v TABLE_NAME_HVv TABLE_NAME_DVv TABLE_NAME_WVv TABLE_NAME_MVv TABLE_NAME_QV


http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_21/ttcr_install.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_21/ttcr_install.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3/history_manage_intro.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3/history_manage_intro.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3/itm623_install632.htm?path=3_0_2_0_8#historical_data_storage

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3/itm623_install632.htm?path=3_0_2_0_8#historical_data_storage

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3/history_configureintro_tep.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3/history_configureintro_tep.htm

v TABLE_NAME_YV

For example, KUB_TASK_SUMMARY_HV, KUB_TASK_SUMMARY_DV, KUB_TASK_SUMMARY_WV,KUB_TASK_SUMMARY_MV, KUB_TASK_SUMMARY_QV, and KUB_TASK_SUMMARY_YV. In otherwords, the result set should contain the HV, DV, WV, MV, QV, and YV tables of every base table. Ifthese views are not present, some metrics or reports might not work.

3. Prepare the Tivoli Data Warehouse to support Cognos dimensions.Preparing the Tivoli Data Warehouse for Tivoli Common Reporting includes creating the IBM_TRAMdimensions, which are required for running the Cognos reports and using the data models.See "Creating shared dimension tables and populating the time dimensions table" in the IBM TivoliMonitoring Administrator's Guide, V6.2.3 "Tivoli Common Reporting" chapter (http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3/tcr_reports_dimensionsshared.htm)

4. Configure the connection to a database to access your dataFollow the instructions at http://infdev.kraklab.pl.ibm.com/tcr21/topic/com.ibm.tivoli.tcr.doc_211/ttcr_config_db.html to connect Cognos to your data source.

5. Import the reports package into Tivoli Common Reporting.a. Copy IBM Tivoli Composite Application Manager Agent for Siebel CRM v7.1 Reports.zip to the

Cognos_Install_Directory/c8/deployment directory on the computer where the Tivoli CommonReporting Server is installed, where Cognos_Install_Directory is the installation directory of TivoliCommon Reporting.

b. Extract the package to the directory.c. Follow the instructions at http://infdev.kraklab.pl.ibm.com/tcr21/topic/

com.ibm.tivoli.tcr.doc_211/ttcr_import.html to import the package into Tivoli Common Reporting.

Important: All prerequisites described here must be met or the reports cannot run.

Running Cognos reports

If you are using a schema other than ITMUSER, you must complete the following steps for the datamodel and reports to run:1. Unzip the package named Siebel CRM Agent Data Model.zip in the model folder of the report

package to your local computer where Framework Manager is installed.2. Open the Siebel CRM Agent Data Model.cpf file with Framework Manager.3. Expand Data Source in Project Viewer, click TDW.4. In the Properties view, change the value of the Schema field from ITMUSER to the schema that you

use.5. Save the change, right-click the Siebel CRM Agent package, and then click Publish Packages in the

pop-up menu to publish the package to the Cognos server.

To run a report, follow the instructions at Running a report.

Working with Cognos reportsWhen all the prerequisites are met, you can use Tivoli Common Reporting to create, modify, and manageCognos reports.

To create reports in Tivoli Common Reporting tool, you can use one of the following report authoringtools:v Query Studio: A web-based product that is used mostly for ad hoc reporting. Users can create simple

queries and reports, and apply basic formatting to the reports.

Chapter 6. Tivoli Common Reporting for the Siebel agent 223

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3/tcr_reports_dimensionsshared.htm



http://infdev.kraklab.pl.ibm.com/tcr21/topic/com.ibm.tivoli.tcr.doc_211/ttcr_config_db.html

http://infdev.kraklab.pl.ibm.com/tcr21/topic/com.ibm.tivoli.tcr.doc_211/ttcr_config_db.html

http://infdev.kraklab.pl.ibm.com/tcr21/topic/com.ibm.tivoli.tcr.doc_211/ttcr_import.html

http://infdev.kraklab.pl.ibm.com/tcr21/topic/com.ibm.tivoli.tcr.doc_211/ttcr_import.html

http://infdev.kraklab.pl.ibm.com/tcr21/topic/com.ibm.tivoli.tcr.doc_211/ttcr_run_moswos.html

v Report Studio: A web-based tool that is used by technical users and professional report writers forcreating advanced reports. Users can retrieve data from multiple databases and create sophisticatedreports that have multiple pages and multiple queries.

Running the sample report for the monitoring agent

You can verify whether the reporting functionality is installed and configured correctly by running thesample report for the Siebel agent. The Siebel agent reporting package that you imported into TivoliCommon Reporting includes the following sample reports:v Siebel Application Server Availability Reportv Siebel Top N CPU & Memory Details by Server Type Reportv Siebel Bottom N CPU & Memory Details by Server Type Reportv Siebel CPU & Memory Details by Server Type Reportv Siebel Component Overview Reportv Siebel Peak Memory Usage Reportv Siebel Retry Summary Reportv Siebel SQL Details Reportv Siebel Top N Components By Running Tasks Across Enterprisev Siebel Top N Components By Running Tasks Across Serversv Siebel Top N Components By Running Tasks On One Serverv Siebel Task Details Reportv Siebel Test Details Reportv Siebel Transaction Overview Report

By using these sample reports, you can monitor the reporting activity and see what a typical Cognosreport includes. These sample reports are available in the Common Reporting panel in Tivoli CommonReporting. The following tables describe these reports.

Table 2. Siebel Application Server Availability Report

Report attribute Attribute description

Name Siebel Application Server Availability Report

Description This report shows the availability of the Siebel Application Server. The trend displayed isdetermined by the summarization type selected (hourly, daily, weekly, monthly, or yearly).

Purpose Show a general trend of the availability of the Siebel Application Server.


Table 2. Siebel Application Server Availability Report (continued)


ParametersReport Period

Date RangeSelect the report period from a predefined date range, such as Last Week,Current Month, Last 30 Days, and so on. You can also enter a start date, anend date, and the time for the reporting period.

Start DateSelect a start date from the calendar and the start time from the time widget.You must select both date and time.

End DateSelect an end date from the calendar and an end time from the time widget.You must select both date and time.

Summarization TypeSelect the summarization types, such as Hourly, Daily, Weekly, Monthly, Quarterly, orYearly.

Shift and Vacation PeriodShift Period

You can specify which shift periods to include (all, peak, or off-peak).

Vacation PeriodYou can specify which vacation periods to include (all, peak, or off-peak).

Output This report shows the average percentage of uptime over a time range in a line graph. Thepercentage is out of 100, not 1. Under the graph is a table with the Status Percentage by date.The Siebel Status line is 100 if the Application Server is up and 0 if it is down.

Usage The report indicates how stable the Siebel Application Server is over a period of time. It alsoshows trends of availability of the Siebel Application Server, which makes it easily determinableto see when the Siebel Application Server has gone down.


Table 2. Siebel Application Server Availability Report (continued)


Table 3. Siebel Top N CPU & Memory Details by Server Type Report


Name Siebel Top N CPU & Memory Details by Server Type Report

Description This report shows the top number n of components by CPU utilization (in percentage) andmemory usage.

Purpose You can use this report to decide which components are consuming the most CPU and memory.


Table 3. Siebel Top N CPU & Memory Details by Server Type Report (continued)






Top N You can enter a number to determine how many results are displayed.


You can specify which shift periods to include (all, peak, or off-peak).

Vacation PeriodYou can specify which vacation periods to include (all, peak, or off-peak).

Output This report shows two bar graphs, one for the components consuming the most CPU resourcesand the other for the components with the highest memory usage. Under the graphs are tableswith the utilization of each application component.

Usage This report helps determine which components use the most CPU and memory in overall.


Table 3. Siebel Top N CPU & Memory Details by Server Type Report (continued)


Table 4. Siebel Bottom N CPU & Memory Details by Server Type Report


Name Siebel Bottom N CPU & Memory Details by Server Type Report

Description This report shows the bottom number n of components by CPU utilization (in percentage) andmemory usage.

Purpose You can use this report to determine which components are consuming the least CPU andmemory.


Table 4. Siebel Bottom N CPU & Memory Details by Server Type Report (continued)






Bottom NYou can enter a number to determine how many results are displayed.


You can specify which vacation periods to include (all, peak, or off-peak).

Vacation PeriodYou can specify which shift periods to include (all, peak, or off-peak).

Output This report shows two bar graphs, one for the least utilized components by CPU and the otherfor the least utilized components by memory. Under the graphs are tables with the utilizationof each application component.

Usage The report helps determine which components use the least CPU and memory, in overall.


Table 4. Siebel Bottom N CPU & Memory Details by Server Type Report (continued)


Table 5. Siebel CPU & Memory Details by Server Type Report


Name Siebel CPU & Memory Details by Server Type Report

Description This report shows a general trend of CPU and memory usage for a summarization period.

Purpose This report shows general trends of CPU and memory usage per component.


Table 5. Siebel CPU & Memory Details by Server Type Report (continued)










Output This report shows a line graph for the specified summarization period.

Usage This report shows a general trend of CPU and memory usage per component.


Table 6. Siebel Component Overview Report


Name Siebel Component Overview Report

Description This report shows an overview of the components, including component crashes andcomponent restarts.

Purpose This report show component details, such as crashes and restarts.









Output This report shows a line graph with the component crashes and restarts over time. Under thegraph is a table with the metrics for component crashes and restarts.

Usage This report shows the overall effectiveness and problem areas of Siebel components.


Table 6. Siebel Component Overview Report (continued)


Table 7. Siebel Peak Memory Usage Report


Name Siebel Peak Memory Usage Report


Table 7. Siebel Peak Memory Usage Report (continued)


Description This report shows the extremes of Siebel memory usage. The extremes are maximums andminimums.

Purpose This report shows general trends of the extremes of Siebel memory usage.









Output This report shows a line graph with two lines, the maximum memory usage and the minimummemory usage.

Usage This report shows a general trend of the maximum and minimum memory usage of Siebelcomponents.


Table 7. Siebel Peak Memory Usage Report (continued)


Table 8. Siebel Retry Summary Report


Name Siebel Retry Summary Report


Table 8. Siebel Retry Summary Report (continued)


Description This report shows a summary of retries. A retry is created when the Siebel database tries to doan action. The different types of retries are database connection (DBConn) and databaserollbacks (DLRbk). After a retry has been attempted a certain number of times, it becomesexhausted.

Purpose This report show general trends of Siebel retries.









Output This report shows a line graph with the different types of retries over a specified summaryperiod. Under the graph is a table with the metrics for each retry.

Usage This report shows trends of database performance by the number of retries that Siebel causes.


Table 8. Siebel Retry Summary Report (continued)


Table 9. Siebel SQL Details Report


Name Siebel SQL Details Report


Table 9. Siebel SQL Details Report (continued)


Description This report shows Siebel SQL command details. This report will only show data if the correctfeatures have been enabled. SQL command metrics include parse time, fetch time, andexecution time.

Purpose This report shows the effectiveness of SQL commands that are being executed by Siebel.









Output The report shows a line graph with a count of each SQL metric over time. Time can besummarized as hourly, daily, weekly, monthly, and yearly.

Usage This report shows the effectiveness of the SQL commands that are executed by Siebel.


Table 9. Siebel SQL Details Report (continued)


Table 10. Siebel Top N Components By Running Tasks Across Enterprises


Name Siebel Top N Components By Running Tasks Across Enterprises


Table 10. Siebel Top N Components By Running Tasks Across Enterprises (continued)


Description This report shows the top number n of components per enterprise by number of running tasks.The report can be filtered by any enterprise or all enterprises. Clicking on an enterprise willdrill through to the Siebel Top N Components By Running Tasks Across Servers report.

Purpose This report shows which components are running the most tasks on the enterprise level.






Enterprise NameYou can select any or all of the enterprises.

Output The report shows a graph with the enterprise name encompassing the top n components onthat enterprise.

Usage This report shows which components are running the majority of the tasks on a givenenterprise.


Table 10. Siebel Top N Components By Running Tasks Across Enterprises (continued)



Table 11. Siebel Top N Components By Running Tasks Across Servers


Name Siebel Top N Components By Running Tasks Across Servers

Description This report shows the top number n of components per server by number of running tasks. Thereport can be filtered by any enterprise, all enterprises, a single server, or all servers. Clickingon a server drills down to the Siebel Top N Components By Running Tasks One On Serverreport.

Purpose This report shows which components are running the most tasks on the server level.







Server NameYou can select any or all of the servers.

Output The report shows a graph with the server name encompassing the top n components on thatserver.

Usage This report shows which components are running the majority of the tasks on a given server.


Table 11. Siebel Top N Components By Running Tasks Across Servers (continued)



Table 12. Siebel Top N Components By Running Tasks On One Server


Name Siebel Top N Components By Running Tasks On One Server

Description This report shows the top number n of components on a single server by number of runningtasks. The report can be filtered by an enterprise.

Purpose This report shows which components are running the most tasks on a single server.







Output The report shows a graph with the component name and running tasks on the y-axis.

Usage This report shows which components are running the majority of the tasks on a single server.


Table 12. Siebel Top N Components By Running Tasks On One Server (continued)


Table 13. Siebel Task Details Report


Name Siebel Task Details Report

Description This report shows a detailed summary of Siebel tasks, including running tasks, completedtasks, and tasks that have an error.

Purpose This report shows a general trend of each task status (running, complete, error).


Table 13. Siebel Task Details Report (continued)










Output This report shows a line graph of each task status (complete, running, and error) with a listunder it containing the metrics for tasks.

Usage This report shows the different counts for tasks.


Table 13. Siebel Task Details Report (continued)


Table 14. Siebel Test Details Report


Name Siebel Test Details Report

Description This report shows details of Siebel internal testing. The metrics included are tests attempted,tests passed, and tests failed.

Purpose This report shows how effective the Siebel internal tests are.


Table 14. Siebel Test Details Report (continued)






Summarization TypesSelect the summarization types, such as Hourly, Daily, Weekly, Monthly, Quarterly, orYearly.




Output This report shows a bar graph with three measures for each summarization; tests attempted,tests passed, and tests failed. Under the bar graph is a list with the test metrics.

Usage This report shows the effectiveness of Siebel internal testing.


Table 14. Siebel Test Details Report (continued)


Table 15. Siebel Transaction Overview Report


Name Siebel Transaction Overview Report


Table 15. Siebel Transaction Overview Report (continued)


Description This report shows Siebel transaction status summaries. A Siebel transaction is an attempt tosynchronize with a PIM Domain. The report contains metrics for transactions attempted,completed, and failed.

Purpose This report shows how Siebel is interacting with a PIM Domain.









Output This report shows a line graph with a count of the different statuses for a transaction. Underthe line graph is a table with the metrics for each status.

Usage This report shows how the interactions between Siebel and a PIM Domain are.


Table 15. Siebel Transaction Overview Report (continued)


Creating or customizing reportsPut your short description here; used for first paragraph and abstract.


Reports can be customized or created using the Cognos Report Studio, which is a web based reporteditor. To edit a report click on the Edit icon next to a report and the report studio will launch in aseparate window. After editing, you can save the report and it will be stored in the same location.

For detailed information about how to create a report, see Web-based report authoring.

Ad-hoc queryingThis topic discusses ad-hoc querying and how to start it.

To start ad-hoc querying, follow the instructions at Performing ad_hoc reporting. When you areprompted to select a package to work with, select the package IBM Tivoli Composite ApplicationManager Agent Siebel CRM v7.1 Reports. The data is loaded and you can drag and drop the data tocreate reports.

The Siebel CRM Data Model is a star schema with dimensions or identifiers separated from facts ormetrics. Metrics are measurable attributes (numeric) that can be aggregated by identifiers. Therelationship between the metric tables is defined using two common identifiers: resources and time.

IdentifiersIdentifiers are used to link the metrics data across agents. The two primary identifiers used forthe Siebel CRM Agent are IDs, such as Task ID and Process ID and Node. Another usefulidentifier, time, is given in the TRAM Shared Dimensions. Time includes a Standard Timestamp(12/28/2010 8:00 AM), date (12/28/2010), hour (12), and so on. This is useful when you want toshow a measurement over a length of time.

AttributesAttributes describe the identifiers. For example, information about a channel such as channeltype, query type, command level, and so on. When doing an ad-hoc query, you can either see thedata live as you drag, or you can switch the mode to show placeholders for the data and thenrun the report. To run the report without data or limited data, select Run Report from thenavigation on the left side and select Preview with Limited Data or Preview with No Data.

To start an ad-hoc query, drag an identifier from within a query subject followed by any of the metricswithin that query subject. The data is grouped by that specific identifier. If you drag Resource followedby Timestamp, it shows No Data available because there is no direct relationship between the twoidentifiers. If you want to see detailed data by timestamp, drag a time attribute from the Time querysubject within TRAM Shared Dimensions. For hourly data, use Hour. For daily data, you can use eitherStandard Timestamp or Date. The data aggregates appropriately by the identifier and timestamp. If youwant to see raw data by raw timestamps, use the Standard Timestamp from the Database View SharedTRAM Dimensions table and not the Consolidation View. You can combine several different metrics inone table. For example, you can drag Average Task Elapsed Time in Siebel Tasks (Hourly) and AveragePercent Processor Time in Siebel Task CPU Usage into one table.

To group the data, click the Type column and then click the Group icon.

To create a chart, click the Chart button. It creates a chart for each section with appropriate groups.

DebuggingThis topic describes the problems that you might encounter when using the reporting feature of theSiebel agent and the solutions to these problems.

Arithmetic Overflow Errors in Ad-Hoc Querying

Arithmetic overflow errors occur in ad-hoc querying as shown Figure 1 on page 253:


http://infdev.kraklab.pl.ibm.com/tcr21/index.jsp?topic=/com.ibm.tivoli.tcr.doc_211/ttcr_authoring.html

http://infdev.kraklab.pl.ibm.com/tcr21/index.jsp?topic=/com.ibm.tivoli.tcr.doc_211/ttcr_adhoc.html

If you drag certain columns during an ad-hoc query and it returns an arithmetic overflow error, switch toLimited Data or No Data preview and add Standard Timestamp to the query. Certain columns mightaverage or sum up to a number that is bigger than the size that the database supports. As a result, anSQL error of arithmetic overflow is returned. If you see the data by hourly timestamp or daily timestamp,or set a query to limit the data, the aggregated value is forced to be within the supported size.

‘No data available’ in Ad-Hoc Querying on querying two tables but data shows upif the two tables are queried individually

This happens if there is no relationship defined between the two tables. Make sure that all your ad-hocqueries have at least one identifier.

Error For Missing Table or Attribute

If you think that you have all the required tables and still get this error, it is possible that the Siebel agentis incompatible with the version used in the generic model. To check the query that runs, open the reportin Report Studio. Go to Tools > Show Generated SQL/MDX. The queries in the report will show up. Youcan view the native SQL.

Figure 1. Arithmetic Overflow Errors in Ad-Hoc Querying


Table Schema is not ITMUSER

In this case, use framework manager to update the schema to the one that you use by completing thefollowing steps:1. Unzip the package named Siebel CRM Agent Data Model.zip in the model folder of the report

package to your local computer where Framework Manager is installed.2. Open the Siebel CRM Agent Data Model.cpf file with Framework Manager.3. Expand Data Source in Project Viewer, click TDW.4. In the Properties view, change the value of the Schema field from ITMUSER to the schema that you

use, as shown in Figure 2:

Figure 2. Properties panel


5. Save the change, right-click the Siebel CRM Agent package, and then click Publish Packages in thepop-up menu to publish the package to the Cognos server, as shown in Figure 3:

Figure 3. Publish packages


Chapter 7. Discovery Library Adapter for the Siebel agent

The Tivoli Management Services Discovery Library Adapter (DLA) discovers resources and relationships,and creates a Discovery Library Book file for the agent.

About the DLA

The Book file follows the Discovery Library IdML schema and is used to populate the ConfigurationManagement Database (CMDB) and Tivoli Business Service Manager products. The Tivoli ManagementServices DLA discovers Siebel CRM resources. For all VMware systems that are active and online at theTivoli Enterprise Portal Server, information is included in the discovery book for those resources. TheTivoli Management Services DLA discovers active resources. It is run on demand and can be runperiodically to discover resources that were not active during previous discoveries.

The DLA discovers Siebel CRM components.

More information about DLAs

The following sources contain more information about using the DLA program with all monitoringagents:v The IBM Tivoli Monitoring Administrator's Guide contains information about using the Tivoli

Management Services Discovery Library Adapter.v For information about using a DLA with Tivoli Application Dependency Discovery Manager (TADDM),

see the TADDM Information Center (http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/topic/com.ibm.taddm.doc_7.2/welcome_page/welcome.html).

DLA data model class types represented in CDMThe source application data objects map to classes in the Common Data Model (CDM) for the Siebelagent.

The following information is provided for each class:

CDM class nameClass name for which the agent is providing information

RelationshipsCDM relationships (hierarchical) between currently identified model objects

CDM attributes, agent attributes, descriptions, and examplesCDM and agent attributes that are required to create an instance of a resource, descriptions of theattributes, and examples of the attributes

DLA data model classes for Siebel agentBindAddress class

The BindAddress class represents the port for the Siebel Gateway Name Server.

CDM class namenet.BindAddress

Relationships

bindsTo


http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/topic/com.ibm.taddm.doc_7.2/welcome_page/welcome.html

v Source: KUBDLAINP.GP-INODESTS.ORIGINNODE-GatewayBindAddressv Target: KUBDLAINP.GIA-INODESTS.ORIGINNODE-GatewayIpAddressv Example: bindsTo Source="1234-inst1:computer2:UB-GatewayBindAddress"

Target="211.161.9.101-inst1:computer2:UB-GatewayIpAddress"

bindsAsPrimaryv Source: KUBDLAINP.GP-INODESTS.ORIGINNODE-GatewayBindAddressv Target: KUBDLAINP.GIA-INODESTS.ORIGINNODE-GatewayIpAddressv Example: bindsAsPrimary Source="1234-inst1:computer2:UB-GatewayBindAddress"


accessedViav Source: KUBDLAINP.GIA-INODESTS.ORIGINNODE-GatewayIpAddressv Target: KUBDLAINP.GP-INODESTS.ORIGINNODE-GatewayBindAddressv Example: accessedVia Source="211.161.9.101-inst1:computer2:UB-GatewayIpAddress"

Target="1234-inst1:computer2:UB-GatewayBindAddress"

CDM attributes, agent attributes, descriptions, and examples

v CDM attribute: LabelAgent attribute: KUBDLAINP.GIA - KUBDLAINP.GPDescription: A user-specified string that is used when displaying a managedelement.Example: kb2kas.tivlab.raleigh.ibm.com

v CDM attribute: PortNumberAgent attribute: KUBDLAINP.GPDescription: The port number for the Siebel Gateway Name Server.Example: 1234

v CDM attribute: PathAgent attribute: noneDescription: The value is none.Example: none

IpAddress class

The IpAddress class represents the IP address of the Siebel Gateway Name Server.

CDM class namenet.IpAddress

Relationships

bindsTov Source: KUBDLAINP.GP-INODESTS.ORIGINNODE-GatewayBindAddressv Target: KUBDLAINP.GIA-INODESTS.ORIGINNODE-GatewayIpAddressv Example: bindsTo Source="1234-inst1:computer2:UB-GatewayBindAddress"


bindsAsPrimaryv Source: KUBDLAINP.GP-INODESTS.ORIGINNODE-GatewayBindAddressv Target: KUBDLAINP.GIA-INODESTS.ORIGINNODE-GatewayIpAddressv Example: bindsAsPrimary Source="1234-inst1:computer2:UB-GatewayBindAddress"



v CDM attribute: StringNotationAgent attribute: KUBDLAINP.GIA


Description: The IP address of the Siebel Gateway Name Server in string form.Example: 211.161.9.101

v CDM attribute: DotNotationAgent attribute: KUBDLAINP.GIADescription: Deprecated. An IPv4 address in string form.Example: 9.27.104.28

v CDM attribute: LabelAgent attribute: KUBDLAINP.GIADescription: A user-specified string that is used when displaying a managedelement.Example: kb2kas.tivlab.raleigh.ibm.com

SiebelComponent class

The SiebelComponent class represents an application component.

CDM class nameapp.packagedapp.siebel.SiebelComponent

Relationships

v providesSource: KUBDLAINP.EN-INODESTS.ORIGINNODE-SiebelEnterpriseTarget: KUBCOMPDET.COMP_NAME-KUBDLAINP.EN-SiebelComponentExample: contains Source="Enterprise1-inst1:computer2:UB-SiebelEnterprise"Target="SalesObjectManger-inst1:computer2:UB-SiebelComponent"

v monitorsSource: INODESTS.ORIGINNODE-TMSAgentTarget: KUBCOMPDET.COMP_NAME-KUBDLAINP.EN-SiebelComponentExample: monitors Source="2345-inst1:computer2:UB-TMSAgent"Target="SalesObjectManager-Enterprise1-SiebelComponent"


v CDM attribute: LabelAgent attribute: KUBCOMPDET.COMP_NAMEDescription: The label of the component.Example: SalesObjectManger

v CDM attribute: NameAgent attribute: KUBCOMPDET.COMP_NAMEDescription: The name of the component.Example: SalesObjectManger

SiebelEnterprise class

The SiebelEnterprise class represents the Siebel Enterprise.

CDM class nameapp.packagedapp.siebel.SiebelEnterprise

Relationships

v containsSource: KUBDLAINP.EN-INODESTS.ORIGINNODE-SiebelEnterpriseTarget: KUBDLAINP.GIA-INODESTS.ORIGINNODE-SiebelGatewayExample: contains Source="Enterprise1-inst1:computer2:UB-SiebelEnterprise"Target="211.161.9.101-inst1:computer2:UB-SiebelGateway"

v containsSource: KUBDLAINP.EN-INODESTS.ORIGINNODE-SiebelEnterpriseTarget: KUBSIEBSRV.SN-INODESTS.ORIGINNODE-SiebelServer

Chapter 7. Discovery Library Adapter for the Siebel agent 259

Example: contains Source="Enterprise1-inst1:computer2:UB-SiebelEnterprise"Target="Server1-inst1:computer2:UB-SiebelServer"

v providesSource: KUBDLAINP.EN-INODESTS.ORIGINNODE-SiebelEnterpriseTarget: KUBCOMPDET.COMP_NAME-KUBDLAINP.EN-SiebelComponentExample: contains Source="Enterprise1-inst1:computer2:UB-SiebelEnterprise"Target="SalesObjectManger-inst1:computer2:UB-SiebelComponent"


v CDM attribute: LabelAgent attribute: KUBDLAINP.ENDescription: The label of the Siebel Enterprise.Example: Enterprise1

v CDM attribute: NameAgent attribute: KUBDLAINP.ENDescription: The name of the Siebel Enterprise.Example: Enterprise1

SiebelGateway class

The SiebelGateway class represents the Siebel Gateway Name Server on which the SiebelEnterprise relies for routing to Siebel Servers.

CDM class nameapp.packagedapp.siebel.SiebelGateway

Relationships

v usesSource: KUBSIEBSRV.SN-INODESTS.ORIGINNODE-SiebelServerTarget: KUBDLAINP.GIA-INODESTS.ORIGINNODE-SiebelGatewayExample: contains Source="Server1-inst1:computer2:UB-SiebelServer"Target="211.161.9.101-inst1:computer2:UB-SiebelGateway"

v accessedViaSource: KUBDLAINP.GIA-INODESTS.ORIGINNODE-GatewayIpAddressTarget: KUBDLAINP.GP-INODESTS.ORIGINNODE-GatewayBindAddressExample: accessedVia Source="211.161.9.101-inst1:computer2:UB-GatewayIpAddress" Target="1234-inst1:computer2:UB-GatewayBindAddress"

v containsSource: KUBDLAINP.EN-INODESTS.ORIGINNODE-SiebelEnterpriseTarget: KUBDLAINP.GIA-INODESTS.ORIGINNODE-SiebelGatewayExample: contains Source="Enterprise1-inst1:computer2:UB-SiebelEnterprise"Target="211.161.9.101-inst1:computer2:UB-SiebelGateway"

v monitorsSource: INODESTS.ORIGINNODE-TMSAgentTarget: KUBDLAINP.GIA-INODESTS.ORIGINNODE-SiebelGatewayExample: monitors Source="inst1:computer2:UB-TMSAgent"Target="211.161.9.101-inst1:computer2:UB-SiebelGateway"


v CDM attribute: LabelAgent attribute: KUBDLAINP.ENDescription: The label of the Siebel Gateway Name Server.Example: Gateway Name Server

v CDM attribute: KeyNameAgent attribute: KUBDLAINP.ENDescription: The name of the Siebel Gateway Name Server.Example: AppServer


SiebelServer class

The SiebelServer class represents a Siebel Server.

CDM class nameapp.packagedapp.siebel.SiebelServer

Relationships

v containsSource: KUBDLAINP.EN-INODESTS.ORIGINNODE-SiebelEnterpriseTarget: KUBSIEBSRV.SN-INODESTS.ORIGINNODE-SiebelServerExample: contains Source="Enterprise1-inst1:computer2:UB-SiebelEnterprise"Target="Server1-inst1:computer2:UB-SiebelServer"

v usesSource: KUBSIEBSRV.SN-INODESTS.ORIGINNODE-SiebelServerTarget: KUBDLAINP.GIA-INODESTS.ORIGINNODE-SiebelGatewayExample: contains Source="Server1-inst1:computer2:UB-SiebelServer"Target="211.161.9.101-inst1:computer2:UB-SiebelGateway"

v monitorsSource: INODESTS.ORIGINNODE-TMSAgentTarget: KUBSIEBSRV.SN-INODESTS.ORIGINNODE-SiebelServerExample: monitors Source="inst1:computer2:UB-TMSAgent" Target="Server1-inst1:computer2:UB-SiebelServer"


v CDM attribute: LabelAgent attribute: KUBSIEBSRV.SNDescription: The label of the Siebel Server.Example: Server1

v CDM attribute: NameAgent attribute: KUBSIEBSRV.SNDescription: The name of the Siebel Server.Example: Server1

TMSAgent class

The TMSAgent class represents the Siebel agent.

CDM class nameapp.TMSAgent

Relationships

v monitorsSource: INODESTS.ORIGINNODE-TMSAgentTarget: KUBDLAINP.GIA-INODESTS.ORIGINNODE-SiebelGatewayExample: monitors source="inst1:computer2:UB-TMSAgent"target="211.161.9.101-inst1:computer2:UB-SiebelGateway"

v monitorsSource: INODESTS.ORIGINNODE-TMSAgentTarget: KUBSIEBSRV.SN-INODESTS.ORIGINNODE-SiebelServerExample: monitors source="inst1:computer2:UB-TMSAgent" target="Server1-inst1:computer2:UB-SiebelServer"


v CDM attribute: ManagedSystemNameAgent attribute: INODESTS.NODEDescription: The node name for the Siebel agentExample: inst1:computer2:UB

Chapter 7. Discovery Library Adapter for the Siebel agent 261

v CDM attribute: ManagedObjectNameAgent attribute: INODESTS.NODEDescription: The name of the component that provides data for the management ofthe Siebel agent instanceExample: inst1:computer2:UB

v CDM attribute: SoftwareVersionAgent attribute: INODESTS.VERSIONDescription: The version of the Siebel agent.Example: 07.01.00

v CDM attribute: ProductCodeAgent attribute: INODESTS.PRODUCTDescription: Product code of the Siebel agentExample: UB

v CDM attribute: AffinityAgent attribute: INODESTS.AFFINITIESDescription: Affinity of the Siebel agentExample: %IBM.SiebelAgent

v CDM attribute: LabelAgent attribute: INODESTS.ORIGINNODE-Siebel CRM AgentDescription: Label of the Siebel agentExample: inst1:computer2:UB-Siebel CRM Agent


Chapter 8. Integration with Tivoli Business Service Manager

The Siebel agent provides data to create, update the status of, and view IBM Tivoli Business ServiceManager services.

The Tivoli Management Services Discovery Library Adapter (DLA) and Discovery Library Toolkitprovides data for the Tivoli Business Service Manager service models. The Tivoli Integration Facility (EIF)probe updates the status of these services, and you use the Tivoli Enterprise Portal to view the data forthe services. To implement the integration of the agent with Tivoli Business Service Manager, perform theintegration tasks.

Components for integrating with Tivoli Business Service ManagerThe data for integrating with Tivoli Business Service Manager is supplied through the followingcomponents: Tivoli Management Services Discovery Library Adapter (DLA) and Discovery LibraryToolkit, Tivoli Integration Facility (EIF) probe, and Tivoli Enterprise Portal.

Tivoli Management Services Discovery Library Adapter (DLA) and DiscoveryLibrary Toolkit

By using data from the Tivoli Management Services Discovery Library Adapter, you can build TivoliBusiness Service Manager service models that include resources monitored by the Siebel agent.

The DLA files can be imported directly into Tivoli Business Service Manager using the Discovery LibraryToolkit or they can be loaded into IBM Tivoli Application Dependency Discovery Manager (TADDM) andthen fed into Tivoli Business Service Manager using the Discovery Library Toolkit.

See the following sources for more information about the DLA and Discovery Library Toolkit:v Resources and relationships that are discovered by the Siebel agent and included in Tivoli Management

Services DLA files: Chapter 7, “Discovery Library Adapter for the Siebel agent,” on page 257v Using the Tivoli Management Services DLA: IBM Tivoli Monitoring Administrator's Guide

v Using the Discovery Library Toolkit: Tivoli Business Service Manager Customization Guide

Tivoli Integration Facility (EIF) probe

Situation events detected by the Siebel agent can update the status of services in Tivoli Business ServiceManager.

The situation events are forwarded from IBM Tivoli Monitoring to the Netcool/OMNIbus Probe for theTivoli Event Integration Facility. The EIF probe then forwards the events to the Netcool/OMNIbusObjectServer. Tivoli Business Service Manager monitors the Netcool/OMNIbus ObjectServer for newevents and updates the status of affected services.

See the following sources for more information about event integration:v Installation (using an existing EIF probe and Netcool/OMNIbus ObjectServer installation or using

Tivoli Business Service Manager to install these components): Netcool/OMNIbus Information Center orthe Tivoli Business Service Manager Installation Guide.

v Setting up event integration between IBM Tivoli Monitoring, the EIF probe, and the Netcool/OMNIbusObjectServer: IBM Tivoli Monitoring Installation and Setup Guide.


Tivoli Enterprise Portal

You can use the integration of the Tivoli Enterprise Portal with Tivoli Business Service Manager to viewthe services in the Tivoli Business Service Manager console.

For more detailed examination and analysis, you can easily link from the Tivoli Business Service Managerconsole to the Tivoli Enterprise Portal to view the data within the Siebel agent.

Tasks to integrate the agent with Tivoli Business Service ManagerTo integrate the Siebel agent with Tivoli Business Service Manager, you must install and configure therequired components. Then, you can view the data in the Tivoli Integrated Portal

To integrate the Siebel agent with Tivoli Business Service Manager and view the data, complete thefollowing tasks:v Install the Discovery Library Toolkit on the Tivoli Business Service Manager server.v Configure the Tivoli Event Integration Facility (EIF) probe to enrich Siebel agent events.v Create a service in the Tivoli Business Service Manager console that you want to monitor.v Create a data source mapping for each data source that you want to access within the Tivoli Business

Service Manager.v Configure an additional IBM Tivoli Monitoring web service for each Tivoli Enterprise Portal Server.v View data in the Tivoli Enterprise Portal for the services that you have created to monitor through

Tivoli Business Service Manager.

Installing the Discovery Library Toolkit on the Tivoli Business ServiceManagerYou must install the Discovery Library Toolkit on the Tivoli Business Service Manager server.

The Discovery Library Toolkit imports data from the DLA files and TADDM, which includes informationabout the hardware and the applications that are discovered by the source.

See “Installing the Discovery Library Toolkit” in the Tivoli Business Service Manager Installation Guide.

Configuring the Tivoli Event Integration Facility (EIF) probe to enricheventsThe Netcool/OMNIbus Probe for Tivoli Event Integration Facility (EIF) forwards the Siebel agent eventsthat are received from IBM Tivoli Monitoring to the Netcool/OMNIbus ObjectServer. Tivoli BusinessService Manager monitors the Netcool/OMNIbus ObjectServer for new events, and updates the status ofaffected services.

Install and configure the Netcool/OMNIbus ObjectServer and EIF probe and set up event integrationbetween IBM Tivoli Monitoring and Netcool/OMNIbus. The probe rules files provided with IBM TivoliMonitoring enrich Siebel agent events to identify the affected service.

Creating a service in Tivoli Business Service ManagerYou must create a service in the Tivoli Business Service Manager console for each service that you wantto monitor.

To create the services that you want to monitor in the Tivoli Business Service Manager console, see“Configuring services” in the IBM Tivoli Business Service Manager Service Configuration Guide.


Creating a data source mapping for each data sourceYou can create a data source mapping for each data source that you want to access within Tivoli BusinessService Manager.

Also, you can create the data fetchers and use the data to create incoming status rules that are populatedin your service templates.

For more information, see “Data sources” and “Data fetchers” in the IBM Tivoli Business Service ManagerService Configuration Guide.

Configuring additional IBM Tivoli Monitoring web servicesYou can configure additional IBM Tivoli Monitoring web services for each Tivoli Enterprise Portal Server.

To configure an additional IBM Tivoli Monitoring web service for each Tivoli Enterprise Portal server, see“Configure TBSM charts” in the IBM Tivoli Business Service Manager Scenarios Guide.

Viewing data in the Tivoli Enterprise PortalFrom Tivoli Business Service Manager, you can open the Tivoli Enterprise Portal and view the Siebelagent.

You can also launch Tivoli Business Service Manager from the Tivoli Enterprise Portal.

For more information about launching applications, see “Launching to and from applications” in theTivoli Business Service Manager Customization Guide.

Chapter 8. Integration with Tivoli Business Service Manager 265

Appendix. ITCAM for Applications documentation library

Various publications are relevant to the use of ITCAM for Applications.

For information about how to access and use the publications, see Using the publications(http://pic.dhe.ibm.com/infocenter/tivihelp/v61r1/topic/com.ibm.itm.doc_6.3/common/using_publications.htm).

To find publications from the previous version of a product, click Previous versions under the name ofthe product in the Contents pane.

Documentation for this product is in the ITCAM for Applications Information Center(http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcama.doc_7.2.1/welcome_apps721.html):v Quick Start Guidev Offering Guidev Download instructionsv Links to Prerequisitesv Installation and Configuration Guide for each agentv Link to Reference information for each agentv Link to Troubleshooting Guide for each agent

Prerequisite publicationsTo use the information about the agents effectively, you must have some prerequisite knowledge.

See the following information at the IBM Tivoli Monitoring Information Center (http://pic.dhe.ibm.com/infocenter/tivihelp/v61r1/index.jsp) to gain prerequisite knowledge:v IBM Tivoli Monitoring Administrator's Guide

v IBM Tivoli Monitoring Installation and Setup Guide

v IBM Tivoli Monitoring High Availability Guide for Distributed Systems

v IBM Tivoli Monitoring: Installation and Configuration Guides for the following agents: OperatingSystem agents and Warehouse agents

v IBM Tivoli Monitoring: User's Guides for the following agents: Agentless OS monitors, Log file agent,System p agents, Systems Director base agent

v IBM Tivoli Monitoring Agent Builder User's Guide

v IBM Tivoli Monitoring Command Reference

v IBM Tivoli Monitoring: Messages

v IBM Tivoli Monitoring Troubleshooting Guide

v IBM Tivoli Monitoring: References for the following agents: Operating System agents and Warehouseagents

v IBM Tivoli Monitoring: Troubleshooting Guides for the following agents: Operating System agents andWarehouse agents

v Tivoli Enterprise Portal User's Guide

Related publicationsThe publications in related information centers provide useful information.


http://pic.dhe.ibm.com/infocenter/tivihelp/v61r1/topic/com.ibm.itm.doc_6.3/common/using_publications.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcama.doc_7.2.1/welcome_apps721.html

http://pic.dhe.ibm.com/infocenter/tivihelp/v61r1/index.jsp

See the following information centers, which you can find by accessing Tivoli Documentation Central(https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Documentation%20Central):v Tivoli Monitoringv Tivoli Application Dependency Discovery Managerv Tivoli Business Service Managerv Tivoli Common Reportingv Tivoli Enterprise Consolev Tivoli Netcool/OMNIbus

Other sources of documentationYou can obtain additional technical documentation about monitoring products from other sources.

See the following sources of technical documentation about monitoring products:v Service Management Connect (SMC)

– For introductory information about SMC, see IBM Service Management Connect(http://www.ibm.com/developerworks/servicemanagement/).

– For information about Tivoli products, see the Application Performance Management community onSMC (http://www.ibm.com/developerworks/servicemanagement/apm/index.html).

– Connect, learn, and share with Service Management professionals. Get access to developers andproduct support technical experts who provide their perspectives and expertise. You can use SMCfor these purposes:- Become involved with transparent development, an ongoing, open engagement between external

users and developers of Tivoli products where you can access early designs, sprint demos,product roadmaps, and pre-release code.

- Connect one-on-one with the experts to collaborate and network about Tivoli and IntegratedService Management.

- Benefit from the expertise and experience of others using blogs.- Collaborate with the broader user community using wikis and forums.

v IBM Integrated Service Management Library (http://www.ibm.com/software/brandcatalog/ismlibrary/) is an online catalog that contains integration documentation as well as otherdownloadable product extensions.

v IBM Redbook publications (http://www.redbooks.ibm.com/) include Redbooks® publications,Redpapers, and Redbooks technotes that provide information about products from platform andsolution perspectives.

v Technotes (http://www.ibm.com/support/entry/portal/software), which are found through the IBMSoftware Support website, provide the latest information about known product limitations andworkarounds.


https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Documentation%20Central

http://www.ibm.com/developerworks/servicemanagement/

http://www.ibm.com/developerworks/servicemanagement/apm/index.html

http://www.ibm.com/developerworks/servicemanagement/apm/index.html

http://www.ibm.com/software/brandcatalog/ismlibrary/

http://www.redbooks.ibm.com/

http://www.ibm.com/support/entry/portal/software

Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer theproducts, services, or features discussed in this document in other countries. Consult your local IBMrepresentative for information on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the user'sresponsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not give you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual PropertyDepartment in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore,this statement might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not inany manner serve as an endorsement of those Web sites. The materials at those Web sites are not part ofthe materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some casespayment of a fee.

The licensed program described in this document and all licensed material available for it are providedby IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement orany equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, theresults obtained in other operating environments may vary significantly. Some measurements may havebeen made on development-level systems and there is no guarantee that these measurements will be thesame on generally available systems. Furthermore, some measurement may have been estimated throughextrapolation. Actual results may vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal withoutnotice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change withoutnotice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before theproducts described become available.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to the names and addresses used by anactual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. You may copy, modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing application programs conformingto IBM‘s application programming interfaces.


Each copy or any portion of these sample programs or any derivative work, must include a copyrightnotice as follows:

© IBM 2009. Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp.2009. All rights reserved.

If you are viewing this information in softcopy form, the photographs and color illustrations might not bedisplayed.

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the web atCopyright and trademark information (www.ibm.com/legal/copytrade.shtml).

Intel, Intel logo, and Intel Xeon, are trademarks or registered trademarks of Intel Corporation or itssubsidiaries in the United States and other countries.

Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Windows is a trademark of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.

Privacy policy considerationsIBM Software products, including software as a service solutions, ("Software Offerings") may use cookiesor other technologies to collect product usage information, to help improve the end user experience, totailor interactions with the end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offerings can help enable you tocollect personally identifiable information. If this Software Offering uses cookies to collect personallyidentifiable information, specific information about this offering’s use of cookies is set forth below.

Depending upon the configurations deployed, this Software Offering may use session cookies that collecteach user’s user name for purposes of session management, authentication, and single sign-onconfiguration. These cookies cannot be disabled.

Notices 271

http://www.ibm.com/legal/copytrade.shtml

If the configurations deployed for this Software Offering provide you as customer the ability to collectpersonally identifiable information from end users via cookies and other technologies, you should seekyour own legal advice about any laws applicable to such data collection, including any requirements fornotice and consent.

For more information about the use of various technologies, including cookies, for these purposes, SeeIBM’s Privacy Policy at http://www.ibm.com/privacy and IBM’s Online Privacy Statement athttp://www.ibm.com/privacy/details the section entitled "Cookies, Web Beacons and OtherTechnologies" and the "IBM Software Products and Software-as-a-Service Privacy Statement" athttp://www.ibm.com/software/info/product-privacy.


http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

Index

Aadditional information

attributes 9situations 149Take Action commands 173Workspaces 1

Agent Health workspace 3Ancient attribute 55Application Component attribute 13, 26, 131Application Performance Management community on

SMC 268Application Server Connection Status attribute 41, 65attribute group 12attribute groups

Availability 13Comp Counts 18Comp CPU Util Rollup 19Comp Detail 20Comp Logs 22Comp Logs Pre77 23Comp Name 25Component Resource 25Component Statistics 31Database File System 33Database Files 35DLA Input 38Enterprise 42File System 43Files 45Gate Log 49Gate Log Pre77 50list of all 9Managed URLs 51Marketing Statistics 54overview 9Performance Object Status 57Server Log 61Server Log Pre77 63Siebel Server 64Siebel Statistics 66Statistic Details 68Statistics AsgnSubsys 91Statistics CommInboundProcessor 92Statistics EAISubsys 93Statistics FlightDataRecorder 95Statistics InfraCore 96Statistics InfraDatabase 101Statistics InfraMultiThread 104Statistics InfraObjMgr 106Statistics InfraRecovery 116Statistics PIMSIENG 118Statistics PSPEngine 120Statistics SearchDataProcessor 121Statistics ServerQueryTime 123Statistics TestSubsys 123Statistics XMLCnv 125Task CPU Util Rollup 126Task Detail 128Task Resource 131Task Summary 138User Session 141

attribute groups (continued)User Session Summary 143

attributes 12additional information 9Ancient 55Application Component 13, 26, 131Application Server Connection Status 41, 65Availability 13Average 20, 127Average Connect Time 68, 106Average OOB Component Time 68, 105Average OOB Queue Size 69, 105Average Reply Size 69, 106Average Request Size 69, 107Average Requests Per Session 69, 107Average Response Time 70, 107Average Think Time 70, 108Avg SQL Execute Time 70, 101Avg SQL Fetch Time 70, 101Avg SQL Parse Time 71, 102Background Count 140Batch Count 140Command Line 17, 30, 135Comp Alias 21, 129, 136Comp Counts 18Comp CPU Util Rollup 19Comp Detail 20Comp Group Alias 129, 136Comp Grp Alias 21Comp Log Name 25, 31Comp Logs 22Comp Logs Pre77 24Comp Name 21, 25Comp PID 25, 31Completed Count 139, 144Completed Transactions from PIM 71, 119Completed Transactions from Siebel 71, 119Component Name 18, 32Component Resource 25Component Statistics 31CPU Time 71, 97Current 54Current Size in MB 35, 46Current Value 32, 67Data Cursor Cache CPU 72, 108Data Cursor Cache Hits 72, 108Data Cursor Cache Memory 72, 108Data Cursor Cache Misses 72, 109Data Cursor Cache Objects 73, 109Database File System 33Database Files 35Description 32, 67Directory Name 35, 46DLA Input 38Duration 56EAI Receiver Total Messages Processed 73, 94Elapsed Time 73, 97, 143End Time 40, 65Enterprise 42Enterprise Name 22, 38, 42, 56, 62, 66, 100, 104, 116, 120,

143


attributes (continued)Enterprise Name0 42Error Code 58Error Count 139, 144Event Type Alias 23, 24, 49, 51, 61, 63Events Processed 74, 92Events Processed Rate 74, 93Failed Transactions from PIM 75, 119Failed Transactions from Siebel 75, 120FDR Avg time between aging 74, 96FDR Buffer Life in seconds 74, 96FDR Buffer Wraps 75, 96File Name 35File System 43Filename 46Files 45Free Space in MB 33, 44Full Name 14, 27, 132Functionality Test Message 18, 30, 136Functionality Test Status 17, 30, 135Gate Log 49Gate Log Pre77 50Gateway Bind Address 39, 42Gateway Hostname 39, 43Gateway IP Address 39, 43Gateway Name 22, 23, 35, 41, 45, 49, 50, 56, 62, 66, 100,

104, 116, 120, 143Gateway Port 39, 43Global Data Cursor Cache CPU 75, 110Global Data Cursor Cache Hits 76, 110Global Data Cursor Cache Memory 76, 110Global Data Cursor Cache Misses 76, 111Global Data Cursor Cache Objects 76, 111Host name 40, 64Hours Until Full 34, 37, 45, 48Install Dir 40, 64Interactive Count 140Invalid 55Log Message 23, 24, 50, 51, 62, 64Logs Timestamp 23, 24, 50, 51, 62, 63Managed URLs 52Marketing Statistics 54Maximum 19, 127Maximum OOB Component Time 77, 105Maximum Peak Memory Usage 77, 98Minimum 19, 127Minimum Peak Memory Usage 77, 98Mount Point 34, 45Name 13, 26, 33, 44, 48, 131Node 13, 18, 19, 20, 22, 24, 25, 26, 31, 33, 35, 38, 42, 43, 45,

49, 50, 52, 54, 57, 61, 63, 64, 66, 68, 91, 92, 93, 95, 97, 101,104, 106, 116, 118, 120, 122, 123, 124, 125, 127, 128, 131,138, 141, 143

Normal Count 141Num of DBConn Retries 77, 117Num of DLRbk Retries 78, 117Num of Exhausted Retries 78, 117Number of Component Crashes 78, 98Number of Component Restarts 79, 98Number of Errors 79, 99Number of object rows assigned 80, 92Number of Sleeps 80, 99Number of SQL Executes 79, 102Number of SQL Fetches 79, 103Number of SQL Parses 80, 103Object Manager Errors 80, 110Object Name 57

attributes (continued)Object Status 58Object Type 57Orphaned 55Other Count 140, 144overview 9Page Faults per Sec 15, 28, 133Page Objects 53Page Size 52Page Title 53Parent Task Id 129, 137Percent Change Average 37, 47Percent Change Last Hour 36, 47Percent Change Total 37, 48Percent Free 34, 44Percent of File System Used 36, 46Percent Privileged Time 16, 29, 134Percent Processor Time 16, 29, 134Percent Used 33, 44Percent User Mode Time 16, 29, 134Performance Object Status 57PID 16, 28, 134PID Group TID 130, 137PSP Cache Hit Total 81, 121PSP Cache Miss Total 81, 121Query Execution Time 123Query Name 57Reply Messages 81, 111Request Messages 81, 112Response Code 53Response Time 52Run Mode 21, 142Run State 21, 129, 137Running Count 139, 144Running Interactive Task Count 18Running Task Count 41, 65Running Tasks 21SARMID 23, 50, 62SearchEvents Processed 85, 122SearchEvents Processed Rate 85, 122Server Log 61Server Log Pre77 63Server Manager Query Name 123Server Name 21, 40, 56, 62, 64, 100, 104, 116, 120, 128, 136,

141Server State 40, 65Server Status 41, 65Server Type 39, 43, 53Severity 23, 24, 50, 51, 62, 63Siebel Adapter Total Query Calls 86, 94Siebel Adapter Total Query Size 86, 94Siebel Adapter Total Sync Size 86, 94Siebel Adapter Total Sync/Upsert Calls 86, 95Siebel Server 64Siebel Server Name 32, 67Siebel Statistics 66Size Change Average 37, 47Size Change Last Hour 36, 46Size Change Total 37, 48Sleep Time 87, 99Source Name 22, 24, 49, 51, 61, 63SQL Cursor Cache Hits 82, 113SQL Cursor Cache Misses 82, 113SQL Cursor Total Cpu 82, 113SQL Cursor Total Mem 82, 113SQL Cursor Total Objects 83, 114SQL Execute Time 83, 103


attributes (continued)SQL Fetch Time 83, 103SQL Object Cache CPU 84, 114SQL Object Cache Hits 84, 114SQL Object Cache Memory 84, 115SQL Object Cache Misses 84, 115SQL Object Cache Objects 85, 115SQL Parse Time 85, 102Start Time 40, 65Statistic 32, 67Statistic Alias 32, 67Statistic Details 68Statistics AsgnSubsys 91Statistics CommInboundProcessor 92Statistics EAISubsys 93Statistics FlightDataRecorder 95Statistics InfraCore 97Statistics InfraDatabase 101Statistics InfraMultiThread 104Statistics InfraObjMgr 106Statistics InfraRecovery 116Statistics PIMSIENG 118Statistics PSPEngine 120Statistics SearchDataProcessor 122Statistics ServerQueryTime 123Statistics TestSubsys 123Statistics XMLCnv 125Status 14, 26, 53, 131Subsystem 32, 67Task CPU Util Rollup 126Task Detail 128Task Elapsed Time 130, 138Task End Time 130, 138, 143Task ID 129, 136, 142Task Label 129, 137Task PID 129, 136, 142Task Ping Time 130, 137Task Resource 131Task Runstate 142Task Start Time 130, 138, 142Task Status 130, 138Task Summary 138Task Type 142Tasks Exceeding Configured Capacity 87, 99Tests Attempted 87, 124Tests Failed 87, 124Tests Successful 88, 124Thread Count 15, 28, 133Timestamp 13, 18, 19, 21, 22, 24, 25, 26, 31, 33, 35, 38, 42,

43, 46, 49, 51, 52, 54, 57, 61, 63, 64, 66, 68, 91, 92, 93, 95,97, 101, 105, 106, 117, 118, 121, 122, 123, 124, 125, 127, 128,131, 139, 141, 144

Total 20, 55, 128Total Database Response Time 88, 109Total Object Size 53Total Reply Size 88, 111Total Request Size 89, 112Total Response Time 89, 112Total Size in MB 34, 45Total Tasks 89, 100Total Think Time 89, 115Total XML Converter Size of Input Buffer 90, 125Total XML Converter Size of Output Buffer 90, 125Total XML Generator Calls 90, 126Total XML Parser Calls 90, 126Transactions form Siebel in Progress 91, 118Transactions from PIM in Progress 91, 118

attributes (continued)Type 14, 23, 24, 27, 38, 49, 51, 61, 63, 132Updated End Time 41, 66Updated Start Time 41, 65URL 52URL Alias 54User Data 54User ID 142User Session 141User Session Summary 143Virtual Size 15, 27, 133Worker Count 141Working Set Size 15, 28, 133

Availabilitysituations 151workspaces

descriptions 3Availability attribute group 13Availability workspace 3Average attribute 20, 127Average Connect Time attribute 68, 106Average OOB Component Time attribute 68, 105Average OOB Queue Size attribute 69, 105Average Reply Size attribute 69, 106Average Request Size attribute 69, 107Average Requests Per Session attribute 69, 107Average Response Time attribute 70, 107Average Think Time attribute 70, 108Avg SQL Execute Time attribute 70, 101Avg SQL Fetch Time attribute 70, 101Avg SQL Parse Time attribute 71, 102

BBackground Count attribute 140Batch Count attribute 140

Ccalculate historical data disk space 145capacity planning for historical data 145Command Line attribute 17, 30, 135commands

Take Action 173Comp Alias attribute 21, 129, 136Comp Counts attribute group 18Comp CPU Util Rollup attribute group 19Comp Detail attribute group 20Comp Group Alias attribute 129, 136Comp Grp Alias attribute 21Comp Log Name attribute 25, 31Comp Logs attribute group 22Comp Logs Pre77 attribute group 23Comp Name attribute 21Comp Name attribute group 25Comp PID attribute 25, 31Completed Count attribute 139, 144Completed Transactions from PIM attribute 71, 119Completed Transactions from Siebel attribute 71, 119Component Counts workspace 3Component Name attribute 18, 32Component Resource attribute group 25Component Statistics attribute group 31Components

situations 155

Index 275

Components (continued)workspaces

descriptions 3Components (Superseded) workspace 4Components workspace 3cookies 271CPU Time attribute 71, 97Current attribute 54Current Size in MB attribute 35, 46Current Value attribute 32, 67

DData Cursor Cache CPU attribute 72, 108Data Cursor Cache Hits attribute 72, 108Data Cursor Cache Memory attribute 72, 108Data Cursor Cache Misses attribute 72, 109Data Cursor Cache Objects attribute 73, 109Database File System attribute group 33Database Files attribute group 35Delete Archived Logs action 174Description attribute 32, 67descriptions 151Directory Name attribute 35, 46Discovery Library Adapter 263

See DLADiscovery Library Toolkit 263

installing 264disk capacity planning for historical data 145DLA 257, 263

data model 257classes 257

SiebelComponent classCDM class name 259provides 259realizes 259Relationships 259

SiebelEnterprise classCDM class name 259provides 259realizes 259, 260Relationships 259

SiebelGateway classCDM class name 260realizes 260Relationships 260uses 260

SiebelServer classCDM class name 261realizes 261Relationships 261uses 261

TMSAgent classCDM class name 261monitors 261Relationships 261

DLA Input attribute group 38documentation

See publicationsDuration attribute 56

EEAI Receiver Total Messages Processed attribute 73, 94Elapsed Time attribute 73, 97, 143End Time attribute 40, 65

Enterprise attribute group 42Enterprise Name attribute 22, 38, 42, 56, 62, 66, 100, 104, 116,

120, 143Enterprise Name0 attribute 42Error Code attribute 58Error Count attribute 139, 144event

mapping 199Event Type Alias attribute 23, 24, 49, 51, 61, 63Events Processed attribute 74, 92Events Processed Rate attribute 74, 93

FFailed Transactions from PIM attribute 75, 119Failed Transactions from Siebel attribute 75, 120FDR Avg time between aging attribute 74, 96FDR Buffer Life in seconds attribute 74, 96FDR Buffer Wraps attribute 75, 96File Name attribute 35File System

situations 158workspaces

descriptions 4File System attribute group 43File System workspace 4Filename attribute 46Files attribute group 45Free Space in MB attribute 33, 44Full Name attribute 14, 27, 132Functionality Test Message attribute 18, 30, 136Functionality Test Status attribute 17, 30, 135

GGate Log attribute group 49Gate Log Pre77 attribute group 50Gateway Bind Address attribute 39, 42Gateway Hostname attribute 39, 43Gateway IP Address attribute 39, 43Gateway Name attribute 22, 23, 35, 41, 45, 49, 50, 56, 62, 66,

100, 104, 116, 120, 143Gateway Name Server Log Pre 77 workspace 4Gateway Port attribute 39, 43Global Data Cursor Cache CPU attribute 75, 110Global Data Cursor Cache Hits attribute 76, 110Global Data Cursor Cache Memory attribute 76, 110Global Data Cursor Cache Misses attribute 76, 111Global Data Cursor Cache Objects attribute 76, 111

Hhistorical data

calculate disk space 145disk capacity planning 145

Host name attribute 40, 64Hours Until Full attribute 34, 37, 45, 48Http URL Add action 175Http URL Remove action 176

Iinclude file 264InfraCore,InfraMultithread and InfraRecovery Statistics

workspace 5


Install Dir attribute 40, 64Integrated Service Management Library documentation 268Interactive Count attribute 140Invalid attribute 55

KKUB_Active_Task_Count_High situation 157KUB_Active_Task_Count_Low situation 157KUB_Ancient_Files_More_Than_10 situation 163KUB_Comp_CPU_Crit situation 153KUB_Comp_CPU_Warn situation 154KUB_Comp_Offline situation 156KUB_Comp_Shutdown situation 156KUB_Comp_Unavailable situation 157KUB_Component_Exit_With_Error situation 164KUB_Component_Failed_Number situation 167KUB_Component_Restarts_Number situation 167KUB_Configuration_Store_Error situation 165KUB_Connect_Time_High situation 168KUB_Connection_Failure situation 155KUB_Data_Cursor_Cache_Misses situation 169KUB_DBFileSys_Space_Avail_Crit situation 159KUB_DBFileSys_Space_Avail_Warn situation 159KUB_Docking_Space_Used situation 162KUB_Error_Amount_High situation 166KUB_Failed_Transactions_Siebel situation 170KUB_FileSys_Space_Avail_Crit situation 158KUB_FileSys_Space_Avail_Warn situation 158KUB_Gateway_Name_Server_Down situation 152KUB_Gateway_NS_Log_Space_Used situation 161KUB_GtwySrvr_Not_Connected situation 166KUB_Incorrect_Password_Config situation 165KUB_Invalid_Files_More_Than_10 situation 163KUB_Log_Archive_Space_Used situation 162KUB_Log_Dir_Space_Used situation 160KUB_Log_File_Rate situation 161KUB_Log_File_Size situation 160KUB_Long_Running_Session situation 170KUB_Object_Problem situation 152KUB_Oracle_Database_Down situation 165KUB_Orphan_Files_More_Than_10 situation 164KUB_Response_Time_High situation 168KUB_Server_CPU_Crit situation 154KUB_Server_CPU_Warn situation 155KUB_Server_Degraded situation 153KUB_Server_Down situation 151KUB_Server_Process_Size situation 155KUB_Server_Space_Used situation 160KUB_SQL_execute_Time_High situation 169KUB_SQL_Fetch_Time_High situation 169KUB_Tasks_Exceed_Configuration situation 167KUB_TxnProc_Space_Used situation 162

LLog Message attribute 23, 24, 50, 51, 62, 64Logs


descriptions 4Logs Pre77


descriptions 4Logs Pre77 workspace 5

Logs Timestamp attribute 23, 24, 50, 51, 62, 63Logs workspace 4

MManaged URLs attribute group 51Marketing Statistics attribute group 54Maximum attribute 19, 127Maximum OOB Component Time attribute 77, 105Maximum Peak Memory Usage attribute 77, 98Minimum attribute 19, 127Minimum Peak Memory Usage attribute 77, 98Mount Point attribute 34, 45

NName attribute 13, 26, 33, 44, 48, 131Node attribute 13, 18, 19, 20, 22, 24, 25, 26, 31, 33, 35, 38, 42,

43, 45, 49, 50, 52, 54, 57, 61, 63, 64, 66, 68, 91, 92, 93, 95, 97,101, 104, 106, 116, 118, 120, 122, 123, 124, 125, 127, 128, 131,138, 141, 143

Normal Count attribute 141Num of DBConn Retries attribute 77, 117Num of DLRbk Retries attribute 78, 117Num of Exhausted Retries attribute 78, 117Number of Component Crashes attribute 78, 98Number of Component Restarts attribute 79, 98Number of Errors attribute 79, 99Number of object rows assigned attribute 80, 92Number of Sleeps attribute 80, 99Number of SQL Executes attribute 79, 102Number of SQL Fetches attribute 79, 103Number of SQL Parses attribute 80, 103

OObject Manager Errors attribute 80, 110Object Name attribute 57Object Status attribute 58Object Type attribute 57Orphaned attribute 55Other Count attribute 140, 144Other Siebel Statistics workspace 5

PPage Faults per Sec attribute 15, 28, 133Page Objects attribute 53Page Size attribute 52Page Title attribute 53Parent Task Id attribute 129, 137Pause Siebel Server Task action 177Percent Change Average attribute 37, 47Percent Change Last Hour attribute 36, 47Percent Change Total attribute 37, 48Percent Free attribute 34, 44Percent of File System Used attribute 36, 46Percent Privileged Time attribute 16, 29, 134Percent Processor Time attribute 16, 29, 134Percent Used attribute 33, 44Percent User Mode Time attribute 16, 29, 134Performance Object Status attribute group 57PID attribute 16, 28, 134PID Group TID attribute 130, 137prerequisite publications 267

Index 277

privacy policy 271probe rules file

include 264PSP Cache Hit Total attribute 81, 121PSP Cache Miss Total attribute 81, 121publications 267, 268

IBM Tivoli Monitoring 267Integrated Service Management Library 268prerequisite 267Redbooks 268related 268Service Management Connect 268SMC

See Service Management ConnectTechnotes 268wikis 268

Put Component Group Online action 179

Qqueries, using attributes 9Query Execution Time attribute 123Query Name attribute 57

RRedbooks 268Reply Messages attribute 81, 111Request Messages attribute 81, 112Response Code attribute 53Response Time attribute 52Resume Siebel Server Task action 181Run Mode attribute 21, 142Run Srvrmgr Command action 182Run State attribute 21, 129, 137Running Count attribute 139, 144Running Interactive Task Count attribute 18Running Task Count attribute 41, 65Running Tasks attribute 21

SSARMID attribute 23, 50, 62SearchEvents Processed attribute 85, 122SearchEvents Processed Rate attribute 85, 122Server Log attribute group 61Server Log Pre77 attribute group 63Server Manager Query Name attribute 123Server Name attribute 21, 40, 56, 62, 64, 100, 104, 116, 120,

128, 136, 141Server State attribute 40, 65Server Status attribute 41, 65Server Type attribute 39, 43, 53Service Management Connect 268Severity attribute 23, 24, 50, 51, 62, 63Shutdown Siebel_Server_Component action 184Siebel


descriptions 2Siebel Adapter Total Query Calls attribute 86, 94Siebel Adapter Total Query Size attribute 86, 94Siebel Adapter Total Sync Size attribute 86, 94Siebel Adapter Total Sync/Upsert Calls attribute 86, 95Siebel Gateway Name Server Log workspace 4Siebel Server attribute group 64

Siebel Server Name attribute 32, 67Siebel Statistics (Superseded) workspace 5Siebel Statistics attribute group 66Siebel workspace 2SiebelComponent class

CDM class name 259monitors 259provides 259Relationships 259

SiebelEnterprise classCDM class name 259contains 259provides 260Relationships 259

SiebelGateway classaccessedVia 260CDM class name 260contains 260monitors 260Relationships 260uses 260

SiebelServer classCDM class name 261contains 261monitors 261Relationships 261uses 261

situations 151additional information

predefined, defined 149KUB_Active_Task_Count_High 157KUB_Active_Task_Count_Low 157KUB_Ancient_Files_More_Than_10 163KUB_Comp_CPU_Crit 153KUB_Comp_CPU_Warn 154KUB_Comp_Offline 156KUB_Comp_Shutdown 156KUB_Comp_Unavailable 157KUB_Component_Exit_With_Error 164KUB_Component_Failed_Number 167KUB_Component_Restarts_Number 167KUB_Configuration_Store_Error 165KUB_Connect_Time_High 168KUB_Connection_Failure 155KUB_Data_Cursor_Cache_Misses 169KUB_DBFileSys_Space_Avail_Crit 159KUB_DBFileSys_Space_Avail_Warn 159KUB_Docking_Space_Used 162KUB_Error_Amount_High 166KUB_Failed_Transactions_Siebel 170KUB_FileSys_Space_Avail_Crit 158KUB_FileSys_Space_Avail_Warn 158KUB_Gateway_Name_Server_Down 152KUB_Gateway_NS_Log_Space_Used 161KUB_GtwySrvr_Not_Connected 166KUB_Incorrect_Password_Config 165KUB_Invalid_Files_More_Than_10 163KUB_Log_Archive_Space_Used 162KUB_Log_Dir_Space_Used 160KUB_Log_File_Rate 161KUB_Log_File_Size 160KUB_Long_Running_Session 170KUB_Object_Problem 152KUB_Oracle_Database_Down 165KUB_Orphan_Files_More_Than_10 164KUB_Response_Time_High 168KUB_Server_CPU_Crit 154


situations (continued)KUB_Server_CPU_Warn 155KUB_Server_Degraded 153KUB_Server_Down 151KUB_Server_Process_Size 155KUB_Server_Space_Used 160KUB_SQL_execute_Time_High 169KUB_SQL_Fetch_Time_High 169KUB_Tasks_Exceed_Configuration 167KUB_TxnProc_Space_Used 162overview 149predefined 149Situation Editor 149

situations, using attributes 9Size Change Average attribute 37, 47Size Change Last Hour attribute 36, 46Size Change Total attribute 37, 48Sleep Time attribute 87, 99SMC

See Service Management ConnectSource Name attribute 22, 24, 49, 51, 61, 63SQL Cursor Cache Hits attribute 82, 113SQL Cursor Cache Misses attribute 82, 113SQL Cursor Total Cpu attribute 82, 113SQL Cursor Total Mem attribute 82, 113SQL Cursor Total Objects attribute 83, 114SQL Execute Time attribute 83, 103SQL Fetch Time attribute 83, 103SQL Object Cache CPU attribute 84, 114SQL Object Cache Hits attribute 84, 114SQL Object Cache Memory attribute 84, 115SQL Object Cache Misses attribute 84, 115SQL Object Cache Objects attribute 85, 115SQL Parse Time attribute 85, 102Start Gateway Name Server action 186Start Siebel Server action 187Start Siebel Server Task action 188Start Time attribute 40, 65Startup Siebel_Server_Component action 190Statistic Alias attribute 32, 67Statistic attribute 32, 67Statistic Details attribute group 68Statistics


descriptions 5Statistics AsgnSubsys attribute group 91Statistics CommInboundProcessor attribute group 92Statistics EAISubsys attribute group 93Statistics FlightDataRecorder attribute group 95Statistics InfraCore attribute group 96Statistics InfraDatabase attribute group 101Statistics InfraMultiThread attribute group 104Statistics InfraObjMgr attribute group 106Statistics InfraRecovery attribute group 116Statistics PIMSIENG attribute group 118Statistics PSPEngine attribute group 120Statistics SearchDataProcessor attribute group 121Statistics ServerQueryTime attribute group 123Statistics TestSubsys attribute group 123Statistics workspace 6Statistics XMLCnv attribute group 125Status attribute 14, 26, 53, 131Stop Gateway Name Server action 191Stop Siebel Server action 193Stop Siebel Server Task action 194Subsystem attribute 32, 67

TTake Action commands

additional information 173Delete Archived Logs 174Http URL Add 175Http URL Remove 176overview 173Pause Siebel Server Task 177predefined 173Put Component Group Online 179Resume Siebel Server Task 181Run Srvrmgr Command 182Shutdown Siebel_Server_Component 184Start Gateway Name Server 186Start Siebel Server 187Start Siebel Server Task 188Startup Siebel_Server_Component 190Stop Gateway Name Server 191Stop Siebel Server 193Stop Siebel Server Task 194Take Component Group Offline 195

take actionsdescriptions 174

Take Component Group Offline action 195Task CPU Details workspace 6Task CPU Util Rollup attribute group 126Task Detail attribute group 128Task Elapsed Time attribute 130, 138Task End Time attribute 130, 138, 143Task ID attribute 129, 136, 142Task Label attribute 129, 137Task PID attribute 129, 136, 142Task Ping Time attribute 130, 137Task Resource attribute group 131Task Runstate attribute 142Task Start Time attribute 130, 138, 142Task Status attribute 130, 138Task Summary attribute group 138Task Type attribute 142Tasks


descriptions 6Tasks Exceeding Configured Capacity attribute 87, 99Tasks Summary workspace 6Tasks workspace 6Technotes 268Tests Attempted attribute 87, 124Tests Failed attribute 87, 124Tests Successful attribute 88, 124Thread Count attribute 15, 28, 133Timestamp attribute 13, 18, 19, 21, 22, 24, 25, 26, 31, 33, 35,

38, 42, 43, 46, 49, 51, 52, 54, 57, 61, 63, 64, 66, 68, 91, 92, 93,95, 97, 101, 105, 106, 117, 118, 121, 122, 123, 124, 125, 127, 128,131, 139, 141, 144

Tivoli Business Service Managercomponents for integrating with 263configuring additional IBM Tivoli Monitoring web

services 265creating a service 264creating data source mapping 265installing Discovery Library Toolkit 264integration 263launching from Tivoli Enterprise Portal 265Tivoli Enterprise Portal

Tivoli Integration Facility (EIF) probe 263viewing data in Tivoli Enterprise Portal 265

Index 279

Tivoli Business Service Managerintegration tasks 264Tivoli Enterprise Console

event mapping 199Tivoli Event Integration Facility (EIF) probe

configuring 264TMSAgent class

CDM class name 261monitors 261Relationships 261

Total attribute 20, 55, 128Total Database Response Time attribute 88, 109Total Object Size attribute 53Total Reply Size attribute 88, 111Total Request Size attribute 89, 112Total Response Time attribute 89, 112Total Size in MB attribute 34, 45Total Tasks attribute 89, 100Total Think Time attribute 89, 115Total XML Converter Size of Input Buffer attribute 90, 125Total XML Converter Size of Output Buffer attribute 90, 125Total XML Generator Calls attribute 90, 126Total XML Parser Calls attribute 90, 126Transactions form Siebel in Progress attribute 91, 118Transactions from PIM in Progress attribute 91, 118Type attribute 14, 23, 24, 27, 38, 49, 51, 61, 63, 132

UUpdated End Time attribute 41, 66Updated Start Time attribute 41, 65URL Alias attribute 54URL attribute 52User Data attribute 54User ID attribute 142User Session attribute group 141User Session Summary attribute group 143User Sessions workspace 7

Vviews

Agent Health workspace 3Availability workspace 3Component Counts workspace 3Components (Superseded) workspace 4Components workspace 3File System workspace 4Gateway Name Server Log Pre 77 workspace 4InfraCore,InfraMultithread and InfraRecovery Statistics

workspace 5Logs Pre77 workspace 5Logs workspace 4Other Siebel Statistics workspace 5Siebel Gateway Name Server Log workspace 4Siebel Statistics (Superseded) workspace 5Siebel workspace 2Statistics workspace 6Task CPU Details workspace 6Tasks Summary workspace 6Tasks workspace 6User Sessions workspace 7

Virtual Size attribute 15, 27, 133

Wwikis 268Worker Count attribute 141Working Set Size attribute 15, 28, 133workspaces

Agent Health 3Availability 3Component Counts 3Components 3Components (Superseded) 4descriptions 2File System 4Gateway Name Server Log Pre 77 4InfraCore,InfraMultithread and InfraRecovery Statistics 5Logs 4Logs Pre77 4, 5Other Siebel Statistics 5predefined 1Siebel 2Siebel Gateway Name Server Log 4Siebel Statistics (Superseded) 5Statistics 5, 6Task CPU Details 6Tasks 6Tasks Summary 6User Sessions 7

Workspacesadditional information 1overview 1


��

Printed in USA

Siebel agent Reference - IBM

Documents

Transcript of Siebel agent Reference - IBM