Product SCM 5.0 in Central SLD Software Catalog

Hi,
I've an installation of NW 2004s, SCM 5.0 and a Solution Manager that is doing of central SLD. I have perform the post installations steps for SCM but I'm not seeing the product SCM 5.0 in the Software Catalog when selecting Software Type "Product" on the central SLD, I just see SCM 4.1.
When selecting Software Type "Software Components" in the Software Catalog screen, there is a software component SAP SCM that has version SAP SCM 5.0.
Why it doesn't show the product for SAP SCM 5.0?
Many thanks.
Rodrigo.

You have to update your CIM file on the Server
SLD content has been updated from time to time.
You can download the most up-to-date files from the SAP Service Marketplace. See SAP Note
669669 for details information.
Procedure for importing the data is
1. Choose Content --> Import. The browser displays the Import Selection screen.
2. Next to the Import File field, choose Browse.
3. To import the component information data, navigate to the following file:
<server>\usr\sap\<SAPSID>\SYS\global\sld\model\cr_content.zip (Microsoft
Windows) and then choose Open.
Objects that already exist in the system are automatically overwritten.
4. If you do not want to import the instances into the current namespace, you can change the namespace.
5. Choose Import.
Gaurav Jain

Similar Messages

SLD: Software Catalog

HI,
we are starting our XI implementation now. Presently I dont have any products and components defined in the Software catalog. My question is, Is it necessary to define the products in the software catalog of SLD. Can I directly create Business systems and Technical systems?.
Could you please help me on that.
Thanks and Regards,
Raj.

Hi Raj,
You need to perform the post-installation activities to see the content in Software Catalog in SLD. Refer to section "Updating the CR Data in SLD" in the XI Post-Installation Guide.
SLD contains software and system catalog.
Software catalog describes installed products and SWCs.
Systems catalog describes the systems in your data center
with 1) physical view(Technical) and 2)logical view(Business System).
Info from Software Catalog is used in Design time of your scenarios.
Info from System Catalog is used in defining the routing rules.
SWC is primary container for all your design objects
You should have content for all of SAP Products and SWC by updating the CR Content.
For all the products other than SAP you have to create Products and SWCs. As I mentioned earlier, these are primary containers or place holders for all your design objects.
Hope this helps.
Rgds,
Sam Raju

Missing my Software Component (SC) within the Software Catalog

Hi all,
we work with different Project tracks within NWDI on SAP NetWeaver 7.31. The current phenomenon where I am getting confused is: I am able to import a track with my Software Components from the SLD (from the NetWeaver Development Studio), but when I check if my Software Components are available in the SLD --> Software Catalog, I am not able to find these. Selft created Software Components of my own are findable.
Do I have to refresh / update anything anywhere in my SLD?
Thanks for assisting.
Cengiz

Hi Cengiz,
I'm confused. Which are missing in SLD?
If it's standard SAP SC, please updated CR contents.
If it's custom ones, you have to define them in SLD.
BR, Tom

Moving Central SLD from XI Development to XI Production ?

Hi,
Please advise what is the impact of changing Central SLD from XI Development to XI Production Server.
Because during initial installation the XI production still not available so our Basis only install SLD in our XI development server and other SAP development like FI, BW also pointing to this SLD.
now the XI production is ready. could i just install new SLD in production and changes all connection from
dev to prod ?
Please advise on the step that i have to do.
Thank you and best Regards
Fernand

Hi,
http://www.riyaz.net/blog/index.php/2008/05/28/xipi-step-by-step-guide-to-xi-transports-using-cms-part-i/
http://www.riyaz.net/blog/index.php/2008/05/28/xipi-step-by-step-guide-to-xi-transports-using-cms-part-ii/
http://www.riyaz.net/blog/index.php/2008/05/29/xipi-step-by-step-guide-to-xi-transports-using-cms-part-iii/
Refer this article
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f85ff411-0d01-0010-0096-ba14e5db6306
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b01876ac-abbb-2a10-788e-95a7c5a5aeca
Regards,
Suryanarayana

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

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

Creating new track - software catalog new product not showing up - Help!!!

Hi,
Creating a new track for custom development.
A new product has been added in the software catalog in SLD.
SLD and NWDI (netweaver 04) are on the same system.
The new product is not showing up when trying to select in the new track, Software Components for Development section. Why??
Does the server need to be restarted after adding a new product? This is difficult for us as SLD has production systems tied to it!!!
Thanks in advance
Regards, Neeta

Thanks - This did the trick. I have awarded points!!!!
Regards, Neeta

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

Pi 7.1 Central SLD

I have installed PI 7.1 and will use it as central SLD. I am installing SCM 2007, ECC Oil and Gas and BI 7.0 and want to point these systems to the central SLD in PI system.
During the install the WAS 7.0 system use SLDDSUSER however there is no user like this on PI 7.1.
SCM 2007 install had as default SLDDSUSER but that user doesn't exist in the PI 7.1 install.
I check SAP notes and can't find nay notes regading this change.
I did find an account that is close to this SLD_DS_DS1 where DS1 is the SID.
Has anyone ran into this issue with WAS 70 and WAS 71 installations? Is it safe to select SLD_DS_SID as the correct one for hooking in my other component systems into the Central SLD on PI 71?
Thanks
Mikie Brogan

We have the same situation. Can you explain How?
Thank you
Raj GA

Access Central SLD Error

Hi Experts,
We are using the SLD SOLMAN and we and the ideia is to use it as Central SLD. In order to allowed PI indentifed the Central SLD we must appllied few oss notes like; 939592, 768148 and 720717, but much as we try it to import we got few errors as describe below:
"Unable to read software component versions from System Landscape Directory "ASPTSSM01:50000"
Another error occurs when trying to access the SLD by the runtime workbench:
"Error during communication with System Landscape Directory: HTTP response code: 403 (Forbidden)"
Anybody help-me.
Regards,
HMattos.

Hi HMattos,
I hope you have created the PI service users in SOLMAN and assigned the same password as the PI service user password.
Open /rep on your PI and click SLD. Check if it opens the SOLMAN page.
Check in VA if SLD data supplier test works fine.
Check SLDCHECK transaction.
If you get errors in any of these, the you will get a hint as to where is the issue. If you unable to resolve, then post the results of the above.
Cheers....,
Raghu.

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

Central SLD and Webdynpro

Dear all,
I have a new EP 6.0 installation running ESS/MSS and BW reporting and implemented central SLD.The SLD server was the CEN Solution Manager system. Because of some issues with support pack application in the solution manager system, the solution manager system was unavailable for a week. As the Webdynpro JCOs that are used in ESS/MSS use SLD, ESS/MSS in my portal systems became unavailable for my users. I had to configure local SLDs for each portal system to avoid the application downtime
I am wondering what people are doing out there to avoid what happened to me: High Availability? Seems a bit over the top as we do not have HA for our mySAP ERP production system which is the most important system of the landscape. Any other thoughts or SAP recommendations would be very much appreciated
Many thanks
Andreas

Hi,
Ofcourse HA should be one of the strategies you should think about. But now that you don't have it in place and cause for downtime is something like upgrade or maintenance, which is unavoidable, you can maintain the ECC system (HCM System) in your SLD, point the JCo Connections to your ECC system and thereby you should be able to use ESS-MSS. This won't take more that an hour, trust me.
Would also like to know what's your User Management Strategy ? If you are using the solution manager as your datasource for user management on portal, then you can hardly do anything.
Cheers,
Sunil
PS: Reward points for helpful answers.

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

Central SLD/Local SLD

Hello All,
Is there limitation with central SLD over Local SLD?.
To deploy Webdynpro applications (Mobile) please let me know if there are any limitations
Thanks

Hello.
SLD architecture is a long discussion
There are different views on how to set up SLD's.
In my oppinion, the limitations of SLD is that it's a central component to a growing number of netweaver component.
Right now, the portal, webdynpro, xi, nwdi wouldn't work very well without the SLD.
Considering this there is aspects on how to set up the SLD's. Usually critical systems have a local SLD, with supplyer briges to central SLD's.
You would have a separate SLD landscape for Production servers, since they usually run on different SLA (service level agreements).
If you're using NWDI, it's usually a good place to have you're central SLD.
If you're running a smaller landscape, go for the local SLD only and don't complicate your landscape too much.
Check this document (about last slide) with different SLD scenarios. https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/204994f3-0e44-2a10-17b3-808fbd8db4aa
Regards, Mikael Löwgren

Central SLD Configuration

Dears,
Recently we installed PI DEV and PI QAS server.At time of configuration we choose local SLD option for configuration.
But now we are getting requirement to configure central SLD.
So please confirm which strategy is good between them and if it is central SLD,Please suggest the
procedure to change local SLD configuration to central SLD.
Shivam

Hi Shivam
The SLD planning guide provided previously is the key source to plan, implement and run an SLD landscape
However what it may not deal with specifically is changing an existing SLD landscape to accomodate a local PI specific
SLD and a new Central SLD for Solution Manager (or other purposes)
Some things to consider when selecting Sync options
1) 1 Dual purpose SLD is not recommended - a central SLD might have different administration requirements than a PI specific SLD
2) Where possible do not change established import or export lines in either SLD
3) Keep all SLDs involved in the sync at the same J2EE version, SP landscape and CIM model/content
As the PI SLD can be productive critical - full consideration has to be given to this SLD as you can
still maintain systems manually in a central SLD manually - or indeed in Solution Manager itself (both manually and automatically via RFC) - therefore I would recommend a unidirectional sync from local PI SLD to Central SLD of PI landscape data only - either manually or automatically or indeed explore any available options to have data suppliers update both SLDs (there was some options similiar to this in older SLD versions - but I am not completely familiar with the latest SLD builds)
I would not however encourage full sync or CIM based sync as there maybe established CIM import lines on either SLD nor would I specifically encourage the Central SLD to influence data on the Local existing PI SLD
Best wishes
Stuart

Product SCM 5.0 in Central SLD Software Catalog

Similar Messages

Maybe you are looking for