on 10-24-2013 1:03 PM
Hi,
We are making a SAP PI copy of the existing system.
Can you please let me know which activities or the components need to ce copied for doing this for
1.Server Set up
2.SLD
3.IR
4.ID
5.RWB(if needed)
Please guide me.
Thanks in advance
Hello,
why do you need a copy?
Generally, I would recommend to use transports in PI. So install or copy and setup your new system, transport all ESR content manually, configure transport routes in SLD to the new system and transport ID, too. SLD you'll probably manage centrally, anyway, so you'll have to do that manually, too. Copying doesn't make much sense, since you probably reuse the same Products and SWC and since you'll have to create everything related to your new system manually, anyway.
Regards,
Jörg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Jörg and Rajesh have rightly mentioned that system copy is not the best practice to follow.
However, if a system copy is the only solution, here is the response.
1.Server Set up
yes with changes to the host names, RFC destinations (based on connecting systems)
2.SLD
this depends upon your landscape whether you have central/child SLD or independant SLDs.
If central SLD, changes should be done there and child SLDs synchronized. If independant, you can create objects manually or export/import can be done
3.IR
yes... ID objects to follow.
4.ID
IR objects to be imported first.
5.RWB(if needed)
Dont think it makes sense.
No point copying the messages which have already passed through a system.
Hope it answers your question.
Ambrish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
it will be appropriate if you can provide the more details behind the copy as the solution varies based on requirement ...
However assuming if its a replication of client setup at your premise...
all you need to copy the SLD, ESR & ID content via export import...
if you have different business systems in your SLD for the same content still you can export and import however the business systems need to be setup in order for a successful import in ID..
HTH
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
As said this varies based on requirement...
SLD - Transportable are Product& Software Component, Technical & Business systems
IR - SCWV
ID - Configuration Scenario objects.
Note the objects can be exported and can be imported directly or transport route can be used...
Also sequence is important - first SLD, IR, ID..
HTH
Rajesh
Generally, all of them. Transport SWCV from ESR and Configuration Scenarios from ID. If you worked properly on that system before you should have all required objects in your transports this way. Especially in ID you could have objects not assigned to a Configuration Scenario. If you're not sure you can just select all objects manually and add them to one big transport.
Regards,
Jörg
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.