> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/system/configuration/activating-the-configuration.md).

# Activating the Configuration

> **Applies to:** Tmedia 3.0, 3.2, 3.3; SBC 3.1, 3.3

Changes made to the configurations are stored in the OAM\&P Configuration and Logging database. Any changes to the configuration must be activated, in order for them to be used by the system. This is done at the system level and accessed from the navigation panel.

Note: To activate a configuration, you must be an **Admin** user or a user with write access to the System menu.

To activate a system configuration:

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

![Systems Navigation Panel B](https://docs.telcobridges.com/w/images/3/38/Systems_Navigation_Panel_B.png)

2. To activate the configuration, click **Activate**.

**Note:** Make certain that the **Lock active configuration** box is **unchecked**. Failure to do so will prevent the configuration from being saved.

![Toolpack Editing System B1](https://docs.telcobridges.com/w/images/a/ae/Toolpack_Editing_System_B1.png)

3. Verify that an activation confirmation message is displayed. The system will remind you to back up your database when you are done configuring (at top of screen):

![Toolpack System Edited B2](https://docs.telcobridges.com/w/images/e/e5/Toolpack_System_Edited_B2.png)

<details>

<summary>Northbound Interface</summary>

**Path**

```
/systems/@[system_name]
```

**Parameters (text)**

```
/systems/@[system_name]
active_configuration           = "@[configuration_name]"
active_package                 = "@[package_name]"
gw_port                        = @[port_number]
lock_active_configuration      = false
migrate_database               = true
name                           = "@[system_name]"
target_configuration           = ""
target_package                 = ""
validate_configuration         = ""
validate_package               = ""
```

**Parameters (json)**

```
{
  "active_configuration" : "@[configuration_name]",
  "active_package" : "@[package_name]",
  "gw_port" : @[port_number],
  "lock_active_configuration" : false,
  "migrate_database" : true,
  "name" : "system_1",
  "target_configuration" : "",
  "target_package" : "",
  "validate_configuration" : "",
  "validate_package" : "",
}
```

</details>


---

# 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://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/system/configuration/activating-the-configuration.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.