cancel
Showing results for 
Search instead for 
Did you mean: 

Changing Transport domain controler.

stephane_lamarche
Active Participant
0 Kudos

Hi,

I'm supporting an old R/3 4.6 landscape that is being used only for historical and audit purposes (old company division servers). We currently still have the 3 systems landscape running and want to decommission the dev server from the landscape and run it only has a 2 system landscape. Since there are no more development being done, we thought we would take dev down. The problem is dev is the Transport Domain Controler and contains the trans directory.

How can I remove/delete the entire transport system configuration and then re-create it on a different server as a 2 system landscape. The goal is to remove dev server from being the domain controller, including the trans folder config.

Any suggestions???

I already tried transferring the domain Controller role over to the other server (backup controller), but once I shutdown dev I get errors because the trans directory is still referred as being on the dev server somewhere in the config.

I would like to delete everything and recreate the transport landscape on another server. Is that possible?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Do the following:

1. Copy the existing transport directory to the new server to the proper directory.

2. Delete the existing transport route configuration from the domain controller: STMS -> Transport Routes -> Edit and delete the configuration.

3. Delete the current transport configuration in each system from STMS and in one of the menus, you will find the option Delet Transport Configuration (I think menu is Environment).

4. Go to the transport directory and under the folder bin, edit the tp parameter file and domain config file to ensure that all past references to the old domain controller now point to the new domain controller.

4. Login to 000 STMS in the system which you want to make as domain controller. As soon as you start this transaction, it will prompt you to create/join a transport domain. Make a new domain with this system as the domain controller.

5. Login to the other system and run STMS to include it in the new domain.

These steps should give u a comprehensive idea and any small mistakes here can be corrected when u start working on it.

Do reply if this helps you.

Regards,

Shitij

stephane_lamarche
Active Participant
0 Kudos

Thanks for the quick reply, I'll give this procedure a try and let you know.

stephane_lamarche
Active Participant
0 Kudos

Your answer really helped and I thought everything was looking good until I realized the new domain controller parameter file was created and still trying to connect to the old DEV server. Everything works and looks like it should, but the trans folder is still being read on the old server even after recreating the whole transport domain configuration.

Any ideas???

Edited by: Stephane Lamarche on May 4, 2010 4:05 PM

Former Member
0 Kudos

Hi,

I think this might be due to the profile parameters DIR_TRANS and DIR_EPS_ROOT. Check your profiles and if you ind this parameter, change it to the new location coz it might be pointing to the old server.

Let me know if that works.

Best Regards,

Shitij

stephane_lamarche
Active Participant
0 Kudos

DIR_TRANS parameter needed to be adjusted on all instances that were in the transport domain.

Thanks for all your help guys.

stephane_lamarche
Active Participant
0 Kudos

After further review, I'm still having issues on the Production server side. From the Transport Domain controller I ran the TMS: Check Transport Tool and got the following errors for system PRD.

Under Transport Profile section:

-tp profile cannot be read

-tp profile has an invalid format

under TP call section:

-Link to database failed

-could not access file as supposed (see..

Any ideas what could be missing?

How can I get PRD to read this new transport domain profile TP_domain_QAS.PFL

Thanks

Former Member
0 Kudos

Hi,

Is the transport dir readable from the PRD server?

Did you configure PRD into the transport config the same way as I had explained earlier.

If yes, then check the error messages for their long texts.

Regards,

Shitij

stephane_lamarche
Active Participant
0 Kudos

I found what the problem was. It was a workstation trust relationship issue on the Transport Domain controller server, so the PRD server couldn't connect to it using the UNC path.

I had to take it out of the network domain, put it in a workgroup, then put it back in the domain.

Every thing looks good now.

Thanks

Answers (0)