> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/other-pages/applications/starting-an-application.md).

# Starting an Application

#### ***Applies to version(s): v2.7, v2.8.***

In order to be able to load and start an application, it will need to have been installed on the Toolpack application server. In addition, at least one Tmedia unit must have been configured on the Toolpack application server so that you are able to connect to it.

When you first log on to the Web Portal, your system application will have been installed on the Toolpack application server, and it will be in a management state. This means that the application is not yet operating and controlling your system. In order to start an application, its state must be changed from Management to Run.

**To start an application:**

1. Select **Applications** from the navigation panel.

![Toolpack v2.7 Navigation Panel Applications](https://docs.telcobridges.com/w/images/d/d2/Toolpack_v2.7_Navigation_Panel_Applications.png)

2. Click the **Status** tab. Select the application that you wish to start/stop and click on its name.

![Toolpack v2.7 Edit Application](https://docs.telcobridges.com/w/images/6/60/Toolpack_v2.7_Edit_Application.png)

3. Start/Stop the application:

* Set the **Oam target state** to **Run** or **Don't Run**.
* Click **Apply States**

![Toolpack v2.7 Editing Application State](https://docs.telcobridges.com/w/images/c/c0/Toolpack_v2.7_Editing_Application_State.png)


---

# 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://tmediadocs.telcobridges.com/other-pages/applications/starting-an-application.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.