10.9 Building Your Report

Before you deploy your report, you need to build it. The source of the report is a set of properties, images, and the JRXML file. You must bundle these files into a report archive before you can deploy the report template.

The process of building the report archive creates an RPZ file. This is a report definition archive containing your report and the report metadata. There might also be additional files such as images or properties that your report depends on.

  1. Select Build in the left-navigation menu in the Report Packaging Tool.

  2. On the Build Report screen, specify the report definition.

    This is the JRXML file generated when you created your report.

  3. Specify the location of your report archive.

  4. Select the type of report.

  5. Select the template to use for the report header and footer.

  6. (Optional) Select to build the report using data source constraints, and then click Next.

    Data source constraints declare the tables, views, and databases that the report requires to run successfully and allow the Reporting Module to inform the user that a target data source does not have the required schema to run the report successfully. Data source constraints are not required.

    You can also specify SQL test constraints that test whether a report and data source are compatible beyond simply checking for the required views and tables. For example, you can check that a required function or columns in a table exist.

  7. (Conditional) Select the type of constraint to add, then specify the constraint name and schema name, if required.

    The schema name is optional for tables and views, and required for databases.

    For example, if a report requires the idmrpt_role_v view in the idm_rpt_cfg schema, select the View type, enter idmrpt_role_v for the name, and enter idm_rpt_cfg for the schema.

  8. (Optional) Add SQL test constraints.

    Provide a syntactically correct SQL statement and, optionally, the expected result. For example, to verify that the identity_cleanup function exists, enter the following SQL statement:

    SELECT routine_name FROM Information_schema.Routines WHERE

    Specific_schema = 'public'

    AND routine_name = 'identity_cleanup'

    AND Routine_type = 'FUNCTION'

  9. Click the Build button to build the RPZ file for your report definition.

After you have built your report, you must import the report in order to use the report. For more information, see Section 6.0, Using the Import Tool.