Specify the Domain Controller as target host (). The system is now waiting to be included in the transport domain. For security reasons you then have to go back to the domain controller to confirm your request. Choose System Overview and Approve of the waiting system. Then confirm the prompt and the configuration will be distributed. This SAP system now contains the necessary information about all the other SAP systems in the transport domain. At the same time, the address data of the new SAP system is sent to all the other SAP systems, and the SAP system is entered in the transport profile of the transport control program. Check whether RFCs and access to the transport directory of the domain work. Go on with the configuration of your transport system as as described in the documentation . How to: Make sure your STMS on premise is configured correctly. Make sure the hostname of the Transport Domain Controller can be resolved by your virtual machine on Azure and vice visa. Call transaction STMS -> Configuration -> Include System in Domain. Confirm the connection on the on premise TMS system. Configure transport routes, groups and layers as In site-to-site connected Hybrid-IT scenarios the latency between on-premise and Azure still can be substantial. If we follow the sequence of transporting objects through development and test systems to production or think about applying transports or support packages to the different systems, you realize that, dependent on the location of the central transport directory, a part of the systems will encounter high latency reading or writing data in the central transport directory. The situation is similar to SAP landscape configurations where the different systems are spread through different data centers with substantial distance between the data centers. In to work around such latency and have the systems work fast in reading or writing from or to the transport directory, you can setup two STMS transport domains (one for on-premise and one with the systems in Azure and link the transport domains. Please check this documentation which explains the principles behind this concept in the SAP TMS: . How To: Set up a transport domain on each location (on-premise and Azure) using transaction STMS Link the domains with a domain link and confirm the link between the two domains. Distribute the configuration to the linked system.
Specify the Domain Controller as target host (). The system is now waiting to be included in the transport domain. For security reasons you then have to go back to the domain controller to confirm your request. Choose System Overview and Approve of the waiting system. Then confirm the prompt and the configuration will be distributed. This SAP system now contains the necessary information about all the other SAP systems in the transport domain. At the same time, the address data of the new SAP system is sent to all the other SAP systems, and the SAP system is entered in the transport profile of the transport control program. Check whether RFCs and access to the transport directory of the domain work. Go on with the configuration of your transport system as as described in the documentation . How to: Make sure your STMS on premise is configured correctly. Make sure the hostname of the Transport Domain Controller can be resolved by your virtual machine on Azure and vice visa. Call transaction STMS -> Configuration -> Include System in Domain. Confirm the connection on the on premise TMS system. Configure transport routes, groups and layers as In site-to-site connected Hybrid-IT scenarios the latency between on-premise and Azure still can be substantial. If we follow the sequence of transporting objects through development and test systems to production or think about applying transports or support packages to the different systems, you realize that, dependent on the location of the central transport directory, a part of the systems will encounter high latency reading or writing data in the central transport directory. The situation is similar to SAP landscape configurations where the different systems are spread through different data centers with substantial distance between the data centers. In to work around such latency and have the systems work fast in reading or writing from or to the transport directory, you can setup two STMS transport domains (one for on-premise and one with the systems in Azure and link the transport domains. Please check this documentation which explains the principles behind this concept in the SAP TMS: . How To: Set up a transport domain on each location (on-premise and Azure) using transaction STMS Link the domains with a domain link and confirm the link between the two domains. Distribute the configuration to the linked system.
SAP%20NetWeaver%20on%20Windows%20Azure%20Virtual%20Machine%20Implementation%20Guide%20V1_5.docx