Fullscreen
[Show/Hide Right Column]

Display remote information in JSON, YAML or SOAP XML format

Plugin Web Service

Web services consumption has been introduced in Tiki3.



1. Introduction

With this you can pull data from any JSON or SOAP enabled service, e.g. those from Yahoo:

File is not an image.


Parameters

Required parameters are in bold
Preferences required: wikiplugin_webservice
Parameters Accepted Values Description Default Since
url Complete service URL
service Registered service name.
template For use with registered services, name of the template to be used to display the service output. This parameter will be ignored if a body is provided.
bodyname word Name of the argument to send the body as for services with complex input. Named service required for this to be useful.
params Parameters formatted like a query : param1=value1&param2=value2.



1.1. WikiSyntax


The result is you can embed a webservice-specific plugin tag, with one named parameter
Picture 74.png (32.38 Kb)


And even change the output format by defining the format in a block after the tag:

Picture 75.png (75.49 Kb)


1.2. Administrator Setup

See Web Services for more information on the admin panel.

  1. Create a plugin alias to the webservices plugin

Picture 71.png (81.39 Kb)

  1. Name any fields
Picture 72.png (83.59 Kb)

  1. Code to format the webservice data goes into the Default Content field
Image

1.3. Fuller explanation movie

For a fuller explanation see the movie taken at WikiSym 2008



2. Why


This powerful plug-in allows you to bring external information in to Tiki easily. There are many contexts where existing legacy corporate systems or remote web sites contain useful information. This plug-in will allow you to display the information from these systems inside Tiki. It will allow administrators to set up information sources as easy and safe to use pre-configured wiki page plug-ins.

A good examples of this are:
  • Including bug tracking information from an external source (such as Bugzilla) in documentation pages.
  • Showing the results of images searches in xxx where the results are automatically refreshed.
  • More examples ...

For a list of some of the web based information sources available have a look at, put URL here.

3. How


The Webservice plug-in consumes content from remote sites and customizes the way it is displayed. It was added in Tiki 3.0.


  • The remote site must export the data in either JSON or YAML, or XML using SOAP.
  • The data must be publicly available as no authentication methods are currently supported.

There are multiple ways to display the information are supported, with various security and portability concerns.
  1. Self-contained, all inline in a page
  2. Defined (by an administrator) as a webservice
  3. Defined (by an administrator) using a plugin alias.

In Tiki 3.0 final release the web service plugin is disabled by default. Also it is marked as unsafe, which means any use or modification requires validation by an administrator or a moderator with the required privileges.

3.1. Output types

The output can generate:
  • Smarty to generate wiki syntax
  • Smarty to generate HTML
  • Javascript to generate HTML

The most basic, and safest, way to display is to use Smarty templates to generate wiki syntax but using Smarty to generate HTML affords more flexibility.

3.2. Hello, World: Yahoo's Madonna Example

The following is the result set from the Madonna example on http://developer.yahoo.com/javascript/json.html

Yahoo's Madonna Example
{"ResultSet":{
  "totalResultsAvailable":"229307",
  "totalResultsReturned":"2",
  "firstResultPosition":"1",
  "Result":[
    {
      "Title":"madonna 116",
      "Summary":"Picture 116 of 184",
      "Url":"http:\/\/www.celebritypicturesarchive.com\/pictures\/m\/madonna\/madonna-116.jpg",
      "ClickUrl":"http:\/\/www.celebritypicturesarchive.com\/pictures\/m\/madonna\/madonna-116.jpg",
      "RefererUrl":"http:\/\/www.celebritypicturesarchive.com\/pgs\/m\/Madonna\/Madonna%20picture_116.htm",
      "FileSize":"36990",
      "FileFormat":"jpeg",
      "Height":"530",
      "Width":"425",
      "Thumbnail":{
        "Url":"http:\/\/scd.mm-b1.yimg.com\/image\/481989943",
        "Height":"125",
        "Width":"100"
       }
    },
    {
      "Title":"madonna 118",
      "Summary":"Picture 118 of 184",
...
      }
    }
  ]
}
}


If all is well with your installation, the following should display as below it:
Simple webservice to format it
{WEBSERVICE(url="http://search.yahooapis.com/ImageSearchService/V1/imageSearch?appid=YahooDemo&query=Madonna&output=json")}
||
Total Results Available|{{$response.ResultSet.totalResultsAvailable}}
Total Results Returned|{{$response.ResultSet.totalResultsReturned}}
||
{{foreach from=$response.ResultSet.Result item=result}}
* Title {{$result.Title}}
{{/foreach}}
{WEBSERVICE}


Result:
Picture 79.png (20.59 Kb)

Note:
  • In Tiki 3.0 there was a fault in the template code meaning the above example would fail. Versions after r19669 have this fixed.


3.3. Fuller Example

Note: this isn't such a good example because it doesn't work out of the box: you'll have to find your own bugzilla instance.

Self-contained in-line example to fetch and display information from Bugzilla
{WEBSERVICE(url=http://bugzilla.example.com/bugexport.pl?id=00002345)}
!! {{$response.title}}
||ID|[http://bugzilla.example.com/bug/{{$response.id|escape|'url'}}|{{$response.id}}]
Status|{{$response.status}}
Assignee|{{$response.assignee.full_name}}
Open Date|{{$response.open_date}}
Last Modification|{{$response.last_modif}}
||

{{foreach from=$response.comments item=comment}}
* [http://bugzilla.example.com/bug/{{$response.id|escape|'url'}}#{{$comment.id}}|{{$comment.title}}] by ''{{$comment.author.full_name}}'' on {{$comment.date}}
{{/foreach}}
{WEBSERVICE}



3.4. Registering a Webservice


To use higher capabilities, such as HTML generation, a web service must be registered. A registered web service contains:
  • A name
  • A URL with parameters
  • A type (REST / SOAP)
  • A list of available templates

A template contains:
  • A name
  • The output format (use value tikiwiki or html)
  • The engine used to execute the template ( smarty or javascript )
  • The content of the template (this is not a content or smarty template, this template is defined where you register the webservice.)

When the output of Smarty is Tiki syntax, Smarty elements use double curly braces rather than single ones to avoid conflicts with the syntax.


To register web services, visit tiki-admin.php?page=webservices on your tiki installation.(this is also where you define the body of the template used, you cannot reference an allready defined content template)


A registered web service can be called using:

Registered plugin
{WEBSERVICE(service=bugzilla,template=complete,id=00002345)/}


3.5. Bundling the webservice in a Plugin Alias


A Plugin Alias can be created to hide complexity by making the web service aspects transparent. The end user sees it as a normal plugin but internally, it's only a reserved name. When encountered, the parameters provided to it are forwarded to an other plugin. Default values can be provided in the process.

For example, a BUGZILLA plugin could be created to access the bug information. This plugin would:
  • Redirect to the WEBSERVICE plugin
  • Always use bugzilla as the service
  • Accept a required id parameter which would be passed directly to WEBSERVICE
  • Accept an optional template parameter, which would provide the required documentation to indicate the supported templates (ex: status|link|short|complete). If not provided, it would use complete as the default value.
  • Ignore any user input in the body
  • Require no validation because all parameters are safe.

Sample usage
{BUGZILLA(id=00002345)/}

{BUGZILLA(id=00002345,template=short)/}


Plugin Alias can be used for other purposes than web services, like shortcut plugins to various tracker lists and item configurations.

To register plugin aliases, visit tiki-admin.php?page=plugins on your tiki installation.




3.6. Implementation notes

  • Other scripting languages or templating engines could be added. However, because Tiki is already bundled with Smarty, it was a natural choice.

4. Security


When including content from remote sites, the primary issue is that to get any kind of special formatting, the content from the remote host must be provided as HTML. One one side, HTML is difficult to manipulate and can hardly be included seamlessly inside the page. Content will always appear to be different. On the other hand, the consumer becomes vulnerable to XSS attacks because unwanted JavaScript may be included in the remote HTML.

The webservice strategy mitigates this risk by applying an age-old concept: separate data from presentation. The web services only request the data from the remote host and nothing of the presentation aspects. The consumer side is responsible to display the information using their preferred display method. In the case of Tiki, Smarty is default option. Before being sent to the template engine, the received data is filtered to avoid XSS coming from the data. The presentation layer is assumed to be audited and safe.

5. Presentation Suggestion


Even if security has to be insured, the remote host still is likely to know best how the content should be presented. Providers are encouraged to provide suggested templates to render the data. These templates can be audited by the site administrator to be used directly or serve as a sample to build custom templates.

The templates are to be provided as part of the body under the _template property.

The webservice registry presents the suggestions proposed by the remote hosts. These suggestions can be registered as valid templates.

Aliases
Plugin Webservice | Plugin Web Services | PluginWebServices

Contributors to this page: Merbster350 điểm  , luciash d' being2160 points  , lindon132 points  , Marc Laporte9140 points  , kebel220 Punkte  , xavi67871 points  and mrjcleaver1923 points  .
Page last modified on Thursday 28 July, 2011 08:58:39 UTC by Merbster350 điểm .
The content on this page is licensed under the terms of the Creative Commons Attribution-ShareAlike License.

Site Language

Reference Guide

Keywords

These keywords serve as "hubs" for navigation within the Tiki documentation. They correspond to development keywords (bug reports and feature requests):



Tiki Newsletter

Delivered fresh to your email inbox!
Newsletter subscribe icon
Don't miss major announcements and other news!
Contribute to Tiki