Common Transport Directory Migration

Our ERP 6.0 system is running on Windows 2003 Server 64 bit. The default install created a separate transport directory on each CI host. As a result users do not have log information of their transports into the PROD system, from the DEV or QAS systems. Currently they have to log into each instance to get their transport log information from the transport organizer.
I have read the online help and reviewed the SAP Notes on creating a common directory however I have not found any solid information to assist migrating/merging an already existing TMS setup. .
I have created the following check list in preparation to merge the separate transport directories into a common transport directory. Is there anything I missed?
1. Schedule maintenance to ensure Business analysts/Developers are out of all ERP systems.
2. Backup the entire \usr\sap\trans directories on DEV, QAS and PROD before beginning.
3. Update the TMS Domain Profiles for each respected system with the common directory path of the Transport Domain Controller. In our case it is the Dev server.
DIR_TRANS = \\hostname\sapmnt\trans
4. Merge the following QAS directories into the respected DEV directories (Confirm to overwrite existing files)
\usr\sap\trans\cofiles
\usr\sap\trans\data
\usr\sap\trans\logs
5.Repeat with the PROD directories into the respected DEV directories (Confirm to overwrite existing files)
\usr\sap\trans\cofiles
\usr\sap\trans\data
\usr\sap\trans\logs
Te goal is to insure that the delta changes between PROD, QAs & DEV are fully merged.
Common Transport directory
[http://help.sap.com/saphelp_erp60_sp/helpdata/EN/de/6b0da5f34d11d3a6510000e835363f/frameset.htm]
Thanks,
Jon Sells

We tried to implement this migration of the common transport directories and it was not successful. We ended up restoring back to the individual EPS directories.
What happened is that the QAS Queues did not reflect all the correct transports. (Yes, Siddhesh, I did as you said) In addition the add to buffer (crooked arrow) not longer functioned for newly released transports from DEV.
Does anyone have a white paper or SAP Note that would help on Migrating a common Tranpsort directory for Windows? Our Developers & Analyst do not like having to logon to each system to see view the transport logs. They are under the impression that they shoul be able to use SE10 in DEV and see the transport/import logs.
Thank you
Jon Sells

Similar Messages

Common transport directory configuration

Dear Gurus,
I installed ECC6.0 sr3 (dev and quality on the same server) windows 2003. Production server on seperate server. Now I want to configure common transport directory.
For dev and qas using same transport directory beacuse they are in the same server.
But production server is having seperate transport directory.
Is it compulsory having the common tranport directory.
Can Any body give the steps to add the production server in the same tranport directory.
Regards
Rao.

Is it compulsory having the common tranport directory.
No, it is not compulsory.
You can use STMS tcode to configure the same.
For further information, please go through the below link:
[Transport Management System|http://help.sap.com/saphelp_erp60_sp/helpdata/EN/44/b4a0137acc11d1899e0000e829fbbd/frameset.htm]
Regards,
Faisal

Common Transport Directory

Hi Experts,
I have some doubt about the procedure to setup a common transport directory.
Lets assume I have a 3 systems landscape (Windows env) with DEV,QTY and PRD systems. After installing SAP on the three servers, now I have to include the above systems in a common transport domain. I want DEV system to be my domain controller.
My doubts are:
1) Before configuring DEV as domain controller using STMS, do I need to share /usr/sap/trans dir for this system ?
2) (Assume /usr/sap/trans dir for DEV is shared by now) After I include the QTY and PRD system into this domain using STMS, How will the QTY and PRD system understant that they shud use the shared "/usr/sap/trans " dir of DEV and not their local /usr/sap/trans. Do I manually edit some settings for QTY and PRD systems to achieve this ? Please let me know exact steps that are involved.
Thanks !
Mandeep

Hello,
Try the following.
http://www.sap-img.com/basis/how-to-do-the-tms-configuration.htm
And also,
STMS configuration.
1.Login to 000 client with user DDIC
2. goto STMS --> prompts to create a domain controller --> check with entries and save.
3. goto systemoverview -->SAP system --> create virtual system ( For QAS and PRD)
4.goto Transport routes -->change --> configuration --> standard configuration --> three system in group --> enter SID's --> specify Three system configuration and distribute configuration to all systems.
Once you created virtual systems and then goto transport routes and configutation -->change --> standard configuration --> threesystem group. specify SID's of three systems and save then specift three system configuration and distridute configuration.
Once you have done above thing add QAS and PRD in to landscape.
1. Login to PRD system 000 client with DDIC user.
2.STMS --> prompts to create domain controller > select other configuration and add to existing domain controller ( i.e DEV because DEV is domain controller).> specify system details for PRD system.
3.Once you added and saved. login to DEV system --> 000 with DDIC --> stms --> system overview --> select PRD system --> SAP system --> Approve and save.
4. follow the same steps for QAS also.
5. A communication user will be created between domain controller and remaining systems in a landscape. ie TMSADM
6. the entire configuration will be stored in DOMAIN.cfg file in trans/bin folder
I hope this information will helpful to you.
Note: Points always encourage me to reply !!

How to share Common transport directory with Production

Dear All,
we are following three-system landscape with Dev & Qas on the same server & production server in a Cluster.Now I am going to start the production server installation but I have few query before starting the installation:
1. The Dev+Qas server is sharing a common transport directory (/usr/sap/trans). The production server needs to share the same transport directory.I have few options:
a)Should I need to share the common transport directory during the installation
b)I install the production server first then I can share the transport directory which is currently being shared by Dev & Qas system
c)I need to share the Common transport directory first & then start the installation so that during installation Production system writes into the Common traansport directory
Please advise.
Thanks in advance,
Sandipan

Hi,
By mounting, do you mean just to share it as we are using Windows Server 2003 x64 bit system, so just by sharing will it work.
Need your suggestion on whether can I install the production system first & then by sharing the transport directory from Dev( or Qas) it can join in the exisitng transport directory. As during installation of production server also,the system will create /usr/sap/trans. If I don't share the already exisitng /usr/sap/trans of Dev system, can I share it later so that production system can join into the common transport directory without any problem.
Please guide,
Thansk & Regards,
Sandipan

Need common transport directory(heterogeneous)

Hello All,
I have to include three ECC 5.0 systems and three BW systems into Domain controller( Production solman 7.0)
1) Three ECC 5.0 System are running on Red Hat Linux (OS)
2) Three BW systems are running on Red Hat Linux (OS).
3) Domain Controller (solman) is running Windows 2003 server
Above situation is Heterogeneous environment.
Now i have to configure common transport directory for all above systems ( seven systems), which are running on Different OS like Red Hat Linux and Windows 2003 Server.
For common transport directory what are the steps have to be done...?
Please help me out.
Thanks and Regards,
Kiranbabu

Kiran-
What i think is you need to work with CTS+ configuration and please see the OSS note: 1003674 this is the central note which might be handy for you.
http://help.sap.com/saphelp_nw70/helpdata/en/45/ec25370fdc3481e10000000a1553f6/frameset.htm
Hope this might help you some way

How to set CTD ( common transport directory ) ????

i need it pls help me ........?????

Hi,
Please reade below link and implement accordingly.
http://help.sap.com/saphelp_nw70/helpdata/en/de/6b0da5f34d11d3a6510000e835363f/content.htm
http://help.sap.com/saphelp_sm32/helpdata/en/c4/6045377b52253de10000009b38f889/content.htm
Regards,
Anil

I want to change the transport directory

Hello gurus,
I want to change the tranport directory in all our systems. Please advise me how to do it.
I really appreciate your help.
Regards,
N.S

Hi N.S,
How about :
http://help.sap.com/saphelp_47x200/helpdata/en/d5/10b4496f0f11d2b41a006094b9ea64/frameset.htm
is it common transport directory ?
To change the common transport directory configuration, you can
first go to transaction AL11 of one of your system, for example, PRD.
Change the 'DIR_TRANS' parameter, so that it points to the directory that you want to change
Then go to STMS, choose 'System Overview' button to display systems
of your transport domain. Double click PRD, with 'Transport
Tool' tab, click 'Display <-> Change' button, you can change the
'transdir' value.
Please make sure it is equal to the same configuration of 'DIR_TRANS'.
Repeat the above steps on your other system. Make sure the configurations
of 'transdir' and 'DIR_TRANS' are the same as that on the PRD system.
cheers,
Vincent

Unable to use global transport directory

Hi,
I have a 3 system SAP landscape consisting of DEV, QAS, PRD. I configured TMS and put all three system into the same transport group. DEV and QAS can shared the same transport directory residing in DEV. However I am unable to get PRD to use the global transport directory. PRD is always using its transport directory. How can I allow PRD to use the global transport directory?
Rdgs

Hi,
The transport directory is shared out which explains why QAS is able to use the same transport directory. DIR_TRANS in PRD points to local transport directory and not the shared transport directory. Is there really a need to set DIR_TRANS parameter if TMS is configured? In QAS, I don't see DIR_TRANS being set in the instance profile.
I did tried setting DIR_TRANS in PRD however the system reported the parameter as unknown.
BTW, PRD is a copied from another system. We migrated the old PRD to a new server.
Rdgs

Change the Transport Directory.

Hi everybody, We have I system installed (S01) and we have just installed a new one (S02), we want to be able to trasnport from the system S01 to the system S02. What I have to do in order to do that?
I read that the systems have to have the same Transport Directory. And I checked with AL11 and the values for the DIR_TRANS parameter are the following for each system:
system S01 -> DIR_TRAN ->
S01\sapmnt\trans
system S02 -> DIR_TRAN ->
S02\sapmnt\trans
I tried to change the DIR_TRANS parameter with the transaction RZ10, but in S02 we don't have any profile.
Cuold you please help me to do that?
Thanks and Regards.

Hi,
read that the systems have to have the same Transport Directory.
not neccesary to have tarnsport directory, it depends upon scenario.
Pls follow the below link for configuring stms configuration.
bbs.cenet.org.cn/UploadImages/200581112435749207.pdf
Also check the below link
Common tranport directory on Windows local installation
Thanks,
Anil

Directory Migration with changing schema

Hi,
We are planning a directory migration as part of an implementation of Sun Identity Manager.
The directory migration is from one set of servers to another and comprises an upgrade from Directory 5.2 to 6.3, and a schema change.
We'd like to have a rollback plan that involves copying changes from the new directory to our legacy servers. A delay is acceptable.
We're doing two things to our schema which increases the complexity:
- Users are being segregated, e.g.:
OLD: uid=123456,ou=People,ou=UK,dc=root
NEW: uid=123456,ou=Internal,ou=Users,dc=root OR uid=567890,ou=External,ou=Users,dc=root
- Replacing an ou hierarchy containing Groups (groupofuniquenames) to nsRoleDN attributes on users.
We'd like to avoid writing some kind of custom script to retrieve changes, modify them and insert them into the old directory.
Directory Proxy doesn't seem to be the right tool for this job.
Could anyone suggest an alternative?

So I have done this migration before - The directory information is not so bad to get migrated in fact the Novell IDM could do that piece for you.
Migrating the files, and security over will be an exercise in icacls
Logon scripts/Group policy preferences will need to be done to convert the existing drive mapping scripts over, Look at DFS for this so you only have to migrate once.
If everything is planned out it will keep the migration smooth, but truly understanding the role of Novell IDM in the environment, analyzing the shared files and data (Good time to cleanup, hint hint), validating the groups and security are set up correctly
will aid immensely.
I would also do in batches based on shared data and not try to move everyone at one big move, that way as departments move you can get the kinks out of the process.
From a workstation that has the novell client you can script the data copy with robocopy over to the new home
once the data is copied over, robocopy can keep the data sync'd until users are migrated over.
Novell has the ability of exporting directory structures with permissions on them, scripting icacls will get the permissions repopulated on the MS side. Groups and users of course would need to be there already.
Thanks,
Brad Held
Windorks.wordpress.com
View
Brad Held's profile

Upgrade - Transport Directory Strategy

Hello All,
We are having the below 4.7 Landscape,
DEV -> QAS -> PRD
We are having central Transport Directory. /usr/sap/trans is present in PRD which is mounted to DEV and QAS.
Now, we are doing DEV Upgrade.
So, we have created a Temporary Development DVP for 4.7 (which is a copy of DEV) so that we can continue our 4.7 Developments. Basically a approach of Dual Landscapes for Upgrades, one for 4.7 and one for ECC6.
Now, DEV has its local /usr/sap/trans, while we have mounted /usr/sap/trans(of PRD) to DVP. So new 4.7 Landscape is
DVP-> QAS -> PRD
After I do my QAS Upgrade, 4.7 Landscape will be turned to a 2 System landscape. Because of H/W constraints we cannot have two QAS (one for 4.7 and other for ECC6).
My question is,
After I do my QAS Upgrade, should my QAS DIR_TRANS point to /usr/sap/trans of DEV or PRD?
I am planning to point it to that of DEV, we will have dual Central Trans Directories,
one for 4.7 Landscape (/usr/sap/trans in PRD) for DVP-> PRD
and the other for ECC 6 (/usr/sap/trans in DEV) for DEV -> QAS
What do I do after PRD upgrade? should my DIR_TRANS for ECC 6 PRD point to /usr/sap/trans of DEV ?
Thanks!

if you are upgrading in a parallel landscape , you really dont need to worry about the transport directory of the 4.7 landscape.
as soon as you upgrade the DEV , i guess you can have a DIR_TRANS pointing locally
and you can make that the Central transport directory for the ECC landscape
As i said earlier , you need to keep track of changes that are performed in the 4.7 landspace after the DEV upgrade and make sure they are recreated(if necessary) in the ECC landspace as part of the Dual maintanence.
As long as you keeo track of the changes that are happening in the 4.7 landspace and manage it approriately , you are fine.
Planning would be crucial.
Gerard

Shared transport directory best practices?

Does anyone have any documentation / knowledge on using a shared transport directory - ie, BI, R3, SolMan, etc in the same '/usr/sap/trans/cofiles + data directories, or is it preferred to keep them separate?
Currently, our R3 system shares one transport directory across the landscape, but BI, SRM, and Solution Manager do not. While thinking about giving each of them their own shared directories (all BI systems share a directory, all SRM system share a directory, etc), I wondered if the preferred method is to have them all share a directory.
I would appreciate any input, thank you.
~TJ

There are different philosophies here, but mine is:
Keep them separate so that a transport does not accidentally get moved to the wrong system. I know that with QA worklist and workflow and other tools that can be incorporated to allow this to not happen, but there is always a chance that a transport gets approval but goes to the wrong system, as in SAP fixes.
Hope this helps.

Change STMS transport directory

Hi gurus,
I have a High Availability SAP ERP system (SAP ECC 6.0) as PRD server. We used an old server for DEV system (Host name = sapdev). These two servers belonged to a STMS domain.
Recently we made homogeneous system copy and created a new Development (PRD copy) system to a new server. the new servers host name is AthinaDEV. We created a new STMS domain, joining the new DEV and PRD systems. The problem is that transport directory in PRD seams to be
sapdev\sapmnt\trans\ and in DEV seams to be
athinadev\sapmnt\trans\. In both servers in Transport Tool I have configured TRANSDIR as
athinadev\sapmnt\trans.
How can I change the transport directory to PRD to look
athinadev?
Thanks in advanced

OK,
I added the profile parameter DIR_TRANS with the correct path to both systems and now both systems use
athinadev\sapmnt\trans as transport domain. All seems to be correct now (all checks return success) but I can't transfer any request.
For example: I have created a test ABAP program. I have created a request for that program. I released the request from SE11 transaction succesffully. But when I use STMS transaction I have the following situation: in import overview I can see both systmes and 1 request waiting. When I double click on PRD to enter to import queue the list is empty.
I have cheked the permissions on trans folder and seems to be ok (prdadm has corrrect permissions).
The two systems has connected with transport routes.
Can anyone help me find the solution?

Central transport directory

Dear all,
we are running ecc 6.0 (v5r4m0), with central transport directory.
How can i switch to local transport directories.
Thanks
Imran Hasware

Hi Imran,
ok, if you don't know how to remove and add links with RMVLNK/DEL or ADDLNK then you should not change anything - otherwise it it 100% sure, that everything is destroyed afterwards
You are having a totally different problem as you write:
/usr/sap/trans/tmp/****.LOC file. already in use.
=> there is a semaphore file still there, that shows, that a TP is running - most likely since 3 days, since you are facing these issues.
If no tp is running anymore, this is an error and should be deleted manually. This kind of file is there by purpose so that the other TPs wait in critical pathes of other TPs. This happens in unshared trans dirs the same way ...
=> you should delete it and import 1 or 2 TPs first and see all is fine - then you can import your 30 TPs in one step - exactly because of these kind of files, it CAN be imported in parallel and will not crash the system.
(unfortunately this process sometimes gets out of sync ...)
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

Cleaning Up the Transport Directory

Dear All
I want to clear the old files from the trans directory, for the same, i exectute the command on Dos prompt,in
Windows
in BIN folder
tp check all
it generate following error
tp version is :- 372.04.57 (release 700, unicode enabled)
kernel release 700
This is tp version 372.04.57 (release 700, unicode enabled)
E-TPSETTINGS could not be opened.
EXIT
Error in TPSETTINGS: transdir not set.
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
error in transportprofil (param missing, unknown,...)
the Transport tool setting, the parameter
TRANSIDR is set
ides\sapmnt\trans &
DIR_TRANS value is
ides\sapmnt\trans
so please suggest me How to Cleaning Up the Transport
Directory
Thanks
Ganesh

Hi Ganesh,
Please go through the below links.
Import of a request failing : ERROR: connect failed due to DbSL load lib fa
how to add request in the buffer
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/tp-finished-with-return-code-208-1433190
http://www.sapfans.com/forums/viewtopic.php?f=12&t=67602
Re: Import of a request failing : ERROR: connect failed due to DbSL load li
-Srini

Common Transport Directory Migration

Similar Messages

Maybe you are looking for