xi landscape

[Former Member]

Hi

I heared like in real time only one SLD instance is maintained for all DEV, QA and PROD boxes and different instances of IR, ID and RWB. Is this correct ?? Please correct if I am worng ??

For DEV, QA and PROD we use different application system or we will use only one system ?? If we use different application systems for each phase (i.e DEV, QA and PROD) after transporting how we will point our scenario to new application sytem ?? shall we manually edit communication channel ?? If we are doing like idoc-xi-file kind scenario shall we re establish all rfc destinations and import of meta data etc ?? How all these issues are tackled in real time scenario ??

thanks

kumar

[Former Member · Accepted solution]

Hi Palnati,

It depends on the client, whether he wants 3, or 2 or a single SLD.

In our project we have a single SLD because that is what SAP recommends(except in few circumstances).

Yes there are different instances for IR, ID , RWB for DEV,QA,PRD.

Now when we transport XI Objects,

No changes needs to be done for Integration Repository Objects.

For Integration Directory objects after we transport them we just need to change Communication Channel paramters and nothing else.

<i>Regarding pointing the schenario to new application system</i> when we transport to QA, for that we define transport targets in SLD.

Secondly as i mentioned above we need to change the communcation channel details to point to new system.

Cheers,

Sumit

[Former Member · Accepted solution]

Hi sumit,

thanks for your reply ! In your answer you mentioned

>>Regarding pointing the schenario to new application system when we transport to QA, for that we define transport targets in SLD.

Could you please explain what do you mean by transport targets in SLD ??

thanks

kumar

[Former Member · Accepted solution]

hey

>>Could you please explain what do you mean by transport targets in SLD ??

in SLD if u go in BS,under transport tab u can see the target BS which comes in handy when u move objects from Dev to QA and prd.

if u have maintained this target BS,the when u move ur ID objects to QA and PRD,the BS will automatically be changed to point to the IS of QA.

this saves u from changing the BS names manually thus saving u lots of time

thanx

ahmad

[Former Member · Accepted solution]

thanks ahmed !! I got the point

[Former Member · Accepted solution]

Hi Kumar,

Buzz if u still not clear..

Sumit

[Former Member]

Hey

>>I heared like in real time only one SLD instance is maintained for all DEV, QA and PROD boxes and different instances of IR, ID and RWB. Is this correct ?? Please correct if I am worng ??

as said by others,it all depends upon ur setup ,but in general we try for what u said,this helps in movin the objects from Dev to QA and prd,if ur using FMS to move ur objects,just create groups and targets for QA and PRD in SLD and when u move ur ID objects,the BS system name is automatically changed,u only need to manually feed user credentials,URL's,directories etc depending upon ur adapters.

thanx

ahmad

[moorthy]

Hi,

This guide will give u an insight into SLDs..

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/29b1f3ea-0c01-0010-2dae-cc64bb38...

and all Communication channels etc needs to be changed in each environment. Once u transport, source directory paths, RFC destinations etc will be blank in the target system, u need to manually configure for that environment then activate it.

Hope this helps,

Thanks,

Moorthy

[Former Member]

Kumar,

It all depends upon your clients requirements. But ideally I would suggest to have one SLD for Dev, QA and one for Prod.

When ever you transport you will not do change in your IR objects. But you will have to edit all the ID objects. All the ID objects you have to keyin manually because they may point to different locations.

---Satish