cancel
Showing results for 
Search instead for 
Did you mean: 

Solution Manager SLD not getting updated completely

Former Member
0 Kudos

Hi,

I have bridged my Solution manager SLD to the central SLD in the landscape. The connectivity is working fine.

For one system in the landscape connected to central SLD -I can see the entry for both ABAP and Java component, but in the SolMan SLD tha data for ABAP component is getting populated while for Java component the entry is not coming.

Can any one help me with the possible reason for this discrepancy?

Regards

Dhiraj

Accepted Solutions (1)

Accepted Solutions (1)

stuart_campbell
Active Contributor
0 Kudos

Hi Dhiraj

Is the CIM and Netweaver version of Solman SLD and Central SLD the same

Sometimes you may get issues in sync options if the source and target SLD are different versions or CIM patch levels

Best wishes

Stuart

Former Member
0 Kudos

Hi Stuart,

Yes both checks suggested are fulfilled. Infact I am able to get the ABAP data updated but not the Java. Seems there is issue in transfer of Java data to central SLD.

Regards

Dhiraj

Answers (4)

Answers (4)

stuart_campbell
Active Contributor
0 Kudos

Hi

I also had a look through this thread and it is not yet clear if you have triggered a manual data supply run from Visual Admin tool -> SLD Data Suppliers tabs of the missing J2EE systems as suggested before

In previous occurances of this issue, if the last update was before the sync was set up- there may not have been a subsequent update to forward to the data to the Solution Manager SLD - some sync options may only react to data supply updates they may not automatically push all the data as soon as you setup the bridge - therefore you may need to manually send an update from the J2EE Visual Administrator of the J2EE data supplier or wait for the next scheduled update to get the system in the target SLD

Best wishes

Stuart

stuart_campbell
Active Contributor
0 Kudos

Hi

How did you setup the bridge - i.e what forwarding option are you using?

In the past I remember a similiar issue because the J2EE Data Supplier could not send information to a gateway - it actually sends the information direct via HTTP

However if you are forwarding via a synch option in the SLD itself and not using bridge distribution then ideally the JAVA system should be part of any ALL or LD based sync

Are no JAVA systems forwarding - what about ABAP and JAVA dual stacks?

Best wishes

Stuart

kunapareddy1
Advisor
Advisor
0 Kudos

Please check when is the last time that the java component information is updated to the central SLD. Please try updating the information manually from the Visual Adminsitrator and check if the information is also passed through the SLD bridge

Former Member
0 Kudos

Hi

Normaly, if the Fetch Job is running successfully the Java System should appear in the Buttom of SMSY under System Comonents --> JAVA.

If the Job is not running; Check the Tx: " sldcheck " the Function LCR_LIST_BUSINESS_SYSTEMS should terminate successfully.

regards

Murat

Former Member
0 Kudos

Hi Murat,

SLDCHECK result is successful

Here is the part of the output

Calling function LCR_LIST_BUSINESS_SYSTEMS

Retrieving data from the SLD server...

Function call terminated sucessfully

I still cant see entry for my java system in SMSY.

Regards

Dhiraj

Former Member
0 Kudos

Hi Dhiraj

are the JAVA Systems listed in /sld with a current sync date?

regards

Murat

Former Member
0 Kudos

Hi Murat,

I can see the time stamp for java component update in SLD is very old.

Is the the possible reason? To understand further how is data from central SLD synchronized to bridged SLD? Is it the delta or transfer is based on time stap or some other algo?

It would be very helpful if you can explain a bit.

Regards

Dhiraj

Former Member
0 Kudos

Hi Dhiraj

It seems that the data is not synchronized correctly!

Delete the old entry in the SLD. Verify that the Username and PW you are using are correct (not locked, permission etc) in the SLD satellite system (Data Supplier). Then restart the JAVA Engine to trigger a data transfer.

Regards

Murat