cancel
Showing results for 
Search instead for 
Did you mean: 

TMS configuration- Extended transport control

Former Member
0 Kudos

Hello

I would like to know if i need to use Extended transport control option to add new system to the transport domain. Here is what I want: I want to add a Sandbox to the transport domain (DEV is a domain controller) So everytime when the transports are relesased from the DEV it should go to the Sandbox Queu and QAS Queue as well. Right now its already configured to go the QAS Queue. Sandbox is the copy of DEV and each has 7 clients. I have few questions:

1). Do i need to create Consolidation Route from DEV >> sandbox? if So do i need to create new transport layer or i could use the same ZDEV transport layer?

2). Can anyone tell me if its better to user the Extended transport Control option or not. what steps i need to take?

3). Currently the transport Group used is /abc/ from DEV to QAS , Can I just add additional target system/clients in that Transport Group or i need a new one?

If someone could give me some idea on how to approach

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

1. No. You can use the same ZDEV/SAP transport layer if you are planning to use the target group.

2. It has lot of advantages(look at the link below or search the help.sap.com) and you can define the systems for parallel consolidation with clients.

3. You can add the sandbox to the same target group as your quality.

Link: [http://help.sap.com/saphelp_nw70/helpdata/en/2e/709533ef9b11d184850000e8a57770/frameset.htm]

Former Member
0 Kudos

Vijay,

Thanks for your reponse. So, you should i dont need to create Consolidation route from DEV to Sandbox, how do I create a transport route then? This is what needs to be done as per your suggestion, please correct me if i am wrong.

- Add the Sandbox System/Clients in the already existing Target Group (/abc/).

- Drag and drop the New System (sandbox) to the bottom pane of Graphical Interface >> Change Mode> Draw a line from DEV to Sandbox with pencil> create Extended Transport Route (Consolidation Route) from DEV to Sandbox.

- Distribute and activate the changes,

am i missing anything above?

thanks

former_member227283
Active Contributor
0 Kudos

Hi,

Most of the things are correct, but one correct.

Drag and drop the New System (sandbox) to the bottom pane of Graphical Interface >> Change Mode> Draw a line from DEV to Sandbox with pencil> create Extended Transport Route (Consolidation Route) from DEV to Sandbox.

You will not drag a line from DEV to SANDBOX, where as you will drag a line from Tranport target group to Sandbox.

Thanks

Anil

Former Member
0 Kudos

Anil ,

Thanks for your helpful answer. As per your suggestion I have dragged the line from 7 Transport group (for 7 clients) and 1 SAP Standard Transport layer to Sandbox. Once I did that i got the pop up with the already defined system/clients (DEV in this case)..so i just inserted another row for each target group and added Sandbox system /Clients. After that i just distributed and Activated the conifuguration. However, I am not sure if I still need to define the Consolidation Route from my DEV to Sandbox systems, If so what should i use as the Transport layer ..should i use ZDEV (for DEV) or Z<client> since there are 7 clients with 7 Traget groups. please let me know how i need to approach with creating Transport routes for the Sandbox (this should be Consolidation system). QAS and Sandbox i think would be considered as consolidation system. Please suggest.

thanks

former_member227283
Active Contributor
0 Kudos

Hi,

Read below how ti should be.

What i understand in your landscape.

1. You have 3 system landscape i.e DEV, QAS & PRD.

2. You have 1 transport target group create as /ABC/

3. You have to use same transport Z and standard layer for Sandbox and QAS.

if above are true, then you TMS should be as follows.

1. DEV should i have connection to /ABC/ transport target group.

2. Then connection move fom /ABC/ to QAS and QAS to PRD.

3. You have to add your sandbox in TMS domain i.e DEV is your domain controller.

4. After adding the system in TMS domain. you have add manual conslidation route between /ABC/ transport target group to QAS system by using tool ADD TRANSPORT ROUT.

5. Activate and distribute the changes.

Thanks

Anil

Former Member
0 Kudos

Anil ,

Thanks again. I am only trying to add new system (Sandbox) to already existing Transport domain. Let me explain in more detail about the existing configs:

-DEV system (Domain Controller) is already hooked up to QAS (consolidation route). So everytime the TR is released in DEV it should also got to Sandbox Quues in parallel to QAS's Queu.

- right now it goes to all clients in DEV as well after the transport released. ZDEV is the transport layer and Z100, z200, z300....and so on are connected to the corresponding Transport Group-/ dev100/ , /dev200/ ..and so on..

- My QAS already hooked up so i dont need to do anything with it.

So far i have connected Transport groups /dev100/./dev200/ ...to Sandbox by including the Sandbox sytem/Clients in the Transprt group dialogue box for each . My question is how do i define the consolidation route from DEV to Sandbox (not QAS)? Should i drag the line from DEV system to Sandbox to create consolidation route and use ZDEV as transport layer? Since ZDEV has already been used to define Consolidation route to QAS from DEV, will that be a problem or not?

Thanks

former_member227283
Active Contributor
0 Kudos

Hi,

It seems there is some confusion between transport group and transport target group.

Just clear me 1 point.

Is there any tyransport target group between DEV and QAS or there is direct connection between DEV and QAS.

Thanks

Anil

JPReyes
Active Contributor
0 Kudos

I think you could be making thinks a lot more simple by just adding a delivery route from QAS to your sandbox. Meaning that anything that has been imported to QAS will be delivered to both your PRD system and your sandbox.

Regards

Juan

Former Member
0 Kudos

Anil,

Yes, there is a Transport Target Group between DEV and QAS (/QAS<client>/) with Z900 transport layer and also for each Clients within DEV (Z<Client>) and for standard objects (SAP).

- ZDEV is the Transport layer for DEV system and there are additonal tranport layers created for each clients within DEV systems .....z100..z200..so on.

Juan,

Thanks for your suggestion, we would like to keep Sandbox in Synch with the DEV , therefore whatever TRs gets released fromn the DEV it should also go to the Sandbox Queues in parallel to QAS queues. So , i thought i have to define the Consolidation route from DEV> Sandbox (simliar to DEV> QAS). Please let me know if this is something that can be done by using delivery route from QAS> Sand as you suggested.

- If Consolidation route is used , in my case do i need to create a new Transport layer (aside from ZDEV)?

Thanks,

Former Member
0 Kudos

Hello All,

I have linked two domains (sanbox and DEV) sytems and created Transport routes between DEV and Sandbox by adding Sandbox sysem in the Transport Target Group. So, now whevever TR is released in DEV ..its supposed to go to the Queus of QAS (which it does) and Sandbox Queue (not happening). I activated/distributed all configs, STMS checks everyting fine.

Also, Sanbox is in different network than (DEV,QAS,PRD). Currently consolidation route already exist form DEV >> QAS with the Target Group .../ xyz/ ..so I added the Sandbox System/clients in the target group along with QAS and other DEV clients.

After Releasing TR in DEV, the TRs is only getting to the import queue of QAS (like it should) but not goign to the Sandbox in parallel (as desired). I checked the cofiles/datafiles in Sandbox ...and they are getting created either. Transport log in DEV shows everything was imported successfully when it was exported(released). The RFC connection is working fine from dEV to Sandbox.

- Since two domains are linked and they dont share central directory, is that the reason why data files/cofiles not transported automatically ? i thought they would be FTPed internally when we release the transport. Please tell me anyother reasons why this could be happening.

Thanks,

Former Member
0 Kudos

Anyone please???

Former Member
0 Kudos

You need to have a common transport directory for both your DEV landscape and your sandbox to see it added to the queue.

STMS has no automatic mechanism to ftp it.

But check the link below for guidance for manual adjustment.

Link: [http://help.sap.com/saphelp_nw70/helpdata/en/06/ea457a12a711d3b46f006094b9ea64/content.htm]

you need to use a script to FTP it for automation.

Former Member
0 Kudos

Vijay,

Thanks for your helpful answer. I undersand the concept of adjusting the import queue if transport Dir are not shared, we need to click on that little green zig zag button next to tranport inorder to transfer cofiles/datafiles. But in my case the Transport (with green arrow) was not even going to the import queue of Sandbox. Now, i just found out that when i release the Transport in DEV and go to STM in DEV >>chose the Sandbox queue there, when i refresh the Queue of Sandbox from DEV and then go to the Sandbox system and refresh the Queue there as well, this way i can see the transports in Sandbox queue for some reason. However, if I just release it in DEV and go to the sandbox queue and refresh sandbox import queue, I dont see any transports here unless i refresh it DEV>sandbox import Queue....its strange. can you please tell me if its normal?thanks

Former Member
0 Kudos

I haven't tried this scenario yet.

Probably adjusting the Sandbox Buffer from the dev system adjusting the buffer becuase of the trans directory exists with your dev system.

When you adjust from your sandbox, probably its reading from your current buffer.

This doesnt sound odd to me.

If someone has this scenario in their systems, he or she can update in this thread.