05004 WDEBU7 JSPM Troubleshooting

8/11/2019 05004 WDEBU7 JSPM Troubleshooting

http://slidepdf.com/reader/full/05004-wdebu7-jspm-troubleshooting 1/61

1

WDEBU7 WorkshopChapter 05

Troubleshooting JSPM

Roland Kramer Rampup Coach nw2004s SAP Switzerland



2

JSPM Operation

Overview

The Logs

General Troubleshooting

Overview



3

© SAP AG 2006, JSPM Troubleshooting / Petar Dochev / 3

Three Steps to the New Support Package Stack

1 2 3

Apply ConfigureDownload



4


Step IDownload the Support Package Stack from the SMP

Download content from Service Marketplace http://service.sap.com/sp-stacks

Download the stack definit ion file (XML). See SAP note 884537.



5


Step IIA) Update JSPM

Finally, restart JSPM so changes can take effect



6


Step IIB) Apply the Support Package Stack with JSPM

Do not forget to stop manually SAP MMC and any dialog instances.



7


Step IIIPost-Configuration

Support Package Stack

Guide

Includes all NetWeaver usage

types and standalone

engines

Provided for each SP stack

until at least SR1

Validated by Solution

Validation



8


Use Cases

Apply Support Package Stack• Bundles multip le software components

• Updates complete usage types

• Ensures consistency and compatibility• Preferred way to update the system

• For more information check SAP Note884537 Benefit and use of the Support Package Stack XML

Apply Single Support Packages• Update individual components selected by the user

• Useful to apply patches

Deploy New Software Component

• Add new components that previously did not exist on the system

Business Packages (since SP7)• Upgrade deployed components to h igher release

• Deploy new components



9


Useful Links

Starting point: http://service.sap.com/jspm

SAP Note 891983 - JSPM: Central note

JSPM Media Library

JSPM User Guide

SAP Support Package Stacks (http://service.sap.com/sp-stacks )

Download content

Access Stack Guide

Upgrade of an NWDI-Driven System Landscape



10

JSPM Operation

Overview

The Logs


The Logs



11


Locating the Logs

JSPM logs all major actions and their results. Logs should provide enoughinformation to resolve most issues or at least hint where to look for moredetails.

JSPM logs are stored under directory/usr/sap/<SID>/<CI>/j2ee/JSPM/log

There is a separate subdirectory for each JSPM session. Each directoryname contains a timestamp when JSPM was started.log_20060106105526

log_20060105172135

log_20051216170843

…

Make sure to look in the right subdirectory, usually the latest one. The

format of the timestamp is year, month, day, hour, minute, second.JSPM_PROCESS.LOG (JSPM_PROCESS_1_01.LOG) is the main JSPM log. It maycontain references to other log files from JSPM or from other tools likeSDM. This is the starting point when looking for answers.

SDM logs can be found in directory/usr/sap/<SID>/<CI>/j2ee/SDM/program/log.



12


Log File Conventions

There are two kinds of JSPM logs:

*.LOG – contain log messages

*.OUT & *.ERR – standard output and error streams from external

processes

Since some operations may repeat, respective log fi les are created

with number suf fixes, e.g.KERNEL_DETECTION_01.LOG

KERNEL_DETECTION_02.LOG

…

Base file names are used in this presentation. The exact fi les are

referenced in the parent log, usually the main JSPM log.

NOTE: Process IDs used in JSPM logs are not OS process IDs.



13


Merged Output Files

The output files (.OUT & .ERR ) of some tools (e.g. jcmon) that are

executed multiple times in a loop, are merged into one file.

The output of separate executions is divided by separators like the

following one. This separator is not part of the original output.************************************************************

Thu Jan 12 11:39:28 EET 2006 , N: 3

************************************************************



14


JSPM Log Viewer

Logs tab in JSPM window provides the easiest view of the logs.

Here you can also access referenced SDM logs.



15


Using Standalone Log Viewer

If you cannot use JSPM GUI, you can uti lize the standalone log v iewer from the J2EE engine.

Launch it with logviewer script from/usr/sap/<SID>/<CI>/j2ee/admin/logviewer-standalone

Choose menu File > Add a File… and browse for the desired log fi le. You may need to select Al l Fi les in the filetype filter to view the files.

For more information about the standalone logviewer check Logviewer_Userguide.pdf in the same directory.



16


Viewing Log Files Directly

Log f iles are actually text f iles. They are usually in two formats

Plain text files

ListFormat - special format designed to be opened with a log viewer.

You can open the log fi les with any text viewer/editor.

Sometimes this is the only opt ion (e.g. no GUI available).

Here is the end of a sample line from a ListFormat log file…#Info#1#com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:263)#Java###Starting {0} dialog...#1#SelectPackageType#

Here

Info is the severity of the message. It can be also Warning or Error.For example, you can quickly find error messages in the file bysearching for #Error#.

{0}, {1}, {2}, etc. are positional parameter placeholders.

SelectPackageType is a parameter value.



17

JSPM Operation

Overview

The Logs


JSPM Operation



18


JSPM directory structure

/usr/sap/<SID>/<CI>/j2ee/JSPM/

go – start script for UNIX/LINUX/OS400

go.bat – start script for MS Windows

StartGui – do not use it, unless instructed to do so

StartGui.bat - do not use it, unless instructed to do so

bootstrap/ - JSPM bootstrap program

config/ - various configuration files

data/ - data model files persisting information between JSPM invocations

deploy/ - if exists, contains newly deployed JSPM content

lib/ - jar files containing compiled Java code

log/ - JSPM log files, separate subdirectory for each JSPM session

param/ - property files

tmp/ - temporary storage for work filestrc/ - trace files

Here

<SID> is the SAP system name

<CI> is the Central Instance name (JCnn or DVEBMGSnn)



19


JSPM Version

JSPM is a regular software component. You can check its version

with the standard tools.Deployed Components tab in JSPM itself .

System Information web page.

SDM Repository view.

Since SP7 it is displayed in the status bar as well as in Help > Aboutdialog. Also logged in JSPM.LOG

Running JSPM tool with version <version>.



20


Patch JSPM First

As described in the guide, JSPM should be patched before updatingany other components.

To apply stack SP X, follow this sequence:

1. Self-patch JSPM to SP-level X as a Single Support Package andrestart JSPM.

2. Apply the stack with Support Package Stack option.

JSPM wil l be skipped since it is already patched to SP X.

Also, fo llow this procedure to deploy Single Support Package orNew Software Component.

Since JSPM deployment is done in uptime, it does not disturb the

work of the SAP system.



21


Common Problems Starting JSPM

go script would not run.

This is usually encountered in UNIX environment, if the script does not haveexecutable permissions.

Possible reason: JSPM is deployed via SDM GUI. Solution: fix the script permissions with command chmod +x go

JSPM GUI does not show.

Again encountered pr imari ly in UNIX environment.

Possible reason: X-server is not work ing. To verify t ry another GUI tool, li kexlogo.

Solution: Fix X-server configuration and graphics redirection depending oncurrent environment.

JSPM cannot recognize system profiles

Possible reason: you have created new files in SYS/profile (e.g. for backup). Solution: move new files to different directory.

Other problems discussed in Troubleshooting section in JSPM User Guide

Not Enough Disk Space Is Available

GUI Connection Port Is in Use



22


JSPM Port Is In Use

Symptom: Af ter starting go script , you get a message like this one

on the console.

Could not start JSPM. GUI connection port 6240 on localhost isalready in use.

Turn off the application which uses this port or change the

/dialog/SDTServerConnection/port property in the

E:\usr\sap\J70\JC03\j2ee\JSPM\param\jspm_config.txt file.

Reason: Most probably JSPM process is s till running. Although

JSPM GUI is closed, it is possible that JSPM process is st ill running

in the background.

Solution: If JSPM process is sti ll running, stop i t and try again

without changing the port. If some other program is using the port,change it (as described in the message) and try again.



23


Side-By-Side Execution

You can run several different instances of JSPM to update different SAP

systems (SID’s) on the same host.

To do so, you have to change JSPM port to avoid collisions. Set/dialog/SDTServerConnection/portproperty in

JSPM\param\jspm_config.txt to a free port number.

If you get the screen below, enter the same port number and select Log on.

Be careful which system you are

working on.



24


Troubleshooting JSPM Bootstrap

If JSPM_PROCESS.LOG does not exist, look for a problem in

bootstrap or JSPM / GUI process startup.

1. Check for error messages in the console where go script has been run.

2. Check that JSPM process is not running already (look for java

executable). Sometimes even if JSPM GUI is c losed, it is possible that

JSPM process is still running in background. If this is the case, stop i t.

3. Check BOOTSTRAP.LOG.

4. Check the output files of JSPM process. You can find their names inBOOTSTRAP.LOG. They should be JSPM_PROCESS.OUT and

JSPM_PROCESS.ERR .

5. Check JSPM.LOG. It contains log messages from JSPM initialization.

6. Check for fi les OsProc*.OUT and OsProc*.ERR .



25


Logon

JSPM uses SDM to detect and deploy J2EE components. So JSPM

needs SDM password to connect to SDM server.



26


Logon Problems Checklist

Things to check if logon fails.

SDM password is correct

SDM server stops after 3 attempts to logon wi th incorrect password.

To recover, start it again with StartServer script from/usr/sap/<SID>/<CI>/j2ee/SDM/program directory.

SDM server is running

SDM GUI is not connected to SDM server

SDM port is correct

JSPM reads SDM port f rom workingPort entry in/usr/sap/<SID>/<CI>/j2ee/SDM/program/localsdmgui.properties

This entry can change if SDM GUI is used to connect to d ifferent SDM server.The correct SDM port usually is 5nn18. Where nn is the central instancenumber.

JSPM logs the host and port used to connect to SDM. Look for messageChecking connectivity for SDM server on host <host>, port<port>...

Other logon problems described in Troubleshooting section inJSPM User Guide

JSPM Hangs On During Logon



27


Component Detection

JSPM detects 3 kinds of components

1. J2EE components

2. SDM - SAP_JAVASL component3. SAP KERNEL

Detected components are displayed in Deployed Components tab of

main JSPM window.

JSPM detects system components

Af ter login

Af ter deployment

Since SP7 JSPM logs component detection in a separate fileDETECT_SYSTEM_COMPONENTS.LOG.



28


Detecting J2EE Components

Two repositories with J2EE component information

SDM repository - /usr/sap/<SID>/<CI>/j2ee/SDM/root

CVERS – BC_COMPVERS table in system database

If there are differences, JSPM uses data from CVERS.

JSPM invokes SDM to synchronize its repository with CVERS. This

is logged in the main JSPM log.System component version tables will be synchronized with SDM repository.

You can find additional information in SDM log file <path to SDM log>.



29


Troubleshooting J2EE Components Detection

Symptom: JSPM cannot connect to SDM.com.sap.sdm.apiimpl.remote.client.APIRemoteExceptionImpl: Server<host> did not accept login request as admin on port <SDM port>.

Details: ERROR: Could not establish connection to server <host>at port <SDM port>: Connection refused: connect

Reason: SDM server is not running. Probably the whole system isdown.

Solution: Start the system manually and retry.

Symptom: Errors like this one can be found in SDM log fromrepository synchronizationError: <SCA name>: Location of software component '<SCA name>'/'<SCA vendor>'/'<SCA location>'/'<SCA counter>' unknown.Error: <SCA name>: system component version store not updated.

Reason: This is actually not an error.

Solution: For more information see note 828978



30


Deployed Components View Out-Of-Date

Symptoms

Data in Deployed Components view different from Repository view in SDM GUI

Component versions not updated after deployment

1. Check the SDM log for the repository synchronization. It is specified in

the main JSPM log.

If the referenced SDM log f ile does not exist, repository synchronization is

disabled in SDM. To enable it, execute the following commands from/usr/sap/<SID>/<CI>/j2ee/SDM/program and restart JSPM.

./StopServer.sh

./sdm.sh jstartup mode=standalone

./sdm.sh systemcomponentstate mode=activate./sdm.sh jstartup mode=integrated

./StartServer.sh

StopServer.bat

sdm jstartup "mode=standalone"

sdm systemcomponentstate "mode=activate"sdm jstartup "mode=integrated"

StartServer.bat

UNIX / LINUXMS Windows

See SAP note 828978 if synchronization prin ts errors.

2. Check the log for problems during component detection.



31


Detecting SDM

JSPM reads SDM version from this file

/usr/sap/<SID>/<CI>/j2ee/SDM/program/version.txt

Here is a sample.

Release: 7.00

SP-Number: 04

SP-Patchlevel: 1

SDM is displayed as SAP_JAVASL component.

Look for this message in the main log.

Retrieving SDM version by parsing <path to version.txt>...



32


SAP KERNEL Layout

/usr/sap/<SID>/SYS/exe/…

/usr/sap/<SID>/<Instance>/exe START Profile…

sapcpe…

DIR_CT_RUN

DIR_EXECUTABLE

7.00 Layout

/usr/sap/<SID>/SYS/exe/ctrun – does not exist

/usr/sap/<SID>/SYS/exe/…

DIR_CT_RUN

DIR_EXECUTABLE

6.40 Upgraded to 7.00 Layout (UNIX Only)

(executable directory)

(central executable directory)

(executable & central executable directory)

DIR_EXECUTABLE and DIR_CT_RUN are profile parameters. Use sappfpar to read

them.sappfpar pf=<path to instance profile> <parameter>



33


SAP KERNEL Layout (continued)

Central executable directories usually use one of these locations:

/usr/sap/<SID>/SYS/exe/run(U)

/usr/sap/<SID>/SYS/exe/(n)uc/<platform>

Separate instances can use different kernels » one SAP system

can have multiple kernels.

Different kernels are displayed under SAP KERNEL component in

Deployed Components tab.

The most popular scenario here is a dual-stack system wi th

ABAP + JAVA central instance using non-Unicode kernel

SCS instance using Unicode kernel

Several instances can share the same kernel.



34


Detecting SAP KERNEL

JSPM looks for the kernel in central executable directories.

You can find this in main JSPM log.

Starting searching for kernel version in directory <path> …

You can find additional information in log file

<KERNEL_DETECTION.LOG>.

Kernel version is detected by running disp+work –V

Since SP7 kernel manifests are used i f available. They are plain

text files located in kernel directory.

sapmanifest.mf

sapmanifestdb.mf



35


Troubleshooting Kernel Detection

1. Check in the main log if kernel directories were detected correctly.Looking for system kernel(s) under directory <path to SYS/exe>.Central instance kernel directory is <path>.SCS kernel directory is <path>.

NOTE: Do no t create additional subdirectories under SYS/exe/… If you need to backup thekernel, copy it to a different location.

2. Check the referenced KERNEL_DETECTION.LOG.

3. Check if kernel manifests (sapmanifest.mf or sapmanifestdb.mf) were foundin kernel directories. If yes, check their content.

Loaded kernel manifest <path>.

4. Check the command-line of disp+work and its exit code (0 is ok).Command line: <full command-line>…Process ID <#>, name <path to disp+work> has been finished, exit code <#>.

5. Check the output f i les of disp+work.Standard out: <path to DISP_WORK.OUT>

Check also the respect ive DISP_WORK.ERR file, if it exists .

6. If output fi les are not present, run disp+work with the same command-line in theconsole and check its output.



36


Troubleshooting Kernel Detection (continued)

Symptom: Error like this one

Could not detect system kernel under the E:\usr\sap\J70\SYS directory.Kernel

directory E:\usr\sap\J70\SYS\exe\uc\NTI386_backup cannot be recognized.Probably this platform is not supported anymore.

Reason: You have created a new directory under SYS/exe/… or

renamed one of the directories there.

Solution: Restore original directory names and move any additionaldirectories outside SYS/exe.



37


Inbox Directory

You can find the inbox di rectory by reading DIR_EPS_ROOT profile

parameter.

sappfpar pf=<path to CI profile> DIR_EPS_ROOT

The inbox di rectory is <DIR_EPS_ROOT value>/in

It is usually /usr/sap/trans/EPS/in

If inbox directory does not exist, JSPM will create it.

JSPM scans this directory and all its subdi rectories recursively. You

can find this in the main log.Starting scanning Inbox <path to Inbox> for deployable J2EE Engine

components...You can find additional information in log file <SCAN_INBOX.LOG>.



38


Scan Inbox

Only applicable components are displayed in Specify Queue step

depending on user selection in Select Package Type step.

You can see in the main log the package type selected by the user.

The user has chosen <package type> for Inbox granulation.

Support Package Stack

• Scans for *.XML files which are valid stack definitions.

• Displays only stacks which contain at least one applicable SP (see next item).

• Not applicable SP’s are dropped.

Single Support Packages

• Scans for valid Kernel, SDM or J2EE SP’s.

• Displays only applicable SP’s• There is a deployed component with the same name, vendor and release.

• Have SP-level higher than SP-level of the deployed component

• If SP-levels are equal, the patch-level is higher than patch-level of the deployed

component



39


Scan Inbox (continued)

New Software Components

• Scans for valid J2EE SP’s.

• Displays only SP’s for which there is no deployed component with the

same name and vendor .

Business Packages (since SP7)

• Scans for valid J2EE SP’s.

• Al lows update of deployed components to higher release or SP and

deployment of new components.



40


Detecting Components in Inbox

SAP KERNEL

Shipped as pair of archives SAPEXE.SAR & SAPEXEDB.SAR . One pair for each

different kernel used by the system.

SP7: If proper manifest is present in the archive, it is used. SAPEXE.SAR – sapmanifest.mf

SAPEXEDB.SAR – sapmanifestdb.mf

SAPEXE.SAR is extracted in a temporary directory and disp+work -V is run (see

Detecting SAP KERNEL above).

Some restrictions for kernel archives are described in note 901270.

Searching for kernel archives in directory <path>.

SDM

Shipped as SDMKIT.JAR archive. version.txt from the archive is used.

Some restrictions for SDM archive are described in note 890175.

Scanning of Inbox <path> for SDM archives...

J2EE Components

Shipped as *.SCA (also *.ZIP since SP7) archives. Manifest META-

INF/SAP_MANIFEST.MF from each archive is used.



41


Troubleshooting Inbox Scan

Component not found

Same or newer version of the same component already deployed.

The same or newer version of software component with name

<name> and vendor <vendor> is deployed on the system. …

Invalid SCA archive or invalid manifest

Stack not found

No stack definit ion file in Inbox. See SAP note 884537.

Stack contains no applicable SP’s.

Support package stack <name> with version <version> is rejected

because it contains no applicable components.

Data in stack definit ion does not match SCA manifest.

Manifest of file <SCA> does not contain component with name

<name> and vendor <vendor> as discribed in the stack

definition file <path>.

SDM not found

SDM archive does not follow the rules from note 890175.



42


Troubleshooting Inbox Scan (continued)

Kernel not found

No archives found for one or more of the kernels of the SAP system.

Kernel archives do not follow the rules from note 901270.

SAR archive extract fails

Symptom: SAPCAR fails (nonzero exit code, errors in output files)

Possible reason: incompatible SAPCAR

Solution: download updated SAPCAR in the same directory as the archiveor copy SAPCAR from central run directory (SYS/exe/…).

Inbox Scan stops with error and this exception can be found in thetrace

java.lang.NullPointerException

atcom.sap.sdt.tools.filter.FileSetElement.applyPathPefix(FileSetElement.java:165)

For SP5 all Inbox subdirectories should be accessible by <sid>adm user.



43


Check Queue

JSPM checks that all necessary archives are present in the Inbox.

J2EE SP’s are sent to SDM for validation.You can see it in the main log.

The user has selected to deploy the following list of

deployable components. The list will be validated by SDM:

Note: only J2EE SP’s are listed here. Kernel and SDM SP’s are not

included even if they are selected too.



44


Troubleshooting Check Queue

Component in status REVISE.

Click Show Details button on the same row to see the details message.

Check if all the archives are present in the Inbox. Check in the main log

Error during validation. See <SDM log> for details.

Check the referenced SDM log.

Search for Error: string.

If SDM log file does not exist , check

free disk space – note 891895

<sid>adm user is the owner of SDM/program/temp directory

SAP Notes

891895 - JSPM: required disk space

874123 - JSPM shuts down with an OutOfMemoryError during validation

909407 - JSPM hangs on dur ing Check Queue wizard step

756084 - Common met SDM v6.30/6.40/7.0 problems



45


Deploy Queue

JSPM deploys the selected support packages in th is order

1. SAP KERNEL

Before SP7 JSPM cannot patch the kernel of a distributed system. See

note 886296.

2. SDM (SAP_JAVASL)

3. J2EE support packages

Note: JSPM should have been updated already.

Finally, information for all deployed components is read again from

the system. See Component Detection above.



46


Troubleshooting Kernel Deployment

SAR archive extract fails

Symptom: SAPCAR fails (nonzero exit code, errors in output f iles)

Possible reason: incompatible SAPCAR, SAPCAR is unable to update itself Solution: put proper SAPCAR in the same directory as the archive. Try copying

SAPCAR from central run directory (SYS/exe/…).

Not enough d isk space

See note 891895 about required disk space.

Cannot overwrite file

Possible reason: the file is in use by some running process.

Note: SAP MMC starts OS services automatically.

To find the process hold ing the file use Process Explorer (Win) or fuser (UNIX).

Solution: stop the process

SAP Notes

901422 - JSPM: problems during KERNEL_SAP update

886296 - JSPM: High Availability and Distributed Systems Support

884281 - JSPM: saposcol permission and kernel patching



47


Retrying Kernel Deployment

If kernel deployment fails, the engine is down.

Choosing Retry brings you to Check Queue step.

Validation of any J2EE components wi ll fail since the engine is down.

Possible solutions

1. If you can start the SAP system manually, choose Retry in JSPM.

2. Otherwise (kernel files partially updated)

1. If JSPM is not closed yet

1. Choose New Deployment

2. Deploy only SAP KERNEL using Single Support Package

2. If JSPM is closed

1. Patch the kernel manually by extracting the archives in proper kernel directories (note

886296)

2. Start the engine manually

3. Restart original deployment with JSPM. Kernel will be skipped as it is updated

already.



48


Troubleshooting Engine Start/Stop

1. Check the referenced ENGINE_OPERATION.LOG.

Execution of several external processes is logged there. Check their exit codes (0 isok) and referenced output fi les (.OUT & .ERR ).

Al though execut ion of jcmon generates JCMON_*.ERR files, they usually indicate noerror.

2. Check the engine logs1. /usr/sap/<SID>/<Instance>/work

Files like *.b00 & *.o00 are backups of o ld logs.

1. sapstart.log & sapstart.trc – pay attent ion to process ID’s

2. dev_w0 if ABAP is p resent

3. dev_jcontrol

4. Check logs from bootstrap, dispatcher, server<n>, sdm.

2. /usr/sap/<SID>/<CI>/j2ee/cluster/server0/log/…defaultTrace.*.trc

system/server.0.log

3. Try to start/stop the engine manually

4. Post a CSN message to

Component owner – specific J2EE component fails

BC-JAS, BC-JAS-SF, BC-JAS-SEC, …



49


Checking The Engine State

You can use one of these tools to check J2EE engine state

SAP MMC – available only on MS Windows

sapcontrol

sapcontrol -nr <inst. nr.> -function J2EEGetProcessList

Run sapcontrol without parameters to see complete syntax.

jcmon

jcmon pf=<path to CI profile>

Then type 20 (Local Adminis tration Menue).



50


J2EE Components Deployment

JSPM sends SCA’s in batches to SDM for deploymentStarting to deploy archive <path to SCA>.

…

Connecting to SDM Server on host <host>, port <port>...

You can find additional information in SDM log file <SDM log>.

1. First, SDM validates the archives Archive <path to SCA> has been admitted for deployment.

2. Then it deploys them Archive <path to SCA> has been deployed.

SDM may restart the engine several times during deployment

Offline deployment phase has been scheduled. J2EE Engine will be

restarted while deployment is running.

JSPM may restart SDM server between deployments.

Restarting SDM server...



51


Troubleshooting J2EE Components Deployment

1. Click Show Details against the failed component to v iew the detailsmessage.

2. Find in the log where the failing archive was deployed and locate therespective SDM log.

Error during deployment. See <SDM log> for details.

3. Check the referenced SDM log. Look for Error: string.NOTE: sometimes SDM logs errors as Info messages, so you may needto look through the entire SDM log to find the error.

4. If SDM log file does not exist, check

free disk space – note 891895

<sid>adm user is the owner of SDM/program/temp directory

5. If component deployment failed for no obvious reason post a CSN to itsowners.

6. If J2EE engine has stopped unexpectedly or SDM failed to start it, checkthe engine logs. See Troubleshooting Engine Start/Stop above.



52


Common Problems During J2EE Deployment

Troubleshooting section in JSPM User Guide

J2EE engine runs out of memory

The J2EE Engine Administrator Password Has Been Changed

JSPM Hangs On During Deployment

SAP notes

129813 - NT: Problems due to address space fragmentation

736462 - Problems increasing Xmx on Windows 32 bit platforms

861215 - Recommended Settings for the Linux on AMD64/EM64T JVM

851251 - SAP NetWeaver 2004s Installation on UNIX Java - JSPM: sapstar t cannot be found

723909 - Java VM sett ings for J2EE 6.30/6.40/7.0

709140 - Recommended JDK and VM Settings for the WebAS630/640/7.0

764417 - Information for troubleshooting of the SAP J2EE Engine 6.40

870445 - SAPJup J2EE Engine Password Does Not Change After an Upgrade

701654 - Deployment aborts due to wrong J2EE Engine login information

891895 - JSPM: required disk space

893946 - SunJCE provider inconsistency

904074 - Broken deployment, check versions of deployed components

903609 - CAF 7. 0 SP5 Deployment prob lem over SP4 using JSPM

710966 - DEPLOY_LOCK error during upgrade

739190 - Timeout when starting or stopping the J2EE engine

914382 - PCD deployment fails due to locked objects

756084 - Common met SDM v6.30/6.40/7.0 problems



53


Resuming Broken Deployment

Broken Deployment screen appears i f JSPM is restarted after

deployment failure. It shows the result from the previous JSPM

session.



54


IGS Handling

Since SP7 JSPM can update IGS.

IGS is handled like the kernel.

Component name: BC-FES-IGS

Location: kernel directory

Inbox archive: IGS*.SAR

Manifest file: igsmanifest.mf

If no manifest is present, this command is used to retrieve version

informationigswd -version



55


JSPM Internal Error

JSPM stops w ith the error screen below. This message can be found in the logException has occurred during the execution of the phase.

If the error message is not enough to resolve the problem, post a CSN message inBC-UPG-OCS-SPJ and attach JSPM.TRC.



56

JSPM Operation

Overview

The Logs





57


Troubleshooting Procedure

1. Diagnose the problem

Check the logs. Start with JSPM_PROCESS.LOG and follow through

referenced logs.

In case of J2EE engine problems check its logs.

2. Look for similar problems

1. Check Troubleshooting section in JSPM User Guide

2. Check JSPM central note 891983, SDM note 756084 and all the

referenced notes.

3. Search in SAP notes and CSN messages. Use expressions specific for

this problem, e.g. error messages, exception names, file names, etc.

3. If not resolved, post a CSN message in appropriate queue

If you have found a related note or message but it doesn’t solve the

problem, post a new message in the same queue.



58


Posting A CSN Message

CSN components

BC-CTS-SDM – problems with SDM BC-CTS-SLU – problems with SLUtils library, provid ing access to

CVERS

BC-JAS – general J2EE engine problems

BC-JAS-SF – problems with s tartup framework (jcmon, jcontrol,jlaunch, etc.)

BC-JAS-SEC – securi ty related issues in J2EE engine

Component owners – problems with specific software/developmentcomponent (SCA/SDA fails to validate or deploy)

BC-UPG-OCS-SPJ – problems with JSPM tool, no content problems (e.g.invalid/missing archive or stack XML).

Check SAP note 67739 Priorities of problem messages.



59


Information To Include In A CSN Message

Describe the situation in detail

What is the scenario, source SP, target SP

At what point did the problem occur

System information OS, DB, ABAP, Usage Types, Release

JSPM used: SP-level, patch-level, internal version

Paste the trouble ticket text

What analysis have you done and what are the results

Paste any error message and where you have found them (log fi le path)

Describe any actions you tried to resolve the problem

Zip and attach JSPM log and trc directories

At tach any other relevant logs (from SDM, engine, etc .), especially those

with errors



60


No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or

registered trademarks of IBM Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and

implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein

as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other

countries all over the world. All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group

shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and

services are those that are set forth in the express warranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additional warranty.

Copyright 2004 SAP AG. All Rights Reserved




Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Formauch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikationenthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auchanderer Softwarehersteller enthalten.

Microsoft, Windows, Outlook, und PowerPoint sind eingetragene Marken der Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, und Informix sind Marken odereingetragene Marken der IBM Corporation in den USA und/oder anderen Ländern.

Oracle ist eine eingetragene Marke der Oracle Corporation.

UNIX, X/Open, OSF/1, und Motif sind eingetragene Marken der Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, und MultiWin sind Marken oder eingetrageneMarken von Citrix Systems, Inc.

HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.

Java ist eine eingetragene Marke von Sun Microsystems, Inc.

JavaScript ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscapeentwickelten und implementierten Technologie.

MaxDB ist eine Marke von MySQL AB, Schweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver und weitere im Text erwähnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschlandund anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligenFirmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte könnenländerspezifische Unterschiede aufweisen.

In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die vorliegenden Angaben werden von SAP AG und ihren Konzernunternehmen („SAP-Konzern“) bereitgestellt und dienen ausschließlichInformationszwecken. Der SAP-Konzern übernimmt keinerlei Haftung oder Garantie für Fehler oder Unvollständigkeitenin dieser Publikation. Der SAP-Konzern steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die inder Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. Aus den in dieserPublikation enthaltenen Informationen ergibt sich keine weiterführende Haftung.

Copyright 2004 SAP AG. Alle Rechte vorbehalten

Documents

05004 WDEBU7 JSPM Troubleshooting