If you are willing to use web services and can start the server with the "-xs http" server switch to start the SQL Anywhere built-in HTTP server, then you could do the following to view the console messages in a browser:
1) Create a web service in your database that accepts requests:
create service console_messages
type 'raw'
authorization off
user "dba"
url off
as call "dba".sp_console_messages();
2) Define the sp_console_messages() procedure:
create or replace procedure sp_console_messages()
result (rawdoc long varchar)
begin
declare @result long varchar;
select list( '<tr><td>'||line_num
||'</td><td>'||message_time
||'</td><td>'||html_encode(message_text)
||'</td></tr>\\n', '' order by line_num desc )
into @result
from sa_get_server_messages(0);
set @result = '<html>\\n'
|| '<head><title>Console Messages - '
|| html_encode( property('name') )
|| '</title></head>\\n'
|| '<body>\\n'
|| '<table border=0>\\n'
|| ' <tr><th>Line</th><th>Time</th><th>Message</th></tr>\\n'
|| @result
|| '</table>\\n'
|| '</body>\\n'
|| '</html>\\n'
;
call sa_set_http_option( 'AcceptCharset', '+,utf-8,*' );
call sa_set_http_header( 'Content-Type', 'text/html' );
select @result;
end;
3) Add "-xs http" to your server start line (if you haven't done this already). E.g.
dbsrv12 test.db -xs http
4) Use your browser to view the console log by browsing to:
http://yourhost.yourdomain.com/console_messages
Note that the messages come out in reverse order - this is due to the "desc" in the order by clause of the list() expression in the sp_console_messages procedure. I did this so the most recent message would be displayed at the top (so you don't have to scroll down all the time to see what has recently happened). If you don't like this, simply replace "desc" with "asc" (or remove "desc" completely).
You can do lots of interesting things using similar methods. E.g. get a list of server properties (call sa_eng_properties), connection properties (call sa_conn_properties), etc.
To be secure, you can either add "AUTHORIZATION ON" to your service definition to require that the dba username/password is specified in order to get the console messages, or add "SECURE ON" (and add appropriate certificates to the "-xs https" server command line) to require that a secure connection is used, or BOTH (which I would recommend!).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.