Within an integration scenario, you can create all connections based on integration scenario definitions. This is done with only a few clicks as the entire integration scenario definition has been well defined during design time. You can also include connections that are based on contracts, service groups or consumer factories. Create bindings only if you do not know which consumer needs to consume your Web service or if you cannot configure the consumer centrally.
You are in a central system.
For all participants in the scenario, IBC references exist in your central system. For more information, see Defining IBC References.
Each participating IBC reference is assigned to the domain system in which the referenced IBC resides.
Option | Description |
---|---|
Create contract connections | You can either create connections on the basis of integration scenario definitions or create single connections manually. |
Create service group connections | You can create one-way or asynchronous request/response connections for one or multiple service groups. |
Create connections for providers only | You can configure endpoints for external consumers. |
Option | Description |
---|---|
Assign logon data | If you know the correct logon data and have created it, you can assign logon data to each connection. |
Activate/deactivate integration scenario | Activated integration scenarios can be released. This means that all of its connections will be configured across the system landscape. If you deactivate an integration scenario, all of its connections will be deleted with the next release request of the scenario |
Check the integration scenario configuration | The consistency of the technical setup is checked. For example, it is checked if all design time objects of the integration scenario exist in the central design time cache. Also, it is checked if the involved domain systems share a common domain. |
Ping the integration scenario configuration | Pings are carried out for all connections of the integration scenario. This means that the central system sends ping commands to all of its domain systems. Every domain system then sends pings to all of its provider systems. |
Release the integration scenario configuration | The central systems checks which connections of the integration scenario need to be configured or deleted and sends out configuration requests to all domain systems. Activated connections will be configured. Deactivated connections will be deleted. |
Check the designtime cache | The central design time cache is updated with information from the design
time caches of the managed systems, if it is not already up-to-date. Note We
recommend to check the central design time cache before releasing an
integration scenario.
|
Carry out health checks | The following three health checks are carried out. You can also schedule
the health checks to run regularly.
Within the health check user interface, you can carry out repairs. |