Skip to end of metadata
Go to start of metadata

Ribo works as a gateway that will sit between the client and the ASE.  Ribo captures the TDS packets that are sent from the client (application) to the ASE, and
the TDS packets returned by the ASE to the client.  This provides support with information that is used to help determine client errors.

The Ribo utility is located in the
Unix:  $SYBASE/jutils-3_0/ribo
Windows: %SYBASE%\jutils-3_0\ribo   directories

When you setup Ribo, follow these steps.

1) Create a RIBO entry in the interfaces/sql.ini file on the machine where Ribo will be running.

It must have a unique port.  The default is 5005 

RIBO
        master tcp ether host-machine-name 5005
        query tcp ether host-machine-name 5005 

2) Set the JAVA_HOME and RIBO_HOME variables 

setenv JAVA_HOME $SYBASE/shared/JRE-6_0_24_32bit (This can vary with SDK versions)
setenv RIBO_HOME $SYBASE/jutils-3_0/ribo  (This can vary with SDK versions)  

3) Start RIBO 

Ribo -l 5005 -s server-machine -p 1250 (1250 should actually be the port of the ASE)

Ribo –l (for listening) –s ASE Host machine –p port the ASE is listening on

Need spaces between attribute and values

OR:

You can also start RIBO in GUI mode.  $SYBASE\jutils-3_0\ribo\ribo -gui


The Listen Port is the port that Ribo is listening on.

Server Host is the Machine Name the ASE resides on.

Server Port is the port the ASE is listening on.

So, if your ASE is running on machine ASE1, and the port is 15764, that is what goes in the Server Host: and the Server Port:
This sets up Ribo to connect to the ASE.
Then you will point the application to Ribo.
So, if Ribo is on machine Client1, you set the application to point to machine Client1 and port 5005.  Ribo is a gateway between the application
and the ASE. 

Start Ribo by selecting the Start Capture button.

Once you have captured the error you can then select the Stop Capture.

The Capture will place the capture files in the Ribo directory.

They will have a naming convention like cap0.tds, cap1.tds, cap2.tds.

Growing in number for each connection that is made. 

You are pointing Ribo to the ASE and the application to Ribo 

4) Connect the failing application to RIBO instead of directly to the ASE

The trace files are created in the Ribo directory. They will have names like cap0.tds, cap0.txt for each connection.
To convert the .tds files to a text format. You will execute the command from a prompt,  Ribo cap0.tds cap0.txt
This will be done for each tds file created


Related Documents

Large Ribo traces 15.7 SP100 and higher:  New -n Command line option in Ribo Utility

  • No labels