## Crawl SAP ASE

URL: https://docs.atlan.com/apps/connectors/database/sap-ase/how-tos/crawl-sap-ase

> Extract metadata from SAP ASE to catalog databases, schemas, tables, views, columns, stored procedures, and functions in Atlan.

Extract metadata from your SAP ASE (Adaptive Server Enterprise) instance into Atlan to catalog databases, schemas, tables, views, columns, stored procedures, and functions. Atlan also generates lineage from view, stored procedure, and function definitions.

## Prerequisites

Before you begin, make sure you have:

* Configured [SAP ASE user permissions](https://docs.atlan.com/llms/connectors/sap-ase/set-up-sap-ase/llms.txt) with catalog read access
* SAP ASE connection details (host, port, credentials, default database)
* Reviewed the [order of operations](https://docs.atlan.com/llms/catalog/connector-capabilities/order-workflows/llms.txt) for workflow execution

## Create crawler workflow

Create a new SAP ASE crawler workflow in Atlan by selecting the SAP ASE connector package, configuring your extraction method and connection details, and running the crawler to extract metadata.

1. In your Atlan workspace, click **Connectors** in the left sidebar.
 * If you are using the **Old UI (Classic)**, click **New Workflow** in the top navigation.

2. Click **Marketplace**.

3. Search for **SAP ASE Assets** and select it.

4. Click **Install**.

5. Once installation completes, click **Setup Workflow** on the same tile.

### Configure extraction

Select your extraction method and provide the connection details.

### Direct

In **Direct** extraction, Atlan connects to your SAP ASE server and crawls metadata directly.

1. For **Host**, enter the hostname or IP address of your SAP ASE server.

2. For **Port**, enter the port number for your SAP ASE server (default: 5000).

3. For **Username**, enter the username you [created during setup](https://docs.atlan.com/llms/connectors/sap-ase/set-up-sap-ase/llms.txt).

4. For **Password**, enter the password for the username.

5. For **Database**, enter the default database to connect to (default: `master`).

6. If your server requires encrypted connections, set **Enable SSL/TLS** to **Enabled**:
 * For **SSL Truststore File**, upload the JKS or PKCS12 truststore you [prepared during setup](https://docs.atlan.com/llms/connectors/sap-ase/set-up-sap-ase/llms.txt).
 * For **Truststore Password**, enter the truststore password. Leave it empty if the truststore has no password.
 * For **Truststore Type**, select **JKS** or **PKCS12**.

7. Click **Test Authentication** to confirm connectivity to SAP ASE.

8. Once authentication is successful, navigate to the bottom of the screen and click **Next**.

### Agent

In **Agent** extraction, Self-Deployed Runtime executes metadata extraction within your organization's environment.

1. Install Self-Deployed Runtime if you haven't already:
 - [Install via Docker Compose](https://docs.atlan.com/llms/platform/self-deployed-runtime/install-on-docker-compose/llms.txt)
 - [Install on Kubernetes](https://docs.atlan.com/llms/platform/self-deployed-runtime/install-on-kubernetes/llms.txt)

2. Select the **Agent** tab.

3. Store sensitive information, such as the username and password, in the secret store configured with the Self-Deployed Runtime and reference the secret keys in the corresponding fields. For more information, see [Configure workflow for SDR mode of execution](https://docs.atlan.com/llms/platform/self-deployed-runtime/configure-workflow-execution/llms.txt).

4. If your server requires encrypted connections, set **Enable SSL/TLS** to **Enabled**:
 * For **SSL Truststore File**, reference the truststore instead of uploading it - provide either an object store key in your deployment bucket (for example, `objectstore://path/to/truststore.jks`) or a secret store path whose value is the base64-encoded truststore. For more information, see [Configure file inputs for workflow execution](https://docs.atlan.com/llms/platform/self-deployed-runtime/configure-workflow-execution/llms.txt).
 * For **Truststore Password**, reference the secret store path whose value is the truststore password. Leave it empty if the truststore has no password.
 * For **Truststore Type**, select **JKS** or **PKCS12**.

5. For details on the remaining fields, refer to the Direct extraction tab.

6. Click **Next** after completing the configuration.

### Configure connection

Set up the connection name and access controls for your SAP ASE data source in Atlan.

1. Provide a **Connection Name** that represents your source environment. For example, you might use values like `production`, `development`, `gold`, or `analytics`.

2. To change the users able to manage this connection, update the users or groups listed under **Connection Admins**. If you don't specify any user or group, nobody can manage the connection, including admins.

3. Click **Next** at the bottom of the screen.

### Configure crawler

Configure which databases and schemas to include or exclude. If an asset appears in both filters, the exclude filter takes precedence. System databases (`master`, `tempdb`, `model`, `sybsystemprocs`, `sybsecurity`, `dbccdb`, `sybmgmtdb`, `sybpcidb`, `sybsystemdb`) are excluded automatically.

### Direct

1. To select specific databases and schemas for crawling, click **Include Metadata**. By default, all assets are included.

2. To exclude specific databases and schemas from crawling, click **Exclude Metadata**. By default, no assets are excluded.

### Agent

In Agent extraction, provide the include and exclude filters as a JSON map of database-name patterns to a list of schema patterns. An empty list selects the whole database.

1. For **Include Databases**, enter the databases and schemas to include. For example, `{"^FINANCE$": []}` includes the entire `FINANCE` database. By default, all assets are included.

2. For **Exclude Databases**, enter the databases and schemas to exclude. By default, no assets are excluded.

### Run crawler

### Direct

1. To verify [permissions and configuration](https://docs.atlan.com/llms/connectors/sap-ase/preflight-checks-for-sap-ase/llms.txt) before running, click **Preflight checks**.

2. Choose your run option:
 - To run the crawler once immediately, click **Run** at the bottom of the screen.
 - To schedule the crawler to run hourly, daily, weekly, or monthly, click **Schedule Run** at the bottom of the screen.

### Agent

Choose your run option:

- To run the crawler once immediately, click **Run** at the bottom of the screen.
- To schedule the crawler to run hourly, daily, weekly, or monthly, click **Schedule Run** at the bottom of the screen.

Once the crawler completes, you can view the assets in Atlan's asset page.

## See also

* [How Atlan connects to SAP ASE](https://docs.atlan.com/llms/connectors/sap-ase/how-atlan-connects-to-sap-ase/llms.txt): Connectivity, authentication, and data access patterns
* [What does Atlan crawl from SAP ASE](https://docs.atlan.com/llms/connectors/sap-ase/what-does-atlan-crawl-from-sap-ase/llms.txt): Complete reference of assets and metadata discovered during crawling
* [Preflight checks for SAP ASE](https://docs.atlan.com/llms/connectors/sap-ase/preflight-checks-for-sap-ase/llms.txt): Validation checks for permissions and configuration before running the crawler

---