# Using Custom Server Profiles

This document explains how to manage Server Profiles in Astera. Server Profiles allow you to configure server behavior including maximum concurrent jobs, active server components, and event severity levels.

### Accessing Server Profiles

To access Server Profiles:

1. Go to *Server* in the menu bar.
2. Navigate to *Cluster > Server Profiles*.

This opens the *Server Profiles* window.

<figure><img src="https://3181888596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEifS4h8yurLAAwiGNX2%2Fuploads%2FtbzXhByxoP7MAbuRuvf4%2F01-server-profile-window.png?alt=media&#x26;token=2ccb0ac8-6ab6-4b54-a2f7-c54efaacfe69" alt="" width="563"><figcaption><p>01-server-profiles-window</p></figcaption></figure>

### Adding a Profile

1. In the Server Profiles window, click the *Add new server profile* <img src="https://3181888596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEifS4h8yurLAAwiGNX2%2Fuploads%2FJGZm0tzyL2IFMhEAtvCB%2Fimage.png?alt=media&#x26;token=19b354a8-a58a-41c6-a8d8-be31d5b5156b" alt="" data-size="line"> button in the toolbar.
2. A new profile is created with a default name.
3. The profile editor opens on the right side with two tabs: **Profile Settings** and **Publishing Settings**.

#### Profile Settings Tab

In this tab, you can configure the following options:

<table><thead><tr><th width="200.39996337890625">Option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Specify a unique name for the server profile.</td></tr><tr><td>Max Concurrent Jobs</td><td>Set the maximum number of jobs that can run concurrently (default: 5).</td></tr><tr><td>Event Severity</td><td>Select the minimum event severity level to record (Info, Warning, Error, or Critical). Server events are recorded based on this choice.</td></tr><tr><td>Active Components</td><td>Select which server components to enable. Components include Analytics, APIServiceAgent, Authorization, ClientHealthManager, ConfigUiSupport, DbAgent, EndpointManager, FailoverProcessor, FileDropListener, InProcJobManager, and othe</td></tr></tbody></table>

<figure><img src="https://3181888596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEifS4h8yurLAAwiGNX2%2Fuploads%2FIu0luwj2ghwewO8MLnxZ%2F02-profile-settings.png?alt=media&#x26;token=bcd91375-528d-49e8-bf12-f1e7833d5a2e" alt="" width="563"><figcaption><p>02-profile-settings-tab</p></figcaption></figure>

#### Publishing Settings Tab

This tab contains API and publishing-related configurations organized into the following sections:

<table data-header-hidden><thead><tr><th width="274.79998779296875">Section</th><th>Configurable Options</th></tr></thead><tbody><tr><td>API Runtime Caching Policy</td><td>Max Concurrent API Pipelines, Non-Paginated/Paginated Pipeline Cache Capacity, Cache Time-to-Live settings</td></tr><tr><td>API Runtime Logging and Tracing</td><td>Request Validator Traces, Processor Traces, Purge API Runtime Traces After (days)</td></tr><tr><td>API File Server Configuration</td><td>Enable File Uploads/Downloads, File Expiration Time, Directory Purge Frequency, Server File Directory</td></tr><tr><td>Service Type Configuration</td><td>Relay Server settings, Agent Server Name, Relay Server URI, Port, Timeout, Ping Delay</td></tr></tbody></table>

Click the *Save* <img src="https://3181888596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEifS4h8yurLAAwiGNX2%2Fuploads%2FH119AAMjBTb72Ssj0DqQ%2Fimage.png?alt=media&#x26;token=5ee072c5-2254-4d2d-94c0-385188c0608a" alt="" data-size="line"> button in the toolbar to save the profile.

<figure><img src="https://3181888596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEifS4h8yurLAAwiGNX2%2Fuploads%2FPjdHS3R8wXlGRj640YLs%2F03-publishing-settings-tab.png?alt=media&#x26;token=2c7e844a-d4cf-48ad-9062-f88476e645ba" alt="" width="563"><figcaption><p>03-publishing-settings-tab</p></figcaption></figure>

### Applying a Profile

To apply a profile to the server:

1. Go to *Server > Manage > Server Properties*.
2. This opens the *Server Properties* window. Here, navigate to the *Configuration Properties* tab
3. In the *Profile* dropdown, select the desired profile from the list.
4. Save the changes.

<figure><img src="https://3181888596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEifS4h8yurLAAwiGNX2%2Fuploads%2Fl7WOw4O3Vg4a2mHGKjKr%2Fimage.png?alt=media&#x26;token=845eae00-ac6b-485e-9635-f239daa4dc90" alt="" width="563"><figcaption><p>04-server-properties-window</p></figcaption></figure>

The selected profile's settings will now be applied to the server.

{% hint style="info" %}
**Note:** Switching between profiles requires a server restart. Ensure no critical jobs are running before applying a different profile.\
To restart server, go to *Services (in windows) > Restart Astera Integration Server.*
{% endhint %}