JSPM - applying SP stacks
Hi Guys,
I have just installed As Java 2004s + EP and it is at SP6. Now, i want to
update it to SP8. I have downloaded the stack 8.
I know JSPM is used to apply the stack. According to the documentation i
have,all the files have to be placed in the usr/sap/trans/EPS/in and then
applied.
But do these SCA files need to be extracted with sAPCAR like the kernel SAR
files?
What steps need to be done before starting JSPM and what steps after?
Can someone throw some light?
Regards
Cyrus
Hi Cyrus,
No other considerations. Just place them in EPS\in as
stated by Costas. Login as <sid>adm and run go.bat from
.../j2ee/JSPM/ folder. It shows the list where you
select the target SP level for the component. Its
recommended to update <i>only jspm</i> first and restart it and then the other components.
Regards
Srikishan
Similar Messages
-
Hi Guru's,
I am installing solman 4.0,ecc 6.0 on ABAP+JAVA stack.
As I am planning to apply the SP stacks here I am having some queries.
1)Can I apply the stack through SPAM,if so please let me know how can I do that
2)Should I need to apply the Stacks for both JAVA and ABAP????
Your help would be more appreciable.
Thanks.
rkHi rk,
You can apply ABAP SP stack using SPAM and SAINT.
And for Java you can use SAPINST or JSPM (if you have >= NW04s SPS09).
In case you are not familier with JSPM, here is document on it.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5006901f-925c-2910-5f98-9ae26cc07eca
Hope this will help.
-Pinkle -
URGENT: How to Apply SP Stacks
Hi everyone,
I am new to the process of applying SP Stacks.
Currently i am going to apply SP Stack 13 for Solution Manager 7 (formerly 4.0).
So i download a group of files, according to the platform and dbms i have on my box.
In the list i see a bunch of .CAR, .SAR and .SCA files.
I know how to extract CAR and SAR files, and after some research i know how to do the same with SCA files. But my first question is , SCA files will be applied also using the SPAM transaction, after decompressing them??
What is the purpose of the SCA files???
Then, is there anyway to extract the CAR and SAR files using SAPCAR tool with one instruction???
Finally, once i extracted everything, the process of applying the patches will be the same as usual?? Meaning, going to SPAM, loading the packages (previously copied to EPS\in folder) and starting the process??
Any help will be great.
cheers,Hi,
ABAP:
1.CAR & SAR, uncar the files using sapcar -xvf *.(CAR/SAR). Copy the PAT & CATT files to usr/sap/trans/EPS/in directory.
2. go to SPAM load the packages from app. server.
3. Define the Queue (DISPLAY/DEFINE)
4. Import
JAVA
1.SCA files, copy the SCA files to EPS/in directory
2. login as sisadm start the JSPM
usr/sap/sid/instance/j2ee/jspm
3.Deploy the components.
If u'r applying kernel also do JSPM first which also updates kernel. -
[SOLVED] Applying bottom stack patch to dwm
I have finally moved to a tiling window manager and am finding it equal parts rewarding and frustrating. I'm using dwm-5.6.1-1.
I would like to apply the bottom stack patch but, after having read the instructions on the dwm site I get the following error:
can't find file to patch at input line 37
Perhaps you used the wrong -p or --strip option?
I used -p0 as the patch page states: http://dwm.suckless.org/patches/bottom_stack
I have also looked at these couple of posts to try and work it out, but the advice seems to conflict:
http://bbs.archlinux.org/viewtopic.php?id=78263
http://bbs.archlinux.org/viewtopic.php?id=61499
Is there a definitive way to apply the patch, or should I just skulk back to a simpler WM?
/edit
OK: so after some experimentation, it works... The updated dwm patch page and the second post solved it.
Last edited by jasonwryan (2009-09-09 00:11:28)axion419 wrote:
sorry to sound dense, I am at work and not at teh dwm pc at home. After I patch, do I just stick this in
'+ { "TTT", bstack },'
Yes, that line, exactly. -
Stuck Applying SP stacks for ERP2005...
Stuck applying SPstacks in ERP2005...
Thanks Jacob for quick response.
I have desktop with Pentium 3.0 GHZ and 4GB RAM, Windows XP.
CPU time and memory use was constant and had not reach to max.
I waited for 65 minutes and then stop the installation.
May be I should have waited little longer.
But, now can not continue EP6 installation because J2EE instance is not coming up. SAP Management Console does not have any process to start/stop.
Any idea how to revert the partial EP6 upgrades or resolve this problem?
Thanks once again.
Abhay -
Unable to apply SPS23 Java Stack using JSPM
Hi,
i'm having serious trouble getting JSPM to apply SPS23 for Solution Manager 7.0 EHP1. JSPM always rejected the XML file downloaded from Solution Manager or OSS. There are two different scenarios.
1. JSPM can't find ISDOTNET8SP01_00-10007435.SAR in EPS/in. When i copy the file to EPS/in he rejected to apply the stack because ISDOTNET8SP01_00-10007435.SAR isn't a valid SCA file. How smart JSPM is.
2. Tried a xml stack definition file downloaded from OSS. Now JSPM rejected to apply because he couldn't find new versions of the component. The log file (SCAN...) says : ...WARNING The same or newer version of software component BASETABLES and vendor sap.com is deployed on the system. The release and version of the software component, which is found in the Inbox directory, are 7.01 and 6.0, and the release and version of the software component, which is deployed on the system, are 7.00 and 14.0.
Know, it though 7.01 is newer than 7.00 but JSPM thinks different. As the message is the same for all components in the end JSPM didn't find anything to apply and rejected the complete stack. Trying to apply as single stack wasn't successful too as he didn't find any target SP Level.
Any clue ?
We urgently need to complete the EHP1 update to start the ERP 6.0 upgrade which would already be finished if not for Solution Manager requirement to download the EHP4 stack.
RegardsSolution found !
You need to update JSPM at least to 7.00 SP17 (7.00.17. Note 1280791).
Restart JSPM, apply Stack which will update JSPM to 7.01.6.0.
Restart JSPM nd now the rest of the Stack could be upgraded to 7.01.6.0.
JSPM 7.00.14.3 or lower will not recognize the JSPM 7.01.6.0 update SCA which is need in order to update the other components to 7.01.6 as well.
Regards -
Error in JSPM to try update stack java.
Hi. sdn team.
We have problem with JSPM . The problem it's .
I try to validate error in LOG FILE " E:\usr\sap\SME\DVEBMGS01\SDM\program\log\sdmcl20090729210415.log"
INTO FILE:
Jul 29, 2009 9:04:22 PM Error: Aborted: development component 'tc/sec/ume/wd/approval'/'sap.com'/'MAIN_APL70VAL_C'/'1219306'/'0', grouped by software component 'UMEADMIN'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.16.0.20080610192745''/'0':
Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.
com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
i try to search notes fot this problem and validate the next notes:
Note 1228507 - Config Tool does not properly save password in Secure Store
Note 701654 - Deployment aborts due to wrong J2EE Engine login information
Apply this notes recomended in this forum. my system not response with this change.
in another link of this forum recomenden execute apply this stacks in level Operating System
We try apply stack of java in leve OS with the next comands:
in sapmmc disable process SDM
sdm jstartup "mode=standalone"
sdm deploy "file=E:\usr\sap\trans\EPS\in\ADSSAP16_0-10003001.SCA" "updateVersions=all"
But send the next error:
Upload information in adobe-XMLForm.sda file.
Processing...
Processing error. Return code: 4
Pease HELPME The session of configuracion it's for 17Ago, and we need SP18 READY.
BEST REGARDS
LUIS CUPA
Edited by: Luis Isaac Cupa Rosales on Jul 30, 2009 1:14 AM
Edited by: Luis Isaac Cupa Rosales on Jul 30, 2009 1:16 AMHi Sunny and Debasis Sahoo
tks for you response, but i try to change passwords in secure store in configtool,
change: admin/password/<SID> in configtool and restart all server.
in transaction SU01 the user J2EE_ADMIN is not found this user is create with sap_all and password equal to value in parameter in secure store in configtool.
Reset Server, and try execute DEPLOY of componnent sap.com/ADSSAP
and send the next error:
Jul 30, 2009 10:14:35... Error: Aborted: development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'800.20070306123954.374077'/'5', grouped by :
Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.
com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
PLEASE HELPME
Note: " Note: " in tool visual Administrator, it's necesary connect with user SAP* to connect, validate in configtool and this user it's active.
the password in tool visual administrator to user default <sid>adm (use value change in secure store ) it's not valid " "
Regards,
Luis Cupa. -
Error during application of stack
Hi all,
I am applying the stack using JSPM.
I got an error
An error occured during execution of JSPM_PROCESS Phase.
java.lang.StringIndexOutOfBoundsException: String index out of range: -9
Provide me solution to solve this error.<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\NW7\DVEBMGS01\j2ee\JSPM\log\log_20071231170532\JSPM_PROCESS_1_01.LOG]/>
<!PATTERN[JSPM_PROCESS_1_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
#1.5#C000AC1A1C5000000000001401AB28FE0004429371740BF8#1199100937899#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#Java###Phase has been started.#1#JSPM/JSPMPhases/JSPM_PROCESS#
#1.5#C000AC1A1C5000000000001501AB28FE0004429371740BF8#1199100937899#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#Java###Phase type is .#1#com.sap.sdt.jspm.phases.PhaseTypeJSPM#
#1.5#C000AC1A1C5000000000001601AB28FE0004429371744A78#1199100937915#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:246)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:246)#Java###Starting Initialize dialog...##
#1.5#C000AC1A1C5000000000001C01AB28FE00044293717AF968#1199100938353#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:342)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:342)#Java###Initializing JSPM data model...##
#1.5#C000AC1A1C5000000000001D01AB28FE00044293717AF968#1199100938353#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.InitialParametersDetector.detectProfileDirectory(InitialParametersDetector.java:1250)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectProfileDirectory(InitialParametersDetector.java:1250)#Java###Detected profile directory .#1#C:
usr
sap
NW7
SYS
profile#
#1.5#C000AC1A1C5000000000001E01AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:261)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:261)#Java###Executing command with arguments .#2#dbinfo#C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
config
DBINFO.XML#
#1.5#C000AC1A1C5000000000001F01AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#Java###Java process ID , name has been started.#2#3#com.sap.sdt.dmt.main.DMT#
#1.5#C000AC1A1C5000000000002001AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#Java###Command line: #2# #C:
j2sdk1.4.2_13
jre
bin
java.exe -cp .;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
sdt_dmt.jar;C:/sapdb/programs/runtime/jar/sapdbc.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
jddi.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
opensqlsta.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
tc_sec_secstorefs.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
frame.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
exception.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
logging.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
jperflib.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
util.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
tc_sec_secstorefs.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
exception.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
logging.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
opensqlsta.jar;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
engine
iaik_jce.jar;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
engine
info
IAIKSecurityFS.list;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
tools
iaik_jce.jar;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
tools
iaik_jsse.jar;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
tools
iaik_smime.jar;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
tools
iaik_ssl.jar;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
tools
info
IAIKSecurityFS.list;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
tools
w3c_http.jar com.sap.sdt.dmt.main.DMT -rootdir=C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM -descriptor=cp-chn-3f-029_NW7 -logfile=DMT_01.LOG dbinfo C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
config
DBINFO.XML#
#1.5#C000AC1A1C5000000000002101AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
log
log_20071231170532
DMT_01.LOG_01.OUT#
#1.5#C000AC1A1C5000000000002201AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#3#
#1.5#C000AC1A1C5000000000002301AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#3#java.exe#
#1.5#C000AC1A1C5000000000002401AB28FE0004429371BEEFD8#1199100942807#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#3#java.exe#0#
#1.5#C000AC1A1C5000000000002501AB28FE0004429371BEEFD8#1199100942807#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:273)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:273)#Java###Command has been executed.#1#dbinfo#
#1.5#C000AC1A1C5000000000002601AB28FE0004429371BFA770#1199100942854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.sysinfo.AbstractInfoController.updateProfileVariable(AbstractInfoController.java:288)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sysinfo.AbstractInfoController.updateProfileVariable(AbstractInfoController.java:288)#Java###Parameter has been detected. Parameter value is .#2#/J2EE/StandardSystem/DefaultProfilePath#C:
usr
sap
NW7
SYS
profile
DEFAULT.PFL#
#1.5#C000AC1A1C5000000000002701AB28FE0004429371BFA770#1199100942854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.InfoController.detectInstance(InfoController.java:601)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.InfoController.detectInstance(InfoController.java:601)#Java###msg.j630.sysinfo.013 #4#SCS00#C:
usr
sap
NW7
SYS
profile
NW7_SCS00_CP-CHN-3F-029#C:
usr
sap
NW7
SYS
profile
START_SCS00_CP-CHN-3F-029#CP-CHN-3F-029#
#1.5#C000AC1A1C5000000000002801AB28FE0004429371BFA770#1199100942854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.InfoController.detectInstance(InfoController.java:601)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.InfoController.detectInstance(InfoController.java:601)#Java###msg.j630.sysinfo.013 #4#DVEBMGS01#C:
usr
sap
NW7
SYS
profile
NW7_DVEBMGS01_CP-CHN-3F-029#C:
usr
sap
NW7
SYS
profile
START_DVEBMGS01_CP-CHN-3F-029#CP-CHN-3F-029#
#1.5#C000AC1A1C5000000000002901AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.InitialParametersDetector.detectHA(InitialParametersDetector.java:865)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectHA(InitialParametersDetector.java:865)#Java###SCS is local, so this is not a High Availability system.##
#1.5#C000AC1A1C5000000000002A01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#4#sappfpar#
#1.5#C000AC1A1C5000000000002B01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 DIR_EPS_ROOT#
#1.5#C000AC1A1C5000000000002C01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_01.out#
#1.5#C000AC1A1C5000000000002D01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#4#
#1.5#C000AC1A1C5000000000002E01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#4#sappfpar#
#1.5#C000AC1A1C5000000000002F01AB28FE0004429371ED3398#1199100945839#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#4#sappfpar#0#
#1.5#C000AC1A1C5000000000003001AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#5#sappfpar#
#1.5#C000AC1A1C5000000000003101AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 SAPSYSTEM#
#1.5#C000AC1A1C5000000000003201AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_20.out#
#1.5#C000AC1A1C5000000000003301AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#5#
#1.5#C000AC1A1C5000000000003401AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#5#sappfpar#
#1.5#C000AC1A1C5000000000003501AB28FE000442937210B958#1199100948167#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#5#sappfpar#0#
#1.5#C000AC1A1C5000000000003601AB28FE000442937210B958#1199100948167#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#6#sappfpar#
#1.5#C000AC1A1C5000000000003701AB28FE000442937210B958#1199100948167#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 INSTANCE_NAME#
#1.5#C000AC1A1C5000000000003801AB28FE000442937210F7D8#1199100948183#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_21.out#
#1.5#C000AC1A1C5000000000003901AB28FE000442937210F7D8#1199100948183#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#6#
#1.5#C000AC1A1C5000000000003A01AB28FE000442937210F7D8#1199100948183#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#6#sappfpar#
#1.5#C000AC1A1C5000000000003B01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#6#sappfpar#0#
#1.5#C000AC1A1C5000000000003C01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#7#sappfpar#
#1.5#C000AC1A1C5000000000003D01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 DIR_EXECUTABLE#
#1.5#C000AC1A1C5000000000003E01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_22.out#
#1.5#C000AC1A1C5000000000003F01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#7#
#1.5#C000AC1A1C5000000000004001AB28FE00044293723C22A0#1199100951012#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#7#sappfpar#
#1.5#C000AC1A1C5000000000004101AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#7#sappfpar#0#
#1.5#C000AC1A1C5000000000004201AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#8#sappfpar#
#1.5#C000AC1A1C5000000000004301AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 DIR_CT_RUN#
#1.5#C000AC1A1C5000000000004401AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_23.out#
#1.5#C000AC1A1C5000000000004501AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#8#
#1.5#C000AC1A1C5000000000004601AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#8#sappfpar#
#1.5#C000AC1A1C5000000000004701AB28FE000442937291FB30#1199100956638#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#8#sappfpar#0#
#1.5#C000AC1A1C5000000000004801AB28FE000442937291FB30#1199100956638#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#9#sappfpar#
#1.5#C000AC1A1C5000000000004901AB28FE000442937291FB30#1199100956638#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 jstartup/vm/home#
#1.5#C000AC1A1C5000000000004A01AB28FE000442937291FB30#1199100956638#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_24.out#
#1.5#C000AC1A1C5000000000004B01AB28FE00044293729239B0#1199100956654#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#9#
#1.5#C000AC1A1C5000000000004C01AB28FE00044293729239B0#1199100956654#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#9#sappfpar#
#1.5#C000AC1A1C5000000000004D01AB28FE0004429372BD25F8#1199100959467#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#9#sappfpar#0#
#1.5#C000AC1A1C5000000000004E01AB28FE0004429372BD25F8#1199100959467#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#10#sappfpar#
#1.5#C000AC1A1C5000000000004F01AB28FE0004429372BD25F8#1199100959467#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 SAPSYSTEM#
#1.5#C000AC1A1C5000000000005001AB28FE0004429372BD25F8#1199100959467#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_01.out#
#1.5#C000AC1A1C5000000000005101AB28FE0004429372BD6478#1199100959483#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#10#
#1.5#C000AC1A1C5000000000005201AB28FE0004429372BD6478#1199100959483#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#10#sappfpar#
#1.5#C000AC1A1C5000000000005301AB28FE0004429372E850C0#1199100962296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#10#sappfpar#0#
#1.5#C000AC1A1C5000000000005401AB28FE0004429372E850C0#1199100962296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#11#sappfpar#
#1.5#C000AC1A1C5000000000005501AB28FE0004429372E850C0#1199100962296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 INSTANCE_NAME#
#1.5#C000AC1A1C5000000000005601AB28FE0004429372E850C0#1199100962296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_25.out#
#1.5#C000AC1A1C5000000000005701AB28FE0004429372E88B58#1199100962311#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#11#
#1.5#C000AC1A1C5000000000005801AB28FE0004429372E88B58#1199100962311#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#11#sappfpar#
#1.5#C000AC1A1C5000000000005901AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#11#sappfpar#0#
#1.5#C000AC1A1C5000000000005A01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#12#sappfpar#
#1.5#C000AC1A1C5000000000005B01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 DIR_EXECUTABLE#
#1.5#C000AC1A1C5000000000005C01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_26.out#
#1.5#C000AC1A1C5000000000005D01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#12#
#1.5#C000AC1A1C5000000000005E01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#12#sappfpar#
#1.5#C000AC1A1C5000000000005F01AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#12#sappfpar#0#
#1.5#C000AC1A1C5000000000006001AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#13#sappfpar#
#1.5#C000AC1A1C5000000000006101AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 DIR_CT_RUN#
#1.5#C000AC1A1C5000000000006201AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_27.out#
#1.5#C000AC1A1C5000000000006301AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#13#
#1.5#C000AC1A1C5000000000006401AB28FE00044293733F1F68#1199100967985#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#13#sappfpar#
#1.5#C000AC1A1C5000000000006501AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#13#sappfpar#0#
#1.5#C000AC1A1C5000000000006601AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#14#sappfpar#
#1.5#C000AC1A1C5000000000006701AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 rdisp/msserv_internal#
#1.5#C000AC1A1C5000000000006801AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_28.out#
#1.5#C000AC1A1C5000000000006901AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#14#
#1.5#C000AC1A1C5000000000006A01AB28FE00044293736A4648#1199100970813#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#14#sappfpar#
#1.5#C000AC1A1C5000000000006B01AB28FE0004429373953678#1199100973627#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#14#sappfpar#0#
#1.5#C000AC1A1C5000000000006C01AB28FE00044293739B6868#1199100974033#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:350)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:350)#Java###JSPM data model has been initialized.##
#1.5#C000AC1A1C5000000000006D01AB28FE0004429373B0E080#1199100975440#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:264)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:264)#Java###Initialize dialog has been processed.##
#1.5#C000AC1A1C5000000000006E01AB28FE0004429373B0E080#1199100975440#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.login(DialogController.java:654)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.login(DialogController.java:654)#Java###Starting dialog...#1#LogIn#
#1.5#C000AC1A1C5000000000007701AB28FE00044293754DE6E0#1199101002508#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.login(DialogController.java:659)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.login(DialogController.java:659)#Java###Dialog has been confirmed by the user.#1#LogIn#
#1.5#C000AC1A1C5000000000007801AB28FE00044293754EDCF8#1199101002571#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.checkConnectivity(DeploymentManagerImpl.java:172)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.checkConnectivity(DeploymentManagerImpl.java:172)#Java###Checking connectivity for SDM server on host , port ...#2#CP-CHN-3F-029#50118#
#1.5#C000AC1A1C5000000000007901AB28FE0004429375703FD8#1199101004759#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.checkConnectivity(DeploymentManagerImpl.java:181)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.checkConnectivity(DeploymentManagerImpl.java:181)#Java###Connection to SDM server on host , port is valid.#2#CP-CHN-3F-029#50118#
#1.5#C000AC1A1C5000000000007A01AB28FE00044293757671C8#1199101005165#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1138)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1138)#Java###Detecting kernel exchange directory of the J2EE Engine...##
#1.5#C000AC1A1C5000000000007B01AB28FE00044293757671C8#1199101005165#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1146)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1146)#Java###You can find additional information in log file $.#1#C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
log
log_20071231170532
KERNEL_DETECTION_01.LOG#
#1.5#C000AC1A1C5000000000008901AB28FE0004429375A0AA60#1199101007932#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1158)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1158)#Java###Parameter DIR_CT_RUN from with value will be used as target directory for unicode kernel update.#2#NW7_DVEBMGS01_CP-CHN-3F-029#C:/usr/sap/NW7/SYS/exe/uc/NTI386#
#1.5#C000AC1A1C5000000000008A01AB28FE0004429375A384D8#1199101008119#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:749)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:749)#Java###Starting retrieving SDM substitution variable with name ...#1#com.sap.portal.deploy.pcd#
#1.5#C000AC1A1C5000000000008B01AB28FE0004429375A384D8#1199101008119#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:756)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:756)#Java###Connecting to SDM Server on host , port ...#2#CP-CHN-3F-029#50118#
#1.5#C000AC1A1C5000000000008C01AB28FE0004429375A3FDF0#1199101008150#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:788)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:788)#Java###You can find additional information in SDM log file .#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/log/sdmcl20071231113648.log#
#1.5#C000AC1A1C5000000000008D01AB28FE0004429375A71AD0#1199101008354#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:749)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:749)#Java###Starting retrieving SDM substitution variable with name ...#1#com.sap.portal.deploy.pcdcontent#
#1.5#C000AC1A1C5000000000008E01AB28FE0004429375A71AD0#1199101008354#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:756)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:756)#Java###Connecting to SDM Server on host , port ...#2#CP-CHN-3F-029#50118#
#1.5#C000AC1A1C5000000000008F01AB28FE0004429375A7CE80#1199101008400#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:788)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:788)#Java###You can find additional information in SDM log file .#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/log/sdmcl20071231113648.log#
#1.5#C000AC1A1C5000000000009001AB28FE0004429375AAEB60#1199101008604#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.deployment.order.DeploymentOrderSet.xinit>(DeploymentOrderSet.java:143)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.deployment.order.DeploymentOrderSet.xinit>(DeploymentOrderSet.java:143)#Java###Parsing of file and extracting the relative deployment data model has finished.#1#C:/usr/sap/NW7/DVEBMGS01/j2ee/JSPM/config/dodf.xml#
#1.5#C000AC1A1C5000000000009101AB28FE0004429375AE7D70#1199101008838#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:197)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:197)#Java###Receiving information about deployed J2EE Engine components...##
#1.5#C000AC1A1C5000000000009201AB28FE0004429375B19668#1199101009041#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:211)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:211)#Java###A valid SQL data source for is obtained.#1#jdbc/pool/NW7#
#1.5#C000AC1A1C5000000000009301AB28FE0004429375D01ED0#1199101011042#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:225)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:225)#Java###API to the system component version tables has been obtained.##
#1.5#C000AC1A1C5000000000009401AB28FE0004429375D01ED0#1199101011042#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:228)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:228)#Java###System component version tables will be synchronized with SDM repository.##
#1.5#C000AC1A1C5000000000009501AB28FE0004429375D2BEB0#1199101011214#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:235)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:235)#Java###You can find additional information in SDM log file .#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/log/sdmcl20071231113651.log#
#1.5#C000AC1A1C5000000000009601AB28FE000442937BD618E8#1199101112097#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:412)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:412)#Java###You can find additional information in SDM log file .#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/log/sdmcl20071231113832.log#
#1.5#C000AC1A1C5000000000009701AB28FE000442937BD65768#1199101112113#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:417)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:417)#Java###Access to SDM repository has been obtained. Start to read SDM repository content.##
#1.5#C000AC1A1C5000000000009801AB28FE000442937BD9E978#1199101112347#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:421)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:421)#Java###Data about components deployed on the engine is obtained from SDM repository.##
#1.5#C000AC1A1C5000000000009901AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#JLOGVIEW#sap.com#
#1.5#C000AC1A1C5000000000009A01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C5000000000009B01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C5000000000009C01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C5000000000009D01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C5000000000009E01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C5000000000009F01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C500000000000A001AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C500000000000A101AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C500000000000A201AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:314)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:314)#Java###Data from SDM repository has been read.##
#1.5#C000AC1A1C500000000000A301AB28FE000442937C8D7A38#1199101124115#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:381)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:381)#Java###Information about deployed J2EE Engine components has been received.##
#1.5#C000AC1A1C500000000000A401AB28FE000442937C8DB8B8#1199101124131#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.readVersionInformation(DetectSDMComponent.java:503)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.readVersionInformation(DetectSDMComponent.java:503)#Java###Retrieving SDM version by parsing ...#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/version.txt#
#1.5#C000AC1A1C500000000000A501AB28FE000442937C8DB8B8#1199101124131#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.readVersionInformation(DetectSDMComponent.java:538)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.readVersionInformation(DetectSDMComponent.java:538)#Java###SDM version with release , SP level , patch level found in .#5#SAP_JAVASL#7.00#06#0#C:/usr/sap/NW7/DVEBMGS01/SDM/program#
#1.5#C000AC1A1C500000000000A601AB28FE000442937C8DF738#1199101124147#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:361)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:361)#Java###Looking for system kernel(s) under directory .#1#C:
usr
sap
NW7
SYS
exe#
#1.5#C000AC1A1C500000000000A701AB28FE000442937C8DF738#1199101124147#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:371)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:371)#Java###Central instance kernel directory is .#1#C:
usr
sap
NW7
SYS
exe
uc
NTI386#
#1.5#C000AC1A1C500000000000A801AB28FE000442937C8E31D0#1199101124162#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1098)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1098)#Java###Starting searching for kernel version in directory ...#1#C:/usr/sap/NW7/SYS/exe/uc/NTI386#
#1.5#C000AC1A1C500000000000A901AB28FE000442937C8E31D0#1199101124162#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1107)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1107)#Java###You can find additional information in log file .#1#C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
log
log_20071231170532
KERNEL_DETECTION_02.LOG#
#1.5#C000AC1A1C500000000000B701AB28FE000442937C9C81E0#1199101125100#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1122)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1122)#Java###Kernel with release , SP level , patch level found in .#5#SAP KERNEL UNICODE WINDOWS_I386#7.00#52#0#C:/usr/sap/NW7/SYS/exe/uc/NTI386#
#1.5#C000AC1A1C500000000000B801AB28FE000442937C9C81E0#1199101125100#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:407)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:407)#Java###SCS kernel directory is .#1#C:
usr
sap
NW7
SYS
exe
uc
NTI386#
#1.5#C000AC1A1C500000000000B901AB28FE000442937C9F21C0#1199101125272#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:285)#Java###Login dialog has been processed.##
#1.5#C000AC1A1C500000000000BA01AB28FE000442937C9F21C0#1199101125272#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:262)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:262)#Java###Starting dialog...#1#SelectPackageType#
#1.5#C000AC1A1C500000000000CE01AB28FE000442938B53B438#1199101371987#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.deployment.SelectInboxViewGranularityStep.processUI(SelectInboxViewGranularityStep.java:159)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.deployment.SelectInboxViewGranularityStep.processUI(SelectInboxViewGranularityStep.java:159)#Java###The user has chosen for Inbox granulation.#1#Support Package Stack#
#1.5#C000AC1A1C500000000000CF01AB28FE000442938B53B438#1199101371987#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:292)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:292)#Java###Dialog : the user has chosen the Next dialog button.#1#SelectPackageType#
#1.5#C000AC1A1C500000000000D001AB28FE000442938B53B438#1199101371987#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:296)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:296)#Java### dialog has been processed.#1#SelectPackageType#
#1.5#C000AC1A1C500000000000D101AB28FE000442938B53B438#1199101371987#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:181)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:181)#Java###Starting scanning Inbox for deployable J2EE Engine components...#1#
CP-CHN-3F-029
sapmnt
trans
EPS
in#
#1.5#C000AC1A1C500000000000D201AB28FE000442938B53EED0#1199101372002#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:195)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:195)#Java###You can find additional information in log file $.#1#C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
log
log_20071231170532
SCAN_INBOX_01.LOG#
#1.5#C000AC1A1C500000000000D301AB28FE000442938B53EED0#1199101372002#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:205)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:205)#Java###Scanning of Inbox for deployable J2EE Engine components has finished.##
#1.5#C000AC1A1C500000000000D401AB28FE000442938B53EED0#1199101372002#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.spstackanalyzer.SPStackAnalyzer.analyzeSPStacksDir(SPStackAnalyzer.java:147)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.spstackanalyzer.SPStackAnalyzer.analyzeSPStacksDir(SPStackAnalyzer.java:147)#Java###Starting searching for stack definition files in the Inbox...##
#1.5#C000AC1A1C500000000000D501AB28FE000442938B583878#1199101372283#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:756)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:756)#Java###Exception has occurred during the execution of the phase.##
#1.5#C000AC1A1C500000000000D601AB28FE000442938B583878#1199101372283#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:755)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:755)#Java###java.lang.StringIndexOutOfBoundsException: String index out of range: -9##
#1.5#C000AC1A1C500000000000D701AB28FE000442938B583878#1199101372283#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#JSPM/JSPMPhases/JSPM_PROCESS#
#1.5#C000AC1A1C500000000000D801AB28FE000442938B583878#1199101372283#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#c -
Java Support Pack Stack - what about additional patches?
Hi Guys,
I have applied Java SP stacks many times before so this is not a technical question as such.
We download the entire SP Stack and apply it via JSPM. But this only updates the system to that stack with patch level 0. For instance, if I apply SP Stack 3, then all the components will have SP3 patch 0. SAP releases bug fixes from time to time in the form of additional patch files like SP3 patch level 1, 2, 3, etc. for individual components but these are obviously not part of the downloaded stack but need to be downloaded separately for each component.
My question is, is it a good strategy to apply the entire stack as downloaded so this makes all the components to patch level 0 in that stack and then also download all of the latest patch files for each component within that SP level and apply all of them in the next run?
So I think this should fix all the bugs that SAP has fixed using these patch files so this would save us a lot of time which usually goes wasted in encountering the bugs, finding solutions and maybe even going to SAP just to find out that the latest patch files are released which already contain these fixes.
So, can someone tell me whether this is a good idea to do it this way? Or is there any downside to this?
Thanks and Regards,
Shitij BaggaHi,
You can apply eaither ways there woun't any problem.
i mean you can apply directly patch with SP leve or apply the SP level with patch 0
When ever if we apply the patch for any SP level, it over write all the file with patch file
Thanks,
Sreeni. -
How to terminate my JSPM process and start fresh
Hi Guys,
I just updated JSPM and restarted to apply the stack, ran into an error. I would like to completely terminate this JSPM run, clean up any files related to this run and start off again picking my stack and stuff. How do I do this?
ThanksSlava,
Added space and when I run JSPM again it goes straight to Error Report basically saying JSPM_MAIN phase failed although the below log says completed, the DIALOG.LOG says aborted. The DIALOG.LOG also has my list of SCA's as scheduled, I should still be able to restart even at this point right?
Here's JSPM_MAIN_1_01.LOG
Dec 3, 2008 4:38:36 PM [Info]: Checking component /usr/sap/trans/EPS/in/WDAPPS06_0-20001899.SCA for upgrade configurations.
Dec 3, 2008 4:39:14 PM [Info]: You can find additional information in log file /usr/sap/DXI/DVEBMGS00/j2ee/JSPM/log/log_2008_12_03_15_56_11/DETECT_SYSTEM_COMPONENTS_02.LOG.
Dec 3, 2008 4:39:29 PM [Info]: Loaded usage type data from data source jdbc/pool/DXI.
Dec 3, 2008 4:39:29 PM [Info]: Detected system products and usage types.
Dec 3, 2008 4:39:32 PM [Info]: Loaded usage type data from data source jdbc/pool/DXI.
Dec 3, 2008 4:39:32 PM [Info]: Detected system products and usage types.
Dec 3, 2008 4:39:32 PM [Error]: Exception has occurred during the execution of the phase.
Dec 3, 2008 4:39:32 PM [Error]: java.lang.NullPointerException:
Dec 3, 2008 4:39:32 PM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been completed.
Dec 3, 2008 4:39:32 PM [Info]: Start time: 2008/12/03 15:56:45.
Dec 3, 2008 4:39:32 PM [Info]: End time: 2008/12/03 16:39:32.
Dec 3, 2008 4:39:32 PM [Info]: Duration: 0:42:47.363.
Dec 3, 2008 4:39:32 PM [Info]: Phase status is aborted.
and TroubleTicket.txt
The execution ended in error.
java.lang.NullPointerException:
java.lang.NullPointerException:
More information can be found in the log file /usr/sap/DXI/DVEBMGS00/j2ee/JSPM/log/log_2008_12_03_15_56_11/JSPM_MAIN_1_01.LOG.
Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:
com.sap.sdt.jspm.phases.PhaseTypeJSPM
com.sap.sdt.util.diag.JavaException
java.lang.NullPointerException:
JSPM_MAIN
JSPMPhases
NetWeaver Upgrade
SAPJup
Java Upgrade
If you think this is a problem in JSPM, you may post a CSN in BC-UPG-OCS-SPJ.
Then I started looking around and tried renaming (basically deleting, hopefully) some .xml files to see if JSPM does not find the previous file and creates a new one resulting in fresh start. I did not do the delete all that changed since last run. But would you know any specific file that I can delete.
Thanks,
Raj -
Error While applying patch to SAP_BASIS component in solution manager
Dear Techies,
Thanks alot for your prompt responses.
I am Patching my Solutionn manager Box for SAP_BASIS Component.Prsently it is on "SP16", I am trying to patch to "SP17".
after Completing all the steps it is giving the below mentioned error.
Conflicts Between Add-On ST 400 and Support Packages
Component Release Support Package Information on
Conflict Resolution
SAP_BASIS 700 SAPKB70017 CRT: NOT-SUPPORTED
"CRT:NOT-SUPPORTED"
How to go about in this situation.
Thanks in advance.
Regards,
KiranHi Kiran,
You would need to proceed by moving to SAP EHP 1 for SAP Solution Manager 7.0 with required SP level.
For this, you would need to download the complete ABAP and JAVA support pack stacks for the target SP level.
Then, you can update the Java stack using JSPM and ABAP stack using SAINT
Please check SMP for guides. The following guide me also be helpful.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f09c8455-4036-2c10-c7a7-bc3c0879462b?quicklink=index&overridelayout=true
Hope this helps.
Regards,
Varun -
Error Message no. F5669 in Returns after installing Stack 17
Greetings Gurus,
After applying the Stack 17 upgrade to our system we started getting Error Message no. F5669
Posting date is initial
Message no. F5669
Diagnosis
Fiscal year and period are derived from the posting date. The posting date, however, is at the initial setting.
System Response
Fiscal year and period cannot be derived.
Procedure
A system error has occurred. The posting date transferred must have a legitimate value.
I am not familiar with this error. I looked it up and nothing I have found applies to RETURNS.
Since my error only applies to returns that have a charge associated with them, I was hoping someone could offer some information. If I try to process a return for checks with insufficient funds that apply a fee to customers account, I will get this error.
The error says the "The posting date... is at the initial setting"; where do I find the "initial" setting in the IMG? If anyone can direct me I really appreciate it.
ThanksThe notes recommended refer to issues with stack 7.0, we are applying stack 17. Do you have any other suggestions that may lead to a solution? The error is saying that the posting date is at the "initial setting", but I am not sure what that means since our other transactions are posting just fine. I have tried to search for relevant IMG activity without success. Can you tell me if there is a transaction for the posting dates "initial setting"? If there is that may point me to the solution.
Edited by: Terrih Turner on May 31, 2011 12:23 PM
Edited by: Terrih Turner on May 31, 2011 12:24 PM -
Support Package Stacks Best Practice
Good morning all,
We're at the start of a mySAP ERP implementation and we'd like to set a strategy as regards how we implement SP Stacks.
We are only using the base mySAP ERP functionality; we're not using the HR, Retail, Public Services extensions. Because of this, I'd like to know what is the best practice for applying SP Stacks in our environment.
Do we need to install the SPs for the HR, Retail, etc.. extensions to keep the SP Stack consistent, or do we simply install only the base SPs that we require?
Any help is greatly accepted.
Thx,
Arwel.Hi Kobby,
Thanks for your information.
The Support Package Stacks for 7.0 version is 15
I would like to know the Stacks for SAP Solution Manager - 4.0
Version.
Thanks and Regards,
Sateesh.Kandula -
Stacked canvases - best settings for Visible / Raise on Entry
Hello,
I'm currently migrating a Forms 6i client-server application to 10.1.2.0.2 WebForms. I'm familiar with the advice that, to minimise network traffic, tabbed canvases should be changed to use stacked canvases with Visible=No, Raise On Entry=Yes. That way, tabs other than the first one don't get loaded into memory unless you actually go to them.
My question is - does this apply to stacked canvases in general? I have a number of forms with quite a few stacked canvases that get called up depending on user actions; the code calls up the canvas by doing a Go_Item. These stacked canvases are generally all set to Raise On Entry=Yes, but Visible=Yes. Would setting Visible to No give me a performance improvement? (I know, it depends on the application, but in general...) If I do set Visible to No, would I have to add code to change Visible back to Yes when the application goes to an item on the canvas, or will that be handled automatically by Raise On Entry..?
Thanks in advance,
JamesHi Gerd,
Thanks for replying. So when you say 'HIDE=Yes', I presume you mean the 'Visible' property on the Canvas? (Looking in my Forms Builder, there's no 'hide' property on canvases - unless I'm being really dim...)
I do have some fairly large forms with a lot (> 8) stacked canvases, so I may need to consider changing those to hidden - although if it involves extra coding, I might wait to see how performance looks once the application is fully up and running. The tab canvases I have tend to be fairly simple so I'll leave those alone.
I'd be really interested to hear of anyone else's experiences of how multiple canvases affects performance.
James -
Errors while activating Integration Process in Stack 14
Hi
We recently applied the Stack 14 of XI 3.0 on our development server which was on Stack 11 earlier.
After applying the above stack we discovered that when we are trying to activate integration process we are getting the following errors:
'Exception ProxyError does not exist'
'Exception SendIDocError does not exist'
'Exception RFCError does not exist'
'Exception MapError does not exist'
These exceptions are thrown using a Control Step in the integration process and were working fine till Stack 11.
Any idea on how to resolve this?
Thanks
YogeshHi,
We are having similar issues on sp14, we have shortlisted the following packs, just see if they solve your case, also is F4 help after you add a container element aceessable, for me thats another issue.
The oss notes are:
904833,
883500,
890760
I think the first one suits your needs, but read it and see.
All the best.
Anirban.
Maybe you are looking for
-
How to sort out fundamental frequencies from harmonic?
Hello, I have a problem, because I have signals with different frequencies and with their harmonic. But I need only fundamental frequencies. I have found a device: Harmonic distorsion analizer that is theoretically able to find all the fundamental fr
-
Inconsistent Disk Utility Results
When I run Verify Disk in Disk Utility from my boot drive, it tells me the drive needs repair. See log below. Then when reboot from the recovery partition and run Verify Disk from the recovery partition, it says the disk is okay. Same if I run repair
-
EoMPLS problem with 6500 and IOS SXF6 + SXE5
My EoMPLS stopped working after one ge-wan interface gone down and up. Before the down it was working fine. The connection is between two 6500 switches, trough GE-WAN (OSM+4GEWAN) ports. One swith have IOS 12.2(18)SXF6 and the other is using 12.2(18)
-
This may be a silly question, but if I save an AI file as an 8x10 can someone print it as a 16x20 while still maintaining the quality if I have created outlines?
-
Reference for working with a data collection retreived from a Web Service
Does anyone have a good resource / example of working with multi row data collections returned from a web service call? In addition to the basic return of x data rows, I will also be getting parent child collections. For example, for each Customer ro