SLD Dependency,

Hi All,
I Have one question, please give me Replay with brief Explanation.
Question is:
What is the SLD Dependency.
What is relation between Product, Software Components, Technical System and Business Systems?
Thanks And Regards
Reddy,

Hi,
SLD:
The System Landscape Directory of SAP NetWeaver (SLD) serves as a central information repository for your system landscape. A system landscape consists of a number of hardware and software components that depend on each other with regard to installation, software updates, and demands on interfaces.
- so talking about the working of an SLD, here if any information is required for the integration server regarding the systems(logical or physical) and the software (installed products) it refers to the SLD.
- to tell you about the other features it has....it captures the dimensions of the system landscape like solution dimension, transport dimension and technical dimension.
- putting it in short XI IS A CLIENT OF SLD
Also go thru this link and understand more about SLD <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/31/f0ff69551e4f259fdad799a229363e/frameset.htm">System Landscape Directory</a>

SOFTWARE CATALOG:
The SLD contains a Software Catalog of all installable SAP products and software components. The Software Catalog includes information about support packages and dependencies between the products and software components. This information is the basis for the description of the system landscape.
Also go thru this link and understand more about Software Catalog <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/a2/2999ef97ea2b4790165f9ca5c05c41/content.htm">Software Catalog</a>
TECHNICAL SYSTEM, BUSINESS SYSTEMS, SOFTWARE PRODUCTS:
Technical system correlates the software to the physical host on which it is installed
Or in other words Technical systems are application systems that are installed in your system landscape.
- they are actually the basis for defining the business systems.
- we assign a technical system to a business system to help the SLD make the appropriate association.
- the software products used by the business system are got from the technical system definition.
- to note 1 technical system can have more than one business system assigned to it....and as told the SLD make the appropriate association between them.
Also go thru this link and understand more about each of it:
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/24/8fa93e08503614e10000000a114084/content.htm">Technical Systems</a>
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/42/c817d9d2296bb2e10000000a1553f6/content.htm">Business Systems</a>
<a href="/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation Preparation</a>
Regards,
Abhy

Similar Messages

Component dependency and sld dependency

hi all,
i need to create,component dependency and sld dependency.how to create and wht is the use of these dependencies.
regards,
AVR

Hi,
it's explained here:
http://help.sap.com/saphelp_nw04/helpdata/en/44/63977c40b54ddfe10000000a1553f7/frameset.htm
Regards
Patrick

SLD should be attached to which WAS?

We are testing SLD with and without an XI configuration in a test landscape. Would appreciate if someone can guide us to SAP's recomendation or their own experience about where to attach SLD to. Our choices are SLD on it's own WAS if we are not doing XI for the first go round. SLD on XI WAS or SLD on R/3 WAS.
As far as number of SLDS in a landscape...reading other messages it looks like the best way is to go with one DEV/QA and one production SLD. HA on PRD SLD is also recomended. We are using SLD on WAS 6.40, ECC5 and EP 6 on 6.40
Thanks,
Jimmy

Hi James,
From my experience, the location of SLD depends on the number of systems you have in your landscape that will use it actively.
You should install it on a system that is almost up and running nearly everytime and doesn't requires restart frequently.
If you have a lot of systems, I will suggest have it on a seperate WAS. Reason being if you have to restart your XI server or R/3 server everytime you bring down SLD as well which will impact all other systems that use this SLD.
Hope this helps.
Regards,
Shubham

SLD in a central insance

Hello experts, my question is about where to direct the SLD when you are configuring the Solman, right now we are doing the initial configuration (in a DEV instance), and we are ponting the SLD to the Netwaver Portal (DEV) but for some problems we got to reintall the Portal so I would like to know what is better for an organization? pointing the SLD to the Portal (DEV)?, Portal (PRD)? or to the Solman itself?.
(Some time ago a SAP consultant told us to point the SLD to the Portal)
Thanks for your answer,
Paul Hurtado

Hello there
What Mateus says is correct where you point and locate your SLD depends on the landscape
and how the SLD will be used
The SLD that is used by Solution Manager or is on the Solution Manager J2EE is traditionally the central SLD
- containing all systems from all sources (data suppliers, other SLDs etc)
You should be careful doubling up SLD useage - i.e have more than one client like Solution Manager and XI using
the same SLD - some applications like XI require the SLD for runtime (at least this is generally the thinking although
it could also be that clients have specific requirements that may conflict with each other) and thefore need a local
dedicated SLD. To give you an example -->
Solution Manager J2EE might be allowed to be brought down or restarted whenever required - there is maybe only a small user group notified or affected if however you using Solution Manager J2EE SLD for XI purpose - the consequences of this flexible downtime policy for XI could be severe
Best wishes
Stuart

Regd Data type enhancement

Hi Experts,
I have a 3rd party to Proxy scenario.The proxy strucuture is a standard structure , and i have created a data type enhancement
for some custome fileds.
its like : SWCV1 : contains the standard proxy
SWCV2 : contains the data type enhacement.
There is a SLD dependency created between SWCV1 and SWCV2. so i can see in SWCV2 the basis objects for SWCV1.
In Abap the append strucuture is created.
Now the issues is while mapping : My source structure passes this enhacned fileds, and i need to map those fileds and call the
proxy.So for target strucuture , which structure i need to select, suppose i select the proxy strucutre from basis object under
SWCV2 (it shows the added fileds so that i can do the mapping) and i can do the mapping IR stuff is fine.
But when i run the configuration should i select receiver Message interface from SWCV1(which doesnt shows the added fileds, or SWCV2 ..actually i cant see Basis objects to select from SWCV2)
My doubt is if i select SWCV1 and finish configuration , the proxy call will happend with SI from SWCV1 which doesnt show the added fileds , then how the fileds will be passed to proxy?
If any one have doen this kind of scenario?
Regards
Srinivas

Hi VJ,
Thanks for the inputs, but i still have a query regarding the use of different service interfaces in Interface mapping and
at the configuration tme (from different SWCV).i believe this is the reason that i am not able to post message successfully from saop tool and getting "missing response". after doing this way.(without enhancements the serives call is happening fine).
As mentioned ,IN Integration Repository i will be using the Service interface from the basis objects under SWCV2 so that i can map the extra fields.
but while selecting the inbound service interface in configuration time i will choose the standard service interface from
SWCV1.
Can you please explain how we can have two different service interface referenced one in IR and and different one in ID and still this work.
@ Sathis , I am doing the enhancement in a similar way as mentioned in the link.
Regards,
Srinivas

Dependency of SWCV in XI-SLD

In XI, In Integration Repository, in a software component, i need to use a RFC structure(Imported Objects-RFCs), which is in a different software component,
so, i created a dependancy between the two software component in the SLD,
but i could not find the Baisis objects tab in my Software component...
I m also not sure which type of dependancy i need to apply....so i used all the three.........Build time, installation time and metadata request.....
what is the difference between them

Hi,
so, i created a dependancy between the two software component in the SLD,
why do u wnat to create dependency between two software components. cant u reimport RFC structure..
At build time describes the context of any build process, like the compilation of sources and the packing of archives. Requirements at build time list external resources needed for the build.
For example, a software component C1 needs software components C2 and C3 to be built. Here, the build of C1 does not work without C2 or C3 to be built first. On the other hand, the build of C1 does not need any other software component, except those required implicitly through C2 and C3.
At installation time describes the context of the installation process. This process may be the first installation or an upgrade to a newer version. Requirements at installation time list external resources needed for the installation. The installation includes a basic getting started.
For example, a software component C1 needs software components C3 and C4 to be installed. Here, the installation and basic usage of C1 does not work without C3 and C4 to be installed first. On the other hand, the installation of C1 does not require any other software component to be installed first, except those required implicitly through C3 and C4.
The getting started part of the installation is in the responsibility of the software owner. It might include just the start ability or the capability to use some kind of functionality. In each case, the at installation time requirements define the minimum preconditions for the installation.
At meta data request describes the context of a process requiring external meta data in an installed system. An example is the content of the XI repository containing the definitions of services and interfaces. The XI content is used by the software components implementing the services and interfaces (in ABAP or Java).
Regards,
pradeep A.

How to define dependancy between sowtware comps in the SLD

how to define dependancy between sowtware comps in the SLD,
i have a software comp, in the IR, where i import all RFCs and IDOCs, so that they can be used across all software comps in the IR,
since, IDOCs imported in one software comp, cant be used in another s/w comp,
i need to create that dependancy..............................
how can i mention the dependancy in the SLD....

Hi,
Please read the Rules OF Engagement,
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement&

Do not use words in capital letters and any of the words: urgent, quickly, burning, etc in your message. Especially not in the title! This just irritates and does not help you get to your goal. From our side, we definitely do not answer faster when we see these words.
The same goes for such things as ??? or !!! in appends. In the English language one ? or ! is sufficient to terminate a sentence. 
Answering you question, Say you have 2 SWCV's. SWCV A and B. All objects imported in SWCV A should be visible in B. In this case, go to SWCV B and in this, Go to the Dependency Tab , and Select SWCV A here as the dependent Component.
In your IR, Clear SLD Cache and Reimport the 2 SWCV's into the IR and now you will see the Basis Objects in SWCV B. All the existing objects will not be affected as a result of this reimport into IR.
Regards
Bhavesh

SLD: Usage dependency

What is the advantage of linking "usage dependency" in a software component version? I'm aware that this process automatically includes objects from other s/w component. But how this is used in real life integration? An example would help in understanding better. To stress the question, lets assume component_B (contains SAP IDOCS MATMAS, CREMAS) is included as "basis components [result of usage dependency]" in components C to Z. If a segment is changed in MATMAS IDOC in source SAP system what are the steps to import the new segment into XI IR, SLD for components C to Z. Is it a complete redo or shortcut exists! Thanks in advance.

Hi,
have a look at my weblog to understand:
/people/michal.krawczyk2/blog/2005/08/26/xi-are-you-independentfrom-your-dependencies
Regards,
michal

Component Reuse - Usage Dependency in SLD

Hi there,
I have an issue reusing objects in the repository. I defined a usage dependency at installation time from component H to component B. I want to reuse interfaces from B.
Afterwards I reimported both B and I into the rep. I cleared tzhe cache, I refreshed and restarted the repository - but I still do'nt see the base objects from B in H - did I miss sth.? We're useing SP14.
Thx in advance,
helge

Hi Michal,
I have an issue for how to transport the usage dependency objects from Development to Consolidation (QA).
We have done the usage dependency in the SLD for one swcv and after reimporting it into DEV from SLD , we can see the node basis objects but we are facing the problem in transporting the objects under basis objects of our new swcv to Cons(QA). other objects under the namespace of our swcv is already transported to QA.
If you have some idea then pls. let me know.
Regards,
Gopesh

Dependency bw SLD and Integration Repository

can you explain how Dependency bw SLD and Integration Repository is created???

In the post installation tasks, the dependencies are added via ABAP (sldapicust and SM59) and Java (exchangeProfile and Java Admin Console)
This link shows the conenctions between ABAP and Java to SLD
http://help.sap.com/saphelp_nw04s/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm

Error in Updating SWCV SLD Info

Hi
When i try to use the 'Update SLD Information' under tools in the enterprise repository i get the following error -
GUID of software component version in SLD has changed To import the software component version with the new GUID, create a new software component version
Why does this occur and what can be done about it?
Thanks
Riaz

Hi,
1. In your SLD of dev, do you have the same GUID for this SWCV ?
if yes, you should do a clear cache of your IS (PI web page -> administration -> cache -> etc..) + SXI_CACHE.
2. if no, eventually, think to this non-normal action.... but...
Do you have this SWCV in another PI environment (exm PI qua) with your GUID (this one of ESR)?
If yes, check if you have this SWCV (same GUID) in the SLD of this other environment (exm XI QUA).
if yes, maybe a solution to avoid your conflict in ESR dev / SLD dev is to do an export of this SWCV from SLD qua to SLD dev... but... that's clearly not the normal way... with perhaps other impacts (I don't know your landscape, your SWCV dependency, your development phase vs production and/or maintenance)... so that's just an idea which could be thank. (coud be)
Mickael

Illegal dependency while using a DC from one Software Component in another

Hi
SCENARIO
I have a Software Product (e.g. SP1) with 2 Software Components (e.g. SC1, SC2) defined in the SLD. Now, we have defined a track with these software components (as per the correct procedure).
This Development configuration was imported into NWDS and we have developed 2 WebDynPro Development Components under each of these Software Components (e.g. DC1 in SC1 ; DC 2 in SC2).
All works fine and everything is smooth till now.
The ISSUE
When I try to use DC1 of SC1 as a used component in DC2 of SC2, I get an error.
The exact step: In NWDS-> DC2, I go to USED DCs -> Add Used DC and try to add DC1's public part (all as per correct procedure),
I get the following error:
Illegal dependency: The compartment of com.test/xss/dc2(com.test_SC1) must explicitly use compartment of com.test/xss/dc1
This error comes only if DC1 is in SC1 and DC2 is in SC2. If 2 DCS are in the same SC (eg: DC1 and DC2 to SC1), then the error does not come.
Should we configure any compartment or other data in CBS/CMS?
Please help.
Thanks in advance.

Sandeep,
In the SLD, has a dependency been setup between SC1 and SC2? If not, you will have to add this dependency, which is done in the same way as adding the initial SAP_JTECHS,
SAP_BUILDT and SAP-JEE dependencies to the SC.
Once the SC1 has been added to SC2, you will have to go to the Landscape Configurator (link is in the CMS), go to the Domain Data tab and click on Update CMS. Next, go to the Track Data tab, add the new SC and then click on Synchronize SC Dependencies. Click on the Save button and then do a "Save and Restore".
Message was edited by:
Stefan Thibeault (added a missing step!)

Plain J2SE adapter and SLD configuration

Hi all,
I'm trying to configure Plain J2SE Adapter to be connected to SLD for purpose of automatic registering to SLD. I followed the description in PDF manual, but I still get following error:
Error creating adapter services for
J2SE_AE_server2.dummy.com_8200 com.sap.lcr.api.cimclient.LcrException: CIM_ERR_FAILED:
SAP_BusinessSystem.CreationClassName="SAP_BusinessSystem",Name="AdapterSenderService"
referenced by association SAP_SenderAdapterForBusinessSystem.Antecedent=ref"SAP_XIAdapterService.CreationClassName=\"SAP_XIAdapterService\",
Name=\"file_sender2is\",SystemCreationClassName=\"SAP_XIAdapterEngine\",SystemName=\"J2SE_AE_server2.dummy.com_8200\"",
Dependent=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"AdapterSenderService\"" does not exist.
Do I need to setup something special in SLD ? I thought the registration should work without adding of any BusinessSystems to SLD ... I suppose it should work as autoregistering in SLD via the user parameter SLD.user mentinoed in the config file SLDaccessor.properties.
Any ideas ?
Thank you in advance.
Regards
Tom

Hi Tomas,
After the PI installation we have to do post installation step, if not done pls refer this SAP help to configure it..
http://help.sap.com/saphelp_nwesrce/helpdata/en/98/fa9b6ec510404dbcfebf35cb107c04/frameset.htm
Hope it helps..
Thanks,
Kumar.

SLD in SAP XI

Hi
I am planning to isntall XI. Can anybody tell me the special considerations while installing. I do not have separate SLD Configured.
Thanks in advance

Hi,
SLD is system landscape directory and it contains all the Technical system and Businsess System of your XI system.
Go through the below link for SLD preparation for your XI system:
u may refer:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
SLD Steps for starting a XI project
Configuration Steps
The configuration steps that you need to perform depend on the type of system. The following system types are relevant for the SAP System Landscape Directory (SLD):
· SAP technical systems
The following SAP systems do not need to be configured manually since they automatically register themselves in the SLD:
¡ SAP Basis systems as of Release 4.0B
¡ All SAP Web AS ABAP systems
¡ SAP Web AS Java systems as of Release 6.40
You do not need to maintain data about SAP software components and products that a system contains since their data already exists in the component repository, which is delivered with the SLD. SAP technical systems automatically register themselves and report data about their installed products to the SLD by means of data supplier programs. However, if you cannot use the data supplier programs (if your Support Package level is too low, for example), you have to define SAP technical systems manually. For more information, see Manually Registering SAP Web AS ABAP Systems.
Other SAP systems (business systems, for example), which have to be registered manually.
· Third-party systems
If you have installed third-party (technical or business) systems in your system landscape, you have to register them manually in the SLD. This includes maintaining data about the software components and software products that they contain.
SLD HELP -
http://help.sap.com/saphelp_nw04/helpdata/en/43/783c00eabd1ad0e10000000a114cbd/frameset.htm
Configuring and Activating the Administrative SLD
Use
In this template, you perform the basic configuration of the administrative SLD. This includes the configuring and starting of both the Object Server and the Data Supplier Bridge.
regards,
Suryanarayana

Error while importing technical systems in SLD

Hi all,
I was importing technical systems from one SLD to another by Export-Import.
While importing the content i got an error 92 out of 93 objects successfully imported.
for one object following error is shown.
CIM_ERR_FAILED: Instance referenced in role Dependent of association SAP_BCSystemJ2EEEngine does not exist:
Antecedent: SAP_BCSystem.CreationClassName="SAP_BCSystem",Name="IRX.SystemNumber.0020312094.SystemHome.prdcixi"
Dependent: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="IRX.SystemHome.prdcixi".
SAP_BCSystemJ2EEEngine.Antecedent=ref"SAP_BCSystem.CreationClassName=\"SAP_BCSystem\",Name=\"IRX.SystemNumber.0020312094.SystemHome.prdcixi\"",Dependent=ref"SAP_J2EEEngineCluster.CreationClassName=\"SAP_J2EEEngineCluster\",Name=\"IRX.SystemHome.prdcixi\""
After that i continued with Business sytems which was sucessfully imported.
Will there be an issue because of the above error? and how to resolve this error?
Regards,
Priya

Read the note listed below, which addresses your issue.
Link: [Note 1178572|https://service.sap.com/sap/support/notes/1178572]

SLD Dependency,

Similar Messages

Maybe you are looking for