on 07-05-2014 1:13 PM
Dear Experts,
we have installed Netweaver 7.4 for PI which was delivered with SPS05. we have updated Netweaver ABAP components into SP06 successfully. when we tried to apply the JAVA patches through JSPM, it shows no longer in maintenance, you have to use SUM tool. we have checked in the note 1589311 and it says JSPM is supported until Netweaver 7.4 SP03.
can you please let us know, is there any way to by-bass sum tool and apply the Java patches using JSPM (totally 76 components need to be updated).
Thanks in advance!
Regards,
Pradeep
Thanks a lot Ashish,
I will check this in sandbox. Thanks once again.
Regards,
Pradeep
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Experts,
We have not imported JAVA components and reverted the ABAP packages into its old level. We really don't have time to update Solman SPS, doing other configurations to generate stack XML file. We have done PI initial configuration wizard run without any issues( We thought to apply latest support packages before run PI wizard to minimize the errors)
Thanks a lot Hemanth and Asish!
@Asish, if you know the work around to start the JSPM, please post here as it will be useful for the SAP customers who don't have time to update the solman SPS and do the JAVA update through SUM. I accept that it is risky way but users will be having backup of the SAP system before they start the activity so that they can easily revert to old stage if SAP doesn't support or if issues occur.
Thanks once again!
Regards,
Pradeep
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pradeep ,
Here you go ...
But again please dont use this now as you will Not get any Support from SAP in case you get stuck in your upgrade
I'll be explaning this for JSPM on Windows . The Same procedure applies for UNIX Flavours.(Of course take care of seperator and environement Varaible in UNIX)
SAP Bundles the JSPM package in a folder <Drive>:\usr\sap\<SID>\J<Instance No>\JSPM
What SAP has really done in latest patches is changed the script go.bat and removed the bootstrap.bat which has been deleted. It hasn't really done anything much with the other files.Hence it becomes easier to trace back and START JSPM
Steps: -
Login to Windows using <SID>adm User
1) Backup the JSPM Folder
2) Open the go.bat file
Remove all entries and add the below entries in BOLD
@echo off
set rc_restart=42
set OLDDIR=%CD%
set rootdir=%~dp0
cd /D %rootdir%
:restar_jspm
call %rootdir%\exe\bootstrap.bat %*
if ERRORLEVEL 1 (
set rc=%ERRORLEVEL%
goto exit_jspm
)
call %rootdir%\exe\jspm.bat %*
set rc=%ERRORLEVEL%
if %rc%==%rc_restart% (
echo Restarting JSPM...
goto restar_jspm
)
:exit_jspm
cd /D %OLDDIR%
exit /B %rc%
Save the File
3) In the JSPM DIrectory goto exe folder
4) Create a file bootstrap.bat and add the below entries in the file
@echo off
Rem Determine JSPM directory
set rootdir=%~dp0
cd /D %rootdir%
cd..
set rootdir=%CD%
Rem Determine java executable
set JAVA_CMD="E:\usr\sap\ED1\J01\exe\sapjvm_6\bin\java.exe"
set JSPM_JAVA_CMD="%JSPM_JAVA_HOME%\bin\java.exe"
set LOCAL_JAVA=%rootdir%\sapjvm\jre\bin\java.exe
set useParentJVM=
if EXIST %JSPM_JAVA_CMD% (
set JAVA_CMD=%JSPM_JAVA_CMD%
set LOCAL_JAVA=%JSPM_JAVA_CMD%
set useParentJVM=-useParentJVM
) else (
if NOT EXIST %JAVA_CMD% (
set JAVA_CMD="%JAVA_HOME%\bin\java.exe"
)
if NOT EXIST %JAVA_CMD% (
set JAVA_CMD=java
)
if NOT EXIST %LOCAL_JAVA% (
set LOCAL_JAVA=%JAVA_CMD%
)
)
set JSPM_CONFIG="jspm_config.txt"
if "%1" == "-remoteui" set JSPM_CONFIG="jspm-rui_config.txt"
Rem Update JSPM and sync local copy of SAPJVM
%JAVA_CMD% -ea -cp %rootdir%\bootstrap\lib\sdt_jspm_bootstrap.jar Jspm -boot=win -rootdir=%rootdir% %useParentJVM% %*
set rc=%ERRORLEVEL%
if ERRORLEVEL 1 (
echo ERROR: could not update JSPM
)
exit /B %rc%
Save the File
5) Now you are Good to Start JSPM .
6) Right Click on go.bat and select Run as Administrator
AGAIN , A humble request to everyone , Do not attempt this procedure in PRODUCTION Environment.
Regards,
Ashish .A. Poojary
Hi Pradeep,
The Munaul Prepared Directory option will not work in case of an SP Upgrade of AS Java Core Components.
You will have Upgrade via SUM.
I suggest you Upgrade your Solution Manager First and then start the process for upgrading PI.
Although there is a way (Work Around) to Start JSPM here , but I wouldn't put it up here as it would be a risky option to go for.
Because, in case you get stuck in the upgrade, and you have to raise an OSS , you WILL NOT get any Support from SAP.
Regards,
Ashish .A. Poojary
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pardeep,
You have to use only SUM tool for upgrading the Java Patched in your PI System.
With the SUM tool you can easily upgrade the Java component.
If you are facing any issue with the SUM tool,then provide the error screen shot.
Regards
Yogesh Kumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Yogesh,
Thanks! our solman 7.1 is in low level (SPS04) it is not supporting to assign the product instance and getting an error "no CR contend available" if we start to update solman, it will take time to complete the update, product assignment and generate XML file for SUM. That's the reason I am asking any alternate way.
Regards,
Pradeep
Hi Pradeep,
You have to place all required software in the USR/SAP/TRANS/EPS/IN directory.you have to give the location of the directory in SUM.
Also check the permission and owner of all the software in USR/SAP/TRANS/EPS/IN directory.
If still issue not resolved,attached the error screen shot.
Regards
Yogesh
Hi Pradeep,
Hope you are doing good.
If there is no other option and you really do not want to use SUM, then try with the telnet tool.
More info:sap note 1715441. If you wish to deploy many files:
1. Create new directory /tmp/dpl
2. Add all the files that are to be deployed into /tmp/dpl directory.
3. connect to the telnet service of the NetWeaver J2EE server
goto cmd-> telnet <hostname> 5<instance number>08 (you will need to
login with an administrator user of the J2ee engine; not the
<SID>adm user.
4. jump 0 (to server node)
5. execute following command
deploy /tmp/dpl version_rule=all
6. The system will restart (telnet will take care of this).
Thank you!
_____________
Kind Regards,
Hemanth
SAP AGS
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.