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

Question

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 ?</b> 
Ralf

Answer 1

ok ! - I think that we will then install in this way.
<b>Another question:</b>
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 !
<u>Here the go.bat from me dispatcher with the problems:</u>
<b>@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</b>
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 ?
<b><u>Here are the go.bat from my colleague:</u></b>
<b>@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</b>
Ralf