# Customization nodes

{% hint style="warning" %}
**Limited Support/End of Life Capabilities**

If you need to request a hotfix or support for these features, please contact [<mark style="color:blue;">**Alemba Support**</mark>](https://alemba.help/production/Portal.aspx)
{% endhint %}

Under every system within the Server Console is a list of tree nodes which allow you to perform various activities. Most of these activities are to do with customizing your installation of ASM Core to meet your specific organizational requirements.

Often, changes made within these nodes must be done in tandem with configuring ASM Core through the Administration module.

This topic will cover the purpose of these nodes but will not go into to detail on how to create the customizations. Additional documentation is available which provides details on configuring and customizing the application. This is referenced as required.

### Configuration Files

Select **Configuration Files** to list all configuration files stored within the main ASM Core directory.&#x20;

The default path for this directory is the following:

Program Files (x86)\Alemba\ASM\\\<system>\Config where \<system> is the system name.

The following files are important when customizations are in place:

| \*.SQL                                    | SQL Query Files                                                                                                                                                                   |
| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| PARSED\_QUERIES.SQP                       | Parsed SQL Query Files                                                                                                                                                            |
| \*.SCP                                    | SQL Script Files                                                                                                                                                                  |
| \*.ICNF                                   | Federated CMDB Connector Configuration Files                                                                                                                                      |
| \*.LDAP                                   | LDAP Query Files                                                                                                                                                                  |
| \*.MOM                                    | Microsoft Operations Manager (MOM) Integration Configuration File                                                                                                                 |
| <mark style="color:yellow;">\*.INI</mark> | SQL Initialization Files For more information on the handling of these files during database upgrades, patch applications and when parsed, see Server Console: Updating Scripts . |

### Letters

Select **Letters** <mark style="color:yellow;">\*where?\*</mark> to view Microsoft Word templates used by ASM Core to generate letters from Calls, Requests and Tasks. These letters merge information contained within the call, request or task into the letter content based on a template. These letters are then saved against the record.&#x20;

Three standard Microsoft Word templates are provided:  <mark style="color:yellow;">\*version of word?\*</mark>

* Calls = C\_ServiceManager.doc
* Requests = R\_ServiceManager.doc
* Tasks = T\_ServiceManager.doc

These templates can be accessed from under the **Letters** node of the Server Console. They can be copied and edited to make additional letter templates available, but they must be saved to this same location.

There is more information on creating and editing letter templates <mark style="color:yellow;">**here**</mark><mark style="color:yellow;">.</mark>

### Knowledge Files

Select **Knowledge Files** <mark style="color:yellow;">\*where?\*</mark>to list all documents stored within the Knowledge Bank directory.&#x20;

The default path for this directory is the following:

**Program Files (x86)\Alemba\ASM\\\<system>\Knowledge** where \<system> is the system name.

This directory is indexed by the Knowledge Bank functionality to allow Knowledge Searches on the contents of these documents in ASM Core, and the Self Service Portal if they're published to portal.

You cannot add, edit or delete displayed documents in the Server Console.

For more information on creating and editing knowledge entries refer to <mark style="color:yellow;">**Knowledge Bank.**</mark>

### Log files

Select **Log Files** <mark style="color:yellow;">\*where?\*</mark>to view log files generated by actions within the Server Console. These actions include:

* Calls archived
* Template imports and exports
* Database upgrades
* Custom SQL scripts run

#### When are log files generated?

Log files are written at the beginning of a database upgrade or when a script is run. For each query, the log file records the following:

* Date and time stamp to indicate when the query was executed
* Time taken (in milliseconds) to execute the query.

<mark style="color:yellow;">\*Where are they held?\*</mark>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.alemba.com/asm-hermes/setup-and-configure-asm/faq/limited-support-end-of-life-capabilities/server-console/customization-nodes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.