> 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-04-optimize-a-java-based-kubernetes-application-online-boutique/aiab-04-create-the-system-and-its-components.md). # \[AIAB-04] Create the system and its components ### Create the System Duration: 02:00 To model the Online Boutique inside Akamas, we need to create a corresponding System with its components in Akamas, and also associate a Prometheus telemetry instance to the system to allow Akamas to collect the performance metrics. The entire Akamas system, together with the Prometheus telemetry instance, can be installed with a single command by leveraging the `create-system.sh` script provided in the `scripts` folder. This script requires, as an argument, the public IP address of the cluster `CLUSTER_IP`. Now you need to first login to Akamas with the following command: ```bash akamas login --user --password ``` and then run the above-mentioned script in a shell where you have the Akamas CLI installed: ```bash bash kubernetes-online-boutique/scripts/create-system.sh ``` The scripts should return a message similar to: `System created correctly`. At this point, you can access the Akamas UI under and verify that the System and its component are listed in the Systems menu:
Notice that this System leverages the following Optimization Packs: * Kubernetes: it provides a component type required to model each Kubernetes Pod - one for each Deployment in the Online Boutique. * Optimization Packs for Web Applications: it models the end-to-end metrics of the Online Boutique, such as the application response time and throughput. --- # 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-04-optimize-a-java-based-kubernetes-application-online-boutique/aiab-04-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 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.