Skip to main content

Install Self-Deployed runtime Public Preview

Use Self-deployed runtime approach when the SAP ECC system can't be accessed directly from Atlan Cloud. This service runs within your network perimeter and establishes secure outbound connections to Atlan, enabling metadata extraction without exposing your system to the Internet.

Prerequisites​

Before you begin, make sure you have:

System requirements​

SAP ECC App deployment requires specific hardware and operating system specifications to reliably connect to your SAP ECC system and extract metadata.

  • Hardware:
    • Instance type: t2.xlarge or equivalent
    • vCPUs: 4 minimum
    • RAM: 16 GB minimum
    • Disk space: 80 GB available
  • Supported Architectures: Atlan provides full multi-architecture support so the Apps runs seamlessly across modern environments.
    • amd64 (x86_64)
      • Standard Intel/AMD 64-bit processors
      • Works on most servers, cloud VMs, and developer machines
    • arm64 (AArch64)
      • Optimised for AWS Graviton, Apple Silicon (M1/M2/M3), and ARM servers
      • Great performance-per-watt and lower cloud cost

Deploy runtime​

Choose the deployment platform and perform corresponding steps

  1. Note the below placeholder values to deploy SAP ECC app:

    • Helm chart name - {app-package-name} → saperp-app
    • Required only in case of using a Private Image Repository:
      • Image name - {app-image-name} → atlan-saperp-app
      • Image tag - {app-image-tag} → latest

  2. Follow the Docker Compose deployment guide, substituting SAP ECC values provided in the step 1.

Next steps​

  • Crawl SAP ECC: Configure and run SAP ECC metadata extraction using Agent mode