> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-admin/embed-and-extend-pentaho-functionality-cp/embed-reporting-functionality/advanced-topics.md).

# Advanced topics on embedding reporting

The following topics help to extend your knowledge of embedding reporting functionality beyond basic setup and use:

* [JAR reference](/pdia-admin/embed-and-extend-pentaho-functionality-cp/embed-reporting-functionality/advanced-topics/jar-reference.md)

  Review a list of the Pentaho-authored and third-party JARs that make up the Pentaho Reporting SDK.
* [Source code links](/pdia-admin/embed-and-extend-pentaho-functionality-cp/embed-reporting-functionality/advanced-topics/source-code-links.md)

  Review a list of individual and modular projects for Pentaho Reporting.
* [Sample 3: Dynamically generated, JDBC input, swing output](/pdia-admin/embed-and-extend-pentaho-functionality-cp/embed-reporting-functionality/advanced-topics/sample-3-dynamically-generated-jdbc-input-swing-output.md)

  Use this sample to render a report in a Swing preview window.
* [Sample 4: Dynamically generated, JDBC input, Java servlet output](/pdia-admin/embed-and-extend-pentaho-functionality-cp/embed-reporting-functionality/advanced-topics/sample-4-dynamically-generated-jdbc-input-java-servlet-output.md)

  Use this sample to dynamically generate an HTML reports.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pdia-admin/embed-and-extend-pentaho-functionality-cp/embed-reporting-functionality/advanced-topics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.