The content in this section is not relevant for China (Shanghai) and Government Cloud (US) regions.
Systems that are included in Eventing Between SAP Cloud Systems formations on the System Landscape page of the SAP BTP cockpit can publish and consume events. The process of publishing and consuming events is in fact an exchange of event information across the customer system landscape and is driven by the system formations on the one hand side and the SAP Cloud Application Event Hub on the other.
By creating a formation of type Eventing Between SAP Cloud Systems, keep in mind that there may be event distribution charges incurred if you exceed the free quota limit when using SAP Cloud Application Event Hub. To learn more about usage and consumption costs, see Usage and Consumption Costs.
When creating Eventing Between SAP Cloud Systems formations, keep in mind the following rule:
- Every system can be included in at most one Eventing Between SAP Cloud Systems formation.
-
You are a global account administrator, or you are a system landscape administrator. See Working with Role Collections.
-
You have subscribed to the SAP Cloud Application Event Hub application. See Subscribing to SAP Cloud Application Event Hub Application.
The following procedure outlines the steps you need to perform to enable the exchange of events across the systems within the system landscape.
-
In the SAP BTP cockpit, in the System Landscape > Systems page of the SAP BTP cockpit, browse the already added systems in your customer system landscape or manually add and register any missing systems.
The customer landscape features systems that are added to the list in one of the following ways:
-
Auto-discovered
An auto-discovered system is a system (associated with the given global account) that has been discovered and added automatically to the list based on information of the existing system landscape. Any SAP system of the supported system types that is associated with the same customer ID, with which your global account in SAP BTP is associated, will be added automatically in the system landscape list.
-
Subaccount/<my-subaccount>**
A subscription in SAP BTP cockpit associated with a given subaccount. The subscription has been discovered and added automatically through the subaccount. Check the value of the Discovery column to see the subaccount where your system is subscribed.
-
Manually added
Specifies that the system has been added to the list manually by the global account administrator, using the Add System button and completing the wizard. The system has been associated with the global account in SAP BTP.
If a given SAP system is missing on the Systems page, it may be associated with a different customer ID on the SAP BTP global account you are working in. In this case, you need to add the system manually, and then, register it.
-
-
Create a formation of type Eventing Between SAP Cloud Systems and include the relevant systems in it.
-
Add any name that helps you identify your formation.
-
In the Formation Type dropdown menu, select Eventing Between SAP Cloud Systems.
-
Select the systems that you want to include in the formation. One of these systems must be of type SAP Event Broker.
Systems can only be added to one formation of type Eventing Between SAP Cloud Systems in a global account.
Also, a formation of type Eventing Between SAP Cloud Systems can contain only one system of type SAP Event Broker.
-
Review your selections and create the formation.
-
When the formation is created, navigate to the SAP Cloud Application Event Hub application and enable the event subscriptions. See Enabling SAP Event Subscriptions.
If you want to remove an SAP system from a formation of type Eventing Between SAP Cloud Systems, make sure that all active event subscriptions are disabled first in SAP Cloud Application Event Hub. You can check your subscriptions in the SAP Cloud Application Event Hub application on the Subscriptions page. See Disabling SAP Event Subscriptions.