Upgrading EP6 SP10(j2ee,portal,KMC) to SP11

Hi,
I am trying to upgrade my EP6 SP10(with KMC) to SP11.
I downloaded all the patch files for J2EE, Portal &
KMC. I unzipped all the sar files in to a common folder
(sp_directory) using sapcar tool, exactly the way it is
listed in the documentation. As a result, there are
two main folders created in the root folder, one for
j2ee and the other for Portal & KMC. The document says,
I need to patch all the 3 components using the same SAPInst file. But, whenever I run the SAPInst exe file,
it is taking me through the same steps that is upgrading J2EE alone. After running SAPInst twice, I checked the versions of these 3 components in the portal and found that only J2EE is upgraded. Neither Portal platform nor the KMC has upgraded. Is there anything else that I need to do ?
regards
Sudheer

Sudheer,
You have to upgrade each component separately. Don't unsar everything together. This is what you do.
1. Unsar all the files required for J2ee upgrade.
3. run the sapinst to upgrade.
4. Delete all the folder/files directory created by unsar
5. Unsar all the files required for EP.
6. run the sapinst to upgrade EP.
7. Delete all the folder/files created by unsar.
8. Unsar all the files required for KMC.
9. run the sapinst to upgrade KMC.
10. delete all the folder/files created by unsar

Similar Messages

Upgrade Ep6 to NW04s portal - deploy error

I am upgrading our EP 6 system to NW04s w/Portal. Java AS only. No ABAP. In the DEPLOY_ONLINE phase it is stopping after about 2 hours.
When I restart it, from the logs it appears to be restarting from the beginning instead of where it stopped. But I can't find the true cause of why it's stopping in the first place.
My arch logs are not full and my tablespaces are ok, so the DB didn't fill up with anything more than it should.
The logs show that most items were deployed, even though with warnings. 2 errored out, although I can't find why in the detailed logs:
Aug 4, 2006 12:10:42 PM Info: Summarizing the deployment results:
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/ADSSAP08_0-10003001.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIIBC06_0.SCA
Aug 4, 2006 12:10:42 PM Info: OK: /usr/sap/put/PD1upg/data/archives/BIWEBAPP06_1.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIMMR08_0-10002782.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIUDI08_0-10002781.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5***03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5BUA03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5BUY02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5COM02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5DCO02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5ESS03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5HRA03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5INV02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5MSS03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5MTC02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PLA02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PRS02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PSS03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5QIN02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5SAL02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5SUP02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAF08_0-10003464.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAFKM08_0-10003478.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAFUM08_0-10003472.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPPSERV08_0-10003474.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPWDC08_0-10003557.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPBC208_0-10003489.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/FSCMBD03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/ISHERCSS03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMKWJIKS08_0-10003021.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCBC08_0-10003491.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCCM08_0-10003492.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCCOLL08_0-10003493.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/LMPORTAL08_0-10003487.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/LMTOOLS08_0-10003486.SCA
Aug 4, 2006 12:10:42 PM Info: OK: /usr/sap/put/PD1upg/data/archives/NETPDK08_0-10003351.SCA
Aug 4, 2006 12:10:42 PM Info: OK: /usr/sap/put/PD1upg/data/archives/RTC08_0-10003494.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/RTCSTREAM08_0-10003488.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPCRMDIC03_0.sca
Aug 4, 2006 12:10:42 PM Error: Aborted: /usr/sap/put/PD1upg/data/archives/SAPEU08_0-10003026.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPPCUIGP03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPASR03_0.sca
Aug 4, 2006 12:10:42 PM Error: Aborted: /usr/sap/put/PD1upg/data/archives/SAPESS03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPMSS03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPPSS03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/UMEADMIN08_0-10003471.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/UWLJWF08_0-10003490.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/VCBASE08_0-10003602.SCA
Aug 4, 2006 12:10:42 PM Info: OK: /usr/sap/put/PD1upg/data/archives/VCFLEX08_0-10003616.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/VCFRAMEWORK08_0-10003624.SCA
Aug 4, 2006 12:10:42 PM Info: OK: /usr/sap/put/PD1upg/data/archives/VCKITGP08_0-10003617.SCA
Aug 4, 2006 12:10:42 PM Info: OK: /usr/sap/put/PD1upg/data/archives/VCKITXX08_0-10003615.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/WDEXTENSIONS08_0-10003618.SCA
Aug 4, 2006 12:10:42 PM Error: Processing error. Return code: 4

Hello,
We are having the exact same issue when DEPLOY_ONLINE encounters WDEXTENSIONS08_0-10003618.SCA as part of the NW2004s upgrade process.
We just submitted an OSS message to SAP about it --- but I am wondering if you have received a solution already?
Is this a bad support package that SAP released?

SSL and EP6 SP10 Issue

We are running EP6 SP10 and trying to use SSL keys for secure access. We are using Hardware SSL key and it is configured on a seperate machine. When we use the
https:// url for the portal it shows the log in screen and after loggin on it refreshes and displays the same screen in http:// format. Is there any SSL key activation that needs to be done in the J2EE Server?
Also if we force the URL to https://portal, it works fine. Its just the login screen that throws us back in a http spin.
Please advise
Thanks,

Hi,
just trying to be of help - here's a link to the documentation for configuring SSL on the J2EE Engine: <a href="http://help.sap.com/saphelp_nw04/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a/frameset.htm">Configuring the Use of SSL on the SAP J2EE Engine</a>.
Regards,
Ivo

I am upgrading it to Enterprise Portal 6.0 Service Pack 22.

Hi,
I need to upgrade Enterprise Portal 6.0 Service Pack 09.
I am upgrading it to Enterprise Portal 6.0 Service Pack 22.
I am writting the download files names:
1> WebAS 6.40 SP22(Part 2/4): SAPInst Control File for Oracl--> CTRLORA22_0-20000118.SAR.
2> EP 60 SP22 SAPInst Control File: EP6CTRL22_0-10002786.SAR.
3> EP 6.0 Tools SP22--> EP6TOOLS22_0-20000394.SAR.
4> WebAS 6.40 SP22(Part 4/4): OS Indep. Parts of Java Runtime--> J2EERT22_0-10001982.SAR.
5> WebAS 6.40 SP22(Part 1/4): SAPINST22_0-20000118.SAR.
6> EP 60 SP22 SAP Installer: SAPINST22_0-20000394.SAR.
7> TREX 6.1 REV34--> TREX61_34-10002767.SAR.
8> KMC NW04 SP22--> EP6KMC22_0-10002972.SAR.
9> WebAS 6.40 SP22(Part 2/4): SAPInst Control File for SAPDB.
10> WebAS 6.40 SP22(Part 2/4): SAPInst Control File for MSS.
11> WebAS 6.40 SP22(Part 2/4): SAPInst Control File for DB6.
12> WebAS 6.40 SP22(Part 2/4): SAPInst Control File for DB4.
13> WebAS 6.40 SP22(Part 2/4): SAPInst Control File for DB2.
I have Oracle 9i as Database. So, I will not use Control Files for SAPDB, MSS, DB6, DB4 and DB2.
I am installing other upgrades files but I need to know the sequence when installing the upgrades.
Regards
Kaushik Banerjee

I am closing it.

Configuring Delayed Failover / Loadbalancing -EP6 SP10

Hi All,
We are installing EP6 SP10 (Single server set up) and plan to add a few more servers to facilitate Loadbalancing & Failover at a later stage. My Question is whether SAP Netweaver allows this procedure and if yes, would the installation steps for EP (initial installation) be the same, or would it different installation process to be followed?
Thanks,
-Mayur

Hi Rizwan,
This is definitely supported by SAP. You may just need to go to a higher SP stack. Check out the High Availability page on Service marketplace.
http://service.sap.com/ha
There are links to the documentation, presentations, how tos, etc. As far as changing you installation steps, the answer is no. The initial installation installs your web AS with the SCS instance, the DB and then you put the portal on after that. If you go back into the SAPinst installer you will find the option to add the server instances.
Hope this helps.
John

Upgrading from BEA Weblogic portal 8.1.5 to BEA Weblogic Portal 10.3

We are upgrading from BEA Weblogic portal 8.1.5 to BEA Weblogic Portal 10.3. We just took over the project from some other vendor since last 9 months. At some of the places in the code, we are using internal APIs of Weblogic Server which should not have been used at the first place.
As weblogic has changed the version and internal structure as well as the classes also, We are facing problems in terms of compilation of the code itself.
The class "ServletRequestImpl" is giving us issues.
Has anybody faced the similar issues, if yes, please let me know.

Andy-
Since the Struts portlet support requires that struts app be converted to a module,
alternate message resources need to be accessed by modifying the bundle name by
appending the module name, since Struts doesn't automatically propogate the alternate
resources from the ServletContext to the Request when a module is selected.
For instance, in suppose your struts application module is /struts/myExample.
To access the alternate bundle from within that module, you'll need to specify
the bundle as alternate/struts/myExample.
-Brodi Beartusk
"Andy Hull" <[email protected]> wrote:
>
Hi,
I'm trying to get the struts-example webapp from Struts 1.1 RC1 working
under
Weblogic Portal 8.1 with the JSR 168 and Struts support patch.
I am having problems with the message bundle properties files ApplicationResources.properties
and AlternateApplicationResources.properties as neither of these files
are being
picked up.
These files are located in org/apache/struts/webapp/example in WEB-INF/src
and
WEB-INF/classes of my webapp (i.e. <WEBAPP>/WEB-INF - my struts-example
resides
in <WEBAPP>/struts-example). I've also tried adding <init-param>'s to
the <WEB-APP>/WEB-INF/web.xml
file for the action servlet as follows:
<servlet> <servlet-name>action</servlet-name> ... <init-param> <param-name>application</param-name>
<param-value>org.apache.struts.webapp.example.ApplicationResources</param-value>
</init-param> <init-param> <param-name>alternate</param-name> <param-value>org.apache.struts.webapp.example.AlternateApplicationResources</param-value>
</init-param> </servlet>
When I use the logon action as the starting action for the portlet, I
get:
Error opening /struts-example/logon.jsp. The source of this error is
javax.servlet.ServletException:
Cannot find message resources under key alternate at weblogic.servlet.jsp.PageContextImpl.handlePageException...
Any help would be appreciated.
--Andy

Error after SPS upgrade from SP10 to SP12

Hi Friends,
Recently we have done SOLMAN 7.1 sp upgrade from sp10 to sp12.
Now I want to perform configuration activities in SOLMAN_SETUP.
But when I am trying to do SYSTEM PREPARATION, I am facing error in first step(Maintain Users).
"Error: Number of elements in the collection of node COMPONENT CONTROLLER.1.NAMESPACES violates the carnality".
Kindly suggest me how to clear this above error and proceed further. Further please let me know as a SOLUTION MANAGER consultant what are the steps I need to perform post SP upgrade. I am not BASIS guy. So please let me know what are the activities which need to be performed by BASIS guy and SOLMAN guy
Please find the attached screen shot for the error screen.
Thanks & Regards,
Solman Starter

Go the transaction STMS, if a window appears when you start the transaction that's mean it is not configured.
Only in this case :
1. Logon on to client 000 with DDIC.
2. Execute transaction SE06
3. Select the Database Copy or migration option
4. Press the Post-installation Processing button.
5. When prompted Do you want to re-install the CTS? Press the Yes button
6. When prompted for the Source System of Database Copy?, make sure that the <SID> of the production system is selected. Press the checkmark button to continue.
7. When prompted Change originals from PRD to QUA?, press the Yes button
8. When prompted Delete TMS Configuration?, press the Yes button
9. When prompted Delete old TMS configuration?, press the Yes button
10. When prompted Delete Old Versions of transport routes?, press the No button
Concerning the initial problem, i found this note :
http://service.sap.com/sap/support/notes/2025884

Upgrade EP6 SP11 to EP6 SP13 - SDM Return Code: 4

Hi,
We are installing EP6 Sp13 on our existing Ep6 SP11 and we are getting the below error during the installation phase "Deploy via SDM/J2EE". Error is as shown in the
callSdmViaSapinst.log :
05/09/29 14:14:10 - ***********************************************************
05/09/29 14:14:11 - Start updating EAR file...
05/09/29 14:14:11 - start-up mode is lazy
05/09/29 14:14:11 - EAR file updated successfully for 218ms.
05/09/29 14:14:11 - Start updating...
05/09/29 14:14:11 - EAR file uploaded to server for 110ms.
05/09/29 14:14:13 - ERROR: Not updated. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/com.sapportals.connectors.sap..
                     Reason: Exception during generation of components of application sap.com/com.sapportals.connectors.sap in container connector.; nested exception is:
                          com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/com.sapportals.connectors.sap in container connector.
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:592)
                          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:294)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
                          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:95)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
                     Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/com.sapportals.connectors.sap in container connector.
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:382)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:379)
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:148)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3033)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:580)
                          ... 10 more
                     Caused by: java.lang.NullPointerException
                          at com.sap.engine.services.connector.jca.deploy.DeployAdmin.mergeDescriptorsConfigProps(DeployAdmin.java:3068)
                          at com.sap.engine.services.connector.jca.deploy.DeployAdmin.mergeDescriptors(DeployAdmin.java:2976)
                          at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:736)
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:376)
                          ... 16 more
                     For detailed information see the log file of the Deploy Service.
Thanks.
regards,
Mike

Hi Mike,
I would first try to stop the installation and start again to see if it continues for where it stopped.
If this do not works, I would try to stop the patch upgrade,
start the SDM and undeploy the com.sapportals.connectors.sap.sda, stop again the SDM and then restart the upgrade.
You also might like to check the SAP Notes 841299, 751175, 750360, 710966 as your problem seems to be related to the sap connectors.
Hope this helps,
Robert

Upgrade EP 6.0 SP2 Patch 4 Hotfix 6 - PL 28 (J2EE, EP, KMC)

Hello,
we have a productive SAP Enterprise portal environment in the version:
- J2EE cluster 6,20 PL 24 (84596.20)
- EP 6,0 SP2 PL 4 Hotfix 6 - 6.0.2.4.6
- cm & Collaboration - 6.0.2.4.2
- SDM PL 12 - 1.3/6.2020030912164144.0000
On the last maintenance weekend we tried to upgrade the whole productive environment to the Patchlevel 28.
For this we proceeded after the installation guides of the SAP.
As follows:
- Upgrade the SDM to PL 14. -> Successfully upgrade !
- Upgrade the J2EE 6.20 Cluster to PL 28 directly -> Successfully upgrade on both Servernodes !
Now our problem:
With the Upgrade of the portal of version 6.0.2.4.6 directly on version PL 28 (after installation
guidance: Installing Patch 28 for Enterprise portal 6,0 SP2) it looks like, as if the Upgrade
would successfully have gone through!
With access to the portal over a Webbrowser the portal cannot be opened. We receive the following
error message:
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
The object found is not an IView: pcd:portal_content/henkel/framework/iviews/com.henkel.AnonPortalLauncher.
Exception id: 05:40_20/03/05_0010
See the details for the exception ID in the log file
With another access of the standard Login site, this side appears, but after the Login only a white empty side appears.
->
http://ntep006.de.henkelgroup.net:50000/irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default
Because the Patchlevel 28 doesn´t function we went back to the old version ! - Therefore it is not possible now to reproduce the error on the both cluster servers.
For this reason we have the Server-Console-Logs and the sapinst-Folder for the PL28-Upgrade attached. The State-Controller and Dispatcher started without problems.
Important point to the end:
Our J2EE server (State, Dispatcher & Application-Node-> Server) is started and stopped over NT services.
With the Upgrade of the portal to PL 28 a DOS window opened ! - This window contained, that the Upgrade program tried to start the go.bat of the dispatcher.
- Could this be the error?
- Must we configure the system in such a way that the J2EE services is not started over NT services ? Must it started over the standard variant -> go.bat.
I hope anybody could help me ?
Ralf

ok ! - I think that we will then install in this way.
Another question:
A colleague said to me that the problem could be, because in the go.bat the parameter: Xms%MEMORY% would be
missing? In his environment this parameter is set !
Here the go.bat from me dispatcher with the problems:
@echo off
set PATH=..\..\os_libs;%PATH%
cd /D "F:\usr\sap\SP2_\j2ee\j2ee_00\cluster\dispatcher"
if not "%JAVA_HOME%"=="" (
goto EDDIF11
set JAVA_HOME=C:\jdk1.3.1
:EDDIF11
set MEMORY=128M
"%JAVA_HOME%\bin\java" -classpath ".;.\system-lib\boot.jar" %1 %2 %3 %4 %5 %6 %7 %8 %9 -Xmx%MEMORY% -Dredirect.input=true -Dmemory.manager=%MEMORY% -Djava.security.policy=.\java.policy com.inqmy.boot.Start
We start the productice System over NT-Service, but i think, that in the upgrade-process the system tries to start the go.bat and not the NT-Service. Could this be me problem ?
Here are the go.bat from my colleague:
@echo off
set PATH=..\..\os_libs;%PATH%
cd /D "F:\usr\sap\CON1\j2ee\j2ee_00\cluster\dispatcher"
if not "%JAVA_HOME%"=="" (
goto EDDIF11
set JAVA_HOME=C:\jdk1.3.1
:EDDIF11
set MEMORY=128M
set MEMORY_QUARTER=128M
"%JAVA_HOME%\bin\java" -classpath ".;.\system-lib\boot.jar" %1 %2 %3 %4 %5 %6 %7 %8 %9 -Xmx%MEMORY% -Xms%MEMORY% -Dredirect.input=true -Dmemory.manager=%MEMORY% -Djava.security.policy=.\java.policy com.inqmy.boot.Start
Ralf

Upgrade EP6 from SP9 to SP11

Hello,
I've installed EP6 SR1 (SP9). Now I am interested to install SP11.
Can I install SP11 right away ? or do I need to install SP10 & then SP11 ?
Please Advice,
Dimitry

Install it direct - there are some patches to SP11 you might want to do them also.

Portal upgrade EP6.0-EP7.0

hi,
We are currently having EP6.0 and we are planning to go for EP7.0.
Kindly let me know what are the prerequisites for that and how to go about.
Thanks,
kris

Gopi,
Please check this
upgrade NW2004 to NW 2004s
Also, refer to this
Upgrading from EP60 to EP70
Hope that helps.
Cheers,
Sandeep Tudumu

Upgrade from SP10 to SP17

Hi Experts,
We are on Netweaver 2004s SP10 portal, now wants to upgrade to SP17.
My question is can directly go from SP10 to SP17 or do we need any patch upgrade in between?
Thanks in advance.
Regards
Sunil

Patch w/ SP17 directly. No need for in-between patches. SP11-16 patches should be included in SP17.
Could take a while to patch though.
goodluck.
Regards,
Jan

EP6 SP9 - 'Personalize Portal' link does not work

Hi,
We've just installed EP6 SR1 SP9 and applied patch 4.
The portal seems to work fine, except for one thing:
The 'Personalize' link on the top right, above the TLN, doesn't seem to work.
When clicking the link, nothing happens. No popup, no error message, nada
Has anyone seen this before, or can give me a guidance where to look for?
With kind regards,
Robin van het Hof
Message was edited by: Robin van het Hof
- Marked topic as a question -

Hi Robin,
i'm afraid you did not understood Hassan right, so I'd like to clarify thinks for you. By default the super_admin_role does not provide an user (i.e. J2EE Administrator) to personalize the portal. In order to do this a user must posses a role which contains the workset "Portal Personalization", (which is not the case for the super_admin_role).
So, you have the option to assign the role "eu_role" to the user J2EE Adminstrator (or to any other user which would like to personalize the portal). The other option is to edit the users role (i.e. super_admin_role) and add the workset com.sap.portal.portal_personalization.
Just try those two options on your portal.
If you do not need all the iviews from eu_role and do not want to change the standard super_admin_role, i would recomend to create a new role which includes only the workset mentioned and assign it to every user who wants to personalize the portal.
Hope this helps,
Robert

Migration Guide from EP6 SP13 to Portal Netweaver EP 7.0 EHP1

Hi Gurus
I am working on a portal migration project EP6 SP 13 (WAS 640) to Portal Netweaver EP 7.0 EHP1 .
Here I am lokking for a migration guide or a document based on our project . I check on SMP and sdn but not able to find the suitable guide
All I got is an how to guide "How Tou2026 Migrate from SAP Enterprise Portal 6.0 SP2 to SAP NetWeaver '04"
Please guide me from where I will get relevant document.
regards
Jaswant

Hello,
Please check out http://service.sap.com/instguides --> SAP NetWeaver --> SAP NetWeaver 7.0 --> Upgrade. On the next screen, open the link "Upgrade Documentation - SAP NetWeaver 7.0 incl. EHP1" under "2 - Upgrade - SAP NetWeaver Systems".
On the next screen, follow the link "SAP NetWeaver 7.0 Including EHP1 - Java", and select the guide you need.
Kind regards, Wilbert

Best Practice for Downgrading J2EE/Portal Patch Version

Hello all,
We're trying to determine the best path to follow and would appreciate any advice. We have an existing Portal implementation with ESS/MSS which has been live for almost a year. It is on NW2004s (i.e., 7.0) and in production it is on ERP stack 8 (ESS stack 8, J2EE stack 11), which matches up with the backend ECC system for the most part. The Portal is under NWDI control, as we have customized the ESS and MSS web dynpros a little bit. So far so good.
However, we were starting a round of implementing SP stacks this summer, and after getting started with the DEV portal, getting it up to ESS stack 12, J2EE stack 14, the organization decided, due to workload and time constraints, to defer the SP stack application for six months. So, the new sp stack is only in the DEV portal, it's not in QA or PRD, and it's not on the DEV ECC system. We have learned, and experienced for ourselves, that there are certain functions which do not work, or do not work well, in MSS when the MSS Portal components are at a higher sp level than the ECC HR components, and we don't really want to have the DEV Portal out of sync with its backend, as well as QA and PRD, for six months. This is especially true as when we revisit the sp's in six months, it will no doubt be to a higher stack level, and this out-of-sync condition will just complicate things then.
So, we'd like to roll the DEV portal back to its prior sp level. The question is, how? There doesn't appear to be a way to do it with JSPM. Should we use SDM with the "update deployed SDAs/SCAs that have any version" option to overwrite the newer components with the older one? Or should we use SDM to undeploy what's on there now and just redeploy the older components with JSPM? With either of these options, what complications will we encounter with NWDI? Or should we try to restore the DEV portal from backup?
And if we do restore from backup... well, just what's involved in that? I'm fully conversant with restoring ABAP systems (we are on SQL Server 2005 by the way), even migrating ABAP systems to new servers, changing SIDs, refreshing QA systems from PRD, all of that. But I haven't worked as long with the J2EE engine, and I'm aware that much of the 'system' is not actually in the database, but in the filesystem. So, which folders would I need to restore along with the database? What considerations with NWDI do I need to be cognizant of? I haven't found any guides or recommendations on this approach so far, so I'm hoping for some direction here.
Best regards, and thanks in advance,
Matt

Hello Matt,
First let me correct you on the statement that most part of the J2EE is on the file system. That is no true. Most part of J2EE Engine is kept in the DB and on the file system. Everything under /j2ee/cluster/dispatcher and /j2ee/cluster/serverX is in the database and if you delete these folders they will be fully restored on startup of the server.
You can not undeploy the core components of the J2EE Engine and then redeploy them. If you do that significant part of the information generated during the installation will be lost and the J2EE Engine will be almost irreversibly broken.
Forced redeployment of the older version works for single applications, but on a grand scale I donu2019t think it will work. There are too many dependencies that will be broken and the deployments of many components will fail.
That leaves us with two options.
1. Restore from backup. Please refer to the following link for information:
http://help.sap.com/saphelp_nw04/helpdata/en/4b/d8f23ea4b42e5ae10000000a114084/frameset.htm
2. System copy from some of the other systems.
There are different kinds of system copy. Please start from the following link for basic information about system copy:
http://help.sap.com/saphelp_nw70/helpdata/en/a2/2f0c173a5e43d19585724239ff4de7/frameset.htm
For more comprehensive information see SAP Service Marketplace at http://service.sap.com/systemcopy
Regards,
Ventsi Tsachev
Technology Development Support (J2EE Engine)
SAP Labs, Palo Alto, Ca (USA)

Upgrading EP6 SP10(j2ee,portal,KMC) to SP11

Similar Messages

Maybe you are looking for