Integration Architecture – Overview (Jira)
The SAP Transport Integration App connects Jira with your on-premise SAP landscape via a bidirectional interface. The diagram below shows the high-level architecture.
What the diagram shows
Internet (left): Jira with the SmartChange Panel (SAP Transport Integration App). Jira Cloud uses dynamic IP address ranges; Jira Data Center uses a fixed, known IP.
External Firewall (center): Must allow the IP range of Jira. All communication passes through here.
Customer Environment (right): Your existing infrastructure (Cloud Connector, Reverse Proxy, or SAP Gateway) routes requests to the SAP System. The SmartChange TM Controller manages all transport distributions to the SAP Target Systems (DEV, QAS, PRD).
Data flow: Jira sends actions to SAP via OData. SAP pushes transport status updates back to Jira via RFC (HTTP Webhook).
Deployment Options
Both options deliver the same functionality. The difference lies in how the connection between Jira and your SAP system is established. Choose based on your existing infrastructure.
SAP BTP & Cloud Connector
The modern, recommended approach. Uses SAP Business Technology Platform with API Management and Cloud Connector for a secure, cloud-based connection. No inbound firewall ports required.
Reverse Proxy & SAP Gateway (DMZ)
The traditional approach for environments with existing DMZ infrastructure. Uses an optional Reverse Proxy and SAP Gateway / Fiori system in the DMZ.