How to Share Transport directory in Landscape

Hi,
I want to know how to make transport direcory shared in windows and mounted in unix.......Please tell me the Step wise procedure.
Thanks in advance.
paramvir

Hi,
For this u kan use the utility cygwin.
http://x.cygwin.com/docs/ug/setup-cygwin-x-installing.html
Above is the link for the installation of the file . Once you install the file you can get it linked with the filesystem you want on the unix.
After getting the file system on unix you can get it mounted on the other system on unix.
Thanks
Rishi Abrol

Similar Messages

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

How to prevent users from creating new folders in share folder directory?

Hello guys
I'd like to know How to prevent users from creating new folders in share folder directory but still keep their power of creating new folders in their personal 'my folder'?
I tried changing the 'manage privilage ---- create folder' to deny certain user accounts, but by doing so, it also stops the user from creating new folders in their 'my folder', which is not good..
I also tried going into these share folders and tried different access types such as 'change/delete', 'read', 'traverse folder' etc, but none of it work ideally. The 'change/delete' access still allows them to create new folders, 'read' access prevents creating new folders but also take away their power of saving reports..
Any thoughts on how to take away their ability to ONLY create new folders in share folder areas without affecting their other privileges?
Please advise
Thank you

Easy, on the shared folders root folder only give them 'read' or 'traverse folder' but on the the folder inside the shared folders root folder give them 'change/delete'. That means they can change anything inside those folders but not create any folders at the shared folders root level.

How do i transport personalisations to different landscapes

Hi All,
I have made some personalisations to some webdynpro for java iviews in dev system .
1.How do i transport those personalisations.when i transport iview will personalisations also gets transported or i need to go to individual systems and do it.
2.I have done the personalisations using a test user (whose userid is mapped to IT105 of real user) ,then changes are getting reflected only for test users not for real users.
How do i solve these problems
Thanks
Bala Duvvuri
Edited by: Bala Duvvuri on Aug 21, 2009 3:58 AM

Hi Bala,
Have a look at [this|http://help.sap.com/saphelp_nw70/helpdata/en/42/ed3ce7f8593eebe10000000a1553f7/frameset.htm] page (though i feel you must have searched already). I think any personalization done by the administrator gets transported when the iview is transport from one landscape to another? What exatly isnt working in your case?
Thanks,
GLM

How to import transport of copies to productive systems

Hello,
I have been experiencing a problem that even the guys from admin could not solve (yet). I should say I work in a development team.
Imagine you have two landscapes, one DEV-QAS(1) to develop big projects and a normal DEV-QAS-PRD(2) landscape where my objects will be imported. After a new group of objects is finished in (1), we ask to import the workbench request in the STMS queue of DEV(2). After this, and after some small test, we create a transport of copies in DEV(2) where we include the first transport, release it and import it to the QAS(2) queue. After the tests in QAS(2) the idea would be to import the transport of copies to productive system PRD(2). But it does not work...
In STMS queue for PRD(2), there is no entry for the transport of copies. Also, when I tried to add the transport request to the import queue (via menu -> Extras -> Other requests -> Add), I get an error message stating that no co-files where found for the transport.
Does anyone know this problem? I suspect it can have sothing to do with the use of a transport of copies, but, if I don't use this kind of transport, how can I get objects from other systems to production?
Thanks in advance.
Davide Sepanas, Portugal

Davide,
Re your latest questions:
> 1) Why this problem with transport of copies doesn't happen from DEV(2) to QAS(2), since these systems are also not in the same transport directory?
>
I think the answer is in your original problem description:
we create a transport of copies in DEV(2) where we include the first transport
>
When you create a transport of copies you must indicate a terget system and I suppose you enter QAS(2) there. In that case the TMS will add the request to the import buffer of the target system when you export the request from DEV(2). I understand that you never have to add transports of copies to the import buffer of QAS(2) manually, which proves the TMS does this for you. However, for further imports into systems that are not designated as target system of the transport of copies, like PRD(2), the TMS will do nothing of the sort and you must add the request to the queue yourself - which in your case also means you have to forward the transport files first.
> Can we assume, then, that, where I was working before, all three systems were configured in the same transport directory, avoiding thus the problem with the transport of copies requests?
Yes, and that is the most common way of setting up the transport system. Having separate transport systems really only makes sense when sharing the transport directory between the dev, qas and prd systems (via NFS for UNIX, via network shares for Windows) is not possible, either because there is no local network between the servers or because some security policy forbids it. I'd advise you to certainly ask the question to your system admin.
Regards,
Mark

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 Configure Transport MAnagement system in CHARM

Hi
How to Configure Transport MAnagement system in CHARM? Here our requirement is when ever a change request approved in the background Transport request should be created automatically. We have configured all the Transport Routes in our lanscape.
Can any one tell me the detailed process? If you have any Configuration document please share it to me
Points will awarded for helpful answer
Thanks
Bhaskar

In a two system landscape is it necessary to make development the domain controller always?
No such compulsion as such exist(correct me if wrong),however why you want to make production your domain controller?
This is not recommended.
Regards,
Ashutosh

How to Setup Transport on Windows Server

Hi guys,
I'm trying to setup a transport between two systems. I have done it inthe past in Unix but never done it in Windows. It is kinda difficult for me in Windows.
Can you please help me understand the setup.
Server 1. >> PC1
Server 2. >> PC2
I have made PC1 a domain controller and shared its /usr/sap/trans to PC2. Also updated TMS parameters in PC2 pointing DIR_TRANS to PC1/usr/sap/trans, but It is not showing up in PC1 (domain controller)
Your help appreciated!!
Thanks,
Afi

On the Server where you want to share \usr\sap\trans for the landscape( I assume Server1 or PC1 in your terms), login as windows domain admin ( or with admin rights) --> right click my computer --> Manage --> click on Local Users and Groups --> Double click on administrators --> and add users of SAPService<SID> of the other server ( your Server 2 or PC2) and clock pk Ok.
This should resolve the problem.
Concept is, giving other server to read and write access to shared drive of Transport directory. There can be no. of days do implement it depending on in House Windows Skills and Secuirty audits, but the above method works.
Thanks,
Krishna

How to use Transport Files

Hi All,
I have generate Transport files .co files and .dat files while transport the package.The package contails Function modules.My question is What is the use of this files??How can the non sap and sap customers use this files ? If any customers need to use this Function modules what is the best way to sent them as the files and how they use?
Thanks in Advance.
Madhu.

Hi Madhu,
Glad to know that now you've the cofile and datafile.
I have generate Transport files .co files and .dat files while transport the package.
I hope you are referring to the cofile and datafile and the correct naming convention for these files are
cofile - K9<5digit>.<SID> found in /usr/sap/trans/cofile
datafile - R9<5digit>.<SID> found in /usr/sap/trans/data
Now these files are generated when you release (i.e export) the change request in the system. cofile is the command file which contains what action to be done for the particular transport request. datafile contains the actual data e.g your function module.
What is the use of this files??How can the non sap and sap customers use this files ? If any customers need to use this Function modules what is the best way to sent them as the files and how they use?
Transport management relies on this files to import the changes to the subsequent system. now these files are generated only when you release/export the change request in DEV system. if there are no files at OS level transport directory, from where SAP would read what to import in the QAS system/next system?.. so these files give that info to tp/r3trans.
Generally, in normal case its not required to play with datafile and cofiles as in customer has the landscape in place (and most develeopment is done in DEV system, and moved further), but in some case, customer develops new stuffs in a system which in not in a landscape, and they want the same developments in another system - here they can just transfer the required datafile and cofile in the target system and then import it.
Hope this clarifies your doubts.
Regards,
Debasis.

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.

Same transport domain. different transport directory, possible?

Hi SAP folks,
A quick query, I work on multiple systems within a single SAP transport domain. Recently we have requirements to move 2 non-ABAP systems to a different transport directory while keeping the rest intact.
The reason for this is we are doing CTS+ for the 2 non-ABAP system and do not want to share the transport directories for the rest of the ABAP system.
Please advise if this can be done and how?
The following link for SAP suggested that it's possible but stop short of how to do it.
http://help.sap.com/saphelp_nw04/helpdata/en/c4/6045377b52253de10000009b38f889/content.htm
Anyone done similar setup? care to share?
Thank you.
Regards,
Jansen

Hi,
You can do this very well. First you should remove the two systems that you wanted to configure for CTS+ from your existing transport domain. To do this, login to your existing transport domain controller and delete the systems you wanted to remove from transport domain.
To perform this:
STMS --> Overview -> Systems -> < choose the system u want to delete> -> SAP Systems -> Delete. Confirm the deletion and save and activate the changes made to ur configuration.
And then add your Non-ABAP systems you wanted to configure for CTS+ using the domain controller you decided for CTS+.
I hope this help you to perform your action.
Best Regards,
Vasanth Govindaraj

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

How to share library on same mac with two users

please provide step by step instruction on how to share library for my two girls on the same computer. my older daughter already has itouch and library. Now for the holidays got younger one an itouch also and want to share the library.
i am a novice with computers...so please help

just in case you haven't already resolved this, see: http://support.apple.com/kb/HT1203
To share your music with other accounts on the computer
On Mac OS X
1. Quit iTunes.
2. Locate your iTunes Music Folder. It is stored by default in ~/Music/iTunes or ~/Documents/iTunes/.
These folders cannot be accessed by other accounts on the computer. In order for other users to be able to access your music, you must move it to a publicly accessible location.
The Public folder in your home directory (~/Public), or to another folder outside your home directory that other users have access to, such as /Users/Shared.
Tip: The tilde "~" refers to your home folder. For more information see Mac OS X: Using Your Home Directory.
3. Drag the iTunes Music Folder to a publicly accessible location.
Important: Do not move the iTunes folder, the iTunes 4 Music Library file or the iTunes Library.xml file.
4. Open iTunes.
5. From the iTunes menu, choose Preferences.
6. Click Advanced.
7. Click the Change button.
8. Navigate in the Change Music Folder Location dialog to the location of your iTunes Music folder.
9. Click Choose.
Repeat these steps for each account that is sharing music with other users.
Note: If multiple users of a computer are storing music in one folder, duplicate song files are generated when a user imports music from CD that has already been imported by another user.

How to share/manage UWL/KM and collaboration with TWO consumer portals?

I'm working with a customer who is configuring a large enterprise landscape consisting of 2 federated portals with the two consumer portals sharing info.
Federated portal A is the primary corporate portal with respective producers.
Federated portal B is a regional producer portal with multiple back end producers.
IF they wish to configure UWL, I realize they can do this on each consumer portal. But how can someone logging into portal A see all their work items from UWL on A and UWL on B without creating two iviews (one for each UWL)? I bascially want to be able to share the UWL from one consumer portal to another. I haven't seen this in any docs, though. Anyone have experience with this?
Likewise, what is the best way to share collaboration rooms and other related services? Should they be configured on the consumer side of each federated portal, and if so - the same question arises - how to share the collaboration data between the two consumers.

Hi David,
we faced your first issue some months ago and found out that there is only the possibility to use 2 UWL iViews.
Maybe this has changed in the last releases.
HTH,
Carsten

How to install transport request files into the SAP system

Hi Experts,
I want to install transport request files into my SAP source and target system . I am from BW/BI background so can anyone help me out with the step by step procedure for the above installation.
Thanks in advance
Regards
Shiva

Hi,
What I understand is, you want to transport request from one server to another.
for example, Development to Qualtiy or Quality to Production.
For this your transport system must be configured. Please search help.sap.com or google for "How to configure Transport System (STMS)".
If you want to copy transport request from one system to another system which is not in your landscape, you need to physically move/copy transport request (cofile and datafile) to the target system in /usr/sap/trans/cofiles and /usr/sap/trans/data
Then import that request using SCC1.
You can alos perform TEST import for result.
Regards.
Rajesh Narkhede

How to Share Transport directory in Landscape

Similar Messages

Maybe you are looking for