Differences between DEV and PRO in using /usr/sap/trans

Question

hello:

I am configuring transport System, PRO is the domain controller.

I recently made a 46C system copy/installation from PRO (production) to DEV (development/test) system and need to reconfigure transport system. After the copy two domain controllers exists, one in DEV and another in PRO. I have 2 questions here:

1) Using STMS, should I delete DEV domain controller and create another that only integrate to PRO domain controller?

2) After this, will the /usr/sap/trans in DEV be populated with new transport orders/tasks generated in this system? or only /usr/sap/trans of PRO will be populated with DEV transport orders/tasks?

Hope I was clear, if not, please let me know. Thanks!!!

Answer 1

Update: Regarding your question in the comment. Both system should look at the same directory. Sap is never transfering files from one trans directory to another. The process is:

• You release a request from dev system. This create files in /usr/sap/trans/(data & cofiles).
• If your stms is configured correctly (another complex issue), you immediately see the request on the prd system import queue and can import it.
• If the route in stms is not configured. You can still add the request to the prd system queue. and then import it to prd.

There is not file movement involved. Since both system look at the same directory tree.

Here is Sap documentation on stms. Its not simple. But you can test and play with it untile you grasp the concept.

Before update:The usual practice is:

1. There should be only one domain controller in your landscape. And one backup domain controller.
2. All system should point to the same trans directory.