AS JAVA technical system not updated/registered in SLD

[Former Member]

Hi,

We have setup the SLD bridge connection from our SLD with 7.0 SAP J2EE

server which is our local SLD to SLD with 6.40 SAP J2EE server which is the master or central SLD. Actually we have this set up, that we have configured a local SLD for our Netweaver 2004s SR2 or Netweaver 7.0 system and connect it to the central SLD which is also a Netweaver system but of lower release, Netweaver 2004 SR1.

Since Netweaver contains both ABAP and Java, I can see that our WAS ABAP technical system (of the SLD 7.0) was

succesfully registered and updated on the central SLD 6.40 but I cannot

register or update the WAS JAVA technical system (of the SLD 7.0) in the central SLD 6.40, but it can be updated in our local SLD which is then connected to the central SLD as mentioned.

Since my update for the WAS ABAP was already working and its updated

in the central SLD 6.40, what can we do to achieve the same result for the WAS

JAVA? Because if it works with WAS ABAP, what is wrong then with WAS JAVA? What might be the cause or some other configurations to be made?

Also can we synchronize the CIM updated with all the SLD? We want to

see if we can just update the CIM content of SLD 6.40 and pushed this

with the other SLD on the system e.g. SLD of 7.0.

[Former Member · Accepted solution]

Hi,

I think you should certain configurations for your system to be listed under SAp Java systems.

1.Go to visual admin,c:\usr\sap\SID\JCxx\j2ee\admin

run go.bat.

Then go to services-----SLD Data supplier.

go to Http settins under that,enter the details of central SLD you want to connect,

hostname,http port,sld admin user and password.save it.

go to CIM client settings,enter the same details there and save.

Then check CIM client generation test.it should be sucessfull.

then trigger SLD data transfer at the top left corner.

it also should be sucessfull.

Then your system will be listed.

2.may be you have to create a role called Lcr administrator with all Lcr* actions assigned to it.

then this Lcr administrator role should be assigned to ur administrator user.

hope this works.........

reward points if helpful............

[Former Member]

Hi,

For information only, this problem is solved and validated with another system accordingly. Please see SAP note 909797 for more details. The bottomline is that JAVA patching solved the issue of Web AS Java not registered in a master or central SLD from a local SLD.

Reagrds,

Jennah

[Former Member]

Hi,

For information only, this problem is solved and validated with another system accordingly. Please see SAP note 909797 for more details. The bottomline is that JAVA patching solved the issue of Web AS Java not registered in a master or central SLD from a local SLD.

Reagrds,

Jennah

[Former Member]

Hello,

Thanks for your response. We have actually configured everything in SLD and also noted your suggestions. There is nothing wrong when it comes to updating the Web AS Java in our local SLD but once we do it on our central SLD to which our local SLD is also connected, the Web AS Java part won't update. Only the Web AS ABAP part have successful updates both with the local and central SLD. But in Web AS Java, only successful updates are achieved in our local SLD and not in central SLD. What might be the cause of this? Are there any other configurations to be made?