> 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-02-optimize-a-java-based-application-konakart-with-jmeter/aiab-02-create-the-system-and-its-components.md).
# \[AIAB-02] Create the system and its components
Akamas provides an out-of-the-box optimization pack called Web Application that comes very handy for modeling typical web applications, as it includes metrics such as `transactions_throughput` and `transaction_response_time` which you will use in this guide to define the optimization goal and analyze the optimization results. These metrics will be gathered from JMeter, thanks to Akamas out-of-the-box Prometheus telemetry provider.
Let's create the system and its components.
The file `system.yaml` contains the following definition for our system:
```yaml
name: konakart
description: The konakart eCommerce shop
```
Run the command to create it:
```bash
akamas create system system.yaml
```
Now, install the Web Application optimization pack from the UI:
Akamas provides an out-of-the-box optimization pack called Web Application that comes very handy for modeling typical web applications, as it includes metrics such as `transactions_throughput` and `transaction_response_time` which you will use in this guide to define the optimization goal and analyze the optimization results. These metrics will be gathered from JMeter, thanks to Akamas out-of-the-box Prometheus telemetry provider.
You can now create the component modeling of the Konakart web application.
The file `comp_konakart.yaml` defines the component as follows:
```yaml
name: konakart
description: The konakart web application
componentType: Web Application
properties:
prometheus:
instance: jmeter
job: jmeter
```
As you can see, this component contains some custom properties, *instance* and *job*, under the *prometheus* group. These properties are used by the Prometheus telemetry provider as values for the corresponding instance and job labels in the Prometheus queries to collect metrics for the correct entities. You will configure the Prometheus integration in the next sections.
You can now run the command to create the component:
```bash
akamas create component comp_konakart.yaml konakart
```
You can now explore the result of your system modeling in the UI. As you can see, your `konakart` component is now populated with all the typical metrics of a web application:
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.akamas.io/quick-guides/quick-guides-akamas-in-a-box/aiab-02-optimize-a-java-based-application-konakart-with-jmeter/aiab-02-create-the-system-and-its-components.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.