Central sld problems ?

Hi Guys,
The scenario is like this.
1. Central SLD installed on solution manager
2. We are trying to connect an XI BOX to this central SLD.
Steps did in XI BOX:
1. SLDAPICUST - points to SLD host.
2. Exchange Profile - values set for Connections like cr.name and landscape.name.
3. SLD Data supplier - in visadm - points to Central SLD - due to this, The Java stack of XIBOX is listed as a technical system in central SLD and data collection works correctly.
3. JcoRfc Destination - LCRSAPRFC_XIBOX - program id registerd in visadm with gateway host and service as XIBOX gateway service itself.
Steps did in Central SLD:
1. Jco Rfc Destination - SAPSLDAPI_XIBOX - program id registered in visadm with gateway host and service as that of the XIBOX.
2. SLD Data Supplier - points to sld itself and when data collection is done - sld itself is added as a technical system in SLD.
Problems:
1. IR and ID are not regsitered in SLD under Technical Systems of type Exchange Infrastructure
2. when trying to import the SWCV from the sld getting the message as "unable to read the data from the centralsldhostname:50000"
3. when i do the cache notifications in ID, i am getting the error as unable to determine the central adapter engine.
4. Adapters not listed under adapter monitoring
5 when i go the administration cache overview, i am not seeing the adapter meta data like af.server
checked the settings according to 720717, 768148, 939592.
any help would be really appreciated
Thanks,
Srini

Hi Agasthuri,
I dont have any issues with the SLDCHECK and it works fine. I have already done the reimporting of the basis component.
Thanks,
Srini
Edited by: srinivas kapu on Jan 29, 2008 2:32 PM

Similar Messages

Central SLD

I try to import SW Component Version into Repository from Central SLD, System gives me the messagebelow:
Unable to read software component versions from System Landscape Directory "brckxiprd.internal.borusan.com:50000"
What must I do to fix this problem?
thanks.

hello cemil,
Check out these note :
Note 720198 - Integration Repository cannot access SLD
Note 836093 - IFR: Updating the application components => error
It may help you out....
regards
Prasad

Migration of local SLD to Central SLD on different host.

Hello Experts,
We have migrate the local SLD existing on the SAP PI System to a new Central SLD on a different host on SAP Solution Manager system.
I followed the OSS Note 720717, which contains the description of the changes that have to be exectued in the SAP XI/PI Environment, during the SLD Migration. This note does not give any details of the description of changes for the other SAP Systems such as SAP ECC, BI etc registered in the SLD.
Can anyone provide the OSS Notes, SAP Doc URL or the steps on how to migrate the local SLD existing on SAP XI/PI System to the new Central SLD on the SAP Solution Manager system.
Thanks for help in advance.
Best Regards,
Haleem

Firstly
I recommend to avoid having 1 SLD for multiple clients - like Solution Manager, BI, ECC
This is because clients may end up having conflicting requirements for the same SLD
- for example the small user group for Solution Manager may have a flexible and easy going policy on J2EE downtime
- but if you take down the Solution Manager J2EE that houses the SLD and PI uses this SLD - then you could have a severe affect on PI useage
Secondly
Although you can migrate content - this still does not guarantee the target landscape will work
- you may still need to manually re-implement target landscape configuration
let me give you an example
SLD 1 is being moved to SLD 2
Portal 1 is pointing to SLD 1
Even if you migrate the content of SLD 1 - including the ECC and Portal technical system landscape information
Portal 1 is still pointing to SLD 1 - this then needs to be manually re-pointed to SLD2
and that might not be all the complete steps either !
The complete steps of migration from the client side may not be available (I have found only steps to
migrate SLD content not migrate client use of the SLD)
- they may only be available as the documentation for the original configuration steps required to step SLD and the client
- therefore when migrating SLD you must go through the client setup documentation for SLD and check your
target landscape is consistent
Lastly - other considerations include
Lets say you also export model and CIM content from SLD 1 to SLD 2 - this means SLD 2 has an import line from SLD 1
- if you decomission SLD1 then you need to switch the import line which is not recommended - this could cause severe problems and may require you to create a new import line to upload content from SAP /swdc (which you need to keep the SLD bug free and latest definitions)
Just a few thoughts on issues you may encounter
Best wishes
Stuart

How to link XI-Development to the central SLD on XI-Production?

Hi,
we have a two systems landscape with XI-DEV and XI-PROD.
So far, we have used the SLD on XI-DEV.
Now we want to use one central SLD that is running on XI-PROD for all developments on XI-DEV.
What is necessary to to that (any documentation available?
1. First we have done an export/import to copy all technical and business systems to the central SLD.
2. Then we have set the following parameters in the exchange profile (Section Connections) of XI-DEV:
 com.sap.aii.connect.cr.name: Host of XI-PROD
 com.sap.aii.connect.cr.httpport: Port of XI-PROD
 com.sap.aii.connect.landscape.name: Host XI-PROD
 com.sap.aii.connect.landscape.httpport: Port XI-PROD SLD
3. Now we have done an SLD data cache cleanup.
4. TEST: I have created a new business system in the SDL (XI-PROD) to check, if this business system is available in the integration builder on XI-DEV. If i try to assign a new business system, I got the error message:Access to object list of type "BusinessSystem" using the InternalEOAService BusinessSystemAccessor failed.
Also i get the error: "No connection to SLD" if i try to compare the adapter-specific entries of a business system with the SLD.
What is the reason? What steps are missing?
Do i need to maintain transactions like LCRSERVADDR (server address of landscape directory?) and SLDAPICUST or anything else??
Thanks for any help!

Chris,
Follow the OSS Notes
720717: Reduce the number of System Landscape Direcotries (SLD) &
768148: Using a separate SLD for XI
This should solve your problem.
regards
Shravan

Local SLD not updating a central SLD

Hi,
In my company landscape, I have
SolMan7.1 with Central SLD (Let's call this SLDA)
Portal 7.02 with local SLD (Let's call this SLDB)
ECC6
Both the Portal and ECC systems are updating SLDB, so I can see both technical systems in SLDB.
SolMan is updating SLDA, so I can see SolMan technical system in SLDA.
I linked SLDB to SLDA via
From SLDB> administration> data suppliers --> add SLDA
For this setting, I use the user SLDDSUSER, which have a role LcrInstanceWriterAll.
The problem now is SLDA does not get the data from SLDB. In SLDA, I see only the SolMan Technical System.
How often does SLDB update SLDA? Can we manually trigger an update SLDB->SDLA?
How can we troubleshoot the SLDB -> SLDA update?
What else needs to be configured other than "From SLDB> administration> data suppliers --> add SLDA" ?
Thanks
Edited by: Nick Foo on Sep 27, 2011 3:53 AM

Hi Sunny,
yes I have done those steps. Very short and easy setup steps to link to another SLD.
OK, just one thing to confirm here.
After Add SLD, the SLD URL syntax should be http://host:port correct?
I have tried all sorts of entires for the URL
http://host:port
http://host:port/sld
http://host:port/
All not working
Checked the user, user is ok, even tried giving the user Administrator role and still not working

Instalation help Central SLD parameters connection

Hi Dear All,
I am installing solman 4.0 SR1 on Windows 2003 and Microsoft SQL.
during the instalation i got a screen which iam not aware of please help me
The scren says :
SELF REGISTRATION OF JAVA ENGINE in CENTRAL SLD:
SLD HTTP HOST -
SLD HTTP PORT -
SLDDATA SUPPLIER USER: SLDDSUSER
PASSWORD:
SELF REGISTRATION OF ABAP ENGINE IN CENTRAL SLD
SLD GATEWAY HOST: -
SLD GATEWAY INSTANCE NUMBER: -
COMMUNICATION WITH CENTRAL SLD:
SLD ABAP API USER: SLDAPIUSER
PASSWORD:
Please help what i have to choose and where i can find the relavent information.
kind regards,
Vamsi.

Hi,
For SLD configuration during installation,
SLD HTTP HOST - can be any name need not be your computer name. E.g <SID>SLD or <SID>SLDSRV or something like that.
SLD HTTP PORT - the port would be 50<instancenumber>00
eg:- 500100 where 01 is instance number.
as SLDDATA SUPPLIER USER and SLD ABAP API USER are automatically populated. just maintain your password.
That's it.
This will solve your problem. Feel free to revert back.
--Ragu

Central SLD - Manipulations

We want to prepare a central SLD by merging many instances of current local SLDs.
We found note about merging and grouping instances... it is ok.
My question deals with next steps because we want to keep local SLD in Production instances (PI, BW instances)...
We will need to export data of central SLD when built, into local production SLD... but some of local production SLD already have data. Do we need to purge them before import ? If yes how ? Is there a risk to create duplicates entries, associations ?
Thanks a lot

Hi,
Since even bringing up the useradmin web page is slow, it cannot be the SLD.
Bad response time is caused by cpu, memory and/or network. Is the SLD server on the same network subnet as XI or your PC?
You can also logon to the SLD server and examine the cpu and memory utilization.
Examine the J2EE log to see if there are any errors. This can also cause response time problem.
Regards,
Bill

Switching from local to central SLD

I installed the ESS business package with a local SLD. Now there is another SLD server we need to use (a central SLD instance). Can we switch easily from an existing local SLD instance to a remote SLD instance?
Tiberiu

Hi Tiberiu,
It's a while since this message was created. Have you solved your problem? I have our SLD's set slightly differently to the suggestion made earlier, although I would say that I'm an expert in this area. For dual stacks I have the CIM.... tab pointing at itself and the HTTP tab pointing at the central SLD. This seems to work for us in all cases where there is a dual stack. We are having a few issues in java only systems which we are trying to solve. At present both tabs point to the central SLD and "seem" to be working!!
Regards,
Paul

Need suggetions on Central SLD as Solution Manager!

Hi Experts,
I need a help/ suggestion on deciding the Central SLD system in our landscape. We are using Solution Manager 7.01 as the Central SLD for the new Installations and including the old Systems too. But We came to know that SAP is not recommending using Solution Manager as Central SLD System. So please tell me, is it recommended or not and what problems may occur in future if we continue Solution Manager as Central SLD.
Thanks,
Ajay.

Read these three blogs. They have the answers that you need.
/people/boris.zarske/blog/2007/06/10/an-overview-of-the-documentation-required-to-set-up-the-system-landscape-directory-sld-of-sap-netweaver
Solution Manager 7.0 and SLD => /people/dolores.correa/blog/2007/10/19/solution-manager-70-and-sld
/people/boris.zarske/blog/2008/03/21/sld-general-recommendation-how-to-set-up-the-system-landscape-directory

Central SLD of higher version than Portal

Hi
Will it be a problem to have central SLD of a higher version than that of Portal server .
Regards,
Priya

Hi,
Always keep latest CR and CIM for SLD. SAP also recommends the same.
Regards,
Dipesh

Central SLD is too slow.

Hello all,
We have central SLD which is contectecd to XI sandbox, dev, NWDI and Portal. This SLD is extremely slow even when trying from the server. Even when I go useradmin web page, it takes about 2 minutes to display page. This server has 4 Gigs fo RAM.
Any suggestions?
Regards,
N.S

Hi,
Since even bringing up the useradmin web page is slow, it cannot be the SLD.
Bad response time is caused by cpu, memory and/or network. Is the SLD server on the same network subnet as XI or your PC?
You can also logon to the SLD server and examine the cpu and memory utilization.
Examine the J2EE log to see if there are any errors. This can also cause response time problem.
Regards,
Bill

Central SLD vs SLD for each XI instance

We are starting our SAP XI project. We are on XI 3.0 sp 9. We are trying to make a decision on which of the SLD configurations is the best for our company. We will have 3 SAP XI systems (dev, qa and Prd) should each have an SLD or should their be a central SLD? What is working for people currently in production? What are lessons learned? Thanks

Hi,
We do not have yet implemented production XI environment but as SAP IT consultant, I am thinking about system architecture design based on SAP NetWeaver platform.
So I would say for good performance, it will be better that each XI connect to its own SLD system but for system landscape maintenance I would advise to have a central SLD only if each XI systems (dev, qa and prod) communicates with the same system landscape.
You also have to think about XI object transport from dev to qa and prod...as XI design and configuration objects are based on SLD model (business system, software components) you should have the same SLD
in each environment...so in that case a central SLD could be a good option but you could also imagine as an alternative solution an SLD model replication strategy between each SLD systems
But we still have the question of SLD maintenance security and I really do not think that it is a good idea for dev purposes to allow changes in a central SLD used by an XI production system !!!
The last point is that in some NetWeaver scenario SLD is not only used by XI but also by EP - WebDynpro with JCo connection for instance - so if you would want to use other NetWeaver components I would say to have a standalone SLD system for security reason and shared efficiency.
So you should have at least two SLD systems (one for dev/qa and one for prod) but we could imagine the following architecture :
1- XI dev with its own built in SLD system which one has an SLD namespace for dev purposes (dev_namespace) as a sand box and an other namespace (rep_namespace) which is the replication of the prod landscape (prod_namespace)
2- XI qa with its own built in SLD system with only one SLD namespace (qa_namespace) as a copy of rep_namespace
3- a standalone SLD system with one namespace (prod_namespace) to share it with other NetWeaver components without the risk to break down connection in case of XI prod problems.
XI prod points to this standalone SLD
4- if you are not using others NetWeaver components, a standalone SLD for production is not useful and then production SLD is in the production XI system itself.
So that my first feeling...but still open for discussion on that important point of system architecture design.
I hope it helps you a bit to have a decision.
Greetings
Nicolas

Urgent - SLD problem

Hi guys,
I have a scenario in which i have a central SLD for developement and quality servers.
I am pointing developement SLD to quality SLD . In the technical system i can see both developement and quality
server
But there is no entry in software catalog.The error i am getting while importing SWCV " java.lang.null.pointer".
Regards,
Keith

Keith,
I had also similar kind of problem. Please check my previous threads, or check your parameters in the exchange profile. You can go to exchange profile sxmb_ifr->adminsitration->exchange profiles(left side).
Thanks,
Raj.

Difference Between Central SLD & Local SLD

Hi All,
Q1) What is the Difference Between Central SLD & Local SLD.
Q2) Maintaining Individual SLD For DEV, QTY, PRD Servers is the Best One Or Maitaining the Single SLD is the Best One ????
Please Ans These Two Q's
Regards
Vamsi

> 2. Maintaining individual SLD for DEV, QTY & PRD
> will be better approach. We follow this approach.
SAP recommends a Single SLD.
Having a separate SLD for every environment beats the concept of SLD itself. SLD is a place where you can look and understand what components/ system run in your landscape. If you are going to hve one for every Environment, it is against the concept of SLD itself. More maintenance is another issue.
Single SLD as recommended by SLD has the problem that you do not want to provide access to a component that can be used in production to developing teams and so on .What Barry has pointed is something that is a more practical approach.
There are no hard and fast rules. A client present across Geographies, havinng multiple vendors and IT teams handling different geographies would prefer to have multiple SLD's one for each Geography and then maybe a master SLD that is going to conain all info of the other Sld's and so on., There is no direct answer to this question other than it purely depends on individual clients.
Regards
Bhavesh

Need Suggestion on Central SLD System

Hi Experts,
I need a help/ suggestion on deciding the Central SLD system in our landscape. In our current SAP System landscape we do not have XI Servers for Central SLD, So we are using Solution Manager 7.01 as the Central SLD for the new Installations and including the old Systems too. But We came to know that SAP does not recommend using Solution Manager as the productive SLD System.
So we have stopped the process of including old systems to Solution Manager now and we decided to build the system for central SLD which is recommended by SAP. So please suggest me which system is more recommended by SAP like EP/ ECC/ NW or any other.
Thanks.

Hello Ajay,
you posted the question on wrong forum.
This forum is for sap business one.
Post your thread on appropriate forum to get the replies.
*Close this thread.
Thanks,
Neetu

Central sld problems ?

Similar Messages

Maybe you are looking for