on 02-15-2013 7:49 AM
Hi Basis Guru,
I'd like to ask some help especially to those who have experience in switching JVM from 1.4 to SAP JVM 4.1. I've done this in one of the BW system in a single instance and it was successful. But for systems with several instances, the system has CI and 4 dialog instances, how will the SAP JVM switching be carried out? Anyone has an idea? Please enlighten me.
Thanks!
Hi Guys,
I have one more thing to consult. The SAPJVM switching activity in PRD was postponed. Now my worry is the System Copy (P->Q) activity is coming up. The current situation is, QAS is already using SAPJVM while PRD is not (still using old JDK). I know there's an issue with the System Copy with this the current setup.
We have this idea to switch back the QAS to old JDK and do the system copy. What can you advice with this?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I am not sure whether I got your question clear.
If you mean that you want to perform the system copy from PRD to QUA via system copy and use JDK in your quality system.
If yes, You don't need to worry about the different version of Java in PRD & QUA.. Just take an export and import it in your QUA system...
Before starting the import, set the JAVA_HOME to your old JDK and start the import.... Nothing else is required...
There is no way that different version of JAVA in PRD & QUA will cause problem....It will work.
Thanks and Regards,
Vimal
Hi Joseph,
Just to be clear. Currently I have the following JAVA versions.
BW System: ABAP+Java Stack
PRD (using old JDK)
QAS (using SAPJVM 4)
Now I want to do System Copy from PRD -> QAS. Will there be any issue with the difference in Java? Because I'm going to export Java from PRD and import these to QAS.
Please enlighten me.
Thanks.
Hi,
Make sure that your jstartup/startup/vmhome instance parameter is pointing to your sapjvm folder.
in the config tool , you need to make sure that old settings are in place ...Please refer the below notes for the parameters that are to be set in your config tool.
Note 1603093 - SAP JVM 4.1 parameters NetWeaver 2004 and 7.0
Note 1522200 - SAP JVM 4.1 parameters when switching from a partner JDK
If possible take a screenshot / backup of your existing values of your config tool that will be helpful to you.
Thanks and Regards,
Vimal
Meaning, i won't change anything in QAS? Just take the screenshot of the current parameters. Then I can do the import to QAS without having any issues?
I thought I need to switch back the old JDK in QAS before doing the import that is why I'm asking what are the parameters need to be changed
Thanks.
Meaning, i won't change anything in QAS? Just take the screenshot of the current parameters. Then I can do the import to QAS without having any issues?
Yes. You don't need to do anything... Just take a screenshot of your current parameters so that in case after the import , system is coming up you can refer the values before the import and change it and start the system.
mostly you dont need to change anything... Iam saying just in case or as a backup...
I thought I need to switch back the old JDK in QAS before doing the import that is why I'm asking what are the parameters need to be changed
No.. You don't need to switch back to JDK.. You can still use SAPJVM in your QAS system. It will work....
Thanks Joseph,
One more thing. I have run through the system copy document and in the "Target System Installation" there is a part in the sapinst that asks for the JDK directory. What should be the entry here? the old java home or the new one, since SAPJVM is already used. This is in QAS system.
I attached the screenshot during the target system installation. It's asking for the Java installation directory. Since the target system is QAS and is using SAPJVM 4 already, would there be any issue installing the old Java in the same directory where SAPJVM is located? Since you recommend to indicate the location of the SAPJVM dir.
Hello
When you do the import using sapinst at one stage you need to provide the JDK and the JCE policy files.
That's the only thing you need to do.
Cheers
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
Have you checked these links ? if not please.
Cheers
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Reagan,
Yes, i've read it already. In fact I already have done this before but it was only in CI. But the scenario now is, I have a CI and couple of Dialog Instances. My question would be, do I need to perform the JVM switching in all of the DI also? Or in the CI only. I tried executing java -version in all of the DI's but no result however in CI there is a result when java -version is executed. Does this mean there's no JVM installed in all of the DI's?
Thanks a lot for your help.
Yes. You need to perform the sam for your DI also.
I have add the same scenario.
1. If your system is ABAP alone, then you can just extract the SAPJVM file and just set the JAVA_HOME environmental variable to the SAPJVM part.
2. If your System is ABAP + JAVA , then you have to set the JAVA_HOME environmental variable as well as in your java instance profile you can see a parameter like jstartup/startup/vmhome... Set the value of that parameter to the path of your SAPJVM location.
3. If your system is JAVA alone, then just set the instance parameter jstartup/startup/vmhome to the path of SAPJVM location. or you can run the SAPJVM switch tool.
You need to restart your system to have the changes effective.
Thanks and Regards,
Vimal
Hello Eleazar
Mostly the SAPJVM gets installed in the /usr/sap/SID/JC00/exe directory which is DIR_EXECUTABLE (local directory for executables).
This is separate for all instances which means if you have CI with AS on different hosts then they will be present on each host.
So the answer to your question is a YES.
Cheers
RB
Hello Joseph,
The system is ABAP+Java Stack. I'm planning to do the following:
1. Perform the switching in CI using the switch tool.
2. Perform the switching in the DIs using the switch tool. (Same procedure with CI)
3. Restart CI.
4. Restart DIs.
Let me know if the above procedure is correct.
Thanks.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.