RE:[sap-basis] How to configure Local SLD in Central SLD?
Posted by
Admin at
Share this post:
|
0 Comments
Posted by Raghav (SAP PI Basis Consultant) on May 5 at 10:55 AM | Mark as helpful |
For the missing Data:
1) What do you see when you trigger RZ70?
You need to click the execute button to activate and send the Data. Just Activating it will not suffice.
a) are you sure you got the gateway info right?
ex: Server: <hostname> and Gateway: sapgw<Sysno>
Ex:
solman.sld.us
sapgw75
b) Does it mention the SLD_UC RFC Connection successfull.
If not, then pls copy/paste the error.
2) What do you see when you trigger in Visual Admin SLD Data Supplier
a) Does it mention that Data Supply Successfull?
=====================================================================
In your earlier reply, to quote:
"So I think we have to register remaining SLDs also to SM SLD."
This is a bit misleading.
Either you are:
A. replacing your Local SLD's with the Central SolMan SLD (OR)
B. your requirement is to have the Solman SLD to have current system Data at any given point of time.
In the case of A:
Then you need to perform the following:
a) RZ70
b) SLDAPICUST
c) Visual Admin SLD Data Supplier
d) Create RFC's SLDAPICUST and LCRSAPRFC and provide the JCO Program ID's and gateway host info pertaininig to SolMan SLD.
e) Validate the Data Push by logging onto SolMan SLD
f) SLDCHECK and ensure all returns fine.
In the case of B:
a) Log onto your Local SLD and setup a data supplier to SolMan SLD.
The steps to do this is in the previous reply.
b) This way, your Local SLD config stays intact and your SolMan SLD gets the current info for all systems. The best part is, the SolMan SLD remains aloof and local to SolMan system. So it does not bear the integration load typically required; coming from all systems.
So, for now, if you think you need to register your remaining SLD to SolMan, review the steps above and requirement and change as apt.
If any errors, post the error logs and we'll try to figure it out why the data is not showing up.
Are your Systems by any chance in maintenance? Is DNS isolation active?
Sometimes give it about 5-10 mins after a push to get the data through.
I have had data push cross a wide network and it took me to push it twice/thrice to get it registered in the target SLD.
Regards,
Raghav
---------------Original Message---------------
From: Ajay_SAP-BASIS
Sent: Thursday, February 04, 2010 7:55 AM
Subject: How to configure Local SLD in Central SLD?
> I have check all the topics related this SLD config. but no one has answered the procedure. Please post the steps need to do on systems.
> My question is...
> we have already installed Solution Manager 70 EHP1 and for ECC we added to solution manager during install itself but now we have more old systems which have local SLDs. Now I have to include them in central SLD what are the configuration steps need to perform?
> As I know go visual admin in the OLD systems and at SLD data suplier give alla the details of Cental SLD details is that the only step needed? Please respond immediately as this is needed now.
> Thanks in advance.
> -Ajay
__.____._ 1) What do you see when you trigger RZ70?
You need to click the execute button to activate and send the Data. Just Activating it will not suffice.
a) are you sure you got the gateway info right?
ex: Server: <hostname> and Gateway: sapgw<Sysno>
Ex:
solman.sld.us
sapgw75
b) Does it mention the SLD_UC RFC Connection successfull.
If not, then pls copy/paste the error.
2) What do you see when you trigger in Visual Admin SLD Data Supplier
a) Does it mention that Data Supply Successfull?
=====================================================================
In your earlier reply, to quote:
"So I think we have to register remaining SLDs also to SM SLD."
This is a bit misleading.
Either you are:
A. replacing your Local SLD's with the Central SolMan SLD (OR)
B. your requirement is to have the Solman SLD to have current system Data at any given point of time.
In the case of A:
Then you need to perform the following:
a) RZ70
b) SLDAPICUST
c) Visual Admin SLD Data Supplier
d) Create RFC's SLDAPICUST and LCRSAPRFC and provide the JCO Program ID's and gateway host info pertaininig to SolMan SLD.
e) Validate the Data Push by logging onto SolMan SLD
f) SLDCHECK and ensure all returns fine.
In the case of B:
a) Log onto your Local SLD and setup a data supplier to SolMan SLD.
The steps to do this is in the previous reply.
b) This way, your Local SLD config stays intact and your SolMan SLD gets the current info for all systems. The best part is, the SolMan SLD remains aloof and local to SolMan system. So it does not bear the integration load typically required; coming from all systems.
So, for now, if you think you need to register your remaining SLD to SolMan, review the steps above and requirement and change as apt.
If any errors, post the error logs and we'll try to figure it out why the data is not showing up.
Are your Systems by any chance in maintenance? Is DNS isolation active?
Sometimes give it about 5-10 mins after a push to get the data through.
I have had data push cross a wide network and it took me to push it twice/thrice to get it registered in the target SLD.
Regards,
Raghav
---------------Original Message---------------
From: Ajay_SAP-BASIS
Sent: Thursday, February 04, 2010 7:55 AM
Subject: How to configure Local SLD in Central SLD?
> I have check all the topics related this SLD config. but no one has answered the procedure. Please post the steps need to do on systems.
> My question is...
> we have already installed Solution Manager 70 EHP1 and for ECC we added to solution manager during install itself but now we have more old systems which have local SLDs. Now I have to include them in central SLD what are the configuration steps need to perform?
> As I know go visual admin in the OLD systems and at SLD data suplier give alla the details of Cental SLD details is that the only step needed? Please respond immediately as this is needed now.
> Thanks in advance.
> -Ajay
Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Related Content
In the Spotlight
_.____.__ White Papers
In the Spotlight
Your SAP Security is at Risk...Learn How to Stay Protected. Read the free white paper from SenSage