Before any data sending be sure if your brewers have sent data to iberonesia before. Look for your brewers in Brewer List<\/a>. If they are not there, contact the admin<\/a>.<\/p>\n The client software can be installed in any computer with access to the brewer data files.<\/p>\n There are two different ways to use the client:<\/p>\n Download the needed interpreter and install it<\/p>\n Be sure that your python interpreter is callable from every path in your system (Open a console and try python<\/b>, exit()<\/b> for exit).<\/p>\n Download and uncompress it in your system.<\/p>\n You can download client_python.zip<\/a>.<\/p>\n Download and uncompress it in your system.<\/p>\n You can download client_exe.zip<\/a> .<\/p>\n Unzip the .zip and try $>refresh.exe (in dist folder) in a console to test if client is working properly. No error message should appear.<\/p>\n The client configuration file is used by the refresh.py program. The default configuration file is client.ini.<\/p>\n The file is a plain ASCII INI file with the INI file syntax<\/a>. The file consists of a global section and several server sections, one for each server to send the files to.<\/p>\n The content of the present example includes lines (bold) that has not to be changed. This information is relative to the server or critical:<\/p>\n The easiest way to configure the client is to specify all options in client.ini file (like the one above) and execute refresh.py without arguments; and execute with arguments overriding the client.ini options if you want any unusual operation, such as sending only certain files. E.g. (using the client.ini above):<\/p>\n gt;python refresh.py -b 157 -i c:\\brewer\\data Parameters -b<\/b> and -i<\/b> are not necessary if specified in client.ini file (recommended).<\/p>\n The global section has the following properties:<\/p>\n A server section is identified by the server alias (i.e. the alias is the name between the brackets), and it has the following properties:<\/p>\n Some of these properties may be overridden using command line parameters when executing refresh.py or alive.py.<\/p>\n You only have to edit the brewerid to your brewer. Comment the lines (put # at the beginning of the line) if not needed (proxy is an example).<\/p>\n Most of the refresh.py options may be configured though command line arguments or client.ini configuration file.<\/p>\n Any option specified in command line overrides the option in client.ini.<\/p>\n All options are shown executing the client with parameter -h<\/i><\/p>\n The mandatory options are:<\/p>\n Try to open a browser and access eubrewnet<\/a>. If not, try to contact your system admins to grant access to the internet.<\/p>\n To debug any problem, it is recommended to execute the client with a command line and using the -v parameter (the more v, the more debugging information shown, with -vvv the maximum).<\/p>\n gt;python refresh.py -b XXX -vvv gt;python refresh.py 1>client.log 2>client_error.log There are two usual methods:<\/p>\n As a brewer routine you can put a routine (an example below) in your schedule who call the sending program to send the data.<\/p>\n In W2k W7 the brewer software waits until the command is finished so if the communication fails or it\u2019s slow it can take too much time for sending and can stop or delay the brewer software. This is not an issue if you use DOSBOX<\/p>\n As an scheduled task you can program the execution of the sending program.<\/p>\n The old MSDOS\/GWBASIC do not allow the sharing use of the files, as the B file is always open could happen that the sending program block the access to the B file and stop the record of the brewer observations.<\/i><\/p>\n So we recommend the send of the data in two steps:<\/p>\n gt;python refresh.py -b %%X -s iberonesia -i %DEST_DIR%\\brw#%%X\\bdata%%X >client%%X.out 2>>client_error%%X.log\n<\/li>\n<\/ol>\n When all parameters are processed, it is known the files to send and the servers to send to. The program loops though the servers and tries to send all the files specified. The client maintains a local database storing md5sum and size of the files that has been transferred to the server, used to determine if a file needs to be sent.<\/p>\n <\/a><\/p>\n The protocol to send the files is:<\/p>\n The transfers cannot be done file to file (would be too many) nor all the files simultaneously (too many data to transfer could cause a time out). So, the files are transferred in blocks. If a threshold size of files is reached, the files are packed in a zip file and sent to the server. Once the file is actually sent, the (md5sum, size) in the local database is updated.<\/p>\n <\/a><\/p>\n The protocol to regenerate the database is:<\/p>\n This way, the local database stores the same info about the file that is stored in the server, so there is no need to query that info to the server for each file in the input, thus saving a lot of network time.<\/p>\n It is possible that the local database gets corrupted or out of sync with the server (e.g., a server is replaced and some files had been sent to the old server that are not in the new server). In that case, the database needs to be deleted, and so regenerated in the next execution.<\/p>\n <\/p>\n 1- Install<\/strong> the python interpreter and then client script (client_python.zip<\/a>) or client executable (client_exe.zip<\/a>).<\/p>\n Copy the scripts to the brewer program directory<\/p>\n 2- Check the configuration<\/strong><\/p>\n Are you bellow a proxy ?<\/p>\n no: change noproxy in client.ini to YES !!! <\/p>\n CLIENT.INI<\/strong> 3 execute the script<\/em><\/strong> XXX is the name of your brewer and brewer_data is a directory where the brewer files are.<\/p>\n it takes long, probably is working fine, its sending all the data<\/span> of your test directory, check the log files.<\/p>\n <\/p>\n 4- Schedule the data sent<\/strong> : We use robocopy to make a copy of the bdata directory, edit this two files to the brewer program directory . Now you can put CK on your brewer schedule to sent<\/span> data<\/span> to eubrewnet<\/span><\/p>\n EUBREWNET<\/span>.BAT<\/strong><\/p>\n set DEST_DIR=e:\\eubrewnet<\/span>\\ CK.RTN<\/strong><\/p>\n 10000 rem Call eubrewnet<\/span>.bat <\/p>\n\n
Install the Software<\/h2>\n
Setup instructions<\/h3>\n
\n
Python Client<\/h4>\n
Python Interpreter<\/h5>\n
\n
Python client<\/h5>\n
+ client_python<\/b>\n + source<\/b>\n alive.py\n client.ini<\/b>\n configure.py\n download.py\n log.py\n refresh.py<\/b>\n refreshdb.py\n util.py\n xmlrpcproxy.py\n<\/pre>\n
Exe Client (Windows Only)<\/h4>\n
+ client_exe<\/b>\n + build\n - bdist.win32\n ...\n + dist<\/b>\n _bbsddb.pyd\n _hashlib.pyd\n _socket.pyd\n client.ini<\/b>\n library.zip\n pyexpat.pyd\n python27.dll\n refresh.exe<\/b>\n select.pyd\n unicodedata.pyd\n w9xpopen.exe\n + source\n ...\n<\/pre>\n
Configuration<\/h3>\n
Client configuration file<\/h4>\n
[global]<\/b>\n brewerid=157\n working_dir=.\n input=c:\\brewer\\data\n servers=iberonesia3<\/b>\n proxy=proxy.xxx.xxx:port\n [iberonesia3]<\/b>\n url=http:\/\/rbcce.aemet.es\/refresh<\/a><\/b>\n db=iberonesia3.db\n noproxy=yes\n serverport=8081<\/b>\n<\/pre>\n
\n
<\/pre>\n
\nYou only have to edit the brewer (-b)<\/b> and the brewer data directory (-i).<\/b><\/p>\n\n
\n
refresh.py options<\/h4>\n
$ .\/refresh.py -h<\/b>\n\n Usage: refresh.py [options]\n\n Options:\n -h, --help show this help message and exit\n -i FILE, --input=FILE\n File to process. If the given file is a directory, all\n files within will be processed.\n -s SERVERS, --servers=SERVERS\n Comma separated list of xmlrpc server aliases\n -b BREWERID, --brewerid=BREWERID\n Brewerid of file\/s to process\n -c FILE, --config=FILE\n Configuration file path\n -v, --verbose Verbosity level. The more '-v' the more verbose is the\n program.\n<\/pre>\n
\n
Check the communications<\/h3>\n
\n
<\/pre>\n
\n - XXX: Id of a brewer
\nIf you want to save the errors and log , try to define log and error file like this:<\/p>\n\n
<\/pre>\n
\nLook for the content in client.log and client_error.log (If there\u2019s any error in the communication contact the Admin<\/a> and send the content of these files).<\/p>\nSchedule the data sending<\/h2>\n
\n
From the Brewer computer<\/h3>\n
\n
set DEST_DIR=e:\\brewer\n set ORIG_DIR=e:\\bdata1\n\n net use x: \/DELETE\n net use x: \\\\10.2.20.20\\brewer \/PERSISTENT:NO\n\n robocopy %ORIG_DIR% %DEST_DIR% \/S \/XO \/V \n<\/pre>\n<\/li>\n
\n
<\/pre>\n
Appendix<\/h2>\n
How it works<\/h3>\n
Sending files to a server<\/h4>\n
Check if the refresh database for the server exists. If not exists, the database is (re)generated<\/a>. \n For each file: \n Check if the file needs to be sent. The client knows if a file needs to be sent comparing the (md5sum, size) stored in the local database with the (md5sum, size) of the actual file. \n If the file entry in the local database does not exist, the file is sent \n If any of the md5sum, size stored in the database differs from the ones in the actual file, the file is sent. \n In other case (md5sum and sizes are equal), the file is not sent.\n<\/pre>\n
Regenerating local database<\/h4>\n
The client sends to the server all the files that is willing to transfer (i.e., the files specified with the input parameter) \n For each file in the previous list, the server returns the appropiate (md5sum,size) tuple of the file stored in the server. If the server knows nothing about that file (i.e., it has never been transferred), no entry is returned. \n Each entry returned to the client is written to the local database.\n<\/pre>\n
Quick Guide<\/h1>\n
<\/a><\/h1>\n
\nyes: Edit the client.ini and indicate your proxy server and port, set the noproxy flag to NO !!<\/p>\n
\n[global]\nservers=iberonesia3
\nproxy=proxy.xxx.xxx:port
\n[iberonesia3]\nurl=http:\/\/rbcce.aemet.es\/
\ndb=iberonesia3.db
\nserverport=8081
\nnoproxy=no<\/p>\n
\npython refresh.py \u2013 b XXX -i c:\\brewer_data -vvv 1>client.log 2>client_error.log<\/em><\/p>\n
\nset ORIG_DIR=e:\\bdata157\\bdata
\nset X=157
\nrobocopy %ORIG_DIR% %DEST_DIR%\\Brw#%%X\\bdata%%X\\ *.%%X \/XO \/V \/MAXAGE:3
\npython refresh.py -b %%X -s iberonesia -i %DEST_DIR%\\brw#%%X\\bdata%%X >client%%X.out 2>>client_error%%X.log<\/p>\n
\n10010 data<\/span> ck
\n20000 shell\u201deubrewnet<\/span>
\n30000 return
\n65529 rem dummy<\/p>\n<\/h2>\n
<\/a>FAQ<\/h2>\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\nxmlrpclib.ProtocolError: ProtocolError for rbcce.aemet.es\/refresh\/xmlrpc\/: 403 Forbidden<\/li>\n<\/ul>\n<\/ul>\n<\/ul>\n<\/ul>\n<\/ul>\n<\/ul>\n<\/ul>\n<\/ul>\n<\/ul>\n<\/ul>\n<\/ul>\n