The SAP Management Cockpit is a centralized web dashboard that provides a single-pane-of-glass view of the entire SAP landscape managed by the Fivetran SAP Specialist Team. It serves as the top-level entry point for all system cockpits, monitoring, and operational links.
| Type | Static HTML + JavaScript |
| Server | sapidesecc8 (port 443) |
| Path | /usr/sap/sap_skills/docs/ |
| Theme | Teal (#0d7377) |
| GitHub | fivetran/SAPManagementCockpit |
The cockpit performs automatic health checks on page load for all 6 servers. Each server card displays a color-coded status indicator.
| Method | GET |
| URL | /sap_skills/api/reachability?system={system} |
| Auth | None required |
| Response | { "reachable": true|false } |
| System Parameter | Server Checked | Status Element ID |
|---|---|---|
s4hana | sapidess4 | reach-s4hana |
ecc8 | sapidesecc8 | reach-ecc8 |
sq1 | sap-sql-ides | reach-sq1 |
saprouter | saprouter | reach-saprouter |
hvrhub | saphvrhub | reach-hvrhub |
sshtunnel | ts-sap-hana-s4-ssh-tunnel | reach-sshtunnel |
| Color | Meaning | Hex |
|---|---|---|
| Gray | Initial state (checking...) | #ccc |
| Green | Server reachable | #27ae60 |
| Red | Server unreachable or check failed | #e74c3c |
checkReachability(system, elementId) JavaScript function is called 6 times on DOMContentLoaded, one for each server. The server-side handler in gcs_explorer_server.py performs the actual connectivity check.
| SAP Notes | me.sap.com |
| Software Downloads | SAP Software Center |
| Connectors | Fivetran Dashboard |
| HVR Locations | HVR Hub Console |
| POV App | Proof of Value App |
| Slab | Internal Knowledge Base |
Each server has its own dedicated cockpit page with server details, start/stop controls, backup management, disk space monitoring, and more.
| Page | File | Features |
|---|---|---|
| S/4HANA 2023 | SAP_S4HANA_2023.html |
SAP + HANA start/stop, BACKINT backup, disk space, status, Web IDE link |
| S/4HANA User Guide | SAP_S4HANA_2023_Guide.html |
Step-by-step guide for using the S/4HANA cockpit |
| ECC6 EHP8 | SAP_ECC6_EHP8.html |
Oracle DB status, SAP start/stop, BR*Tools backup, SBP patching |
| ECC6 SQ1 | SAP_ECC6_SQ1.html |
SQL Server SAP instance, start/stop, disk space |
| SAPRouter | SAP_SAPRouter.html |
SAPRouter service management, route table, connection testing |
| HVR Hub | SAP_HVRHub.html |
HVR service status, location management, replication channels |
| SSH Tunnel | SAP_SSHTunnel.html |
SSH key management, tunnel status, Fivetran connector access |
| Repository | fivetran/SAPManagementCockpit |
| Local Directory | ~/SAP_Skills/docs/ (Management Cockpit files are part of the portal) |
| Production Path | /usr/sap/sap_skills/docs/SAP_Management_Cockpit.html |
| File | Purpose |
|---|---|
SAP_Management_Cockpit.html | Main cockpit dashboard page |
SAP_Management_Cockpit_Documentation.html | This documentation page |
SAP_S4HANA_2023.html | S/4HANA system cockpit |
SAP_S4HANA_2023_Guide.html | S/4HANA cockpit user guide |
SAP_ECC6_EHP8.html | ECC Oracle cockpit |
SAP_ECC6_SQ1.html | ECC SQL Server cockpit |
SAP_SAPRouter.html | SAPRouter cockpit |
SAP_HVRHub.html | HVR Hub cockpit |
SAP_SSHTunnel.html | SSH Tunnel cockpit |
All cockpit pages are static HTML served from disk. No server restart needed after updates.
scp ~/SAP_Skills/docs/SAP_Management_Cockpit.html root@sapidesecc8:/usr/sap/sap_skills/docs/ scp ~/SAP_Skills/docs/SAP_Management_Cockpit_Documentation.html root@sapidesecc8:/usr/sap/sap_skills/docs/
To add a new server to the Management Cockpit:
SAP_NewServer.html) in ~/SAP_Skills/docs/SAP_Management_Cockpit.html inside the .status-grid divgcs_explorer_server.pycheckReachability('newserver', 'reach-newserver') in the DOMContentLoaded handlerThe reachability check is handled server-side in gcs_explorer_server.py on sapidesecc8. The handler receives the system query parameter and performs a network connectivity check (typically SSH or ping) to the corresponding server.
gcs_explorer_server.py, you must restart the service: systemctl restart gcs-explorer
The Management Cockpit includes a Monitoring Agent section for managing email distribution lists and sending test emails. All servers relay email via smtp2go using the fivetran-internal-sales.com verified domain.
| Property | Value |
|---|---|
| SMTP Provider | smtp2go (mail.smtp2go.com:2525) |
| Portal From | sap-skills@fivetran-internal-sales.com |
| Verified Domain | fivetran-internal-sales.com |
| Vault Key | smtp2go |
| List Name | Recipients | Usage |
|---|---|---|
SAPSpecialists | antonio.carbone@fivetran.com, richard.brouwer@fivetran.com | Alerts, notifications, reports |
Distribution lists can be edited directly from the Management Cockpit or the Server Documentation page. Changes are persisted to the HTML files on disk.
| Endpoint | Method | Description |
|---|---|---|
/sap_skills/api/get_mailing_list | POST | Read a distribution list by name |
/sap_skills/api/update_mailing_list | POST | Update a distribution list (rewrites HTML) |
/sap_skills/api/send_test_email | POST | Send a test email to a distribution list |
The Service Monitor is a real-time health dashboard embedded in the Monitoring page. It checks all 6 servers and their critical services every 5 minutes.
| Component | Location | Purpose |
|---|---|---|
| Health check script | /usr/local/bin/sap_health_check.sh on sapidesecc8 | Runs every 5 min via cron, checks all servers and services |
| JSON status file | /usr/sap/sap_skills/health_status.json | Written by the script, read by the web UI |
| History log | /var/log/sap_health_check.log | Append-only log of all checks (last 2000 lines) |
| Health log API | POST /sap_skills/api/admin/health_log | Returns last 50 log entries |
| Web UI | SAP_Monitoring.html | Auto-refreshing dashboard with status cards |
| Server | Services | Check Method |
|---|---|---|
| sapidess4 | SAP Dispatcher, Gateway, ICM, IGS; HANA FIV; HANA PIT | sapcontrol via SSH (nr 03, 00, 96) |
| sapidesecc8 | SAP Dispatcher, Gateway, ICM; Oracle DB; Web Server | sapcontrol local; ora_pmon process; HTTPS curl |
| saprouter | Server reachability; SAPRouter service | SSH; systemctl is-active saprouter |
| sap-sql-ides | Server reachability; SAP Instance (SQ1); SQL Server DB | Ping; SOAP sapcontrol port 50013; WinRM via API |
| saphvrhub | Server reachability; HVR Hub; PostgreSQL 14 | SSH; systemctl is-active for both |
| SSH Tunnel | Server reachability | SSH to 10.142.0.37 |
| Indicator | Meaning |
|---|---|
| Green dot | Service is running |
| Red dot | Service is down or unreachable |
| Gray dot | Check in progress (initial state) |
| REACHABLE | Server responds to SSH or ping |
| UNREACHABLE | Server did not respond within timeout |
Each server card has a Cockpit button that opens the individual server management page where you can start/stop services, view disk space, manage backups, and more.
| Server | Cockpit Page | Actions Available |
|---|---|---|
| sapidess4 | SAP_S4HANA_2023.html | Start/stop SAP + HANA, backup, disk space |
| sapidesecc8 | SAP_ECC6_EHP8.html | Start/stop SAP + Oracle, BR*Tools backup |
| saprouter | SAP_SAPRouter.html | Start/stop SAPRouter, edit route table |
| sap-sql-ides | SAP_ECC6_SQ1.html | Start/stop SAP, SQL Server backup |
| saphvrhub | SAP_HVRHub.html | Start/stop HVR + PostgreSQL, manage locations |
| SSH Tunnel | SAP_SSHTunnel.html | Manage SSH keys, view sessions |
For complete documentation on the email relay, SMTP configuration, distribution lists, health check script internals, and service restart procedures, see the Monitoring Agent User Guide.