Queries regarding Approach to me made for a XI Project

[Former Member]

Hi Folks,

I have few queries :

1. How to configure SLD in a project?

<b>--> Should a company go for single SLD for all Dev,QA or PRD or separate SLD for all..?

What are the pros and cons in each case..?</b>

2. What is the best approach :

<b>a.> Developing all scenarios in one Software Component ?

b.> Developing each scenario in different Software Component ?

c.> Developing same Legacy System(or business process) related scenarios under one Software Component and other legacy related scenarios in other software components and further differentiating the scenarios by namespaces in IR ?</b>

How it will affect the transportation ?

Let me know the pros and cons also..

<b>Will you also help me in figuring out the deciding elements for making the decisions pertaining to above cases..</b>

Regards,

[Shabarish_Nair · Accepted solution]

<i>1. How to configure SLD in a project?

--> Should a company go for single SLD for all Dev,QA or PRD or separate SLD for all..?

What are the pros and cons in each case..?</i>

>>>>

ref the planning guide to help you

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0a1a8fb-0527-2a10-f781-8b67eab1...

<i>a.> Developing all scenarios in one Software Component ?

b.> Developing each scenario in different Software Component ?

c.> Developing same Legacy System(or business process) related scenarios under one Software Component and other legacy related scenarios in other software components and further differentiating the scenarios by namespaces in IR ?</i>

>>>

refer the series of blog part 1 is as below,

/people/thorsten.nordholmsbirk/blog/2006/07/25/structuring-integration-repository-content--part-1-software-component-versions

[Former Member]

An excerpt

This is advisable to run Single SLD by SAP.

The cost of running the SLD infrastructure increases with the number of SLD instances. In particular,

adding a second SLD involves additional costs for synchronizing data between these two

instances. From a cost perspective, it is preferable to configure a single SLD.

The following factors can make a multiple-SLD architecture necessary:

• Legal constraints

• Company rules

• Network constraints (for example, firewalls, availability of resources)

Thanks

[Former Member]

Hi

Share you email id in your business card

Thanks

[Former Member]

Hi

Centralized SLD

-All systems and products at one place.

-No need to change in all systems,a change is reflected in all.

-Therefore no replication required.

-Load maintainance is difficult.

Different SLD for Dev,QA,Prod

-Easy Maintainance

-Load Balancing

-A change in one is not reflected in other therefore problem tracking is easy.

Refer to a similar kind of discussion

Thanks

[Former Member]

Hi Shabarish,

Thanx for the quick response..

Points rewarded...:-)

but i am not able to access Planning guide..getting the message that file is corrupted...what to do..?

Do you have planning guide ..? If yes then can you share it with me ?

Regards,

[Shabarish_Nair]

hmmm i am able to access the document though.

in any case send in a mail to shabarish.vijayakumar@wipro.com i will share the doc with you.