cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SID remains in SLD as WAS Java entry even when Java Stack is deleted

Former Member
0 Likes
381

Hi there,

Can somebody help me with next strange behaviour in the SLD.

Some SID's in our Landscape Components (tc SMSY) on Solution Manager has as Data Source 'SLD'.

These SID's comes from the SLD and are feeded by RZ70 for the ABAP part and by the SLD Data Supplier for the JAVA stack.

The SLD Data Supplier service is set up by the Virtual Administrator.

Now, we have systems in the SMSY with an sidname like <SID>_NABP.

These kind of entries has then SLD as datasource.

The problem is that I don't want these entries in the SMSY beacuse ther is no JAVA stack anymore.

The Java stack is removed completely.

I removed the WAS Java entry in SLD.

But, this enty in SLD is reset after a while.

So, when I remove the entry in SMSY on SolMan and in the SLD WAS JAVA, still the component is recreated in SMSY with datasourrce coming from SLD.

The data in SMSY is empty (no instance, no database). Only the SID and hostename is available.

What i believe is that something triggers the SLD Data Supplier but I can not reach it because JAVA and so Visual Administrator included is removed from the system.

Maybe, if somebody can tell me how SLD is feeded for the JAVA stack, I could find the solution.

I really hope that somebody can help me out.

Thanks

Paul Van Daele

Edited by: Paul Van Daele on Sep 9, 2009 11:06 AM

View Entire Topic
stuart_campbell
Active Contributor
0 Likes

Hi Paul

This is indeed unusual

As Solution Manager gets the data from SLD - I have to believe the problem lies with SLD

Is the SLD obtaining data from another SLD or Central SLD via export/import track or automatic forwarding - it could be this is where the entry is coming from

I guess also check data supplier connections between the WAS JAVA server and SLD server to see if there

is a data supplier update occuring - this would require someone from BASIS team or with network experience to

identify

Hope this helps

Stuart