Versions Compared

Old Version 1

changes.mady.by.user Former user

Saved on

compared with

New Version 2

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

This may be a matter of taste, but I set this in sakai.properties:

  1. Indicates whether or not we allow web-service logins
    webservices.allowlogin=true

One less file to change when upgrading.

Aaron Gerow
Example of a Perl script connecting to Sakaiscript:

Panel

Paul, our scripts bind to Axis something like this in Perl:

use SOAP::Lite;
...
my $loginURI = "https://sakai.plu.edu/sakai-axis/SakaiLogin.jws?wsdl";
my $scriptURI = "https://sakai.plu.edu/sakai-axis/SakaiScript.jws?wsdl";
($loginsoap = SOAP::Lite
-> proxy($loginURI)
-> uri($loginURI));
$session = $loginsoap->login($app_user, $app_password)->result;
$scriptsoap = SOAP::Lite
-> proxy($scriptURI)
-> uri($scriptURI));
...
$scriptsoap->addNewSite($session, $siteid, $title,
$desc, $sdesc, $icon_url,
"", $false, $JOIN_ROLE, $false,
$false, "", $SITE_TYPE);
...

Notice the first two URIs. I had some trouble with our dev-box that was
worked around by binding to something like
'http://sakai.plu.edu:8080/...'. Notice this isn't SSL, and goes
directly to Tomcat (no Apache). Another little check is to browse to
something like https://sakai.plu.edu/sakai-axis/SakaiScript.jws and see
what Axis gives you. Upon clicking the link at that page you should get
some WSDL-style XML. If not, you might check out Apache or permissions
of the jws files. Here you might also get a sort of syntax error if
SakaiScript.jws is in bad shape.