lambda-report-gen

Lambda-Pentaho Integration

Overview

The Pentaho-Lambda Integration can be found in the pentaho-report-generator project. This project allows an AWS Lambda function to execute a Pentaho report in an S3 environment and depositing the report result to a parameterized S3 location.

Installation Instructions

Create the Lambda function

1. From the Lambda console, click the Create function button
2. Set the Runtime to Java 8
3. Upload the pentahosyncreporting-x.x.x.jar file
4. Set the Handler to com.amazonaws.lambda.pentahoreporting.PentahoAsyncReportHandler
5. Create Environment variables as needed for the following:
   • prpt_s3_bucket: The S3 bucket where the report file (prpt) to be executed is stored
   • prpt_file: The name report file (and report properties file) to be executed, without the extension
   • output_type: pdf, excel, or html
   • output_s3_bucket: The destination S3 bucket for the report
   • output_file: The destination file name (without the extension)
   • use_cors: If you want to use CORS response headers enter true. It defaults to false.
   • cors_domain: If use_cors = true then this variable may contain the CORS domain. It defaults to "*".
6. Set the execution role
   • It will probably need to be custom
   • It will need the AWSLambdaBasicExecutionRole
   • It will need the AmazonS3FullAccess policy
   • If logging is desired, the CloudWatchLogsFullAccess policy will be needed
7. Ensure enough Memory is allocated to hold the entire final report, as it must be contained in memory before it can be saved back to the S3 environment
8. Click the Save button

Create the API Gateway

1. From the Triggers tag, click the Add trigger button
2. Select the API Gateway trigger type
   • Configure as appropriate for your uses
3. Select the function in the Resources column, a process flow should appear to the right
4. Open the Integration Request
5. Ensure Use Lambda Proxy integration is checked
6. Return to Method Execution and open the Method Request details
7. Add the following parameters, they don't need to be set required if the values are configured in the environment properties:
   • prpt_s3_bucket
   • prpt_file
   • output_type
   • output_s3_bucket
   • output_file
8. Configuration should be completed at this point

Usage

The four parameters set up when creating the API Gateway are the bare minimum required to run a report and are interpreted as follows:

• report - This is the name of the report to be executed. It must have a corresponding PRPT file in the s3_bucket Environment variable.
  • There may also be a properties file with the name of the report, which can be used to define data sources if they are not embedded in the prpt file; it should contain the following values
    • dataDriver - the java class that supports the database interface (i.e. com.mysql.jdbc.Driver)
    • dataUrl - the URL of the database to be used (this will be passed directly into the driver)
    • dataUser - the username to be used as part of the credentials
    • dataPassword - the password associated with dataUser
    • One or more entries mapping to named datasources in the report which are set to the SQL query to be used
    • One or more entries that start with "parm" and end with the name of a report parameter, the value of the parameter indicates what it should be converted to before being submitted to the report; these types are currently supported:
      • integer
      • double
• outputType - one of three values indicated the desired output for the report
  • pdf
  • html
  • excel
• folder - the S3 bucket where the final report will be created
• file - the name of the file to create the report as, including the extension

In addition to the four core parameters, any parameters required by the report itself should be included in the query string. These parameters will automatically be passed into the report when it is run.

An example of the parameters string could look something like this:

• ?report=customers&outputType=pdf&folder=mys3bucket&file=customers.pdf&lastName=Wilson