6 min read
Over 70 recipes for implementing the most important functionalities of Alfresco
You all know about Web Services – which took the web development world by storm a few years ago. Web Services have been instrumental in constructing Web APIs (Application Programming Interface) and making the web applications work as Service-Oriented Architecture. In the new Web 2.0 world, however, many criticisms arose around traditional Web Services – thus RESTful services came into the picture. REST (Representational State Transfer) attempts to expose the APIs using HTTP or similar protocol and interfaces using well-known, light-weight and standard methods such as GET, POST, PUT, DELETE, and so on.
Alfresco Web Scripts provide RESTful APIs of the repository services and functions. Traditionally, ECM systems have been exposing the interfaces using RPC (Remote Procedure Call) – but gradually it turned out that RPC-based APIs are not particularly suitable in the wide Internet arena where multiple environments and technologies reside together and talk seamlessly. In the case of Web Scripts, the RESTful services overcome all these problems and integration with an ECM repository has never been so easy and secure. Alfresco Web Scripts were introduced in 2006 and since then it has been quite popular with the developer and system integrator community for implementing services on top of the Alfresco repository and to amalgamate Alfresco with any other system.
What is a Web Script?
For example, the http://localhost:8080/alfresco/service/api/search/person.html ?q=admin&p=1&c=10 URL will invoke the search service and return the output in HTML.
All the Web Scripts are exposed as services and are generally prefixed with http://>/>/>. In a standard scenario, this is http://localhost:8080/alfresco/service
Web Script architecture
Alfresco Web Scripts strictly follow the MVC architecture.
- View: Written using Freemarker templates, you implement exactly what you want to return in your Web Script. For data Web Scripts you construct your JSON or XML data using the template; and for presentation Web Scripts you build your output HTML. The view can be implemented using Freemarker templates, or using Java-backed Web Script classes.
Types of Web Scripts
Depending on the purpose and output, Web Scripts can be categorized in two types:
- Data Web Scripts: These Web Scripts mostly return data in plenty after processing of business requirements. Such Web Scripts are mostly used to retrieve, update, and create content in the repository or query the repository.
- Presentation Web Scripts: When you want to build a user interface using Web Scripts, you use these Web Scripts. They mostly return HTML output. Such Web Scripts are mostly used for creating dashlets in Alfresco Explorer or Alfresco Share or for creating JSR-168 portlets.
Note that this categorization of Web Script is not technically different—it is just a logical separation. This means data Web Scripts and presentation Web Scripts are not technically dissimilar, only usage and purpose is different.
Web Script files
Defining and creating a Web Script in Alfresco requires creating certain files in particular folders. These files are:
- Web Script Descriptor: The descriptor is an XML file used to define the Web Script – the name of the script, the URL(s) on which the script can be invoked, the authentication mechanism of the script and so on. The name of the descriptor file should be of the form: >.>. desc.xml; for example, helloworld.get.desc.xml.
- Freemarker Template Response file(s) optional: The Freemarker Template output file(s) is the FTL file which is returned as the result of the Web Script. The name of the template files should be of the form: <
>.>.>.ftl; for example, helloworld.get.html.ftl and helloworld.get.json.ftl.
- Configuration file (optional): You can optionally include a configuration XML file. The name of the file should be of the form: >.>.config.xml; for example, helloworld.get.config.js.
- Resource Bundle file (optional): These are standard message bundle files that can be used for making Web Script responses localized. The name of message files would be of the form: >.>.properties; for example, helloworld.get.properties.
The naming conventions of Web Script files are fixed – they follow particular semantics.
Alfresco, by default, has provided a quite rich list of built-in Web Scripts which can be found in the tomcatwebappsalfrescoWEB-INFclassesalfrescotemplateswebscriptsorgalfresco folder. There are a few locations where you can store your Web Scripts.
- Classpath folder: tomcatwebappsalfrescoWEB-INFclassesalfrescotemplateswebscripts
- Classpath folder (extension): tomcatwebappsalfrescoWEB-INFclassesalfrescoextensiontemplateswebscripts
- Repository folder: /Company Home/Data Dictionary/Web Scripts
- Repository folder (extension): /Company Home/Data Dictionary/Web Scripts Extensions
It is not advised to keep your Web Scripts in the orgalfresco folder; this folder is reserved for Alfresco default Web Scripts. Create your own folders instead. Or better, you should create your Web Scripts in the extension folders.
Web Script parameters
You of course need to pass some parameters to your Web Script and execute your business implementations around that.
You can pass parameters by query string for the GET Web Scripts. For example:
In this script, we have passed three parameters – q (for the search query), p (for the page index), and c (for the number of items per page). You can also pass parameters bound in HTML form data in the case of POST Web Scripts. One example of such Web Script is to upload a file using Web Script.