cancel
Showing results for 
Search instead for 
Did you mean: 

EWA: Outdated SAP JVM Information - Update Stores

Former Member
0 Kudos

Dear Experts,

I have already switched to SAP JVM about a month ago. The EWA alerts for the system are still showing the message:

"SAP JVM 4 is recommended to use instead of SAP partnersu2019 JDK 1.4. Please refer to SAP Note 1495160 for more details."

The jvm switch was performed succesufully and I´m able to confirm this at: http:// configuration:

Instance.properties and instance.properties.vmprop are OUTDATED. The information from the files as operating system level was taken about 3 months ago, and at this point the java jvm hasn't been updated yet.

Then, my question is how to get updated datain my EWAs? or if I´m right about that thin info is taken from the stores then, how to manually trigger a store update??

Regards,

Diego.

Accepted Solutions (1)

Accepted Solutions (1)

Paul_Babier
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello,

Did you perform a Managed system setup in Solman_setup after you performed the JVM switch? You didn't mention you did, just the JVM switch was successful.

The managed system setup is how you setup am EWA for a Java system. If something changes on the managed system, such as a software update, or a new JVM, Solman_setup to perform the managed system setup again, and you did not, then I would advise you do so because this is how SMD will et updated. It won't update merely by changing the JVM, you need to pick up those changed witht eh managed system setup.

However if you did run the managed system setup afterwards, you should let us know.

Regards,

Paul

Former Member
0 Kudos

Paul,

Thank u very much for your reply.

Iu00B4ve already executed the introcope agent configuration again, because it was running using the partner (Sun) JDK after the switch. Nowadays the instroscope agent has the following properties:

            1. - 4103350 - server0

JDK Location: C:\usr\sap\###\DVEBMGS00\exe\sapjvm_4

Enterprise Manager Host: #######l

Enterprise Manager Port: 6001

Introscope Agent Name: ###_DVEBMGS00_server0

Introscope Agent Profile: IntroscopeAgent.profile

Autoprobe Directives: sap_typical.jar,sap_sapvm.jar,sap_smd.jar

Wily Version: 8.2.3.5

Introscope Agent Version: ISAGENT.8.2.3.5-2011-09-13

Introscope Agent Log Location: C:/usr/sap/DAA/SMDA97/SMDAgent/temp/IntroscopeAgent.log

If you mean to execute the whole managed system configuration again, it doesnu00B4t make sense at all. It means i have to recreate the RFCs again for example. It shouldnu00B4t be that way.

Thank you!

Diego.

Paul_Babier
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello,

Yes, I mean perform the entire managed system setup again, run Solman Setup > Managed system setup, and performt he procedure again on the SID having the issue. This is required and not optional.

Regards,

Paul

Former Member
0 Kudos

Paul,

Is there a note or some SAP official documentation where this is write down?.

You´re telling me that EACH TIME I change some software in my managed system I HAVE TO re-execute ALL the steps AGAIN

in SOLMAN_SETUP for this managed system. As I said before, this shouldn´t be that way. As an example, the kernel information

was updated AUTOMATICALLY and I didn't re-execute ANY configuration step again. SAP MUST provide a automatic way to fetch the system configuration.

If there´s a SAP note that states: "you MUST re-execute managed system configuration again each time you change some software component in your managed system"

please let me know and I'll inmediately open an OSS message to claim for an automatic functionality, because this would be not only an issue, but an incorrect concept.

Thank very much indeed for your responses.

Diego.

Paul_Babier
Product and Topic Expert
Product and Topic Expert
0 Kudos

Diego,

What I say is what needs to be done to resolve this issue.

There is not a Note that states this to my knowledge.

There may be a reference to this int he COnfiguration guides.

You may take my advice or not. You can wait for others to confirm what I have stated.

I have attempted to help you. If you do not wish to accept the assistance that is your choice.

However if you would like this issue resoloved, then you need to do perform a managed system setup.

It shouldn't be as work intensive as you are making out, as it should have the old values retained, and you really will be changing very little, as you will be accepting the values there from the last setup.

But I stand firm, Java systems must have the Managed system setup performed when the software is updated.

And this is especially true for EWAs to be correctly generated.

Your own diagnosis has determined that SMD stores for SAPJVM have not been created....why? You have not run the Managed system setup. You have stated you changed the JVM and the EWA is not reflecting it. Why? Because you have not

run manage system setup.

If you want this issue to resolve, then I recommend you accept the advise and run the Managed system setup on this system again.

Regards,

Paul

Former Member
0 Kudos

Hello,

This problem has been solved. I decided to delete the stores for this java instance. Stores were recreated after the execution of the extractors.

SAP JVM info is now updated an is also getting checked every day after the corresponding extractor runs. I guess the issue was due a some corrupted store. Unfortunately this problem occurred in a solman

7.01; for 7.10 there are a lot of tools for store admin: http://wiki.sdn.sap.com/wiki/display/TechOps/ConfVal_CCDB_Admin

@Paul: Thank you very much indeed for your support

Regards.

Former Member
0 Kudos

Hello Diego,

I know that this is quite an old blog now.

But we are facing the same issue and our Solman version is 7.01.

Could you please provide the steps you performed to delete the stores ?

And is there any impact in deleting the same ?

Regards,

Abin

Answers (0)