Difference between revisions of "RCUG 1 Introducing RootCause"
m |
m |
||
| Line 25: | Line 25: | ||
<DIV> | <DIV> | ||
| − | <P><A HREF=rcc-5.html>[Next]</A> <A HREF=rcc-3.html>[Previous]</A> <A HREF=rcc-1.html>[Top]</A> <A HREF=rcc-3.html>[Contents]</A> <A HREF=rcc-14.html>[Index]</A></P> | + | <P><A HREF=rcc-5.html>[Next]</A> <A HREF=rcc-3.html>[Previous]</A> <A HREF=rcc-1.html>[Top]</A> <A |
| + | |||
| + | HREF=rcc-3.html>[Contents]</A> <A HREF=rcc-14.html>[Index]</A></P> | ||
<P>RootCause</P> | <P>RootCause</P> | ||
| Line 42: | Line 44: | ||
<H2> What Is RootCause?</H2> | <H2> What Is RootCause?</H2> | ||
| − | <P> RootCause is a sophisticated tool designed to help software organizations solve a problem as quickly | + | <P> RootCause is a sophisticated tool designed to help software organizations solve a problem as quickly |
| − | + | as possible, ideally from a single occurrence, while simultaneously reducing support costs. Fundamental | |
| − | + | to this is a tracing capability. We have designed RootCause to make powerful application tracing and | |
| − | <P> The RootCause Console tools are used in the application development and support environments to define what to trace and also ultimately to view the trace data. The application being traced may be run in the development environment as well, of course; or it may be run remotely, on a separate test platform or on a customer's computer, without access to the development environment.</P> | + | root cause analysis as simple as possible.</P> |
| + | |||
| + | <P> The fundamental concept is that all of the data needed to debug an application problem is recorded | ||
| + | |||
| + | in its RootCause workspace. The RootCause Console Graphical User Interface (GUI) allows you to choose | ||
| + | |||
| + | the data to be collected and to navigate the collected data.</P> | ||
| + | |||
| + | <P> When an application problem occurs, the "user" sends the RootCause workspace to the support | ||
| + | |||
| + | organization as the problem report. If the support organization has defined the trace correctly, this | ||
| + | |||
| + | RootCause workspace contains sufficient information to do the root cause analysis of the problem. | ||
| + | |||
| + | There's no need to recreate the problem or ask the user further questions.</P> | ||
| + | |||
| + | <P> The RootCause Console tools are used in the application development and support environments to | ||
| + | |||
| + | define what to trace and also ultimately to view the trace data. The application being traced may be run | ||
| + | |||
| + | in the development environment as well, of course; or it may be run remotely, on a separate test | ||
| + | |||
| + | platform or on a customer's computer, without access to the development environment.</P> | ||
<P> You can choose to | <P> You can choose to | ||
<!-- <A NAME=MARKER-2-154></A> --> | <!-- <A NAME=MARKER-2-154></A> --> | ||
| − | deploy the RootCause trace to the application environment after a problem occurs, or you can include RootCause as part of your shipped application so that any time a problem occurs you can immediately examine the data collected by RootCause to perform a root cause analysis of the problem.</P> | + | deploy the RootCause trace to the application environment after a problem occurs, or you can include |
| + | |||
| + | RootCause as part of your shipped application so that any time a problem occurs you can immediately | ||
| + | |||
| + | examine the data collected by RootCause to perform a root cause analysis of the problem.</P> | ||
| + | |||
| + | <P> Note that RootCause is designed to work on shipped applications. No change is needed to your | ||
| + | |||
| + | application or your build processes! The traces will be automatically inserted into your application | ||
| + | |||
| + | when a copy of it is loaded into memory; the traces remain only while your application is running, and | ||
| − | + | they vanish afterwards.</P> | |
<!-- <A NAME=HEADING4-8></A> | <!-- <A NAME=HEADING4-8></A> | ||
| Line 61: | Line 95: | ||
<H2> Java, C++, or Both?</H2> | <H2> Java, C++, or Both?</H2> | ||
| − | <P> RootCause is packaged as <EM>RootCause for Java</EM> and <EM>RootCause for C++.</EM> This is the user's guide for the | + | <P> RootCause is packaged as <EM>RootCause for Java</EM> and <EM>RootCause for C++.</EM> This is the |
| + | |||
| + | user's guide for the | ||
<!-- <A NAME=MARKER-10-155></A> --> | <!-- <A NAME=MARKER-10-155></A> --> | ||
| − | <EM>C++</EM> version only. You should read the documentation and do the demos that correspond to the | + | <EM>C++</EM> version only. You should read the documentation and do the demos that correspond to the |
| − | <P> The differences in features between <EM>RootCause for Java</EM> and <EM>RootCause for C++</EM> are determined solely by the license key(s) you are issued by OC Systems. If this isn't the version you want, or you want to use RootCause on native code libraries loaded by Java, or Java run as applets or beans from a compiled application, you will need licenses to enable both the Java and C++ features. For more information see | + | version of RootCause you're interested in.</P> |
| + | |||
| + | <P> The differences in features between <EM>RootCause for Java</EM> and <EM>RootCause for C++</EM> are | ||
| + | |||
| + | determined solely by the license key(s) you are issued by OC Systems. If this isn't the version you | ||
| + | |||
| + | want, or you want to use RootCause on native code libraries loaded by Java, or Java run as applets or | ||
| + | |||
| + | beans from a compiled application, you will need licenses to enable both the Java and C++ features. For | ||
| + | |||
| + | more information see | ||
<A HREF="rcc-5.html#MARKER-9-259">"Licensing"</A>, and | <A HREF="rcc-5.html#MARKER-9-259">"Licensing"</A>, and | ||
<A HREF="rcc-13.html#MARKER-9-2192">"Tracing Java and C++ In One Program"</A>.</P> | <A HREF="rcc-13.html#MARKER-9-2192">"Tracing Java and C++ In One Program"</A>.</P> | ||
| Line 80: | Line 126: | ||
on the Unix | on the Unix | ||
<!-- <A NAME=MARKER-10-158></A> --> | <!-- <A NAME=MARKER-10-158></A> --> | ||
| − | platform. Your feedback is desired, both on problems that you encounter and on suggestions of how the product could better accomplish its goals of solving problems from a single occurrence and of reducing support costs.</P> | + | platform. Your feedback is desired, both on problems that you encounter and on suggestions of how the |
| + | |||
| + | product could better accomplish its goals of solving problems from a single occurrence and of reducing | ||
| + | |||
| + | support costs.</P> | ||
| − | <P> Please e-mail feedback to | + | <P> Please e-mail feedback to [mailto:support@ocsystems.com support@ocsystems.com] |
<A HREF="mailto:support@ocsystems.com">support@ocsystems.com</A> | <A HREF="mailto:support@ocsystems.com">support@ocsystems.com</A> | ||
and indicate what version of RootCause you are using. The version number can be obtained by | and indicate what version of RootCause you are using. The version number can be obtained by | ||
| Line 88: | Line 138: | ||
with the command <CODE>rootcause help</CODE>.</P> | with the command <CODE>rootcause help</CODE>.</P> | ||
| − | <P> If you are evaluating RootCause, or you are a first time user, we suggest that you install RootCause in a local directory (no special system administrator privileges are needed) and do the demonstrations outlined in | + | <P> If you are evaluating RootCause, or you are a first time user, we suggest that you install RootCause |
| + | |||
| + | in a local directory (no special system administrator privileges are needed) and do the demonstrations | ||
| + | |||
| + | outlined in | ||
<A HREF="rcc-8.html#MARKER-9-707">Chapter 5, "RootCause Demo"</A>. | <A HREF="rcc-8.html#MARKER-9-707">Chapter 5, "RootCause Demo"</A>. | ||
| − | Then return to this manual to get specific questions answered. If the information is not clear, let us know.</P> | + | Then return to this manual to get specific questions answered. If the information is not clear, let us |
| + | |||
| + | know.</P> | ||
<P> <A HREF="rcc-5.html#MARKER-9-205">Chapter 2, "Installing RootCause"</A> | <P> <A HREF="rcc-5.html#MARKER-9-205">Chapter 2, "Installing RootCause"</A> | ||
| Line 98: | Line 154: | ||
<P> <A HREF="rcc-6.html#MARKER-9-335">Chapter 3, "Terminology and Concepts"</A> | <P> <A HREF="rcc-6.html#MARKER-9-335">Chapter 3, "Terminology and Concepts"</A> | ||
| − | introduces some terminology and concepts that RootCause users should know to make best use of the product. This chapter also contains a | + | introduces some terminology and concepts that RootCause users should know to make best use of the |
| + | |||
| + | product. This chapter also contains a | ||
<A HREF="rcc-6.html#MARKER-9-386">Glossary</A>.</P> | <A HREF="rcc-6.html#MARKER-9-386">Glossary</A>.</P> | ||
<P> <A HREF="rcc-7.html#MARKER-9-508">Chapter 4, "Getting Started"</A> | <P> <A HREF="rcc-7.html#MARKER-9-508">Chapter 4, "Getting Started"</A> | ||
| − | discusses how an individual user would set up to use RootCause after it is installed and gives a quick description of getting started with RootCause.</P> | + | discusses how an individual user would set up to use RootCause after it is installed and gives a quick |
| + | |||
| + | description of getting started with RootCause.</P> | ||
<P> <A HREF="rcc-8.html#MARKER-9-707">Chapter 5, "RootCause Demo"</A> | <P> <A HREF="rcc-8.html#MARKER-9-707">Chapter 5, "RootCause Demo"</A> | ||
| Line 108: | Line 168: | ||
<P> <A HREF="rcc-9.html#MARKER-9-873">Chapter 6, "Deploying the RootCause Workspace"</A> | <P> <A HREF="rcc-9.html#MARKER-9-873">Chapter 6, "Deploying the RootCause Workspace"</A> | ||
| − | explains how to define a RootCause trace session at your local site and then send it to a remote site to do remote debugging.</P> | + | explains how to define a RootCause trace session at your local site and then send it to a remote site to |
| + | |||
| + | do remote debugging.</P> | ||
| + | |||
| + | <P> <A HREF="rcc-10.html#MARKER-9-946">Chapter 7, "RootCause Files and Environment | ||
| − | + | Variables"</A> | |
discusses the environment variables | discusses the environment variables | ||
<!-- <A NAME=MARKER-10-162></A> --> | <!-- <A NAME=MARKER-10-162></A> --> | ||
| Line 116: | Line 180: | ||
<P> <A HREF="rcc-11.html#MARKER-9-1320">Chapter 8, "RootCause GUI Reference"</A> | <P> <A HREF="rcc-11.html#MARKER-9-1320">Chapter 8, "RootCause GUI Reference"</A> | ||
| − | describes the RootCause Graphical User Interface in detail, briefly describing each dialog, menu item, and button.</P> | + | describes the RootCause Graphical User Interface in detail, briefly describing each dialog, menu item, |
| + | |||
| + | and button.</P> | ||
<P> <A HREF="rcc-12.html#MARKER-9-2008">Chapter 9, "RootCause Command Reference"</A> | <P> <A HREF="rcc-12.html#MARKER-9-2008">Chapter 9, "RootCause Command Reference"</A> | ||
| Line 129: | Line 195: | ||
Release Notes for the current release of the product.</P> | Release Notes for the current release of the product.</P> | ||
| − | <P> Check our web site at | + | <P> Check our web site at [http://www.ocsystems.com/ www.ocsystems.com] |
<A HREF="http://www.ocsystems.com/">www.ocsystems.com</A> | <A HREF="http://www.ocsystems.com/">www.ocsystems.com</A> | ||
for | for | ||
| Line 142: | Line 208: | ||
<!-- | <!-- | ||
| − | <P><A HREF=rcc-5.html>[Next]</A> <A HREF=rcc-3.html>[Previous]</A> <A HREF=rcc-1.html>[Top]</A> <A HREF=rcc-3.html>[Contents]</A> <A HREF=rcc-14.html>[Index]</A></P> | + | <P><A HREF=rcc-5.html>[Next]</A> <A HREF=rcc-3.html>[Previous]</A> <A HREF=rcc-1.html>[Top]</A> <A |
| + | |||
| + | HREF=rcc-3.html>[Contents]</A> <A HREF=rcc-14.html>[Index]</A></P> | ||
<P></P> | <P></P> | ||
<ADDRESS>Copyright 2006 OC Systems, Inc.</ADDRESS> | <ADDRESS>Copyright 2006 OC Systems, Inc.</ADDRESS> | ||
Revision as of 23:42, 15 August 2017
RootCause User Guide
Contents
Introducing RootCause
RCUG 1 Introducing RootCause
What Is RootCause?
RootCause is a sophisticated tool designed to help software organizations solve a problem as quickly as possible, ideally from a single occurrence, while simultaneously reducing support costs. Fundamental to this is a tracing capability. We have designed RootCause to make powerful application tracing and root cause analysis as simple as possible.
The fundamental concept is that all of the data needed to debug an application problem is recorded in its RootCause workspace. The RootCause Console Graphical User Interface (GUI) allows you to choose the data to be collected and to navigate the collected data.
When an application problem occurs, the "user" sends the RootCause workspace to the support organization as the problem report. If the support organization has defined the trace correctly, this RootCause workspace contains sufficient information to do the root cause analysis of the problem. There's no need to recreate the problem or ask the user further questions.
The RootCause Console tools are used in the application development and support environments to define what to trace and also ultimately to view the trace data. The application being traced may be run in the development environment as well, of course; or it may be run remotely, on a separate test platform or on a customer's computer, without access to the development environment.
You can choose to deploy the RootCause trace to the application environment after a problem occurs, or you can include RootCause as part of your shipped application so that any time a problem occurs you can immediately examine the data collected by RootCause to perform a root cause analysis of the problem.
Note that RootCause is designed to work on shipped applications. No change is needed to your application or your build processes! The traces will be automatically inserted into your application when a copy of it is loaded into memory; the traces remain only while your application is running, and they vanish afterwards.
Java, C++, or Both?
RootCause is packaged as RootCause for Java and RootCause for C++. This is the user's guide for the C++ version only. You should read the documentation and do the demos that correspond to the version of RootCause you're interested in.
The differences in features between RootCause for Java and RootCause for C++ are determined solely by the license key(s) you are issued by OC Systems. If this isn't the version you want, or you want to use RootCause on native code libraries loaded by Java, or Java run as applets or beans from a compiled application, you will need licenses to enable both the Java and C++ features. For more information see <A HREF="rcc-5.html#MARKER-9-259">"Licensing"</A>, and <A HREF="rcc-13.html#MARKER-9-2192">"Tracing Java and C++ In One Program"</A>.
About This Guide
This User's Guide describes version 2 of the RootCause product for C/C++ on the Unix platform. Your feedback is desired, both on problems that you encounter and on suggestions of how the product could better accomplish its goals of solving problems from a single occurrence and of reducing support costs.
Please e-mail feedback to support@ocsystems.com
<A HREF="mailto:support@ocsystems.com">support@ocsystems.com</A>
and indicate what version of RootCause you are using. The version number can be obtained by
with the command rootcause help.
If you are evaluating RootCause, or you are a first time user, we suggest that you install RootCause in a local directory (no special system administrator privileges are needed) and do the demonstrations outlined in <A HREF="rcc-8.html#MARKER-9-707">Chapter 5, "RootCause Demo"</A>. Then return to this manual to get specific questions answered. If the information is not clear, let us know.
<A HREF="rcc-5.html#MARKER-9-205">Chapter 2, "Installing RootCause"</A> discusses the installation of RootCause.
<A HREF="rcc-6.html#MARKER-9-335">Chapter 3, "Terminology and Concepts"</A> introduces some terminology and concepts that RootCause users should know to make best use of the product. This chapter also contains a <A HREF="rcc-6.html#MARKER-9-386">Glossary</A>.
<A HREF="rcc-7.html#MARKER-9-508">Chapter 4, "Getting Started"</A> discusses how an individual user would set up to use RootCause after it is installed and gives a quick description of getting started with RootCause.
<A HREF="rcc-8.html#MARKER-9-707">Chapter 5, "RootCause Demo"</A> demonstrates how to apply RootCause to a simple program.
<A HREF="rcc-9.html#MARKER-9-873">Chapter 6, "Deploying the RootCause Workspace"</A> explains how to define a RootCause trace session at your local site and then send it to a remote site to do remote debugging.
<A HREF="rcc-10.html#MARKER-9-946">Chapter 7, "RootCause Files and Environment Variables"</A> discusses the environment variables and files that affect RootCause.
<A HREF="rcc-11.html#MARKER-9-1320">Chapter 8, "RootCause GUI Reference"</A> describes the RootCause Graphical User Interface in detail, briefly describing each dialog, menu item, and button.
<A HREF="rcc-12.html#MARKER-9-2008">Chapter 9, "RootCause Command Reference"</A>
describes the rootcause command line.
<A HREF="rcc-13.html#MARKER-9-2163">Chapter 10, "Selected Topics"</A> contains technical discussions for issues of interest to RootCause users.
Problems and platform-specific issues are discussed in the Release Notes for the current release of the product.
Check our web site at www.ocsystems.com <A HREF="http://www.ocsystems.com/">www.ocsystems.com</A> for white papers and the newest version of the product.
Copyright 2006-2017 OC Systems, Inc.