Ribo is basically a proxy server that needs to be between your application and your database. So your application will call Ribo (localhost, port 5005), then Ribo will forward the data to your database which is set when you start Ribo.
For those troubleshooting Sybase on CentOS/RedHat or Ubuntu:
(Assuming ASE installation at /opt/sybase, working unixODBC connection and full Java JRE installation)
Set Environment Variables:
sudo vi /etc/profile.d/ribo.sh
Description = Sybase ODBC Data Source
UserID = sa
Driver = Adaptive Server Enterprise
Server = 127.0.0.1
Port = 5005
Database = <your database name>
UseCursor = 1
Change ODBC call in your application to call RIBO instead of other DSN entry.
Set ownership of /opt/sybase/jutils-3_0/ribo to your account (Ribo will try to write to this directory with your credentials; if you use sudo when running Ribo, you must add Environment Variables to the root account.)
Should get the response "Listening on port 5005"
Run your query from either your application or from another session using isql.
Should see "Accepting new connection from:", then "Sending captured traffic.." then "Closing dump file...". Ctrl C to exit
Convert raw data to readable format:
/opt/sybase/jutils-3_0/ribo/Ribo capX.tds tds_capture.txt (where X is the number in the .tds file you want to convert)