Server API

The key concept in REST is the idea that each resource should have a unique global identifier and that operations can be applied to the resource through a set of well-defined operations (GET,POST,PUT and DELETE). In Elixir Repertoire, this means that each repository file and folder, user, group, report,datasource, target, even log, all have distinct identifiers - URLs - that allow direct interaction. For example, creating a new user called bill can be done through the Web Interface with your browser, as described previously, but can just as easily be done by sending a PUT request to the URL /user/bill.Similarly, accessing a server log is as simple as sending a GET request to /log/file/server.log. You can integrate that log into a portal if you choose, or maybe write a utility to scan the log for specific tasks you are monitoring.

Here's a few examples of accessing resources on a Repertoire Server.

To render a report template ( CustomerListing^? ) to output PDF.
- http://localhost:8080/report/ElixirSamples/Report/CustomerListing.rml?mime-type=application/pdf
To render a report template ( CustomerListing^? ) to Ms Excel
- http://localhost:8080/report/ElixirSamples/Report/CustomerListing.rml?mime-type=application/vnd.ms-excel

To render a datasource
- http://localhost:8080/data/ElixirSamples/DataSource/ChartData.ds

Client API

Elixir Repertoire server provides a set of Java standalone client APIs for connection to the server. This API allows you to trigger all the report-related or ETL functionalities. Access to the functionality is controlled by the Server license. The report-related functionality allows listing of reports deployed on the server repository, extracting dynamic parameters in the report and generating reports. The ETL functionality allow you to access data generation and DataStore^? functions.

This client library may be deployed as part of a J2EE solution.

The detailed version of the Java API documentation is shipped with the server.

Version 7.1

• Repertoire Client for Java 5 and above Environment -

• Repertoire Client for Java 1.4 Environment -

Version 7.0.1

• Repertoire Client for Java 5 and above Environment

The JAR files is located at Repertoire-Server-7.0.1\RepertoireServer\clients\lib

• • Glint.jar
  • log4j.jar
  • RepertoireClient.jar

Known Issues

Version 7.1.0

• ERSClient does not allow large JSON parameter to be passed.
  

Version 7.0.1

• A renderReport() API Call followed by a getParameter() API call will cause the server to remember the previous parameter name and subsequent getParameter Calls will not be able to work correctly. The server remembers the parameters already passed in, so it doesn't ask for any more
• IJobInfo.JOB_RECEIVED - The correct value is not returned
• IJobInfo.JOB_STARTED - The correct value is not returned

-- IrwinTan - 25 Aug 2007