cancel
Showing results for 
Search instead for 
Did you mean: 

Connecting AS Java System (old) to the SLD (new)

former_member80258
Participant
0 Kudos
1,229

Hi SAP Community

We have an old BW (7.01) and we wish connect it to a new SLD (7.41). Trying to find some SAP notes or documentation in sap.com We haven't found any documentation.

The main target is it can to calculate java components through Maintenance Planner

Regards and Thank you...!

Accepted Solutions (1)

Accepted Solutions (1)

Matt_Fraser
Active Contributor
0 Kudos

Hi Erick,

First off, I added a secondary tag for NetWeaver Application Server Java, as your question is specifically about doing this with a Java system, yes? If I've misunderstood, please feel free to change the tags.

So, I understand you have a BI Java system on NetWeaver 7.01. I had to dredge up memory a bit here, since almost all of our Java systems are now at 7.4 or higher, where the method is different (and easier). Then I recalled we still run our SolMan system on 7.1, and that has a Java component on NW 7.02, so not too terribly different from 7.01.

To configure the SLD connection in a Java 7.0x system, you need to use remote console to the server, then run Visual Administrator. Drill down to the first Server node, then Services -> SLD Data Supplier. Switch to the HTTP Settings (Data Supplier) tab, and enter the connection information for your SLD, i.e. Host, Port, User (usually SLD_DS_<SLD_SID>), and Password. Then switch to the CIM Client Generation Settings tab and enter the same information, though here you'll probably want to use the SLD_CL_<SLD_SID> user. On this tab you can test the connection with the CIMClient Test button.

Once it's all done, there is a button at the top, looks a bit like a lightning-bolt arrow, which will trigger a send of data to the SLD. You should then be able to see right away if it's working, or within a few minutes. After that, it should happen automatically every 12 hours or so -- that is configurable on the Properties tab.

That should do it. This is independent of the version of your SLD itself. For SLD, higher is better, so having a higher-version SLD than the client connecting to it is a good thing.

I'm assuming your connection from SLD to Solution Manager, and from there to the SAP Customer Portal (and Maintenance Planner), is already working, as you didn't ask about that.

Cheers,
Matt

former_member80258
Participant

Hello Matt

OMG, you are the Man...!

I could to trigger and see AS Java in our main SLD. Thank you for your great and fast support

Kind Regards

Answers (1)

Answers (1)

patelyogesh
Active Contributor
0 Kudos

Hello Erick Verbena,

I do not see any issue pushing your system data to SLD.

Helpful SAP note: 2287046 - How to Generate the System Info XML and upload to Maintenance Planner

Thank you

Yogesh

former_member80258
Participant
0 Kudos

Hi Yogesh

Thank you for your time...! Have a nice day

patelyogesh
Active Contributor
0 Kudos

Hello Erick Verbena,

Happy to see that you found the answer but not sure you will able to use Maintenance Planner with your SAP NW AS java 7.01

Cheers,

Yogesh

former_member80258
Participant
0 Kudos

Hello Yogesh. I could to see it 😄

patelyogesh
Active Contributor
0 Kudos

Hello Erick Verbena,

Are you able to calculate update stack on it? If yes, then its surprising to me!

-Yogesh

former_member80258
Participant
0 Kudos

Hi Yogesh

That's correct...!

Matt_Fraser
Active Contributor
0 Kudos

To Yogesh's point, an update stack is surprising, given that NW Java 7.01 is out of maintenance. But an upgrade stack is not at all surprising, since this is still a completely legitimate source release for an upgrade to a supported release. So, I would not be surprised that your system would show up in Maintenance Planner; after all, my out-of-support SolMan system shows up in Maintenance Planner. I would be surprised if Maintenance Planner allows you to plan a Support Package update that stays on release 7.01 for the Java component.

patelyogesh
Active Contributor
0 Kudos

That is the reason why I mention that you will not able to do anything with it even it is in Maintenance Planner...

Pushing data of the system to SLD make sense but in Maintenance Planner!!!

Matt_Fraser
Active Contributor
0 Kudos
It's necessary to still get the data into Maintenance Planner if you want to upgrade the system to a supported release. MP will still support an upgrade activity from an unsupported release to a supported release; it just won't support an update activity (i.e., support packages, not upgrade) within an unsupported release. For this to be possible, MP has to have the data on the old/start release of the software.

patelyogesh
Active Contributor
0 Kudos

Agreed!

BTW what is wrong with fonts?

Matt_Fraser
Active Contributor
0 Kudos

Not sure. I thought perhaps it was due to being so many levels deep in "reply-to"?