> For the complete documentation index, see [llms.txt](https://docs.akamas.io/quick-guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akamas.io/quick-guides/quick-guides-akamas-in-a-box/aiab-03-optimize-a-java-based-application-konakart-with-lre.md).

# \[AIAB-03] Optimize a Java-based application (Konakart) with LRE

In this guide, you'll learn how to optimize [Konakart](https://konakart.com), a real-world Java-based e-commerce application, by leveraging Micro Focus LoadRunner Enterprise performance testing tool and Prometheus monitoring tool.

Please refer to this knowledge base article on how to set up a Konakart test environment and to this page on how to integrate LoadRunner Enterprise with Akamas.

#### **What you'll learn** <a href="#user-content-what-youll-learn" id="user-content-what-youll-learn"></a>

* How to optimize a real-world Java application with Akamas in a realistic performance environment
* How to integrate the Prometheus monitoring tool with Akamas
* How to automate the configuration of the parameters in a containerized Java application
* How to conduct an optimization with performance constraints
* How to analyze and identify performance insights from study results

#### What you'll need

* An Akamas-in-a-box instance installed with a valid license - see the Akamas In a Box guide.
* The Konakart performance environment - see the Konakart setup guide.
* A working LoadRunner Enterprise installation


---

# 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.akamas.io/quick-guides/quick-guides-akamas-in-a-box/aiab-03-optimize-a-java-based-application-konakart-with-lre.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.
