Unsupported product PATROL for Oracle Tuxedo and its documentation are no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Verifying Discovery


After you have registered a Oracle Tuxedo instance, verify that your instance and applications classes are discovered and that the BEATUX_SYSTEM icon appears in the PATROL Console.

To Verify Discovery

  1. From the PatrolMainMap, open the computer window and verify that the Tuxedo icon (BEATUX_SYSTEM) is present, as shown in the following figure:

    Tuxedo Icon in PATROL Console

    worddavdd4f9d7e44af72731156e85bec0223f6.png

    Note

    If the BEATUX_SYSTEM icon does not appear within two or three minutes, open the PATROL system output window and read the status messages. Look for messages that indicate a specific problem, such as an incorrect port number or user authentication failure. Correct setup problems as described in Registering-a-Tuxedo-Instance

  2. Double-click BEATUX_SYSTEM to see which instances are being monitored. This level will show one icon for each instance that you registered. 
  3. Double-click a Tuxedo instance icon.
    You should see several icons in the PATROL window, depending on what Tuxedo features you have configured and running, as shown in the following figure. For a complete list of all application class icons, see Components.

    Note

     It may take several minutes for a server to be fully monitored because some application classes are discovered on different schedules. 

    The application class icons and parameter icons that are displayed during the discovery cycle depend on how your Tuxedo environment is configured. Some features and icons are available only after you perform configuration or administration tasks. 

    Icons that you may not see include the following:

    Tuxedo Feature Icons
    worddav657867db1ab7d47ce957d5a3e11d5a71.png


    • BEATUX_PROCESS—the icon appears only after you have specified servers to monitor. This icon does not appear for Unix servers. For more information, see "Monitoring Specified Servers" on page 169.
    • BEATUX_CLIENT—the icon appears only after you have specified clients to monitor. For more information, see "Monitoring Specified Clients" on page 167.
    • BEATUX_SERVICE—the icon appears only after you have specified services to monitor. For more information, see "Selecting Services to be Monitored" on page 124.
    • BEATUX_ACL—the icon appears only if your Tuxedo system is configured to use ACL.
    • BEATUX_EVENT—the icon appears only if TMSYSEVT or TMUSREVT is running.
    • BEATUX_M3—the icon appears only if the Tuxedo system is a WebLogic Enterprise system.

      Note

      If you are using multi-thread clients (supported in TUXEDO for Sun Solaris 2.6 or Windows), you need to set the environment variable TMCONTEXTS to 1 before setting up the monitoring instance. See your PATROL Console documentation for information about setting environment variables. 

Where to Go from Here

After verifying that PATROL has discovered your server and has instantiated application instances, see Using PATROL for Oracle Tuxedo to begin configuring and using the product monitoring features. 
 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*