cancel
Showing results for 
Search instead for 
Did you mean: 

Query - /usr/sap/trans

former_member759680
Contributor
0 Kudos

Hello,

We just installed our QA system. The question we are faced with is whether we should mount the /usr/sap/trans from DEV on QA. OR we can use QA's own /usr/sap/trans, because when we configure TMS, the files will be automatically FTPed by SAP to QA from DEV.

So, what are the advantages of mounting the same /usr/sap/trans in QA, furthermore, how should we go about doing the same. I mean should we just delete the existing 'trans' directory and mount it from DEV ?

Thanks in advance.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

Could you tell me what permissions and groups did you assigned to /usr/sap/trans file? because I´ve the same doubt.

Thanks a lot and best regards, Sapera

raoul_serra2
Participant
0 Kudos

Hello,

There are many advantages of having an nfs mounted shared /usr/sap/trans directory for all the systems of a landscape regardless of having a landscape composed of only DEV and PROD or more complicated

(Sandbox, Development, Test/Quality, Training, Production)

- one location to manage for disk space requirements

- no file transfer waiting time

The bigger advantage is probably: easiest and less maintenance work especially with Stack/Patches upgrades, all SAP files uploaded once in /usr/sap/trans or /usr/sap/trans/EPS/in

When a DEV system is patched with SPAM (for ABAP) or JSPM (for Java) every thing will be ready and identical for the next system in the landscape to be patched

Another possible advantage would be to make it easier to implement STMS Transport Automation

with usage of Approval Queue

And finally in case of full database copy, system refresh, homogenous system copy,

it will be easier to have that trans directory already shared

Kind regards,

Raoul

Former Member
0 Kudos

Hi all,

Sorry if this question would seem out-of-place given that the initial question has been answered. Suppose that we have a global shared NFS mounted /usr/sap/trans directory for all of our SAP systems (ie, several transport domains accessing the same /usr/sap/trans directory), would somebody know how we should setup the file system permissions for the trans directory and all subdirectories under it? Normally, we would have it as follows:

/usr/sap/trans

permission: 775

owner: <sid>adm

group: sapsys

/usr/sap/trans/*

permission: 770

owner: <sid>adm

group: sapsys

/usr/sap/trans/.sapconf

permission: 775

owner: <sid>adm

group: sapsys

However, since we have several domains and several <sid>adm users accessing the NFS mounted /usr/sap/trans directory, what would be your recommended configuration for the permission, owner and group? I believe the group should still be sapsys since this is the common group for all SAP OS users but then who should be the owner and do we need to modify the file system permission? Thank you in advance.

All the best,

Albert

Former Member
0 Kudos

Hello Gautam,

Every System has its own trasnport directory and need not to mount each other. When you wil define the transport route it will captured all the system information into TP_DOMAIN_SID_PFL file, there you can see the information of all the system on a particular domain.

Another thing is when yo configure a trasnport layer and define the consoidation and delivery path the file will be moved directly in the trans directory of another server, yo need not to move the file manually.

Hope this helps.

Regards,

Subhash