PI 7.1 and central SLD

Hello, colleagues.
We have already central SLD based on SAP Solution Manager (SM+ERP systems). Now we plan to setup PI 7.1 (three-system configuration).
Should we include PI-systems in the central SLD or organize second separate SLD for PI-systems?
We have some doubts about it and cannot yet make right decision.
Can we hear your suggestions of this matter?

Hi,
Personally I recommand to have at least two SLD for PI systems: one for PI prod, and another for PI non-prod (dev, Qua, Pre-prod). As your current SLD is linked to ERP, I presume it has a high criticity, so for me I think you can use it for your PI prod.
Or you can have only one central SLD (yours) which populate the local SLD of each PI, by synchronization.
with SLD, there are several choices, but keep in mind that for the SLD of PI prod, it should have a "hight" criticity. If its SLD is shut down, PI can work only during several minutes without SLD info... thanks to its SLD cache, but after that PI exchanges are down.
Regards.
Mickael

Similar Messages

Local SLD and Central SLD

Hi,
Can we still change Local SLD to Central SLD after the installation has been done?
Rgds,
Hapizorr Rozi Alias

Hello Rozi/Naveen,
Yes u can change the SLD configuration from central to local or a vice versa...
Please check the following SAP Note for u r ready reference
Note 720717 - Reduce the number of System Landscape Directories (SLD)
If usefull then give reward point..
Thanks

Adapter monitoring with central SLD!

Hi ,
we have central SLD in our landscape(different host from XI server),and our basis guys installed PI7.0 SP12.And AE is local as I can see under Integration server.
I can see JPR in adapter in adapter monitoring.
I have question here!
should it needs to show all the list of adapters (FILE,JDBC,JMS,SOAP etc)in adapter monitoring in RWB?does it vary,if sld is central or local ?
what is the ideal way.
thank you,
babu

where the adapter engine should appear in RWB under integration server or under non central adapter engine if we have installed central AE and central SLD?
Under Component monitoring -> Integration server -> Adapter Engine
and it has show all the adapters when we install central AE and with central SLD when we furthur click the show all adapters?
As i mentioned above, u may view all the adapters after clicking
Adapter Engine -> Adapter Monitoring
or is it changed since PI 7.0 to cummunication channel monitoring and no adapter monitoring?
Yes. Now the monitoring of adapters r much intensively done by Communication Channel Monitoring
Regards,
Prateek

XI installation with central SLD

Hello,
I have installed solution manger to generate key for XI installation. But, when i in stall solution manager, it installed MaxDB and local SLD and also i think WEBAS ABAP. After that i generated the key.
And, I am installing XI on the same host. There is no configuration as such i did.I tried to use the same solution manger DB, but i t failed. So i started with New DB creation. And central SLD........
Is there any configurations that i need to do to install XI with our any errors.
When i used existing SLD, is there any configuration i have to do.
More important, i have to install solution manager and XI on same host
Can anybody any issues here.
Please advice,
Srini

This should be straight forward.
If the SLD is set up for Sol Man, you enter these details on the in the installation wizard.
You will need seperate SIDs and you will need to assign the Virtual host names for each installation.
You will need to check the SLD config after install. the two sm59 conenctions - LCRSAPRFC & SAPSLDAPI, the sldapicust, the JCo Connections in Visual Admin and the SLD Data Supplier in Visual ADmin.

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.

Solman_setup and central&local solution manager SLD

Hello,
I'm configuring our solution mananger system with transaction solman_setup. The local SLD of the solution manager will also be the central SLD of all our systems. After finishg the basic configuration in solman_setup, and go to "managed system configuration", I can only see the only solution manager system, as ABAP and as JAVA, but no more systems (right, as I haven't defined more systems).
I cannot create more ABAP system with the link "maintain technical systems", the ABAP option when I select create isn't there.
If I create another type of system as a test, for example, third party, the transaction SMSY can see this new system, but the SLD in http://<my_solution_manager_system>:50000/sld doesn't show this new system at all.
Where must I create the systems? and how can I connect the SLD and the SMSY transaction? Should I "add SLD" at the Administration in http://<my_solution_manager_system>:50000/sld and put the suolution manager itsefl system?
Thanks in advance for your help and best regards,
Ana

Hi,
To ensure a system is registering into the SLD and synchronising with SMSY, go to transaction RZ70 and define the Host and Service.
Also, set up a user for accessing the SLD in transaction SLDAPICUST. The user has to exist in the Java stack to log into the SLD.
Also ensure your RFCs are correctly set up for LCRSAPRFC and SAPSLDAPI as per this link:
https://cw.sdn.sap.com/cw/docs/DOC-37953?treeid=DOC-7936
Then use transaction SLDCHECK to ensure your connection is working.
Finally enable SLD synchronisation into SMSY by transaction SMSY > Goto > Setup System Landscape Maintenance. Define the same host and port of your SLD and schedule the data transfer.
This should pick up the system once the landscape_fetch background job executes into SMSY.
You can use this approach for all your managed systems and is the most logical way to connect systems to the SLD.
Regards,
-Rohan

Regarding Central SLD and Local SLD

Hello,
Can we maintain Central SLD as well as Local SLD?
We have maintain central sld during installation , now i want to maintain local sld also.
How can we do this? what is the benifit and disadvantage for maintaing both?
Regards,
V.Singh

Hi V.Singh
You can have as many SLD as you like - the service is available as part of a WAS JAVA install
Bear in mind the more SLD = the more administration and if you wish to sync them there is also many considerations
It is best you check the SLD planning guide at System Landscape Directory (SLD) to select the landscape that
best suits the intend use
The Central SLD concept is primarily to have an SLD containing all systems in your company i.e complete overview - this might not be specifically used for runtime of these systems - say PI useage etc - it might be used to populate Solution Manager with landscape data or just track all systems and changes in the organization
The central SLD concept is also not essential however an SLD (a local or app specific one) is essential for certain applications like PI, ESS etc
Best wishes
Stuart

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

Howto export and import SLD data to different SLD's

Hi All,
I have a landcape with 4 SLD's. A central SLD within Solution Manager and 3 SLD's for resp. XI dev,qas,prd.
The central SLD is version 7.0 and the XI versions are 2.2. (model versions are the same, CR are different -> XI SAP_CR 2.18 -> Solman SAP_CR 2.0)
The idea is that all changes in Bussiness (including new products and software components) and Technical Systems take place in the Solution Manager. After a change we make an export and import it into XI dev, qas and so on.
However....
When adding, for example, an exsisting product to a technical system, export it on Solman and import it into XI dev, all entries dissapear(sapms/host/clients).
We filled Solman with a full export of XI development and that worked fine.
Does anybody has an idea about actions to be taken?
Thanks,
Sjoerd Lubbers

Hi All,
I have a landcape with 4 SLD's. A central SLD within Solution Manager and 3 SLD's for resp. XI dev,qas,prd.
The central SLD is version 7.0 and the XI versions are 2.2. (model versions are the same, CR are different -> XI SAP_CR 2.18 -> Solman SAP_CR 2.0)
The idea is that all changes in Bussiness (including new products and software components) and Technical Systems take place in the Solution Manager. After a change we make an export and import it into XI dev, qas and so on.
However....
When adding, for example, an exsisting product to a technical system, export it on Solman and import it into XI dev, all entries dissapear(sapms/host/clients).
We filled Solman with a full export of XI development and that worked fine.
Does anybody has an idea about actions to be taken?
Thanks,
Sjoerd Lubbers

Not Updating in Central SLD

Hello,
Upon performing our daily system checks, one of the item is to monitor the sending of SLD data of the installed systems in the System Landscape to the Central SLD which in our case is the XI box. Four of our systems having Java stack did not update. With that, i performed the necessary steps to trigger it so that it'll update in both Web AS ABAP and Web AS Java. With regards to ABAP, i triggered and activated the system to collect and send SLD data via RZ70. As for the Java Systems, i triggered and activated it in the SLD Data Supplier in the visual admin. I performed the CIMOM test and it was a success. Furthermore, i've triggered the send SLD data. In order to check whether it worked or not, i've checked the respective local SLDs of the systems and viewed that it is updated there for both ABAP and JAVA. Furthermore, i've checked the system landscape and viewed the systems are updated for both ABAP and JAVA except for our APO system, both ABAP and JAVA as well. As another step, i reconfigured the Data supplier in the administration of the SLD of APO in order to make sure that the password of xisuper is correct or something. However, until now, it has yet to be updated.
Hope you could help me.
Thanks so much!

Have you checked the Log on the receiving and sending SLDs to see of there is an error?

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.

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

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

PI 7.1 and central SLD

Similar Messages

Maybe you are looking for