Module 2: SLT Installation and System Setup
This module covers the installation and initial setup of SAP Landscape Transformation (SLT). You'll learn system requirements, installation steps, and post-installation configuration.
1. System Landscape Overview
Before installation, understand the typical SLT system landscape.
1.1 Typical Architecture
graph TB
subgraph "Source System Layer"
A1[SAP ECC Production]
A2[S/4HANA System]
end
subgraph "SLT Layer"
B1[SLT Server<br/>ABAP Stack]
B2[SLT Database<br/>Logging Tables]
end
subgraph "Target System Layer"
C1[SAP HANA DB]
C2[BW/4HANA System]
end
A1 <-->|RFC| B1
A2 <-->|RFC| B1
B1 <--> B2
B1 -->|DB Client| C1
B1 -->|RFC| C2
style B1 fill:#667eea
style B2 fill:#764ba2
1.2 Deployment Options
| Option | Description | Use Case |
|---|---|---|
| Standalone Server | Dedicated SLT server | Production environments, high volume |
| Embedded in HANA | SLT on same server as HANA | Small to medium deployments |
| Cloud Deployment | SLT in SAP Cloud Platform | Hybrid scenarios, cloud targets |
| Multiple Instances | Multiple SLT servers | Load distribution, multiple sources |
2. System Requirements
2.1 Hardware Requirements
Minimum Requirements:
- CPU: 4 cores (8+ recommended)
- RAM: 8 GB (16-32 GB recommended)
- Disk: 100 GB minimum
- Network: 1 Gbps connection
Sizing Guidelines:
| Data Volume/Day | Tables | RAM | CPU | Disk Space |
|---|---|---|---|---|
| < 1 GB | < 100 | 8 GB | 4 cores | 100 GB |
| 1-10 GB | 100-500 | 16 GB | 8 cores | 200 GB |
| 10-50 GB | 500-1000 | 32 GB | 16 cores | 500 GB |
| > 50 GB | > 1000 | 64 GB | 32 cores | 1 TB+ |
Logging tables typically require 20-30% of the source data volume. Add buffer for peak loads and error scenarios.
2.2 Software Requirements
SLT Server:
- SAP NetWeaver 7.31 SP9 or higher
- SAP NetWeaver 7.4 SP5+ (recommended)
- SAP NetWeaver 7.5 SP0+ (latest features)
Supported Databases:
- SAP HANA (primary)
- Oracle 11g/12c
- IBM DB2 10.5+
- Microsoft SQL Server 2012+
Source Systems:
- SAP ECC 6.0 EHP4+
- SAP S/4HANA 1511+
- SAP BW 7.3+
- Non-SAP databases (with ODBC)
Target Systems:
- SAP HANA 1.0 SPS09+
- SAP HANA 2.0 (recommended)
- BW/4HANA 1.0+
- SAP Data Warehouse Cloud
3. Installation Process
3.1 Pre-Installation Checklist
Before starting installation:
✅ Infrastructure:
- Server provisioned with required specs
- Network connectivity verified
- Firewall rules configured
- DNS resolution working
✅ Software:
- SAP Software downloaded (SWDC)
- Database client installed
- Java Runtime Environment (JRE) installed
- SAPCAR extraction tool available
✅ Authorizations:
- OS administrator access
- Database administrator access
- SAP installation credentials
- License key obtained
✅ Documentation:
- Installation guide reviewed
- Network ports documented
- Naming conventions defined
- Backup strategy planned
3.2 Installation Steps
Step 1: Download SLT Software
Access SAP Software Download Center:
- Go to: https://support.sap.com/swdc
- Navigate to: Support Packages and Patches → By Alphabetical Index (A-Z) → L
- Select: SAP LANDSCAPE TRANSFORMATION
- Download latest version (e.g., SLT 3.0 SP15)
Required Components:
DMIS 2011 - Data Migration Server
└── DMIS 2011 SP15
├── Installation Export (DMIS2011_0_15.zip)
├── Installation Master (SWPM)
└── SAP Kernel (720_REL or higher)
Step 2: Extract Installation Media
# Extract using SAPCAR
cd /usr/sap/install/SLT
# Extract installation export
SAPCAR -xvf DMIS2011_0_15.SAR
# Extract SWPM (Software Provisioning Manager)
SAPCAR -xvf SWPM20SP04_0-80003424.SAR
# Extract kernel
SAPCAR -xvf SAPEXE_200-80002573.SAR -R ./kernel
Step 3: Run Software Provisioning Manager (SWPM)
Start SWPM:
cd /usr/sap/install/SWPM
./sapinst SAPINST_INPUT_PARAMETERS_URL=/tmp/params.properties
Select Installation Option:
- SAP NetWeaver 7.5
- Application Server ABAP
- Standard System
- SAP HANA Database
Installation Parameters:
| Parameter | Value | Notes |
|---|---|---|
| SID | SLT | System ID (3 characters) |
| Instance Number | 00 | Default instance |
| Master Password | ******** | Initial admin password |
| HANA Host | hana.company.com | Target HANA server |
| HANA Instance | 00 | HANA instance number |
| HANA DB Name | SLTDB | SLT database name |
Step 4: Installation Process Flow
sequenceDiagram
participant SWPM as SWPM Installer
participant OS as Operating System
participant DB as HANA Database
participant SLT as SLT Server
SWPM->>OS: Create OS users (sltadm, sapadm)
SWPM->>OS: Create directory structure
SWPM->>DB: Create database schema (SLTABAP)
SWPM->>DB: Load R/3 load data
SWPM->>SLT: Install ABAP stack
SWPM->>SLT: Install DMIS components
SLT->>SLT: Generate instance profile
SLT->>SLT: Start SAP system
SWPM->>SWPM: Complete installation
Installation Time: 2-4 hours (depending on hardware)
Step 5: Post-Installation Steps
1. Verify Installation:
# Check system processes
ps -ef | grep SLT
# Expected processes:
sltadm msg_server
sltadm dw.sap<SID>_DVEBMGS00
sltadm gwrd
sltadm icman
2. Verify Database Connection:
# Connect to HANA
hdbsql -n hana.company.com:30015 -u SLTABAP -p <password>
# Check schema
SELECT COUNT(*) FROM TABLES WHERE SCHEMA_NAME = 'SLTABAP';
3. Login to SLT System:
- Transaction:
SU01 - User:
SAP* - Password: Master password set during installation
- Client:
000
4. Post-Installation Configuration
4.1 System Administration Tasks
1. Change Default Passwords:
-- In transaction SU01, change passwords for:
SAP* -- Super admin
DDIC -- Data Dictionary user
SAPUSER -- RFC user
2. Set System Parameters:
Transaction: RZ10 (Edit Profiles)
# Instance Profile: SLT_DVEBMGS00_<hostname>
# Memory Configuration
em/initial_size_MB = 2048
em/max_size_MB = 4096
ztta/roll_extension = 2000000000
# RFC Configuration
gw/acl_mode = 1
gw/reg_no_conn_info = 0
# SLT-Specific Parameters
rsdb/max_blocking_factor = 1000
rdisp/max_wprun_time = 3600
3. License Installation:
Transaction: SLICENSE
- Enter license key received from SAP
- Apply to all clients
- Verify expiration date
4.2 Network Configuration
Configure RFC Connections:
Transaction: SM59 (RFC Destinations)
Create Connection to Source System:
Connection Name: SRC_ECC_PRD
Connection Type: 3 (ABAP Connection)
Target Host: ecc-prd.company.com
System Number: 00
Client: 100
Logon & Security Tab:
Language: EN
User: SLTUSER
Password: ********
Special Options Tab:
☑ Trace: Off (enable only for troubleshooting)
Test Connection:
- Click "Test Connection" button
- Verify: ✅ Response time < 1 second
Create Connection to Target HANA:
Transaction: DBACOCKPIT (Database Connection)
Connection Name: TGT_HANA_PRD
Database Type: HANA
Host: hana-prd.company.com
Port: 30015
Database Name: HDB
User: SLTREPL
Password: ********
Schema: SLTREPL
4.3 Authorization Configuration
Create SLT Administrator Role:
Transaction: PFCG (Role Maintenance)
Role Name: Z_SLT_ADMIN
Required Authorization Objects:
| Authorization Object | Field | Value |
|---|---|---|
S_DMIS_MTC | ACTVT | 01, 02, 03, 06 (CRUD) |
S_DMIS_LOG | ACTVT | 03 (Display) |
S_DMIS_REP | ACTVT | 01, 02, 03 |
S_RFC | RFC_TYPE | Function Group DMIS* |
S_TABU_DIS | DICBERCLS | * (All tables) |
S_BTCH_ADM | BTCADMIN | Y (Background jobs) |
Assign Role to Users:
Transaction: SU01
User: SLTADM01
Roles Tab: Add Z_SLT_ADMIN
4.4 Monitoring Setup
Configure Job Scheduling:
Transaction: SM36 (Define Background Job)
Critical SLT Jobs:
| Job Name | Transaction | Frequency | Purpose |
|---|---|---|---|
DMIS_LOGGING_TABLE_CLEANUP | - | Daily | Clean processed logging records |
DMIS_ERROR_NOTIFICATION | - | Hourly | Send error alerts |
DMIS_STATISTICS_COLLECTOR | - | Every 15 min | Collect replication statistics |
DMIS_HEALTH_CHECK | - | Every 5 min | Monitor system health |
Schedule Example:
Job Name: DMIS_LOGGING_TABLE_CLEANUP
Start Condition: Daily at 02:00 AM
Program: /DMIS/LOG_CLEANUP
Variant: STANDARD
5. Network and Firewall Configuration
5.1 Required Network Ports
SLT Server Ports:
| Port | Protocol | Direction | Purpose |
|---|---|---|---|
| 3200 | TCP | Inbound | SAP Dispatcher |
| 3300 | TCP | Inbound | SAP Gateway |
| 8000 | HTTP | Inbound | ICM (Web) |
| 44300 | HTTPS | Inbound | ICM (Secure Web) |
| 30015 | TCP | Outbound | HANA SQL connection |
Firewall Rules (Linux iptables example):
# Allow SAP Dispatcher
iptables -A INPUT -p tcp --dport 3200 -j ACCEPT
# Allow SAP Gateway
iptables -A INPUT -p tcp --dport 3300 -j ACCEPT
# Allow HANA connection
iptables -A OUTPUT -p tcp --dport 30015 -d <HANA_IP> -j ACCEPT
# Save rules
service iptables save
5.2 Network Latency Testing
Test network latency between systems:
# From SLT server to source ECC
ping -c 10 ecc-prd.company.com
# Acceptable latency: < 5ms (LAN), < 50ms (WAN)
# From SLT server to target HANA
ping -c 10 hana-prd.company.com
# Test bandwidth
iperf -c hana-prd.company.com -t 60
SLT requires stable, low-latency network connectivity. High latency (>100ms) or packet loss (>1%) will severely impact replication performance.
6. Database Configuration
6.1 HANA Database Setup for SLT
Create Dedicated Schema for Replication:
-- Connect as SYSTEM user
CREATE SCHEMA SLTREPL;
-- Create database user
CREATE USER SLTREPL PASSWORD <SecurePassword>
NO FORCE_FIRST_PASSWORD_CHANGE;
-- Grant required privileges
GRANT CREATE ANY ON SCHEMA SLTREPL TO SLTREPL;
GRANT SELECT, INSERT, UPDATE, DELETE ON SCHEMA SLTREPL TO SLTREPL;
GRANT EXECUTE ON SCHEMA SLTREPL TO SLTREPL;
-- Grant catalog read (for metadata)
GRANT CATALOG READ TO SLTREPL;
-- Grant monitoring (for statistics)
GRANT MONITORING TO SLTREPL;
6.2 Logging Table Tablespace
Create Dedicated Tablespace for Logging:
-- On SLT server database (if not HANA)
CREATE TABLESPACE SLTLOG
DATAFILE '/data/sltlog01.dbf' SIZE 10G
AUTOEXTEND ON NEXT 1G MAXSIZE UNLIMITED;
-- Set as default for SLTABAP schema
ALTER USER SLTABAP DEFAULT TABLESPACE SLTLOG;
For HANA (automatic management):
-- HANA manages space automatically, ensure storage is sufficient
SELECT * FROM M_DISK_USAGE WHERE USAGE_TYPE = 'LOG';
7. System Verification
7.1 Health Check Procedures
1. Transaction: SMLT (SLT Dashboard)
Check dashboard indicators:
- System Status: ✅ Green
- RFC Connections: ✅ Active
- Logging Tables: ✅ No overflow
- Replication Engine: ✅ Running
2. Transaction: SM21 (System Log)
Verify no critical errors:
Filter: Message Type = E (Error), W (Warning)
Search: DMIS*, /DMIS/*
3. Transaction: ST22 (ABAP Dumps)
Check for runtime errors:
Search: Program Name contains "DMIS"
Expected: No dumps in last 24 hours
4. Transaction: DB02 (Database Performance)
Monitor database space:
Check:
- Tablespace Usage < 80%
- Logging Table Growth Rate
- Missing Indexes (should be 0)
7.2 Connectivity Tests
Test RFC to Source:
Transaction: SM59
1. Select RFC destination (e.g., SRC_ECC_PRD)
2. Click "Connection Test"
3. Expected: ✅ Connection OK, Response Time < 1000 ms
4. Click "Unicode Test"
5. Expected: ✅ Compatible
6. Click "Authorization Test"
7. Expected: ✅ User has required authorizations
Test Database Connection to Target HANA:
Transaction: DBACOCKPIT
1. Select database connection
2. Click "Test Connection"
3. Expected: ✅ Connected
4. Execute test query:
SELECT CURRENT_USER, CURRENT_SCHEMA FROM DUMMY;
5. Expected: Returns SLTREPL, SLTREPL
8. Initial System Configuration
8.1 SLT Configuration Transaction
Launch SLT Configuration:
Transaction: LTR or LTRC
Configuration Wizard Steps:
-
Define Configuration Name
Configuration ID: CFG_ECC_HANA
Description: ECC to HANA Real-Time Replication -
Select Source and Target
Source System: SRC_ECC_PRD (RFC)
Target System: TGT_HANA_PRD (DB Connection) -
Advanced Settings
☑ Enable transformations
☑ Enable error handling
☐ Enable data validation (slower)
Package Size: 10000 rows
Parallel Jobs: 4
8.2 System Parameters Tuning
Transaction: LTRC → Configuration → Advanced Settings
Key Parameters:
| Parameter | Default | Recommended | Purpose |
|---|---|---|---|
DATA_TRANSFER_PACKAGE_SIZE | 10000 | 50000 | Rows per package |
NUMBER_OF_JOBS | 3 | 8-16 | Parallel jobs |
LOGGING_TABLE_RETENTION | 7 days | 3 days | Keep logging data |
ERROR_RETRY_INTERVAL | 60 sec | 30 sec | Retry failed records |
HEARTBEAT_INTERVAL | 300 sec | 60 sec | Connection check |
9. Backup and Recovery Setup
9.1 Backup Strategy
What to Backup:
- SLT Configuration (Mass Transfer IDs, transformations)
- Logging tables (during replication)
- SLT database (SLTABAP schema)
- System profiles and parameters
Backup Frequency:
| Component | Frequency | Method |
|---|---|---|
| Configuration | Weekly | Export via transaction LTRC |
| Database | Daily | HANA backup or DB backup |
| System Logs | Daily | Archive /usr/sap/SLT/D00/work |
| Transformation Rules | After changes | Export as transport |
9.2 Disaster Recovery Plan
Recovery Time Objective (RTO): 4 hours
Recovery Point Objective (RPO): < 1 hour
Recovery Steps:
graph TD
A[Disaster Occurs] --> B[Stop Source Triggers]
B --> C[Restore SLT Server from Backup]
C --> D[Restore SLT Database]
D --> E[Restore Configuration]
E --> F[Test RFC Connections]
F --> G[Verify Logging Tables]
G --> H[Resume Replication]
H --> I[Validate Data Consistency]
10. Troubleshooting Installation Issues
10.1 Common Installation Errors
Error 1: SWPM cannot connect to HANA
Symptoms:
Error: Cannot establish connection to database
HDB: [0]: Connection failed (RTE:[-10709])
Solution:
# 1. Verify HANA is running
ps -ef | grep hdb
# 2. Check HANA port accessibility
telnet hana.company.com 30015
# 3. Verify HANA user credentials
hdbsql -n hana.company.com:30015 -u SYSTEM -p <password>
# 4. Check firewall rules
iptables -L -n | grep 30015
Error 2: Insufficient Memory
Symptoms:
SWPM fails at "Import ABAP" phase
Error: TST-2603 ABAP: Memory allocation failed
Solution:
# 1. Check available memory
free -g
# 2. Increase swap space
dd if=/dev/zero of=/swapfile bs=1G count=8
mkswap /swapfile
swapon /swapfile
# 3. Adjust kernel parameters
echo "vm.swappiness=10" >> /etc/sysctl.conf
sysctl -p
Error 3: License Key Issues
Symptoms:
System starts but transaction SMLT not available
Error: License key is invalid or expired
Solution:
Transaction: SLICENSE
- Delete old license (if any)
- Install new hardware key
- Apply valid license from SAP
- Restart SAP system: stopsap r3 / startsap r3
Summary
In this module, you learned:
✅ SLT system landscape and deployment options
✅ Hardware and software requirements
✅ Complete installation procedure using SWPM
✅ Post-installation configuration steps
✅ Network and firewall setup
✅ Database configuration for SLT
✅ System health verification procedures
✅ Backup and disaster recovery planning
✅ Troubleshooting common installation issues
What's Next?
In Module 3, you'll learn:
- Creating your first Mass Transfer ID
- Configuring source and target connections
- Table selection and filtering
- Basic replication scenarios
- Monitoring initial loads
Ensure your SLT system is running and accessible before proceeding to Module 3. Test all RFC connections and database connectivity.