WeBWorK Main Forum

Setting up External Client

Setting up External Client

by Homer White -
Number of replies: 2
Is the documentation on External Clients (http://webwork.maa.org/wiki/Client_Editor#.V2_aUY7VNms) up to date? I'm trying to set one up on my machine.

I note that the current version of WebworkClient.pm calls for XMLRPC::Lite rather than SOAP::Lite as in the documentation, so I installed XMLRPC::Lite.

I did all other configurations as directed, including, on our webwork server, changes to the webwork.apache2.4-config file followed by a restart.

I tried our webwork server (currently http), and for that I get the following the HTML file:

Error in xmlrpcCall to server: Server, Webservice.pm: Error when trying to authenticate

I've also tried test.webwork.maa,org and the rochester site (both https), and for these I get a blank HTMLfile and in my shell the message:

There were a lot of errors for renderProblem
Errors:
500 Can't connect to test.webwork.maa.org:443 at /Users/homer/webworkClient/WebworkClient.pm line 126.

Thanks,
Homer
In reply to Homer White

Re: Setting up External Client

by Homer White -
Ignore the above post for now. I realized today that the scripts referred to are in old subdirectory, and that sendXMLPRC.pl is the thing to do now. I'm having trouble with that one, too, but I'd like to work with a while before giving up.

Homer
In reply to Homer White

Re: Setting up External Client

by Michael Gage -
XMLRPC::Lite is part of the general SOAP::Lite installation.  I think if you ask for XMLRPC you automatically get the whole package.  

The error when trying to authenticate is probably because you were using the old scripts.  One thing to pay attention to is that the old scripts use the key  password="..."  while the new scripts use the key  course_password="...".  (There is also a site_password which doesn't do much at the moment but may be useful later to prevent DNS exploits. ) 

Let us know if the sendXMLRPC.pl works.  It has better instructions than the old scripts.  Those are already housed in a directory called "old" and will eventually go away completely.