> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/start-here/systems-setup/sap-ase-server.md).
# SAP ASE Server
### How to Configure SAP ASE Database for Monitoring
1\. In the IT-Conductor main menu, navigate to **Dashboards > Administrator.**
2\. In the Administrator Dashboard, locate the ASE Servers panel and click 
to start adding a system to be monitored
3\. Before connecting to an ASE Server, please make sure that the following configuration parameters are properly configured.
> **Note** Please take note of the SAP ASE Configuration requirements.
4\. In the Create New ASE Server wizard, fill out all the necessary information. Once completed, click to add the system.
5\. A pop-up message will appear to confirm that the SAP ASE has been added successfully. Click **OK** to dismiss and proceed to configure the ASE Server user to be used for monitoring.
6\. Provide the new SAP Account information in the wizard and click **Finish** to complete the configuration.
7\. A pop-up message will appear to confirm that the JDBC DB account has been created successfully. Click **OK** to complete the process.
8\. The newly added server will appear in Server under the ASE Servers panel.
> **Note** It may take a few minutes to change the status to "In Progress," refresh the panel if needed. If there are issues with the configuration, such as wrong connection parameters or an invalid account etc. the status will stay "Ready", troubleshoot by displaying the log (click on  tools for the new record or click object icon and select Log from the menu popup)
9\. ASE System will show up in the service grid within 5-15 minutes.
### IT-Conductor SAP ASE Monitoring Configuration Requirement
Please create a dedicated ASE monitoring account for IT-Conductor. The account needs to be granted **mon\_role** role.
---
# 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.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/start-here/systems-setup/sap-ase-server.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.