Sapnote J2EE PAtch Installation

7/31/2019 Sapnote J2EE PAtch Installation

http://slidepdf.com/reader/full/sapnote-j2ee-patch-installation 1/8

18.12.2007 Page 1 of 8

Note 657763 - Installing SAP J2EE Engine Support Packages (Web AS6.30)

Note Language: English Version: 21 Validity: Valid from 30.09.2004

Summary

Symptom

CAUTION: THIS NOTE APPLIES TO SP02 ONLY!

This note describes how to install SAP J2EE Engine Support Packagesfor the SAP Web Application Server 6.30 up to SP02, only!

-----------------------------------------------------------------------

Caution: If you are installing SAP Web Application Server Java 6.40

Support Packages (SP04 and higher), use the installation description in therespective Support Package Stack Guide.Caution: If your source release is 6.30 SP02, you have to install SP04

first, before you can install higher Support Packages!

You can find the Guide on SAP Service Marketplace at

service.sap.com/instguidesnw04 -> Operations, and on the page from which

you download the NetWeaver Support Packages (link to documentation). You

can find Support Package number used for the Stack in chapter "List of

Required Support Package Levels and Names".

Note: If you are installing Support Package 04 for SAP Web Application

Server Java 6.30, use the installation description from SAP ServiceMarketplace: service.sap.com/instguides -> SAP Components -> SAP Web

Application Server -> Release 6.30 -> SAP Web AS Support Package Guide

630SP2 to 640SP4.

Note:

o For information on deploying Support Packages for the SAP J2EE

Applications, see SAP Note 656711.

o For information on deploying Support Packages for theSAP J2EE Engine on IBM iSeries, see SAP Note 667064.

-----------------------------------------------------------------------

As this note is updated regularly, make sure that you use the most current

version.

More TermsJ2EE Support Packages, SAPinst, patch, J2EE Engine

Cause and PrerequisitesA Support Package for the SAP J2EE Engine consists of four different files:

o SAPINST<SP number>.SAR



18.12.2007 Page 2 of 8


This file contains SAPinst and is operating system-dependent.

o CTRL<database><SP number>.SAR

This file contains the control files and is operating

system-dependent.

o J2EERTOS<SP number>.SAR

This file contains the operating system dependent parts of the SAP

J2EE Engine, the SCS server, the SCS client, and SAPCCMSR. It is

operating system-dependent.

o J2EERT<SP number>.SAR

This file contains the SCAs and SDAs of the SAP J2EE Engine. It is

operating system-independent.

The "SP number", for example, 01_0-12345678, is made up of

o the number of the Support Package

o the patch level

o an eight digit ID, which is used for SAP internal purposes

To unpack the archives, use tool SAPCAR. You can find SAPCAR on SAP Service

Marketplace under

http://service.sap.com/patches -> Technology Components -> SAPCAR.

For further information on the use of SAPCAR, see Note 212876.

Before you start SAPinst, make sure that the total freespace in yourdatabase is at least 1 GB.

Caution: To avoid inconcistencies, the SAP J2EE Engines of you developmentenvironment should have the same release and Support Package level as the

SAP J2EE Engine of your runtime environment.

Solution

ContentsI/ ..... Downloading Support Packages

II/ .... Unpacking Support Packages

III/ ... Deploying Support Packages

IV/ .... Troubleshooting

V/ ..... Post-Installation Activities on the Dialog Instances

VI/ .... Other Post-Installation Activities

VII/ ... Information on Support Package Contents

Note: If you are using IBM iSeries, follow the instructions in Note

667064.



18.12.2007 Page 3 of 8


I/ Downloading Support Packages

1. On your host, create one directory in which to save the packed files.

There are no special prerequisites for the directory.

2. Download the Support Packages from SAP Service Marketplace. You can

find the Support Packages under:

http://service.sap.com/patches -> SAP Support Packages and Patches ->

Entry by Application Group -> SAP NetWeaver Components -> SAP

NetWeaver Components (< SAP NW 04) -> SAP Web AS -> SAP Web AS 6.40 ->

SAP J2EE Engine 6.40.

You can find the operating-system dependent files in the folder

named after the operating system and the operating-system

independent file in folder "OS independent".

3. Save files SAPINST<SP number>.SAR, CTRL<database><SP number>.SAR,

J2EERTOS<SP number>.SAR, and J2EERT<SP number>.SAR in the directory

you created.

II/ Unpacking Support Packages

Unpack the files using the SAPCAR executable file. Example: In the Command

Prompt window, type

o (Windows) <path to SAPCAR.EXE>\sapcar.exe -xvf <file name>.SAR

o (UNIX) <path to SAPCAR>/sapcar -xvf <file name>.SAR

Files SAPINST<SP number>.SAR and CTRL<database><SP number>.SAR will be

unpacked in a folder called SAPINST-CD, files J2EERTOS<SP number>.SAR,

J2EERT<SP number>.SAR will be unpacked in a folder called J2EE-RUNT-CD.

III/ Deploying Support Packages

1. Log on to your SAP System host:

- on Windows as a user who is a member of the local

administration group.

- on UNIX as user "root".

2. On UNIX, create an installation directory with sufficient space and

permissions 777. To create the directory, enter:

mkdir <SAPinst_INSTDIR>



18.12.2007 Page 4 of 8


chmod 777 <SAPinst_INSTDIR>

3. Stop SAPOSCOL with Command saposcol -k (UNIX) or using service

saposcol (Windows).

4. Start tool SAPinst:

- On Windows: From the directory in which the SAPINST<SP

number>.SAR and CTRL<database><SP number>.SAR have been

unpacked, go to subdirectory SAPINST\NT\<OS > (e.g., \NT\I386)

and double-klick on file sapinst.exe.

- On UNIX: Change to the installation directory with command "cd

<SAPinst_INSTDIR>". To start SAPinst, enter:

<Path to directory of SAPINST<SP number>.SAR and

CTRL<database><SP number>/SAPINST/UNIX/<OS >/sapinst

A selection screen with the following options appears:

- Install a dialog instance (as of SP 01).

For more information, see SAP Service Marketplace at

service.sap.com/instguides -> SAP Web Application Server ->

Release 6.30 -> "Installation Guide - SAP Web Application

Server on <Platform>: <Database>.

- Install the Support Package.

This option will be described in the following.

5. Choose option "Install the Support Package".

The "Selecting the Instance Profile" screen appears.

6. Select the instance profile of the Java central instance and choose

"Next".

If you have installed the J2EE Engine as part of SAP Web

Application Server, the "RFC User Information" screen appears.

Enter the SAP Web AS RFC user, the SAP Web AS RFC password, and the

SAP Web AS RFC client.

If you have installed the SAP J2EE Engine as standalone or after

you have filled in the "RFC User Information" screen, the "Defining

Patching Parameters" screen appears.

7. Enter the password of user <SIDADM> and the password of user

SAPService<SID>.

Entering the values for the Windows domain for the SAP system is

optional.

8. Choose "Next".

The "CD Browser" screen appears.



18.12.2007 Page 5 of 8


9. Specify the file "LABEL.ASC", which is located in the directory into

which J2EERTOS<SP number>.SAR and J2EERT<SP number>.SAR files have

been unpacked.

10. Choose "O.K.".

The "Start Installation" screen appears.

11. If all parameters on this screen are specified correctly, choose

"Start" to start the deployment.

The "Installation Progress" screen appears.

If the parameters are not correct, use the "Back" button to return

to the "Defining Patching Parameters" screen and correct the

parameters.

12. If the deploying process has finished successfully, the "FinishedSuccessfully" screen appears.

Choose "OK" to complete the installation.

IV/ Troubleshooting

Read this section before you start the installation, as the occurence of

some errors may be prevented.

Client SDM version is higher than SP02 SDM If you want to install Support Package 02 and, for some reason, the client

SDM version in your landscape is higher than the SDM version included in

the Support Package 02, you must make the following adjustments before you

install the Support Package:

1. Go to the SDM home directory (for example, usr/sap/<SID>/

<INSTANCE>/SDM/program.

2. Enter the following commands:

- UNIX: StopServer.sh

sdm.sh jstartup mode=standalone

- Windows: StopServer

sdm jstartup "mode=standalone"

- Start with the Support Package installation.

Support Package 2: Hot Fix for JMS ProviderIn order to make JMS run with SAP J2EE Engine Support Package 2, you have

to install a hot fix. For more information, see Note 667303 .

Text file busySAPinst may report the error "SAPCAR: could not open for writing <path>



18.12.2007 Page 6 of 8


<file name>. Text file busy." in log file SCS.log, where <file name> is,

for example, libicudt20b.sl (Unicode on UNIX) or sapevents.dll (Windows).

If this error occurs, proceed as follows:

1. Rename the busy file, for example, to <file name>old.dll.

2. Continue SAPinst using the option "Retry".

3. As soon as possible after the installation, restart the SAP system so

that both SAP Web AS and SAP J2EE Engine are using the latest version.

If your SAP system is a non-productive Unicode system, you can prevent

these errors by stopping the SAP system before the Support Package

installation.

File sapevents.dll is used by "Windows Managment Instrumentation". Instead

of renaming the file, you can simply stop the service, or, if you are

working on a non-productive SAP system, stop the SAP system before the

Support Package installation.

SAPinst does not startIf a previous installation has failed and you want to start from scratch,

delete folder "C:\Program Files\SAPINST" (Windows) or "tmp/sapinst" (UNIX).

If you do not delete this folder, SAPinst cannot startand will issue errors

like "control.xml is inconsistent" or will report wrong table entries.

Do not delete the sapinst folder, if you want to continue an aborted

installation.

Class definition not foundDuring the deployment with SAPinst a dialog window appears with an error

message. The log file displays the error "class definition not found".

Proceed as follows:

1. Restart the SAP J2EE Engine.

2. Continue SAPinst using the option "Retry".

SAP J2EE Instance does not startThe SAP J2EE instance does not start and there are two entries for the

message server port. The error occurs, if you did not choose the default

port when installing the SAP J2EE Engine SP0. Proceed as follows:

1. Stop the SAP system with user <SID>adm using command "stopsap". Ifthis command does not stop the complete system, stop each instance

separately.

2. In directory /etc/services, delete the wrong standard port (36

<instance number>)

3. Change the port in the SDM-Repository in directory /usr/sap/<SID>/

<CENTRAL-Instance>/SDM/program/config/sdmrepository.sdc. Look for

"msport..."

4. Change the message server port in the instance profile of the SCS

instance in diretory /sapmnt/<SID>/profil/<SID>_<CENTRAL-Instance>_<host>.



18.12.2007 Page 7 of 8


5. Restart the complete system with user <SID>adm using command

"startsap".

V/ Post-Installation Activities on the Dialog Instances

Post-installation steps for dialog instances, on which the SAP J2EE Engine

has been installed, will be provided soon.

VI/ Other Post-Installation Activities

SAP NetWeaver Developer Studio: Set flagMake sure that the flag "Perform build automatically on resource

modification" is activated. This flag is located in the SAP NetWeaver

Developer Studio under Window -> Preferences -> Workbench. VII/ ...

VII/ Information on Support Package Contents

For more information on the contents of Support Packages and Patches, see

the following Notes:

703403 Information on SAP J2EE Engine 6.30 SP02 Patch Level 01

Header Data

Release Status: Released for CustomerReleased on: 30.09.2004 14:14:37Priority: Recommendations/additional infoCategory: Installation information

Main Component BC-CTS-SDM Software Delivery Manager for Java

Valid Releases

Software Component Release FromRelease

To Release and Following

SAP_BASIS 60 640 640

Related Notes



18.12.2007 Page 8 of 8


Number Short Text

703403 Information on SAP J2EE Engine 6.30 SP02 Patch Level 01

667303 Hot fix for the JMS provider

Documents

Sapnote J2EE PAtch Installation