Configuring Links Between Transport Domains
Use
If you have configured multiple transport domains (see Transport Management System - Setting Up a System Landscape) and want to make transports between systems in different domains, you can use domain links to link the two domains.
Prerequisites
There must be a permanent network connection between the systems in the two domains, similar to the connection between systems within the same domain.
Note
If you cannot operate a permanent RFC connection between systems in the two domains, you can use external systems to make transports between the two.
Features
- You can make transports between systems in different domains in the same way as you make transports between systems in different transport groups; RFC is used to transfer transport files between the transport directories involved.
- You can display transport logs of systems in the other domain.
- You can compare versions of Repository objects in systems in different domains.
- Domains are independent administrative units. You can only make changes (such as transport route changes) in the controller of the domain.
- If you need to administrate a large number of systems (more than 50), it makes sense to split the systems into domains; place systems which transport to each other frequently in the same domain. This makes is easier to distribute changes to the configuration, since changes are distributed more quickly in domains that contain fewer systems.
- Transport routes are not distributed between domains. You can, however, configure a route between systems in different domains, but must configure it twice, once in each domain.
- You can choose to configure the Workflow Engine in each domain, or you can use the Workflow Engine of a different domain.