I think what you probably need to do is to configure all systems in a common transport domain, but put them in separate transport groups within that domain. Each transport group shares a common /usr/sap/trans location, so in your case each system would be in its own group. However, you still have just one common domain, with one system as the transport domain controller. I admit, I've not had to setup or work with a setup like this, but it is described in the online documentation (Transport Management System - Concept (SAP Library - Change and Transport System - Overview (BC-CTS))), so it should be possible to do. It's also possible to setup domain links, allowing each system to be its own transport domain. In all of these setups, however, I believe you will find that the systems must have a way to talk to common files. If you cannot do that, then you will need to find a way of manually moving the files from system to system, and you will have undone many of the significant advantages of the SAP transport infrastructure and concept. I would urge you to take a look at this older thread on this same topic: Transporting without nfs directory. In it, Markus Doehr, who has probably forgotten more about this stuff than I will ever know, says much the same thing, and as he points out, SAP's transport concept regularly passes the most stringent of audits.
↧