Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Hi Scott:
A.
For PI its preferable to configure a Local SLD because of the Criticality for XI Interfaces.
>> If you have the choice, i would say individual SLD for the PI systems is better.
>> Alternatively, Having a High availability Central SLD controlling QA and PRD separately is preferable as opposed to having your SLD in QA for QA and PRD.
Robert:
What do you opine over this? '
B.
In relation to SPROXY Config in ECC:
Unless you create a separate RFC Destination in ECC pointing to the ESR in your PI System, the SPROXY would work ONLY if you already have configured PI System as your Integration Server.
>> What this does is establish a link for ECC to read the ESR details from the Exchange Profile in your PI System.
* Make sure the Configuration as below is maintained in your ECC system.
This is what i do to link my ECC system to XI System
1) Enter the PI System/Gateway info for SLD Data Supplier (RZ70)
2) Enter the SLDAPICUST info for PI System. (user ID#PIAPPLUSER)
3) Create the TCP/IP RFC LCRSAPRFC and SAPSLDAPI with their respective Program ID's that are configured on XI Server.
4) Create the Business System for ECC in PI SLD.
5) Create HTTP Destination Type H for PI Server
6) Configure the Integration Server in SXMB_ADM to be your PI Server.
SXMB_ADM >> Integration Server >> IS_URL >> Set to your HTTP Destination type H which points to the PI System.
Just went thru the doc URL sent. This is what constitutes step 1.3.
C.
Moving SLD Data:
1) For Non-PI SLD's the data can be fed by Sync from DataSupplier. (For Example: SolMan getting the Current Data feed from individual Local PI SLD's)
2) For Each PI SLD, you need to take into Consideration of the SLD Transport Targets, which will be used for importing XI objects into Integration Directory.
XI Dev SLD: Mandatorily Needs Dev systems
XI QA SLD: Mandatorily Needs Dev Systems with SLD Targets for QA Systems
XI PRD SLD: Manadatorily Needs Dev Systems with SLD Targets for PRD Systems
D.
CTS is what you need configured.
>> All the info for PI Specific configuration is in the link provided.
Regards,
Raghav
---------------Original Message---------------
From: scottslater
Sent: Tuesday, September 07, 2010 10:28 PM
Subject: SLD - central , local , design-time ,runtime
> For PI ( 7.1 EHP1) ,ECC 6.0 and BI ( 7.0) dev ,qa and PRD systems , how many SLDs should I deploy ? To make Guids unique in the software components , what strategy should I use if I want DEV PI system to have its own local SLD ... and QA and PRD to use the SLD lcoated in the PRD Pi system?
>
> Is it advisable to connect ECC DEV , BI DEV to the DEV PI SLD ...and ECC QA , ECC PRD ,BI QA and BI PRD to connect to the PI PRD SLD?
>
> I think solution manager local SLD will get the data by using the SLD bridges from DEV PI SLD and PRD PI SLD. Is it okay to do?
>
> In the above case, can I call PI DEV SLD as design-time SLD and PI PRD SLD as runtime? What are the differences between design-time SLD and runtime SLD?
>
> Also what is the central SLD...In my case which one is central SLD? If there is none, do I need one central?
>
> Thanks for all your help.
| __.____._ Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| |  Raghav
SAP Basis Helper
Posted helpful replies on 5 threads in a group to earn a Bronze Achievement Related Content White Papers
In the Spotlight  _.____.__ |
Mark as helpful
