> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/1-10-2/documentation/services/setting-up-and-configuring-services/installing-services.md).
# Installing Services
You can upload service commissioning files to Connectware to install services.
1. On the navigation panel, click **Services**.
2. Click **Upload Service** to add a new service commissioning file.
3. In the **Create Service** dialog, click **Choose File**.
4. In your file browser, select your service commissioning file and click **Open**.
5. The configuration of your service commissioning file are added to the **Configure the new service** section.
Optional:
* If your service commissioning file provides configurable parameters, you can here customize the values for your service. Depending on the service commissioning file, parameter descriptions and default values may be available.
* You can click **Click to see commissioning file** to review your service commissioning file.
6. Once you are finished, click **Install** to install the services.
7. Upon successful configuration, your new service will appear in the service list. Initially, the services has the status **Disabled**.
8. After installing services, you must enable them. For more details, see [Enabling Services](/1-10-2/documentation/services/setting-up-and-configuring-services/enabling-services.md).
---
# 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.cybus.io/1-10-2/documentation/services/setting-up-and-configuring-services/installing-services.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.
