Applying JAVA Support Packs in JED

System

Client: SunAmerica Retirement Services.

Document by
Kannan.K
SAP Basis
Mphasis Finsolutions Pvt Ltd, Chennai

Page 1 of 11
Java Support Package Manager (JSPM)

Purpose

You can use the Java Support Package Manager (JSPM) to apply support packages on
deployed software components. You can also deploy SAP and third-party software
components to which you can then apply support packages and patches. You can
deploy new business packages of mySAP Business Suite. You can also upgrade and
update business packages of mySAP Business Suite that are deployed on the system
to a higher release and support package level respectively. In addition, JSPM detects
SAP software components that have been modified and allows you to apply support
packages to them.

Integration

JSPM connects to the SDM server to deploy support packages and software
components. The SDM server performs additional validation of the support packages
and software components for deployment.

JSPM is integrated with the SAP NetWeaver Development Infrastructure (NWDI).

JSPM detects SAP software components that have been modified and allows you to
apply support packages to them.

Features

JSPM has the following features:

● Maintenance certificate

You can update SAP components only if you have a valid maintenance certificate. For
more information see note 1236587.

● Usability

○ Offers a simple and intuitive graphical user interface (GUI)

○ Shares common GUI with SAPinst and SAPJup

○ Automatically detects and offers you only components that can upgrade
deployed components

○ Shows only necessary information. Shows additional details at your

request.

● Deployed Component Overview

○ Displays support package level information

● Support Package Level Administration

Besides Support Packages JSPM also supports Enhancement Packages.

Page 2 of 11
 ○ Allows definition of dependencies between versions of software components

○ Checks whether a new software component version may correctly upgrade

an existing software component version

● Development Component Level Administration

○ Checks deployment dependencies between development components

● Update of Kernel Binaries, Software Deployment Manager (SDM), Internet

Graphics Server (IGS), and JSPM

● Deployment

○ Allows you to apply a support package stack

○ Allows you to apply single support packages

○ Allows you to deploy SAP and third-party software components

○ Allows you to deploy and upgrade business packages of mySAP Business

Suite

○ In NWDI development (DEV) and consolidation (CONS) systems, detects

modified software components and transports them for deployment to NWDI

○ In NWDI test (TEST) and production (PROD) systems, detects and deploys
modified software components

○ Informs you if restarting of the J2EE Engine is necessary during the

deployment process

○ Offers a better support of the patch process in a distributed systems

scenario

○ Monitors and logs the deployment process

○ Allows you to restart the deployment of support packages

Applying JAVA Support Packs in JED System

Here we are upgrading the support pack stack level from 15 to 19 in JED System. As
Java support packages are cumulative, it is enough if we can directly upgrade to the
required support package level (here, it is 19.) without bothering for the middle
package stack levels.

I have listed down the steps in deploying JAVA support packages along with the
issues we faced and the resolutions we found for them.

Page 3 of 11
1. Downloading the required support package stack level from SAP
Service Market Place.

• Login to Service market place

• Go to DownloadsàSAP Support packagesà Entry by application
groupàSAP NetweaveràSAP Netweaver 7.0àLink to SP stack
application
• Mention the target stack and source stack and select the required
usage types as shown:

And click next.

• Select all the java support packages and add to download basket for
approval from solution manager.

Page 4 of 11
 • Login to solution manager system.
• Go to Solution_manager transaction
• Go to change managementà Maintenance Optimizer and click on maintain
optimizer created for the purpose

• Click on Confirm files to download.

• Go to Download basket and download the required files to your hard disk.

Page 5 of 11
2. FTP the files to JED.

• FTP all the files from your hard disk to JED server into /sapcd/JAVASPS19
folder
• Then move all the files to the /usr/sap/trans/EPS/in directory for the
processing.

3. Start Applying the JAVA support packages.

• First of all, we have to the launch JSPM.

• Set the environment variable by following below command.
• Setenv DISPLAY <ip address>:0.0

• Now we have to start JSPM.

Go to usr/sap/JED/JC01/j2ee/JSPM
And execute the go shell script
. /go

• This will connect to SDM server and invokes JSPM GUI screen.

Page 6 of 11
ISSUE 1: Here we faced an issue as we don’t have the SDM password. So we have
changed SDM password at OS level in the following way.

Login to OS as jedadm and do the following:

cd /usr/sap/JED/JC01/SDM/program
./StopServer.sh "sdmhome=/usr/sap/JED/JC01/SDM/program"

./sdm.sh jstartup "sdmhome=/usr/sap/JED/JC01/SDM/program" "mode=standalone"

./sdm.sh changepassword "sdmhome=/usr/sap/JED/JC01/SDM/program"

"newpassword=malibu23"

./sdm.sh jstartup "sdmhome=/usr/sap/JED/JC01/SDM/program" "mode=integrated"

./StartServer.sh "sdmhome=/usr/sap/JED/JC01/SDM/program"

Page 7 of 11
Click on ‘Single support packages’.

Click ‘next’.

This will display all the support packages that are ready to be deployed.

Page 8 of 11
 • Click next and start the deployment.

This will first schedule all the support packages to be deployed and
automatically process all the support packages one by one.

ISSUE 2 and Resolution:

After click start to deploy all the support packages for the stack it returned an error
called “Not enough memory for the device”.

The filesystem in /usr/sap is having around 1.5GB of free space at that time which
may not be sufficient to process all the support packages.

So we have decided to start deploying the patches a few at a time and not all.

• We started deploying the patches few at a time and even after that we faced
with an issue.

ISSUE 3 and Resolution:

The Deployment ended with an error and after checking the JSPM logs, we came to
find out that the password for administrator in the Secure Store area was not
correct.

We launched the configtool and clicked on Secure Store mode.

Page 9 of 11
We changed the password of Administrator to the current password (malibu23) and
saved the changes and the restarted the SDM server.

This resolved the issue.

• We continued the deployment of JAVA support packages a few at a time and

the process went on smoothly.

Page 10 of 11
All the JAVA Components are successfully upgrade to Support package level 19 in
JED Portal Server.

Page 11 of 11