Nw04 to nw04s

Hi,
got a couple of questions regarding nw04 to nw04s
currently we are on ep 6.0 sp14 and interested to use the features of NW04s.
1. is it an upgrade or migration from nw04 to nw04s? i hope it is an upgrade, am i right?
2. is it mandatory to upgrade all the systems in our landscape i.e. XI, BW, SRM, R3 to nw04s...or is there a facility to use only nw04s PORTAL.
3. as far as i know, nw04s and nw04, the SPs release are going in parallel.. i.e.
are the ep6.0 sp14 and nw04s portal sps5 have the same features or does nw04s portal has additional features compared to EP 6.0 SP14.
my point here is, we are only interested in upgrading portal, so is it ok to continue sp stacks of nw04 or should we shift to nw04s.
could someone please clarify
thank you

Hi,
The code developed on 2004 will work on 2004s.
Some minor changes have been made refer to the documentation for specific details
SAP NW2004s is the mySAP Business Suite edition of SAP NW 2004.it is a minor release that delivers on specific needs of the mySAP and xapps solutions delivered by SAP in 2005. the "s" stands for "mySAP Business Suite Edition".
The next major release of NW will deliver on Business Process Platform(BPP) it will be released in 2006.
Few of the New capabilities in NW2004s
1)Developing a web based user interface with Web Dynpro fro ABAP.
2)Enhancements to enabling B2B processes
3)Enhancements to business task management
4)Enhancements to business planning
5)Enhancements to enterprise data warehousing
6)mass setup of mobile devices
7)implementing a global portal
Refer the link for more info
http://help.sap.com/saphelp_nw04s/helpdata/en/5b/8c3842bb58f83ae10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/57/a21f407b402402e10000000a1550b0/frameset.htm
NW04 is a 'Java version' which means you can develop applications using Java and export them to portal.
NW04s is a 'ABAP version'.Here you can develop ABAP reports and transactions and export them to portal. There you can create iViews using them.
Netweaver 04s, includes both the ABAP and Java stacks. The Sneak preview for NW04s is only for the ABAP stack, and the Sneak Preview NW04 SP15 is only the java stack. If you are using the sneak preview for ABAP, you can develop WDA applications and BSP applications, they run directly in the engine, not in a portal. But they can be embeded in an iView in some portal. You don't have to have a portal to run your application. If you are using the java side, you can develop WDJ applications and JSP applications. Same applies here, they run on the java engine, not in a portal, but can be embeded into an iView which runs on the portal. But you don't need a portal for your application to run. The portal is just a frontend UI, the apps themselves run on the underlying engine, whether its ABAP or JAVA.
Refer to the following threads for more information
Re: What is NW04 s?
Re: Differences between NW04 SP11 and NW04 SP15

Similar Messages

NW04 vs NW04s

Dear all,
What is the difference between NW04 and NW04s? There appears to be some confusion here as to what is required for CRM4.0 and CRM5.0 in terms of which version of the Portal to run? We are currently implementing EP6 SP13 (part of NW04) and are wondering to to upgrade to the NW04s version of EP. Any pointers to documentation on this topic would be greatly appreciated.
Thanks, Neeta

Hi Neeta,
SAP NW2004s is the mySAP Business Suite edition of SAP NW 2004.it is a minor release that delivers on specific needs of the mySAP and xapps solutions delivered by SAP in 2005. the "s" stands for "mySAP Business Suite Edition".
The next major release of NW will deliver on Business Process Platform(BPP) it will be released in 2006.
Few of the New capabilities in NW2004s
1)Developing a web based user interface with Web Dynpro fro ABAP.
2)Enhancements to enabling B2B processes
3)Enhancements to business task management
4)Enhancements to business planning
5)Enhancements to enterprise data warehousing
6)mass setup of mobile devices
7)implementing a global portal
Refer the link for more info
http://help.sap.com/saphelp_nw04s/helpdata/en/5b/8c3842bb58f83ae10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/57/a21f407b402402e10000000a1550b0/frameset.htm
NW04 is a 'Java version' which means you can develop applications using Java and export them to portal.
NW04s is a 'ABAP version'.Here you can develop ABAP reports and transactions and export them to portal. There you can create iViews using them.
Netweaver 04s, includes both the ABAP and Java stacks. The Sneak preview for NW04s is only for the ABAP stack, and the Sneak Preview NW04 SP15 is only the java stack. If you are using the sneak preview for ABAP, you can develop WDA applications and BSP applications, they run directly in the engine, not in a portal. But they can be embeded in an iView in some portal. You don't have to have a portal to run your application. If you are using the java side, you can develop WDJ applications and JSP applications. Same applies here, they run on the java engine, not in a portal, but can be embeded into an iView which runs on the portal. But you don't need a portal for your application to run. The portal is just a frontend UI, the apps themselves run on the underlying engine, whether its ABAP or JAVA.
Refer to the following threads for more information
Re: What is NW04 s?
Re: Differences between NW04 SP11 and NW04 SP15

What is the Upgrade program used to upgrade NW04 to NW04s

Hi,
What is the Upgrade program used to upgrade NW04 to NW04s?
Thanks Sri

SAPup - Program to upgrade Web AS ABAP and related components BW,XI
SAPJup- Program to upgrade WebAS Java and related components EP.
Vijay Kothapalli

J2EE supported versions for NW04 and NW04S

Hi ,
Can Pls anyone pointout some documents for the list of J2EE version support list( For Ex: JSP 2.0 suported in NW04S ) for NW04 and NW04S releases ?
Thanks
Praveen

Praveen,
Both NW04 and NW2004s are J2EE 1.4 compliant. You can get these details by accessing PAM [here|http://service.sap.com/pam]
Check this [wikipedia link|http://en.wikipedia.org/wiki/Java_EE_version_history] as well for more information.
And Java EE is supported in NW7.1
Chintan

Differences between NW04 and NW04s

Hello SAPians,
Can anybody explian me the diffrences between NW04 and NW04s. Or please tell me, where I can find regarding this information.
Thanking you.
Regards,
Ajaykumar

hi
good
NW04->
The Support Platform is an open platform to develop and run small utilities (known as plug-ins) that perform support-oriented activities on any and all components of SAP NetWeaver. The Support Platform is included NW04 SP13 and higher.
Plug-ins generally perform tests or create reports. A plug-in might check the configuration of the system, check if permissions are set correctly, or check the name of your current Web AS version. You can create plug-ins for any task that can be performed by a Java program.
Each plug-in is a single Java class, and groups of plug-ins are deployed to the Support Platform in JAR files. The Support Platform comes with a collection of out-of-the-box plug-ins; developers can write their own plug-ins, which administrators can then deploy and run.
The Support Platform can monitor the entire Web AS system on which it runs, and can run plug-ins on any of the Java processes in the cluster. The Support Platform provides a user interface for deploying plug-ins, displaying available plug-ins, running them and displaying the results.
NW04s -> This is an advance version of NW04 server.
thanks
mrutyun^

Webdynpro error after upgrade NW04 to NW04s sp9

Hi,
I created some WD in NW04 using JDI. After upgrade to NW04s i got error messages in the program. The messages look like:
Error com.sap.tc.webdynpro.progmodel.api.IWDApplicationStateChangeInfo cannot be resolved (or is not a valid type) for the argument stateChangeInfo of the method wdDoApplicationStateChange LeaveReqComp.java OJL_TEST_Dpoczelfbedwebdynreqbelastingdienst.nl/gen_wdp/packages/nl/belastingdienst/zelfbed line 203
Hope somebody can help me solve my problem.
Kind regards,
Maarten.

Hi Maarten
I am also facing similar sort of problem when i am trying to import the local web dynpro DC into 2004s that was build n exported from 2004 and when i try to build it in 2004s i get error
com.sap.tc.webdynpro.progmodel.api.IWDApplicationStateChangeInfo cannot be resolved for the argument stateChangeInfo of the method wdDoApplicationStateChange
com.sap.tc.webdynpro.progmodel.api.IWDApplicationStateChangeReturn cannot be resolved for the argument stateChangeReturn of the method wdDoApplicationStateChange
were u able to solve the problem if yes please help me in that case
thanks !
Asif

ABAP Dynpro available in NW04 and NW04s

Hello:
Is ABAP Dynpro available in NW04 as well as in NW04s? I think that WebDynpro (Java) is already available in NW04 but I was not sure about ABAP Dynpro.
Can anyone help me verify this?
Thank you...
George Lu

WD ABAP is fully useable in WAS 7.0(NW 2004s). There are reminants of WD ABAP in WAS 6.40(NW 2004). You can access the WD objects, but you may have some problems. But to answer, WD ABAP is only in 2004s.
Regards,
Rich Heilman

Connect ECC 6.0 with EP NW04, BW NW04 and CRM 4.0

Hello All,
We have R/3 Enterprise 47 x 200, we have connected to it the EP version NW04, BW version NW04 and CRM version 4.0 so, we need to upgrade only the R/3 to the new ECC 6.0 without upgrading the other components.
My questions is if anyone knows if, Is it possible connect those old version to the new ECC 6.0 and where can I found this information?
I was looked into marketplace, help.sap and in this forums but I didn't found anything so if you can help me to solve it, I will be very grateful.
Thanks in advance,
Alfonso

EP6.0 will work perfectly fine with ECC6 but as previous posters have pointed out, technically its not a supported landscape.
You would have little problem with simple transactional, BSP access etc but you would need to be careful about the use of any business packages you might want to use. You would need business packages appropriate to the backend version you have (particularly for ESS/MSS) and then you would need to validate whether they actually work with EP6.0.
Bit of risk as its not supported.
Haydn

Checklist after upgrade from EP NW04 to NW04s?

Hi, Gurus:
what should be checked after EP NW04 upgradd to NW04s?
iview display
business struture
system connection
assigned role
any other should be paid attention to?
Br,
Nikko

Hi,
quick summary :
verify TREX connection / indexing
business package
SSO between user --> portal and portal --> R/3
Test systems in system landscape
Verify Url generator config
Verify services in monitoring
Local and online editing (test some office files)
Password rules in configtools
Logoff link
Notification/subscription emails (connection to mail server)
Backup online/offline (test the backups for a restore)
As said before, all custom services/programs, etc.
You need to rebuild them with the new 2004s developper studio (with 2004s api).
Brad

Upgrade from NW04 to NW04s

Hi,
We have a NW04 WAS 6.40 and we would like to upgrade it to a NW04s.
How can we perform it?
Has anyone some idea about which packages are necessary and how long does it take?
Thanks in advance!

Hi Christophe:
You can choose NW04 that is already in GA or you can choose NW04s that is currently in ramp-up; If you are going to start your implementation you can take full advantage and start using NW04s directly getting more value from the new functionalities of WAS 7.00.
You can get additional information from https://service.sap.com/rampup
Read this from the Marketplace:
SAP NetWeaver 2004s is the mySAP Business Suite edition of SAP NetWeaver 2004. It is a minor release that delivers on specific needs of the mySAP and xApps solutions delivered by SAP in 2005. The "s" stands for "mySAP Business Suite Edition". SAP NetWeaver 2004s will initially be made available through the ramp-up of the mySAP Business Suite Solutions. SAP NetWeaver is a comprehensive platform comprising former components like SAP EP or SAP BI, which do not longer carry an individual release number.
For customers looking to implement SAP NetWeaver during 2005 in the course of integration or development projects, or in the context of an ESA roadmap strategy, an implementation of SAP NetWeaver 2004 is recommended, as this is the current default release. An implementation of SAP NetWeaver 2004s is only recommended where new capabilities made available with SAP NetWeaver 2004s are absolutely required (e.g. Web Dynpro ABAP, new BI capabilities, MI - mass client administration).
Hope this helps!
Best Regards,
Federico

Error in ACTIVATE_CURRENT_USAGES phase of portal upgrade (NW04 to NW04s)

hello gurus,
i am upgrading Netweaver 04 to netweaver 04s (Enterprise Portal)
oracle upgrade from 9.2.0.7 to 10.2.0.1 successfully
but i am getting error in 78 phase out 100 in java upgrade program management
ACTIVATE_CURRENT_USAGES
i am unable to track the cause.......
log file is shown below
kindly help......
its urgent
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[D:\usr\sap\jupgrade\log\ACTIVATE_CURRENT_USAGES_ACU_07.LOG]/>
<!PATTERN[ACTIVATE_CURRENT_USAGES_ACU_07.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
#1.5#C000AC1908C2000000000029014A8CD1000432D6B5DD7008#1181797662421#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:713)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:713)#Java###Phase has been started.#1#UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES#
#1.5#C000AC1908C200000000002A014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:714)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:714)#Java###Phase type is .#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask#
#1.5#C000AC1908C200000000002B014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#Java### Parameter =#2#inputFile#ExecuteTasks.xml#
#1.5#C000AC1908C200000000002C014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#Java### Parameter =#2#taskName#ACTIVATE_CURRENT_USAGES#
#1.5#C000AC1908C200000000002D014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.checkParameters(PhaseTypeExecuteTask.java:191)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.checkParameters(PhaseTypeExecuteTask.java:191)#Java###Phase parameters have been checked. All required phase parameters have been set.#1#2#
#1.5#C000AC1908C200000000002E014A8CD1000432D6B5F009C0#1181797663640#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#Java###Configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks.xml#
#1.5#C000AC1908C200000000002F014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#Java###Configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks_WIN.xml#
#1.5#C000AC1908C2000000000030014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildGlobalConfiguration(ConfigurationBuilder.java:251)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildGlobalConfiguration(ConfigurationBuilder.java:251)#Java###Global configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks.xml#
#1.5#C000AC1908C2000000000031014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##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#2#com.sap.engine.offline.OfflineToolStart#
#1.5#C000AC1908C2000000000032014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##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_09
jre
bin
java.exe -cp d:/usr/sap/W60/SYS/global/sltools/sharedlib/launcher.jar;d:/usr/sap/W60/SYS/global/sltools/sharedlib; com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain d:/usr/sap/W60/SYS/global/sltools/sharedlib;D:/usr/sap/W60/SYS/global/security/lib/tools;D:/usr/sap/w60/jc00/exe/classes12.jar -activated -sid=W60 -dsn=jdbc/pool/W60 -ssprops=D:/usr/sap/W60/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/W60/SYS/global/security/data/SecStore.key -log=D:
usr
sap
jupgrade
log/ACTIVATE_USAGE_AS.LOG -prod_name=NetWeaver -usage_name=AS -usage_vendor=sap.com -action=true#
#1.5#C000AC1908C2000000000033014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##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# #D:
usr
sap
jupgrade
log
ACTIVATE_USAGE_AS_ACU_01.OUT#
#1.5#C000AC1908C2000000000034014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##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#2#
#1.5#C000AC1908C2000000000035014A8CD1000432D6B5F1B770#1181797663750#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##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#2#java.exe#
#1.5#C000AC1908C2000000000036014A8CD1000432D6B6B9BE78#1181797676859#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##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#2#java.exe#64#
#1.5#C000AC1908C2000000000037014A8CD1000432D6B6B9BE78#1181797676859#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:735)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:735)#Java###Exception has occurred during the execution of the phase.##
#1.5#C000AC1908C2000000000038014A8CD1000432D6B6B9FCF8#1181797676875#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.execute.AbstractExtProcessOperation.generateResultProcessingException(AbstractExtProcessOperation.java:579)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.execute.AbstractExtProcessOperation.generateResultProcessingException(AbstractExtProcessOperation.java:579)#Java###Could not activate usage AS. Could not execute 'C:
j2sdk1.4.2_09
jre
bin
java.exe -cp d:/usr/sap/W60/SYS/global/sltools/sharedlib/launcher.jar;d:/usr/sap/W60/SYS/global/sltools/sharedlib; com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain d:/usr/sap/W60/SYS/global/sltools/sharedlib;D:/usr/sap/W60/SYS/global/security/lib/tools;D:/usr/sap/w60/jc00/exe/classes12.jar -activated -sid=W60 -dsn=jdbc/pool/W60 -ssprops=D:/usr/sap/W60/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/W60/SYS/global/security/data/SecStore.key -log=D:
usr
sap
jupgrade
log/ACTIVATE_USAGE_AS.LOG -prod_name=NetWeaver -usage_name=AS -usage_vendor=sap.com -action=true', return code '64'. You can check the file(s) 'D:
usr
sap
jupgrade
log/ACTIVATE_USAGE_AS_ACU.OUT', 'D:
usr
sap
jupgrade
log/ACTIVATE_USAGE_AS_ACU.ERR' to which the output of the process has been redirected.##
#1.5#C000AC1908C2000000000039014A8CD1000432D6B6B9FCF8#1181797676875#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.execute.AbstractExtProcessOperation.execute(AbstractExtProcessOperation.java:176)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.execute.AbstractExtProcessOperation.execute(AbstractExtProcessOperation.java:176)#Java###Error while processing the result.##
#1.5#C000AC1908C200000000003A014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.execute(PhaseTypeExecuteTask.java:173)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.execute(PhaseTypeExecuteTask.java:173)#Java###Error while executing PhaseTypeExecuteTask with input file ExecuteTasks.xml and task ACTIVATE_CURRENT_USAGES.##
#1.5#C000AC1908C200000000003B014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:779)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:779)#Java###Phase has been completed.#1#UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES#
#1.5#C000AC1908C200000000003C014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:780)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:780)#Java###Start time: .#1#2007/06/14 10:37:42#
#1.5#C000AC1908C200000000003D014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:781)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:781)#Java###End time: .#1#2007/06/14 10:37:56#
#1.5#C000AC1908C200000000003E014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:782)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:782)#Java###Duration: .#1#0:00:14.453#
#1.5#C000AC1908C200000000003F014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:783)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:783)#Java###Phase status is .#1#error#
waiting for solution
thankx in advance....
shoeb

Could you please share us the solution?

Upgrade NW04 to NW04S

Hi Brad,
We are doing the Upgrade of Portal but it is on phase 72/118 for 4 days. Is it normal?
There is no error reported.
Regards,
Nivia

Hi Nivia,
I remembered something this morning, and verified in my migration/upgrade notes from last year.
I too had problems in my "deploy online" phase.
I had to update the oracle jdbc driver to the last 10.2.0.2 one.
You may give that a try (update the oracle jdbc driver) if the j2ee restart does not help you.
Brad

Migration from NW04 to NW04s

Hi,
I have two servers.
One is the DTR/SLD/CMS/CBS working on NW2004.
The other is the DTR/SLD/CMS/CBS working on NW2004s ie NW 7.0 SP11
I have trackd on both the DTRs
I need to transport the SC & DCs created on the track on NW2004, to the new track on NW2004s(NW7.0).
Is there any SAP document or blog about this transportation??
I read on help.sap about importing the project into the NWDS04s & then copy pasting the src files to the DCs of the new track. But i want to avoid this.
Is there any other systematic way of going ahead with this??
Regards,
Hanoz

go thru dis
/people/guenter.schiele/blog/2007/02/12/how-to-migrate-developed-software-components-to-a-new-release-in-nwdi

Error while upgrading NW04s to sp5

I installed NW04s in my machine. I am trying to upgrade it to sp5. I could upgrade the ABAP stack to sp5 without any problem. When i am doing java stack, i could update all other support packages except the one 'CAF05_0-10003464.SCA'. When this package is on progress, the process gets almost completed and gives the status also 'deployed'. But after that it throws the following error and the status also changed to 'not deployed'.
ERROR: Not updated. Deploy Service returned ERROR:
 java.rmi.RemoteException: Exception in operation update with application sap.com/caf~tc..
 Reason: com/sap/caf/metamodel/ApplicationInterface; nested exception is:
 java.lang.NoClassDefFoundError: com/sap/caf/metamodel/ApplicationInterface
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:682)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
 Caused by: java.lang.NoClassDefFoundError: com/sap/caf/metamodel/ApplicationInterface
 at java.lang.Class.getDeclaredMethods0(Native Method)
 at java.lang.Class.privateGetDeclaredMethods(Class.java:1655)
 at java.lang.Class.privateGetPublicMethods(Class.java:1778)
 at java.lang.Class.privateGetPublicMethods(Class.java:1788)
 at java.lang.Class.getMethods(Class.java:832)
 at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getWithNotSpecifiedMethodInterface(MethodsExtractor.java:156)
 at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getAllMethodsInBean(MethodsExtractor.java:103)
 at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.getMethodXml(EJBJarParser.java:1168)
 at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processContainerTransaction(EJBJarParser.java:1023)
 at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processAssemblyDescriptor(EJBJarParser.java:924)
 at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:156)
 at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:97)
 at com.sap.engine.services.ejb.deploy.DeployAdmin.parseSingleJar(DeployAdmin.java:298)
 at com.sap.engine.services.ejb.EJBAdmin.buildAppDescriptorBeforeUpdate(EJBAdmin.java:408)
 at com.sap.engine.services.ejb.EJBAdmin.needUpdate(EJBAdmin.java:341)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.getContainersWhichNeedUpdate(UpdateTransaction.java:537)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.getConcernedContainers(UpdateTransaction.java:493)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:263)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:670)
 ... 10 more
 For detailed information see the log file of the Deploy Service.
06/11/29 12:14:54 - ***********************************************************
Nov 29, 2006 12:14:54... Info: End of log messages of the target system.
Nov 29, 2006 12:14:54... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Nov 29, 2006 12:14:54... Error: Aborted: development component 'caf/tc'/'sap.com'/'MAIN_APL70VAL_C'/'644873':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Exception in operation update with application sap.com/caf~tc..
Reason: com/sap/caf/metamodel/ApplicationInterface; nested exception is:
 java.lang.NoClassDefFoundError: com/sap/caf/metamodel/ApplicationInterface
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Nov 29, 2006 12:14:55... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Can anyone help me to sort out this problem?

Symptom
JSPM hangs by upgrade from SP4 to SP5 with the following message into the log file:
ERROR: Not updated. Deploy Service returned ERROR: java.rmi.RemoteException: Exception in operation
update with application sap.com/caf~tc..
Reason: com/sap/caf/rt/exception/CAFDeleteException; nested exception is: ,,java.lang.NoClassDefFoundError:
JUP fails by NW04 SP14 -> NW04s SP5 upgrade with the message into log file:
ERROR: Not updated. Deploy Service returned ERROR: java.rmi.RemoteException: Exception in operation
update with application sap.com/caf~tc..
Reason: com/sap/caf/rt/exception/CAFDeleteException; nested exception is: ,,java.lang.NoClassDefFoundError:
Reason and Prerequisites
Deployment of CAF component sap.com/caf~tc failed by deployment scenario of type:
1. The application is deployed with a reference to Lib1, where Class A
is included.
2. Then class A is moved from Lib1 to Lib2 (removed from Lib1);
3. Then the new version of the application which has references to both
libraries Lib1 and Lib2 is deployed via SDM;
4. The deployment fails with NoClassDefFoundError: class A.
For patricular case we have the situation:
The class com/sap/caf/rt/exception/CAFDeleteException was moved from
caf/runtime/ear to caf/runtime/api/lib between the SPs.
Solution
Please follow the steps:
1. Close JSPM application
2. Start <device>:\usr\sap\<sid>\JC<instance number>\SDM\program\RemoteGui.bat
3. From the menu invoke "SDM Gui" -> "Login" and enter your SDM password
4. Navigate to tab "Undeployment" and select CAF component caf~tc, press button "Select" and "Start Undeployment" and complete undeployment confirming it.
5. Navigate to tab "Deployment" and select CAF component using plus button and select option "Update deployed SDA/SCAs that have any version" into Deployment configuration options below and complete deployment confirming it.
6. Close "SDM Gui" application.
7. Restart JSPM and on the step "Select package type" select option "Single support packages" in order to update all other components, which left not deployed.
8. On step "Specify Queue" select all not deployed components and complete their deployment.
An alternative way is:
1. If there is a problem with CAF deployment do not stop the upgrade application.
2. Open command prompt and go to SDM\program directory
3. Execute: sdm jstartup "mode=integrated"
4. Execute: startserver
5. After that start the SDM remote GUI application
6. From the menu invoke "SDM Gui" -> "Login" and enter your SDM password
7. Navigate to tab "Undeployment" and select CAF component caf~tc, press button "Select" and "Start Undeployment" and complete undeployment confirming it.
8. Logout and close "SDM Gui" application.
9. In the command prompt execute: stopserver
10. In the command prompt execute: sdm jstartup "mode=standalone"
11. Go to the Upgrade application and restart the process from the point of failure
Best Regards,
Barry.

What is the quickest to upgrade disaster recovery system to NW04s in MSCS?

Hi,
I have an issue which I need assistance from SAP/Windows 2003 experts.
Hope you can share your opinion on an SAP upgrade issue we're grappling with.
Objective : Upgrade our SAP Bank Analyzer disaster recovery environment from NW04 to NW04s SR2, to be same as production. Both production and disaster recovery (DR) run under two node WIN2003 Enterprise MSCS. The SAP CI usually runs on node A and Oracle 10g runs on node B.
The Oracle software, parameters, database files and the SAP folder \usr\sap are already matching. These files and folders are on EMC mirrored disks, so this will be automatically synchronized from production status.
Therefore I believe it is only the SAP software components on the local hard disks - binaries, DLLs, registry, DCOM, environment variable etc, that need to be upgraded on the two DR machines.
For your information, the current SAP 6.40 instance, Oracle 10g instance, MSCS failover capability are all working in the DR environment as we just did an exercise a month ago to prove this.
 Disaster Recovery Environment :
On shared drives that are synchronized between prod and DR : SAP folder \usr\sap including the kernel binaries, Oracle parameter files, database datafiles, redologs, sapbackup etc.
Issue : What is the quickest and reliable method to achieve the objective? Other than the SAP kernel binaries and profiles, I'm not certain what other related components are updated/replaced that are stored locally on each of the clustered machine.
There are three different approaches we can think of :
1) Repeat the whole NW04s upgrade process in the DR environment. This takes several days. The exposure of not having a disaster recovery environment for several days is a minus.
 or
2) Un-install the SAP CI and MSCS definitions. Synchronise the DR shared disks from production to have the upgraded production NW04s database contents and SAP folder \usr\sap.
Use SAPINST to re-install either traditional CI or ASCS option 'System Copy". And then re-create the MSCS definitions for SAP CI using SAPINST again.
The disadvantage is I can't trial this in any other of our environments. Also, we want to run with the traditional CI instead of ASCS until early next year for other reasons. So we would have to reverse the ASCS back to traditional CI with this method, by reversing the steps in OSS NOTE 101190 "Splitting CI after upgrade to 700".
 or
3) Somehow identify all the SAP components that are stored locally on each machine (eg. environment variables, registry settings, DCOM definitions, DLL in various folders). Then just copy them from Production to DR machines or recreate them. I'm not confident of identifying the local SAP components. And I have not been able to find any good OSS NOTEs or forum threads on this topic. The most helpful OSS NOTE I can find is 112266 point 13 and 19.
Thanks for any input.
Benny Kwan

See:
* https://support.mozilla.com/kb/Form+autocomplete
* Firefox > Preferences > Privacy > History: "Remember search and form history"
* Autofill Forms: https://addons.mozilla.org/firefox/addon/autofill-forms/

Nw04 to nw04s

Similar Messages

Maybe you are looking for