Patching Ecom Portal

HI Experts,
We have the Enterprise Portal system 6.0 at SP 15. We have
deployed ISA 4.0 (Internet sales application) over EP 6.0 system. ISA
is linked to CRM system.
The present SP level of the respective systems are :
SAP WAS - 6.4 SP 15
Enterprise Portal - 6 SP 15
KMC - 6.4 SP 15
TREX - 6 6.1SP 15
IPC - 4 SP 06
ISA - 4.0 SP 9
BBPCRM - 4.0 SP 9
We have planned to patch only EP system from 6.0 SP 15 to a higher
version. Is it possible to patch a single system in a integrated
environment like explained above..?
Whether there are any dependencies between the Portal SP levels and
other systems like IPC, ISA BBPCRM,TREX...etc.?
Thanks in advince.
Regards,
Murugan Arumugam.

EP upgrade is mostly independent of BBPCRM, ISA and related components. If you are using CRM business packages and have custom modified then you may have some dependency there. But this is rare.
I would always check Product Availability Matrix (/pam) in SAP Service Marketplace.
Easwar Ram
http://www.parxlns.com

Similar Messages

How to implement a patch in portal

I have been given the task for making ep7.0 with sp 7 compatible with the IE version 7.0 ,for that i have downloaded a patch which will make ep 7 with sp 7 compatible but now the issue is what all steps you want me to do follow so that we can upload teh patch in portal .plz help me with this as iam new to EP.

Hi Priyanka,
The simplest way to apply a patch is to do it by JSPM.
U have to copy all pacth files in the JSPM inbox and start JSPM.
Follow ne patch guide u have to start the deployment.
If u face a pblm wid a single file try deploying it with SDM.
I hope it helps.
Regards,
Sumit

LDAP loadbalancing EP 6.0 SP2 / Patch 35 portal based on J2EE 6.20

Currently our EP is using LDAP authentication against a DNS alias which utilizes round-robin resolution to the domain controllers in our environment. We occasionally have an issue where a windows admin, or DNS admin takes a server down for maintenance. It seems that upon startup each j2ee server process will attach to an IP. If the server becomes unavailable the authentication requests will fail dropping entries in the ume logs.
Our intent is to move toward a high-availability setup detailed in:
http://help.sap.com/saphelp_ep60sp2/helpdata/en/89/ed92be4e414f86ab8ac040010d5396/frameset.htm pointing primary and alternate to independent pools of domain controllers through two additional alias's.
Does anyone know a method of determining which IP address a j2ee server process has attached to? If we could determine the IP's it would greatly simplify our testing efforts.
Thanks in advance,
Michael T. McHugh

Thank you for your response.
In the cluster administration, the Server IP column reflects the IP of the OS instance on which the server runs. The question is relative to which LDAP server each server process grabs from a round-robin type resolution.
Any other thoughts?
MMcHugh

New Patch Release 3.0.9.8.1 for Oracle9iAS Portal 3.0.9.8.0

The patch can be found on metalink. The patch number is: 1841088.
Oracle9iAS Portal 3.0.9 Patch Release Notes
July 2001
Contents
For the latest release note updates, visit the Oracle Technology Network
and click the Documentation tab.
Installation and Setup Patch Contents
Installation (Windows) Bugs fixed by this patch
Installation (UNIX)
Post-installation steps
Installation (Windows)
You can only apply this patch to Release 3.0.9 of Oracle Portal
(Oracle9iAS v1.0.2.2). To apply this patch, do the following:
From the command line prompt, execute the patch command according to
the following syntax:
patch.cmd [-m patch_mode] [-s schema_name]
[-p schema_password] [-u sys_password]
-c connect_string [-l log_file_name]
-m patch_mode is the patch mode. Valid values are
loginserver or portalschema. Default value is
portalschema.
-s schema_name is the name of the Portal schema that you
want to patch. Default value is PORTAL30.
-p schema_password is the password of the schema you want
to patch. Default value is PORTAL30.
-u sys_password is the SYS Password. Default value is
CHANGE_ON_INSTALL.
-c connect_string is the TNS connect string information.
-l log_file_name is the name of the log file. Default value
is patch.log.
Examples:
To patch Login Server Only:
patch -m loginserver -s portal30_sso -p portal30_sso -u
change_after_install -c mydatabase -l mypatch.log
To patch Portal Schema Only
patch -m portalschema -s portal30 -p portal30 -u
change_after_install -c mydatabase -l mypatch.log
To patch both Portal Schema and Login Server
patch -m loginserver -s portal30_sso -p portal30_sso -u
change_after_install -c mydatabase -l mypatch.log
patch -m portalschema -s portal30 -p portal30 -u
change_after_install -c mydatabase -l mypatch.log
To complete the application of the patch, follow the instructions in
Post-installation steps.
Installation (UNIX)
You can only apply this patch to Release 3.0.9 of Oracle Portal
(Oracle9iAS v1.0.2.2). To apply this patch, do the following:
From the command line prompt, execute the patch command according to
the following syntax:
patch.csh [-m <patch_mode>] [<-l log_file_name>]
-m <patch_mode> is is the patch mode. Valid values are
loginserver, portalschema, or both. Default value is both.
-l log_file_name is the name of the log file. Default value
is patch.log.
Examples:
To patch Login Server only
patch.csh -m loginserver -l mypatch.log
To patch Portal Schema only
patch.csh -m portalschema -l mypatch.log
To patch both Portal Schema and Login Server
patch.csh -m both -l mypatch.log
patch.csh -l mypatch.log
To patch both Portal Schema and Login Server with default
log file
patch.csh -m both
patch.csh
To complete the application of the patch, follow the instructions in
Post-installation steps.
Post-installation steps
The bug fixes for bug numbers 1817550, 1830898, 1832632, 1840420, 1664594,
1810741, 1807325, and 1819442 are not installed via the patch script
because you must shut down your Web server prior to applying them. The
sections that follow describe how to apply these fixes.
JPDK.ZIP
On the Web server where the provider is running:
Unzip the contents of jpdk.zip into a directory (e.g., JPDK_30901).
Shut down your Web server.
Change your zone.properties file to include <extract
dir>/jpdk/lib/provider.jar in the wrapper.classpath.
If you are using Java Portal Development Kit (JPDK) samples from a
previous release of the JPDK, update your samples using those
included in the zip file. Refer to <extract dir>/installing.jpdk.html
for more details.
Restart your Web server.
Note: Refer to <extract dir>/release.notes.html for a list of changes made
in this release.
wwpage.jar
On the middle tier where the Portal listener is running:
Shut down your Web server.
Create a backup of your current wwpage.jar file.
Replace /$IAS_HOME/Apac he/Jserv/servlets/wwpage.jar with the new
wwpage.jar provided in this patch.
Restart your Web server.
New Parameters
The Parallel Page Engine now accepts two new parameters in the
zone.properties file:
minStall is the minimum stall value allowed for a contentfetcher
before it assumes there is a problem and times out. This value
defaults to 120 seconds. It was added to help upgrades from
308, which had a normal stall value of 40 seconds. The meaning
of stall has changed slightly, raising the need for a minimum
value.
minTimeout is the minimum timeout that may be sent by a
portlet. At times portlets send very small values, like 1
second. This almost always fails, and pages are rendered
incomplete. The minTimeout defaults to 5 seconds, but may be
set otherwise if this is not large enough. The minTimeout is
different from the requestTime. The requestTime is used when no
timeout value is sent for a portlet.
opca.jar
Back up your current opca.jar file, which is found in the
<IAS_HOME>/assistants/opca/ directory.
Copy the opca.jar file provided with this patch to the
<IAS_HOME>/assistants/opca/ directory.
To install the Portal repository, run the launch.bat (on NT) or
launch.sh (on Solaris) to invoke the Portal Configuration Assistant.
Follow the steps in the configuration assistant.
Oracle Portal Cache
Go to Oracle MetaLink and retrieve the patch for bug number 1817550.
Stop your Oracle HTTP Server.
Apply the patch you downloaded from Oracle MetaLink as per the
instructions in the README.txt file.
Login to your system as root and delete all cache files and
subdirectories under the directory
<IAS_HOME>/Apache/modplsql/cache/plsql. Make sure the directory
<IAS_HOME>/Apache/modplsql/cache/plsql is empty.
Start your Oracle HTTP Server.
Bugs fixed by this patch
This patch fixes the following known bugs:
Bug Number Bug Subject and Description
1817550 ON SOLARIS, WHEN RUNNING ON PORT 80, ORACLE PORTAL CACHE
GETS DISABLED
Due to a bug in the Oracle HTTP Server powered by Apache,
the Oracle Portal cache gets disabled when it is running
on port 80.
1819194 EXCEPTION THROWN IF A USER'S PASSWORD HAS AN AMPERSAND.
Special characters such as an ampersand (&) in passwords
or any text node that is sent to the Web providers were
causing errors.
1664594 XML TAGS IN THE JAVA STACK - CAUSING PARSER TO CRASH.
(Duplicate Bug: 1788506) Control characters were not
being properly escaped appropriately and causing errors
in the database SOAP parser.
1823166 PORTLET SECURITY IS RAISING AN ERROR FOR NON-ADMIN USERS
W/ ANY_PORTLET MANAGE.
1782458 NOT ABLE TO CREATE MASTER DETAIL REPORT.
1802055 308-309 UPGR: CLICKING ON "REFRESH ERROR" IN PORTLET
REPOSITORY GIVES ERROR.
1815257 UPGRADE: 306-309:308-309:SEARCH PEOPLE PORTLET: SHOWS
ERROR.
1744458 REPORTS FROM SQL: VALID SQL:GIVES AMBIGUOUS COLUMN ERROR
FOR JOINED TABLES.
1783257 REPORT COMPONENT AS PORTAL IN PAGE CAN'T BE ASSOCIATED
WITH TAB.
1801961 UPGRADE:307-309:ADD PORTLETS REGION IS SHOWING UP VERY
SLOW.
1807325 FETCHERS TIMEOUTS, AND PORTLET PRODUCED AN ERROR.
This bug pertains to a synchronization issue in the 3.0.9
fetching of portlet content. The Document could not be
contacted error is randomly raised. However, it may be
that other problems are causing this error. This bug only
refers to the synchronization issue in which the Parallel
Page Engine causes the problem.
1810741 PROVIDER USER DOES NOT DETECT PUBLIC USER CORRECTLY.
Previously, the JPDK did not correctly detect if the
current user was logged in or accessing the portal using
a public session. This bug also affected providers
registered with a login frequency of PUBLIC. Failure to
detect the logged in state of the user correctly caused
ProviderUser.isPublicUser() to return an incorrect value
when a provider written using JPDK release 3.0.9 was used
with earlier releases of Oracle9iAS Portal.
The most common symptom of thi s error is the Customize
link being shown to public users when the provider
definition specified that it should be hidden. A new
username parameter has been added so the JPDK can
correctly detect the logged in state of users while
maintaining backwards compatibility with older versions
of Oracle9iAS Portal.
1811275 GROUP NAME IS REPEATED IN LIST OF GROUPS IN SPANISH,
FRENCH ETC.
1812018 PERSPECTIVES ARE REMOVED FROM ITEMS IF THEY ARE EDITED.
1815037 OPCA HANGS AT 90%
Oracle Portal Configuration Assistant hangs at 90% during
the Oracle9iAS 1.0.2.2 installation.
1819442 PROVIDE MINTIMEOUT FOR PPE TO OVERRIDE SMALLEST
TIMEOUT(S).
Previously, there were no minimum values for timeouts.
The fix for this bug adds some minimum values for
timeouts and changes the defaults such that the Parallel
Page Engine works better without any configuration by the
user. These changes help to prevent getting the Portlet
could not be contacted error message.
1830898 SSOUNLCK.SQL DOESN'T UNLOCK SSO USER ACCOUNT.
1832632 BITMAP INDEXES IN EXPORT-IMPORT FAIL TO INSTALL ON ORACLE
8I STANDARD.
1833509 SITE MANAGER BUGS FOR CATEGORY, ITEMTYPE, FOLDERTYPE, AND
PERSPECTIVE.
This bug covers the following:
Showing the category popup correctly when you hide
categories.
Same Banner appears more than once while rendering.
All Item Types show up when you create Custom Item
Types.
All Folder Types show up when you create Custom
Folder Types.
No data found error occurs in perspective list of
content area manager.
All item types get hidden when you hide different
item types in different content areas.
Categories are not displayed appropriately when you
go into content areas of default languages other
than "us."
Minor issues with Bulk action.
1840420 CUSTOM WRITTEN EXTERNAL AUTH MODULE NEED TO BE UPDATED
AFTER 3.0.9 UPGRADE SSOXOID.PKB DOESN'T LOAD.
External authentication modules that were written before
3.0.9 need to be updated after upgrading to 3.0.9.
ssoauthx.pks is updated in 3.0.9 and contains additional
routines that need to be implemented.
null

Richard,
I have just applied patch to upgrade from Portal 3.0.9 to 3.0.9.8.1 (Patch applied to loginserver and portal schema) and the External Applications that were previously set up have gone from the portlet.
Does this relate to your note at the bottom:
"Minor issues with Bulk action. 1840420 CUSTOM WRITTEN EXTERNAL AUTH MODULE NEED TO BE UPDATED AFTER 3.0.9 UPGRADE SSOXOID.PKB DOESN'T LOAD.
External authentication modules that were written before 3.0.9 need to be updated after upgrading to 3.0.9. ssoauthx.pks is updated in 3.0.9 and contains additional routines that need to be implemented." ??
If I go to the "Login Server Administration" portlet and select the link "Administer External Applications" I get a list of 5 External Applications that have previously been set up.
If I go back to the Home Page and select "customize" on the "External Applications" portlet I get the message "Your Login Server administrator has not registered any external applications".
Does that mean I should just run 'ssoauthx.pks' & 'ssoxoid.pkb' or do I need to do something else ??
Thanks
Simo

9.0.2.6 Portal Repository Upgrade Patch problems.

We got some problem with Portal when tryed to apply
9.0.2.6 Upgrade. Could anybody give advice on this issue:
Initial configuration:
Solaris8, Portal 9.0.2.2.14, Oracle 9iAS R2 v.9.0.2.0, RDBMS 9.0.1.3. The infrastructure and midtier work on different SPARC-servers.
Accordingly upgrade procedure we succesfully applied:
a) Infrastructure: 9.0.1.4 Patchset for Oracle RDBMS server, 9.0.2.2 Patchset for OID, Oracle 9iAS SSO-server
migration to 9.0.2.5, 9.0.2.2 Patchset for 9iAS Core.
b) 9.0.1.4 Patchset for Oracle RDBMS server, 9.0.2.2 Patchset for OID, Oracle 9iAS SSO-server migration to 9.0.2.5, 9.0.2.2 Patchset for 9iAS Core, Portal 9.0.2.6
patch.
After this we needed to make just one last step:
Portal 9.0.2.6 Repository Upgrade Patch (2981297) for
changing Portal's repository schemes. It worked but
like a result we got the next errors after patch upgrade
was done:
a) "The following invalid non-Portal objects exist in the Portal Schema: INDEX ABC (the name of portal object), PACKAGE BODY WWMON_REP_REPOSITORY, PACKAGE BODY WWMON_REP_REPOSIT_DTL, PLS-00103: Encountered the symbol "," when expecting one of the following: (-+case mod not null <an identifier>,...) The symbol "null" was substituted for "," to continue.)" See upgtmp/nonportal.log
b) "ERROR: 1 invalid objects remain; ERROR: Failed while updating the new portlet IDS..."
c) "ERROR: ORA-01407: cannot update ("PORTAL"."WWSBR_URL$"."URL") to NULL.
d) Two package body of packages at PORTAL scheme became invalid: WWMON_REP_REPOSITORY, WWMON_REP_REPOSIT_DTL. About 20 package body of packages at PORTAL_DEMO became invalid (It seems like initial portlet ID's disappeared
and except of pportlet_id there is nothing:
Example:
inital statement at body:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
PORTAL.wwpro_api_invalidation.invalidate_cache(
p_provider_id => p_provider_id,
p_portletid => 1065753336,
p_instance_id => p_reference_path,
p_subscriber_id => PORTAL.wwctx_api.get_subscriber_id ,
p_user => PORTAL.wwctx_api.get_user);
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
after upgrade repository patch:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
PORTAL.wwpro_api_invalidation.invalidate_cache(
p_provider_id => p_provider_id,
p_portletid => ,
p_instance_id => p_reference_path,
p_subscriber_id => PORTAL.wwctx_api.get_subscriber_id ,
p_user => PORTAL.wwctx_api.get_user);
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Like a result after 9.0.2.6 Portal Repository Upgrade Patch application we lost the possibility to edit user's
profiles at Portal and other nesessary features. It seems
like some portlet ID's just dissapeared from Portal scheme. Could anybody had the same problem with Portal Upgrade 9.0.2.6? Quite possible that we missed some important element at during upgrade but ,really, we didn't wait so unlucky result. Advice something, please...
Regards. Igor.

Igor,
Since you've encountered undocumented errors, your repository upgrade has failed. You'll want to leave the repository as is for troublshooting, if at all possible, and log a TAR with support if you haven't already. They'll ask you to upload your upgrade log file and your upgrade tmp directory.
Regards

Unable to patch portal with stack 15?

Hi,
We got BI system with portal running on windows 2003 server.
I am trying to patch up portal/jave stack with stack 15.
After JSPM successfully logged on with SDM and it shows target sp 15 for all components.
But after i click deployment jspm is giving the following error:
"<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[E:\usr\sap\RAB\DVEBMGS20\j2ee\JSPM\log\log_2008_03_10_06_25_04\OperateSDM_01.LOG]/>
<!PATTERN[OperateSDM_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
Apr 10, 2008 6:27:30 AM Info:
Apr 10, 2008 6:27:30 AM Info: ==========================================
Apr 10, 2008 6:27:30 AM Info: = Starting to execute command 'ping' =
Apr 10, 2008 6:27:30 AM Info: ==========================================
Apr 10, 2008 6:27:30 AM Info: Sending "ping" command to the SDM server...
Apr 10, 2008 6:27:30 AM Error: SDM server is running, but authentication failed because of wrong password.
Apr 10, 2008 6:27:30 AM Error: Processing error. Return code: 104
If i click sdm gui tool i can logon with the master password successfully.
I don't understan why the same password not working with in JSPM.
Appreciate your help.
Thx
Rama

Hi Rama,
 Try the following steps of SAP Note 701654. you have to change the property admin/password/<SID> as described below. You have to use the working password related to user id - admin/user/<SID>...
 1. Start the Config Tool.
 (Execute <SAPj2eeEngine_install_dir> \configtool\configtool.bat.)
 2. Select the secure store node.
 The configuration for the secure storage in the file system appears.
 3. Select the admin/password/<SID> entry.
 4. Enter the administrator user's new password in the "Value" field and choose "Add".
 5. Choose "File" --> "Apply" to save the data.
 Note: Contrary to the message that appears, you do not need to restart the server or cluster for this change to take effect.
 6. Finally restart SDM server.
Consider Reward points, if helpful..
Regards,
Uday.

Portal patch 1841088

Hi, have tried applying patch on portal 309, solaris 8, 9ias 1022 to get rid of Portlet could not be contacted errors (downloaded on 06/09/01). Applied OK through OUI.
However, looking at release notes, trying to do post-installation tasks, the files jpdk.zip, wwpage.jar, opca.jar do not exist under unzipped patch area!
Where are they???
I am still receiving the Portlet error after applying only the OUI part of the patch.
cheers,
John.

I found that this patch only works for a fresh install of 9ias
1.0.2.2 with portal 3.0.9.
From upgrades of previous version of 9ias/portal it didn't make
any difference, in fact it made my "Error: The Portlet could not
be contacted" problems even worse.

Error when installing 9.0.1.4.0 patch set for the Oracle Database Server.

Hi to all.
Currently, i am trying to install patches for portal server.
The server OS is Sun Solaris 8.
We are using Oracle9iAS.
Now, we are installing 9.0.1.4.0 patch set for the Oracle Database Server.
We managed to install the patch, but have problem with the Post Install Action.
We managed to run
-ALTER SYSTEM ENABLE RESTRICTED SESSION;
-@rdbms/admin/catpatch.sql
-ALTER SYSTEM DISABLE RESTRICTED SESSION;
-CONNECT / AS SYSDBA
-update obj$ set status=5 where type#=29 and owner#!=0;
-commit;
But, when we come to the next command, which is to shutdown, it gives us like
this..
SQL> update obj$ set status=5 where type#=29 and owner#!=0;
1402 rows updated.
SQL> commit;
Commit complete.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORA-00604: error occurred at recursive SQL level 1
ORA-01219: database not open: queries allowed on fixed tables/views only
We tried to startup the database..it gives us this error..
SQL> startup
ORA-01081: cannot start already-running ORACLE - shut it down first
So, we tried to shutdown again..
SQL> shutdown immediate
ORA-01089: immediate shutdown in progress - no operations are permitted
I been informed that this is maybe a Database problem related. Any ideas?
Best Wishes,
Rushdan Md Saad.

Patchsets could be obtained (only) from http://metalink.oracle.com
You need to have valid CSI for access.
P.S: Sorry Werner, I didn't see you post.
Message was edited by:
Ivan Kartik

Portal Runtime Error in contentCatalogTree after applying SP11

HI,
I am getting a POrtal Runtime Error for the contentCatalogTree iView after I applied SP11. It was working fine before I patch the portal. Has anyone got a solution to this?
Here is the error stack:
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
iView not found: pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.portal_content/com.sap.portal.contentCatalogTree.
Exception id: 09:49_11/04/05_0022_6990050
See the details for the exception ID in the log file
And the log file says:
#1.5#001279D06329005D0000000700000F280003F423583156CF#1112857570796#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#178####856f12c0a73311d9b39c001279d06329#SAPEngine_Application_Thread[impl:3]_23##0#0#Error#1#/System/Server#Java###Exception ID:03:06_07/04/05_0005_6990050
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: iView not found: pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.portal_content/com.sap.portal.contentCatalogTree
     at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1937)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:230)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
     at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:435)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     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:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Anyone out there can help. Thanks in advance.

Hi all,
Apprantly it seems that the sequence to applying the SP Stacks plays a part. I reverted back to SP9 then went on to SP10, SP10 patch2 and then SP11 and it appears fine now.
Cheers

Having problem to install Oracle Portal Forms Reports and Discoverer 11g on Windows Server 2008 64 bit

Dear All Precious Friends,
I am having problem while installing Oracle Portal Forms Reports and Discoverer 11g on Windows Server 2008 64 bit,
I have already installed Oracle Database 11g Release 2 -------
----Then i configured JAVA Access bridge
--------then installed and configured Required Schema using Repository Creation Utility of same version of Database 11g,
-----------then installed Oracle Business Intelligence 11g version 11.1.1.6.0 which includes Web logic..............I am feeling that i did right at this point...........
..............also feeling comfortable after install Oracle Identity and Access Management 11g ..................
-----------------but don't know how to configure OID to install Oracle Portal Forms Reports and Discoverer 11g...............
Please help my Oracle Friends
Your early help will be highly appreciated.
thanks and regards
Hassan

You said, "...+I would like to install Release 2(11.1.1.2.0)+ ...". Be careful. 11.1.1.2.0 is not Release 2. The version for Rel 2 is 11.1.2.0, notice that there is one less "1". Also, there is no way to patch from Release 1 to Release 2.
In EDelivery, this is what you should find if you search on "Oracle Fusion Middleware" for "Microsoft Windows x64 (64-bit)":
First look for this link then drill into it:
Oracle Fusion Middleware 11g Media Pack for Microsoft Windows x64 (64-bit)
In this section you will find the following:
This is the full product installation of FMw 11 Release 2 (Forms & Reports)
Oracle Forms and Reports 11g R2 (11.1.2.0.0) for Microsoft Windows x64 (64-bit) V28761-01
This is the full product installation of FMw 11 Release 1 (includes Portal, Forms, Reports, and Disco)
Oracle Portal, Forms, Reports and Discoverer 11g (11.1.1.2.0) for Microsoft Windows x86 (64-bit) (Part 1 of 4) V18785-01
Oracle Portal, Forms, Reports and Discoverer 11g (11.1.1.2.0) for Microsoft Windows x86 (64-bit) (Part 2 of 4)
Oracle Portal, Forms, Reports and Discoverer 11g (11.1.1.2.0) for Microsoft Windows x86 (64-bit) (Part 3 of 4)
Oracle Portal, Forms, Reports and Discoverer 11g (11.1.1.2.0) for Microsoft Windows x86 (64-bit) (Part 4 of 4)
This is the FMw 11 Release 1 patch set that will bring the above 11.1.1.2.0 installation to 11.1.1.6. This is NOT a full product installation - just a patch
Oracle Portal, Forms, Reports and Discoverer 11g Patch Set 5 (11.1.1.6.0) for Microsoft Windows x86 (64-bit) V29850-01
There are no patch sets for Release 2 as of yet.

How can I upgrade to 10g Portal?

Hi All,
I seem to have made a rod for my back...
We have a portal instance (Version 9.0.2.3) that is running on old obsolete hardware. It is connected to a portal repository that is running in a seperate RAC enabled database (Customer database as Oracle call it).
We wish to transfer to 10g Release 2 and have therfore installed a brand new 10g Infrastructure & Middle Tier. (Portal Version 10.1.2.0.2 Build139)
I have also cloned our RAC Customer database to another server for test purposes.
Customer databases are running on Windows, Applications servers are Linux.
I am thinking that I need to upgrade the Customer portal repository to 9.0.4 and then to 10.1.2.0.2. (Can I do this without it being connected to the mid tier?) and then configure the middle tier to connect to the customer database.
Sorry but the more Oracle documentation I read the more confused I get. Each version seems to say something different.
Thanks
Steve

I already looked at this one. There is no Middle Tier home on the database host. It's just a vanilla database node. It has an Oracle 9.2 home and a Forms 6 Home.
The precheck logfile lists the correct Oracle_home as D:\Oracle\ora92
Environment variables:
===========================================================
ALLUSERSPROFILE: C:\Documents and Settings\All Users
APPDATA: C:\Documents and Settings\XXX\Application Data
CLIENTNAME: Console
COMMONPROGRAMFILES: C:\Program Files\Common Files
COMPUTERNAME: MIS6401
COMSPEC: C:\WINDOWS\system32\cmd.exe
CURRENT_DIR: D:\Patch\log
CYGWIN: tty
FP_NO_HOST_CHECK: NO
HOMEDRIVE: C:
HOMEPATH: \Documents and Settings\XXX
HOMESHARE: \\MIS\XXX
JSERV: D:\oracle\ora92/Apache/Jserv/conf
LIB: C:\Program Files\Microsoft.NET\OracleClient.Net\
LOGONSERVER: \\CDC2
MRUA_JAR: ..\..\..\jlib\mrua.jar
NUMBER_OF_PROCESSORS: 1
OPCA_JAR: ..\..\..\assistants\opca\jlib\opca.jar
ORACLE_HOME: D:\Oracle\Ora92
ORACLE_SID: wh
OS: Windows_NT
PATH: D:\Oracle\Ora92/bin;../../../perl/5.6.1/bin/MSWin32-x86;D:\oraNT\bin;D:\oracle\ora92\jre\1.4.2\bin\client;D:\oracle\ora92\jre\1.4.2\bin;D:\Borland\Delphi7\Bin;D:\Borland\Delphi7\Projects\Bpl\;D:\Programs\Windows Resource Kits\Tools\;D:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;D:\Programs\OpenSSH\bin;D:\oraNT\jdk\bin
PATHEXT: .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PERL5LIB: ../../../perl/site/5.6.1/lib;../../../perl/5.6.1/lib
PROCESSOR_ARCHITECTURE: x86
PROCESSOR_IDENTIFIER: x86 Family 15 Model 15 Stepping 0, AuthenticAMD
PROCESSOR_LEVEL: 15
PROCESSOR_REVISION: 0f00
PROGRAMFILES: C:\Program Files
PROMPT: $P$G
PWD: D:/Patch/PortalCD/portal/admin/plsql
REPCA_HOME: ..\..\..
REPCA_JAVA: ..\..\..\jdk\bin\java
SESSIONNAME: Console
SQLPATH: .;owa;D:\Patch\log\prechktmp/gen;upg/frwk;sql;wwc
SYSTEMDRIVE: C:
SYSTEMROOT: C:\WINDOWS
TEMP: C:\DOCUME~1\XXX\LOCALS~1\Temp
TMP: C:\DOCUME~1\XXX\LOCALS~1\Temp
UPGARGS: -precheck -l D:\Patch\log\upgrade.log -t D:\Patch\log\tmp -oh D:\Oracle\Ora92
USERDNSDOMAIN: XXX
USERDOMAIN: XXX
USERNAME: XXX
USERPROFILE: C:\Documents and Settings\XXX
WINDIR: C:\WINDOWS
WORKING_DIR: d:\Patch\PortalCD\portal\admin\plsql\
WV_GATEWAY_CFG: D:\oracle\ora92\Apache\modplsql\cfg\wdbsvr.app
Some of the entries for MRUA_JAR & OPCA_JAR look a bit odd.
Maybe there should be a trailing slash on the ORACLE_HOME? Clutching at straws I know, but I've seen it happen before.
No wasn't that. Didn't want unix style slashes either.
It definately looks like the problem in Note 334828.1 but setting the correct oracle_home is not fixing it.

Portal Content - Business Packages for CRM 7.0 and IC Webclient

Hi all

We are looking at CRM 7.0 and SAP Netweaver Portal 7.0 integration. 
I've noticed that the Business Package (BP) for CRM 7.0 contains very limited business roles for: 
Channel ManagerChannel Manager 
Partner Manager 
Channel Manager (Telecommunications) 
Partner Manager (Telecommunications) 
Customer 
Digital Asset Management 
Incentives and Commissions 
only.

In the past, there the BP for CRM 5.0 contains a lot more roles including customer service representatives and managers. Given that the standard business role export (from CRM 7.0) and import (EP 7.0) does not work for IC Web client business roles, is there a standard way for functionality delivered in IC Webclient like Customer Service to be integrated into EP 7.0?

Otherwise, if we were to configure each BSP page individually for IC Webclient, will there be functions that do not work? eg: alerts, manager realtime view of CSR activities, call tracking, telephony integration etc..

Thanks!

There are two approaches (that I'm aware of):
- install external authentication (such as an LDAP which can be populated from the R/3 backends)
- install an additional Java instance
I would go for both of them because
- it will make things easier if you implement other functionality that is in the portal (non-ESS)
- it will avoid patching one portal and to keep the SPs of both backend systems in sync with the portal
Markus

Doubt about apply PATCH 10.1.2.3 in middleware tier after apply mrua 10.1.4

Hello Gurus,
Can i apply middle tier patch 10.1.2.3 in PORTAL(middleware) after apply MURA 10.1.4 in Infraestructure tier?
Best regards,
Thiago Leôncio

Thiago,
My first response, although correct, may have caused some confusion. I was under the assumption that you had installed a 10.1.4 SSO repository which for IM 10.1.4.x. This repository ships with 10.1.2.0.2 Portal. But from the information in this thread, it seems that you want to patch a Portal midtier with the 10.1.2.3 patch while the Portal repository is still 10.1.4.0.0.
The AS 10.1.2.3 patch set contains two sorts of patches:
1. Patches for the Oracle 10.1.2.x Application Server binaries and libraries. These are copied to the file system when applying the patch set
2. Patches to upgrade the Portal repository. These PL/SQL packages are installed in the Portal repository database.
In order to patch a 10.1.2.0.2 environment with Portal, the Universal Installer of the patch set needs to be run three times in this specific order :
1. Update the binaries/libraries of the Portal 10.1.2.x midtier
2. Update the binaries/libraries of the Identity Management 10.1.2.x midtier.
3. Upgrade the Portal and Wireless repository to either 10.1.2.3 or 10.1.4.
You can install the binary/libraries to both the Portal midtier and Identity Management midtier without running the repository upgrade immediately. This option is available for large scale deployments where the upgrade of the midtiers / identity management and the repository upgrade is spread over two downtime periods. This should however always be a temporary arrangement, it is not intended for production purposes. So to answer your question :
No, you can upgrade your Portal midtier to 10.1.2.3 without patching the Portal repository to 10.1.4.2 or 10.1.2.3 unless it is a temporary arrangement to accommodate for small downtime windows.
Note :
As mentioned before, the Portal repository upgrade part of the 10.1.2.3 patch set behaves different pending on the repository version :
All 10.1.2.x repositories are upgraded to 10.1.2.3
All 10.1.4.x repositories are upgraded to 10.1.4.2
Hope this helps,
EJ

Patch Guide for EP6

Hi,
I have just migrated from EP5 to EP6 version 6.0.2.4.1
Portal_Service_Pack_2.
I have downloaded patch 33 for (Portal,Sapinst,J2EE)
Where can I find documentation relating to the patch
sequence and can I go directly to this patch level.
Kind regards,
Morgan ([email protected])

Hi Morgan,
it is very important to read the notes released with the new patches for references to the installation process. For the portal patch check the note 806271 and the notes mentioned there.
As stated in the note above you'll need at least Portal Patch 4 and CM & Collaboration patch 5 to upgrade to the latest patch level, which actually now is Patch 34!!!
So for installing the latest portal patch check SAP Note 858873 and for the latest CM & Coll Patch check SAP Note 855491.
Also, this threads might be usefull to check if you have understand the process mentioned in the SAP Notes:
CMCOLL patch4 ....... (UPGRADE EP TO THE LATEST PATCH)
ep6SP2 portal patch 29 installation : shud i stop IRJ application?
Hope this helps,
Robert

Portal on WAS 640 JAVA cluster

Can anyone help me with the install sequesnce for this scenario.
I have 2 physical hosts
I want to run a java CI on one and a java DI on the other
I also want the portal to be installed as an application
I would like to patch the JAVA WAS to SP13
I would also like to patch the portal to SP 13
What order would I do this in??
Thanks

Hi Jeremy,
You need to do the following.
Patch WAS first
1. Patch your J2ee (WAS) on central instance by running the patch install on the central instance host. Portal installation will automatically start the central instance. Don't try to start the dialog instance because it will not start before it has not been upgraded.
2. Patch your J2ee(WAS) on dialog instance by running the patch install on the dialog instance host. Make sure you map the "central host\saploc\XXX\Sys" to a drive. You are going to need the drive for installation step where it wants you to enter the dialog instance profile.
Patch Portal
1. Make sure dialog instance is shut down and only one cluster server node is running on central host(disable the node via configtool.bat).
2. Start the patch install on the central host. After the installation is complete enable the cluster node on the central host.
3. Restart the central instance. After it is completely up, start the dialog instance. You patch installation for portal is complete.

Patching Ecom Portal

Similar Messages

Maybe you are looking for