Portal PPE Clarification

All,
I'm working with a large company with an international presence. They are considering hosting Oracle9iAS (Portal) at a central US location for this initiative. They wanted to know a little more about the PPE (parallel page engine). We have read the details of this in the documentation but are unclear how it would render a page in the following situation.
Primary Portal Infrastructure & DB in US
9iAS Cache in Mexico (pushed to the edge of network.
The customer has applications running on Informix in Mexico. They have existing perl scripts to access the app running on Informix. If they utilize Oracle Portal and either with the PDK or a URL portlet, develop a portlet that accesses the app running on Informix in Mexico, where will the page actually be rendered. Due to bandwidth issues, they don't want data going from Mexico to US back to Mexico.
Thanks
Chase

I'm not sure what you mean by "it depends on how your backend R/3 is declared in the portal." Do you mean whether the not the system profile is either a SAP_R3_Dedicated or SAP_R3_LoadBalancing? Comparing the two, it looks like the latter gives some option for entering the message server of the system. I've set up the ABAP application servers we have as SAP_R3_Dedicated, so I'm guessing I'll need to change these to SAP_R3_LoadBalancing?
Reading the help files, it suggests that I could use the Web Dispatcher along with existing logon groups we use to load balance on our backend ABAP applicaition servers:
http://help.sap.com/saphelp_nw70/helpdata/en/5f/7a343cd46acc68e10000000a114084/frameset.htm
If I understand what it's saying, I could have my hardware load balancer at the front managing
requests from the Web to the portal. Then, and this is where it gets unclear, I could have
the Web Dispatcher (one running on each portal instance?) load balance via logon groups.
If this is the case, I'm also unclear on how to get the logon groups we have set up for
load balancing in our ABAP app servers to work with the logon groups set up in the portal.
I have documention and instruction on how to load balance with Web Dispatcher/logon groups
in the portal for multiple Java instances, but not how to do it with multiple Java instances that
connect, or are connected, to multiple ABAP instances...via logon groups. I think I could get something working with the Web Dispatcher (without the front end hardware load balancer, since we dont' have it yet) so that I can see how it all works...but I'll need some instructions first for "connecting" the ABAP logon groups to portal logon groups (still looking...).
Could anyone verify I have this correct? And if so, point me to some detailed instructions?
THANKS!!

Similar Messages

Production Portal hangs with timeouts

Hi all,
Several times during the day the Portal 10.1.4.0.0 hangs with timeouts.
In order to recover, Portal needs to be re-started.
(The timeout also occurred during the time they had a db corruption, but now that corruption has been resolved, the hangs still occur.
After running the SVU in CLEANUP mode, the issue still occurs.
Timeout has been set to well over the default. Stall has been increased also. Neither have helped to resolve the issue.
The java portlets are from a specific OC4J Provider, and all of them are on pages under a Page Group.
These portlets reads (also trough views) data on portal schema in order to create the "style" and css of the portal pages. All of the database statements are select, exception of rare insert operation on a table of their custom schema.
User load:
The access statistics indicates that about 800 users access this site in 1 hour.
The more high user access in one hour was 1100 users.
The concurrent user access are about 500.
Thanks for any help.
Edited by: hmannila on May 11, 2010 11:50 PM

Hello Helenna,
In this particular case, the PPE timeout settings are set to very high values causing exhaustion of fetcher threads in the PPE fetcher thread pool :
<servlet>
   <servlet-name>page</servlet-name>
   <servlet-class>oracle.webdb.page.ParallelServlet</servlet-class>
   <init-param>
<param-name>requesttime</param-name>
<param-value>120</param-value>
   </init-param>
   <init-param>
       <param-name>minTimeout</param-name>
       <param-value>180</param-value>
   </init-param>
   <init-param>
       <param-name>stall</param-name>
       <param-value>200</param-value>
   </init-param> This should be the action plan for you :
>
As you already pointed out, the portal seems to become unresponsive because the Edison provider is not responding fast enough to requests from the Portal framework. Oracle Portal should be able to recover from thi in normal cases. Unfortunately the configuration settings in the Portal were changed from the default values making it almost impossible for the framework to recover from the error. To understand this, we will need to go through the theory :
The Oracle Portal framework collects information from various sources and assembles these to web pages which are then sent to the end users internet browser. Providers are one source of information. To retrieve the information from providers, Oracle Portal allocates a so-called fetcher thread in OC4J_Portal. This fetcher thread will create a session with the (remote) provider and fetch the content, similar to how a web browser would contact a web server to retrieve an HTML page. It is important to note that Oracle Portal allocates a fetcher thread for each portlet on a page. For a page with five portlets, five fetcher threads are allocated as the content is fetched in parallel.
In a default configuration with only one OC4J_Portal process, the number of fetcher threads is limited to 25. With five portlets on a page, the Portal will be able to serve up to five requests simultaneously before the pool of fetcher threads gets exhausted. This is normally not a problem because the fetcher threads are allocated for just a few seconds normally. Once they have received the response from the provider, they are returned to the pool and will be available to the Portal again.
The problems start when the provider's response becomes sluggish. The fetcher thread is not returned to the pool immediately. The requests start to queue up until the system doesn't have any fetcher threads available anymore. Once there are no fetcher threads available, the Portal will wait for a new fetcher thread for a certain period of time (as specified by the queueTimeout). After expiration of this queue timeout, the Portal will return an error to the Oracle HTTP Server. This is when end users will start to experience errors in the pages.
To keep the Portal alive and healthy, administrators should take care that the fetcher threads pool doesn't get exhausted. Obviously the best way to do this is to ensure that all providers respond in a reasonable amount of time. If there is no control on the response times of the providers, administrators can use the timeouts in the framework to assure that long running requests are killed off by the framework to assure that the fetcher threads are returned to the pool again. These parameters are configured in the web.xml from the application portal in the OC4J container called OC4J_Portal. Obviously users will see timeout errors for particular portlets on certain pages but the overall framework will be available. In addition, administrators can decide to increase the number of fetcher threads by starting more than one OC4J_Portal process. Each additional process will increase the amount of fetcher threads with 25. There is a memory penalty for this however as each process can consume between 256 - 512 Mb of memory. Administrators should only increase the amount of processes when they have checked that the Portal midtier system has enough free memory available to accommodate for these additional processes.
Action plan :
1. Change the timeout values for the Portal framework to the default values :
a. Navigate to $ORACLE_HOME/j2ee/OC4J_Portal/applications/portal/portal/WEB-INF
b. Copy the web.xml :
% cp web.xml web.xml_23MAR2010
c. Edit the web.xml :
For both the RepositoryServlet and the PortalServlet, remove the STALL timeout
For the page servlet, remove the requesttime, minTimeout, stall and queueTimeout parameters
2. Increase the number of OC4J_Portal processes from 1 to 4 :
a. Create a copy of the file $ORACLE_HOME/opmn/conf/opmn.xml :
% cp opmn.xml opmn.xml_23MAR2010
b. Open the file opmn.xml
c. Locate the following section :
<process-type id="OC4J_Portal" module-id="OC4J">
d. Within the section for the process OC4J_Portal, change the following line :
<process-set id="default_island" numprocs="1"/>
to
<process-set id="default_island" numprocs="4"/>
3. Synchronize the DCM repository :
% $ORACLE_HOME/dcm/bin/dcmctl updateconfig
4. Restart the midtier processes
% $ORACLE_HOME/opmn/bin/opmnctl stopall
% $ORACLE_HOME/opmn/bin/opmnctl startall
4. Check whether the changes have are in effect :
a. Number of OC4J_Portal processes :
Run opmnctl status and count the number of OC4J_Portal processes. You should see four of them.
b. Timeout parameters in OC4J_Portal
Open the file $ORACLE_HOME/j2ee/OC4J_Portal/application-deployments/portal/OC4J_Portal_default_island_1/application.log and check for the following line at the end of the file :
10/03/08 06:32:32 portal: PPE version : 10.1.2.0.2 (29022008)
10/03/08 06:32:32 portal: Tuning parameter values : poolSize(Fetchers)=25[default=25] : minTimeout(MinTimeout)=5s[default=5s] : requesttime(DefaultTimeout)=15s[default=15s] : stall(MaxTimeout)=65s[default=65s] :
queueTimeout(QueueTimeout)=10s[default=10s] maxParallelPortlets=20[default=20] maxParallelPagePortlets=10[default=10]

Error while upgrading 10g AS from 10.1.2.0.2 to 10.1.2.3

Hi All,
I am in process of doing 10g AS integration with 11.5.10.2.
As per documentation i have seen that 10g AS has to upgrade
My 10g AS version is 10.1.2.0.2
and my database version is 10.1.0.4.2
I have downloaded patch p5983622_10123_LINUX.zip
and first tried to upgrade infrastructure home
but while upgrading it says
oracle universal installer has detected that your database is version 10.1.0.4.2 before you can continue you must apply a required database patch set.
But in documentation i have seen
Supported Database Releases
The portal schema may be residing in an OracleAS Metadata Repository, or in a customer database. The database in which the portal schema resides must be one of the following supported releases:
Oracle Database 10g (10.1.0.4.2) or later
Please let me know what should i do now
Thanks in advance
Regards,
Bhanu Chander.

Hi ,
$ORACLE_HOME/j2ee/OC4J_Portal/application-deployments/portal/OC4J_Portal_default_island_1/application.log
09/09/24 06:24:21 portal: Max URL _debug value '1'.
09/09/24 06:36:33 portal: [module=PortalServletContextListener, thread=Shutdown] Portal Servlet Context Listener destroy started
09/09/24 06:36:33 portal: [module=PortalServletContextListener, thread=Shutdown] Repository Service destroy started
09/09/24 06:36:33 portal: [module=PortalServletContextListener, thread=Shutdown] Repository Service Config destroy started
09/09/24 06:36:33 portal: [module=PortalServletContextListener, thread=Shutdown] Repository Service Config destroy finished, 0 ms
09/09/24 06:36:34 portal: [module=PortalServletContextListener, thread=Shutdown] Repository Service destroy finished, 1003ms
09/09/24 06:36:34 portal: [module=PortalServletContextListener, thread=Shutdown] Portal Servlet Context Listener destroy finished, 1004ms
09/09/24 06:36:34 portal: Page Servlet destroy started at 1253788594974 millis
09/09/24 06:36:34 portal: Page Servlet destroy ended at 1253788594977 millis, duration was 3 millis
09/09/24 06:36:34 portal: [module=RepositoryServlet, thread=Shutdown] Repository Servlet destroy started
09/09/24 06:36:34 portal: RepositoryServlet: destroy
09/09/24 06:36:34 portal: [module=RepositoryServlet, thread=Shutdown] Repository Servlet destroy finished, 0ms
09/09/24 06:36:34 portal: [module=PortalServlet, thread=Shutdown] Portal Servlet destroy started
09/09/24 06:36:34 portal: PortalServlet: destroy
09/09/24 06:36:34 portal: [module=PortalServlet, thread=Shutdown] Portal Servlet destroy finished, 0ms
09/09/24 06:36:34 portal: Stopped
09/09/24 06:36:34 Stopped (Shutdown executed by jazn.com/admin from 127.0.0.1 (localhost.localdomain))
09/09/24 08:35:53 Started
09/09/24 08:36:13 portal: ServletLogger - Logging level: 2
09/09/24 08:36:13 portal: [module=PortalServletContextListener, thread=Orion Launcher] Initializing Portal Servlet Context Listener
09/09/24 08:36:13 portal: jsp: init
09/09/24 08:36:13 portal: Started
09/09/24 08:38:37 portal: PortalServlet: init
09/09/24 08:38:37 portal: ServletLogger - Logging level: 2
09/09/24 08:38:37 portal: [module=PortalServlet, thread=AJPRequestHandler-ApplicationServerThread-5] Initializing Servlet: PortalServlet
09/09/24 08:38:38 portal: RepositoryServlet: init
09/09/24 08:38:38 portal: ServletLogger - Logging level: 2
09/09/24 08:38:38 portal: [module=RepositoryServlet, thread=AJPRequestHandler-ApplicationServerThread-5] Initializing Servlet: RepositoryServlet
09/09/24 08:38:39 portal: page: init
09/09/24 08:38:39 portal: Cache: Cache is enabled.
09/09/24 08:38:39 portal: Pool: Initialized with the following pools : [oracle.webdb.pool.http.HTTPConnectionKey]
09/09/24 08:38:39 portal: Created mobileXML to HTML stylesheet object
09/09/24 08:38:39 portal: PPE version : 10.1.2.0.2 (11082005)
09/09/24 08:38:39 portal: Tuning parameter values : poolSize(Fetchers)=25[default=25] : minTimeout(MinTimeout)=5s[default=5s] : requesttime(DefaultTimeout)=15s[default=15s] : stall(MaxTimeout)=65s[default=65s] : queueTimeout(QueueTimeout)=10s[default=10s] maxParallelPortlets=20[default=20] maxParallelPagePortlets=10[default=10]
09/09/24 08:38:39 portal: Max URL _debug value '1'.
what do you see when you get the error on trying to login.
Same error
An error occurred while processing the request. Try refreshing your browser. If the problem persists contact the site administrator

Clarification on SSXA Support with WebCenter Portal

Hi,
I saw a few threads requesting on this and other forums requesting clarification of SSXA and WebCenter Portal.
To clarify: SSXA is not supported by WebCenter Portal.
Our recommended route is to leverage ADF based templates/Content Presenter for integrating WebCenter Portal,
WebCenter Content and Site Studio.
Thanks,
Ashish
Sr. Director, Product Management
Oracle WebCenter Portal

Hi Ashish,
Just for curiosity, there's some technical explanation for this?
I know that there's some conflicts in JavaScript functions from SSXA and Composer, there's some more problems already mapped?
Thks

Port Numbers Clarification During Portal Installation

I have installed Portal 9.x. My infrastructure port is set at 7777 and my midtier port is set at 7779. This is how it was configured during the configuration stage.
Therefore shouldn't I be able to access Portal through the port 7777? Did I do any wrong thing when I installed?.
If I did then is there a way to change the port from 7779 to 7777 so that I can access it via 7777?
Thanks.

There are instructions on Metalink for changing the port numbers but they are spread out and hard to find and pick the right ones. I have gotten 2 files that I use to change my port numbers. Here they are:
How to Change the Port used for Oracle 9iAS Portal 9.0.x
1. Add the New port to Web Cache and map to the OHS (Apache)
a. Login to Webcache as an admin user
b. Select the Listening Ports link
c. Click the Add button, and use these settings to create the additional port
I. For Cache: <Select the webcache in use>
II. IP Address: ANY
III. Port Number: 80
IV. Protocol: HTTP
V. Wallet: <Leave null>
d. Select the Site to Server Mapping link
e. Select the radio button for the top entry (Priority 1) and click the button Insert Above
f. Select the radio button for Enter Site Name, and enter the following
I. Host Name: <Your ServerName directive from OHS (Apache)>
II. Port Number: 80
g. Check the box the HTTP entry located under the Select Application Web Servers Section
h. Accept Remainder of Defaults and click the Submit button
i. Click the Apply Changes button in the upper right of the screen
2. Restart the WebCache Server
3. Add a Partner Application to the Oracle 9iAS Single Signon for the new port using ptlasst script in SSOPARTNERCONFIG mode
(Passwords required may be lookup in OID using the note referenced below)
/u01/ora9portal/assistants/opca/ptlasst.csh -i custom -mode SSOPARTNERCONFIG \
-s <portalSchema> -sp <portalPassWord> -c <iasinfraServerName:1521:iasdb> \
-sdad <portalDad> -o <ssoSchema> -odad <ssoDad> -host <apacheServerName> \
-port 80 -silent -verbose -sso_c <iasinfraServerName:1521:iasdb> \
-sso_h <OHSServerName> -sso_p <ssoWebPort> \
-pa <ssoPartnerAppSchema> -pap <ssoPartnerAppSchemaPassWord> \
-ps <ssoProcessStoreSchema> -pp <ssoProcessStoreSchemaPassword> \
-p_tns <tnsConnectStringtoInfraDB> -s_tns <tnsConnectStringtoInfraDB> \
-iasname <iasMiddleTierInstanceName>
Here is an example on a Unix Server
/u01/ora9portal/assistants/opca/ptlasst.csh -i custom -mode SSOPARTNERCONFIG \
-s portal -sp W18Wqn49 -c www.oracle.com:1521:iasdb \
-sdad portal -o orasso -odad orasso -host www.oracle.com \
-port 80 -silent -verbose -sso_c www.oracle.com:1521:iasdb \
-sso_h www.oracle.com -sso_p 7777 \
-pa orasso_pa -pap A2u3g00t \
-ps orasso_ps -pp BRKU0C6a \
-p_tns iasdb -s_tns iasdb \
-iasname iasmid.www.oracle.com
4. Modify the httpd.conf file located in the 9iAS Middle tier home to use port 80
a. Edit the httpd.conf file and change the Port directive to 80
Port 80
b. Do NOT modify the Listen directive in the file
5. Restart the http server in the Middle Tier
The port has now been modified and the site may be accessed using Port 80.
6. Login to Portal as an admin user, and reset the SSO Server Settings
a. Login to Portal as portal
b. Select the Builder link
c. Select the Administer tab
d. Select the Global Settings link
e. Select the SSO/OID tab
f. Under the SSO Server Settings section, modify the Query Path URL Prefix to use the correct sso port.
The SSO Server is usually running on Port 7777, but creating the partner application would also change this port to 80.
g. Select the apply, and ok buttons
I use this for Running the script above:
Windows Script to Determine orasso Password in 9iAS Release 2 (9.0.2)
1. Paste the following script in a file named showPassword.bat and copy it in
a directory. Please also ensure that ldapserach is there in PATH on your
widnows machine.
8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<
set OIDHOST=bldel18.in.oracle.com
set OIDPORT=4032
if "%1"== "" goto cont
if "%2"== "" goto cont
ldapsearch -h %OIDHOST% -p %OIDPORT% -D "cn=orcladmin" -w "%1" -b "cn=IAS Infrastructure
Databases,cn=IAS,cn=Products,cn=OracleContext" -s sub "orclResourceName=%2"
orclpasswordattribute
goto :end
:cont
echo Correct Syntax is
echo showpassword.bat orcladminpassword username
:end
8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<8<
Note that the "ldapsearch...orclpasswordattribute" commands should be put on
one line.
2. Edit the script and update with your own hostname and OID port
OIDHOST=bldel18.in.oracle.com
OIDPORT=4032
3. Ensure that you have ldapsearch from the correct ORACLE_HOME in the PATH
4. Check that OID is up and running before proceeding.
5. Run the script, and enter the schema name as: orasso, and the password value
is shown.
For example:
(all ONE line...may be easier to copy/paste from Notepad)
C:\> showPassword.bat oracle1 orasso
OrclResourceName=ORASSO,orclReferenceName=iasdb.bldel18.in.oracle.com,cn=IAS Inf
rastructure Databases,cn=IAS,cn=Products,cn=OracleContext
orclpasswordattribute=Gbn3Fd24
The orasso password in this example is Gbn3Fd24.

Clarification on Portal eventing

Hi,
I found this documentation
http://help.sap.com/saphelp_nw04s/helpdata/en/f6/7d6f4151dc5758e10000000a1550b0/frameset.htm
This has the following text
"All participating events must also belong to the same domain."
I am unclear what domain is being talked of here. I am trying to use portal eventing to communicate across 2 iViews in a page one belonging to WD Java and another WD ABAP.
Please can someone clarify.
Regards,
Sabarish

Here browser feature will restrict to event in other opened session.
session variable will be associated with entire session only it can't be overlapped with other.
Same domain is correlating with opened session only . So all event will be triggered through current session.
Regards,
Ashish Gautam

Required Clarification with portal

Hi,
Urgently Looking for some excellent inputs for the following question.
1)What are the list of components which are used in EP for implementing different scenarios. Like (iviews, dynpro , other components) >?
2) Does portal have itz own database?
3) Architectural requirement for Implementing EP / Net weaver. What are the technical requirements in terms of Software, Hardware, licenses, database, SAP components, and other then Sap software or components?
Thanks in advance.
*POINTS TO BE GIVEN ASAP*
Cheers,
*RAJ*

hi
Rajesh
1)creation of iviews ,pages,worksets comes under portal administration
to implement portal content basically we have two technologies
on JSPDynpages,Webdynpro
ofter creation applications using either two of them .We create iviews
2) yes
3) Sap Netwear easily integrates information and application from virtually any source
implementing EP nothing but people integration
technical requirements
j2sdk 1.4
jce policy
Sneak Preview Server

PLM portal - clarifications

Hi All,
I am new to the PLM portal .
Currently i am working in the project where PLM ( Portal & ECC) landscape is up and runnung, but i have couple of questions which are to be clarified. please do the needful.
In the PLM portal how the portal objects like (Iviews,pages,workset,roles) get into the portal, as i gone thru the properties of many objects says that those are created by "SAP", then in that case how the objects are handledsd either from business package deployment of PLM in portal or it comes along with SAP PLM ECC box ?? please clarify
As i found those are SAP standard portal objects , some are java webdynpro and some are ABAP webdynpro objects, are those not implemented or comes by default alongwith portal??
Please get back to me on the same then it would be great help to me.
Thanks in advance
Regards,
PortalUser100

Currently we are using ECC 7.0 system, but i have one dought.
I think you mean ECC 6.0 since there is no ECC7.0 system available yet.
Do you have any specific documentation how to deploy the PLM business package in portal, currently i am seeing some of the objects are ABAP Webdynpro and other are JAVA Webdynpro. but i dont have any clue where these objec ts gets created in portal, do we need to create those thru PLM/PLV template in portal or objects are already available in portal after deployment of business package?
The deployment of the business package is similar to the deployment of any other business package. You will just need to download the .SCA file for the business package from SMP based on your versions and deploy it onto your portal using SDM or JSPM.
After you deploy the business package - all the portal content is available for your use.
Please let me know the complete picture of this PLM integration with Portal, that would be great help to us.
I am not sure how to give you a "complete picture" in one forum post.
Please go through the help link I have given above and search on SDN for other possible information. If you have specific questions, please post them here.
Currently i am seeing that all the ABAP Webdynpro objects in ECC 7.0 are SAP Standard ABAP components, not even they created single new object.
can you tell me more on this ??
You create custom objects/applications if you need to. The whole idea of the business package is to utilize ready-to-use applications delivered by SAP.

BI Java Installation: Clarification Needed!

I'm wondering if someone could help clear this up for me:
We have installed NW2004s SPS08 on Solaris with only the usage type EP (AS Java/EP). Awhile back I was tasked with connecting our BW ABAP system to our Portal ("Integration into the Portal" - transaction SPRO etc).
After starting this task I noticed I was missing things that the instructions were telling me to configure; i.e. Items that were related to BI that weren't in the Portal such as certain roles, the BI Repository Manager etc.
Reading around, it seemed like I need to install the BI usage type.
I have now been tasked with another installation of the Portal (NW2004s SR1 this time), but am trying to head off the problems I'm experiencing trying to connect the Portal to our BW ABAP system. This will be a Java only installation. I've read that BI-Java requires EP and AS Java, and that if I install the BI-Java usage type, EP and AS-Java will be installed automatically.
My question is, if I do the BI-Java installation and it automatically installs EP/AS-Java, will the Portal still act the same way as it does in my EP/AS-Java only installation I already have? We have many plans to use the Portal as an entry point for all of our backend systems, so if the Portal's capabilities are not what we see already (in our first installation of just EP/AS-Java) then we will have problems.
Any clarification is greatly appreciated and I will award points accordingly.
THANKS!
Beau.

I think that's what I needed to know.
I was actually wondering about DI as well. Our developers are having problems deploying .EAR files to our original EP-only install. They can deploy .PAR files with no problems, but .EAR files always error out. Maybe having DI will solve this problem as well? I'm a little concerned about the hardware capacity of this box with having BI, EP and DI all installed on it. I had contacted SAP about installing DI a while back and basically they had told me to install it on a seperate server, by itself. We're running a Sun Enterprise 420R, 4G of memory and a 450 mhz processor for this new installation. Do you think this box is capable of handle EP, BI and DI (AS-JAVA)?
Thanks for your help!

What do you NOT like about Oracle Portal?

Using a theme from a post on AskTom, I thought I would start one that details what customers don't like about Portal.
I've got a few:
PPE
When load balancing, it forces us to use NAT in the load balancer. Extra configuration, extra time, etc.
Java or MOD_PLSQL?
Mod_plsql has been around for a long time. It is robust and stable but a simple Dad for Portal is a mix of Java and Mod_plsql. It is not nearly as clean and stable as a mod_plsql application.
SSO
SSO should be part of the middle tier, not the Infrastructure. It just adds another hop and another thing to manage.
PTLConfig
ssoreg is for SSO registration of Partner applications. Easy enough. But wait, it doesn't work for Portal. You have to run ptlconfig for it.
SSL configuration
Wow, what a pain. A Java application or Mod_plsql application is easy to configure for SSL. Not true with Portal.
OC4J Portal In Process
Showing the status with opmnctl won't show in-process things like Portal. It can only be seen in OEM.
Explicit Path
In the HTML Portal generates, it has the full path to everything. I tried just changing the hostname in the httpd.conf file but that doesn't work either. We used setup.exe OUI_HOSTNAME= to change the host name of an install which works ok. When using multiple middle tiers, you have to use the real host name for each server and then use a VirtualHost all because Portal uses the full path instead of a relative path.
Migration of code
Portal doesn't really support the idea of multiple environments which every large company (which is a big part of Oracle's customer base) uses. Migrating a page group with all content from Test to QA isn't something built in like it should be.
I've got some more complaints about Forms, Reports, Discoverer, and SSO but this is just about opportunities for Portal.

heh. why so negative?
what about a thread about what you LIKE about Portal :-)

I have Struts 1.1 working in the portal

Hello all,
I was having the same problem you have all seen. The long:
com.bea.netuix.nf.UIControlException: No ActionResult returned for action [/Home] in Struts module []. Please ensure that both module and action are correct in portlet StrutsContent element.
Here's how you solve it. Follow the "Integrating Struts Applications" tutorial, except realize the following: Workshop creates a Java Page Flow (JPF) application for you when you create a new Portal Web Project. JPF is a proprietary extension to struts by BEA. You cannot have a JPF application and a struts application in the same "module". So you are all probably doing exactly what I did and putting all your struts app's JSP's, images, html files, etc. in the root of the web application folder. This won't work because the root folder is a "module" that already is owned by JPF.
Instead create a sub folder in the web app root. Call it whatever you want, like "strutsModule" for example. Put all your struts applications jsp's, etc. that you would normally put in the web root in there instead. Still put all your source for the action classes, etc. in the web-inf/src folder like normal. Put your struts config in the web-inf folder but call it struts-auto-config-strutsModule.xml. Then when you create the "portlet" in step 4 specify "/strutsModule" as your "module" uri, and the first struts action your app should run as the struts action.
Everything will magically work now.
Good luck
Rob
Rob Butler
Architect @ chariot solutions
e-mail: rbutler at chariotsolutions.com

Hi Rob,
I am fresher in as far as portal is concerned and i am
using weblogic portal. I want to deploy Simplae struts application in
weblogic portal but i m not able to do that. I have seen ur post in forum
http://forums.bea.com/bea/thread.jspa?threadID=200076096&messageID=202412291#202412291
but i still want more clarification abt directory structure(where to
store which file??) and changes necessary in web.xml and all things
related to struts-config.xml.
Will u help me please??
Regards,
Mitesh Soni

Problem when trying to publish Query through BeX in Portal as iView

Hi ,
We are trying to publish BW 3.5 query in EP 6.0.
when we are trying to publish the query as iView in portal, it gives the error message 'System Error'. The J2EE Error Log contains the following error :
#1.5#001321FC0EDF001D0000000100000AF800042349427FEAFD#1164697462095#com.sap.security.core.server.jaas##com.sap.security.core.server.jaas#J2EE_GUEST#2##BID#AMARNATH_RR                     #6AA3FE0EADF14B2593F0019B1DB52607#SAPEngine_Application_Thread[impl:3]_17##0#0#Error##Java###Authentication stack: [].
[EXCEPTION]
#2#evaluate_assertion_ticket#javax.security.auth.callback.UnsupportedCallbackException: Unsupported callback!
     at com.sap.engine.services.rfcengine.security.impl.RFCCallbackHandlerImpl.handle(RFCCallbackHandlerImpl.java:49)
     at javax.security.auth.login.LoginContext$5.run(LoginContext.java:812)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.login.LoginContext$SecureCallbackHandler.handle(LoginContext.java:808)
     at com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule.removeSSOHeader(EvaluateAssertionTicketLoginModule.java:736)
     at com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule.login(EvaluateAssertionTicketLoginModule.java:390)
     at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:69)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:154)
     at com.sap.engine.system.SystemLoginModule.login(SystemLoginModule.java:90)
     at sun.reflect.GeneratedMethodAccessor206.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at javax.security.auth.login.LoginContext.invoke(LoginContext.java:675)
     at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129)
     at javax.security.auth.login.LoginContext$4.run(LoginContext.java:610)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:607)
     at javax.security.auth.login.LoginContext.login(LoginContext.java:534)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:60)
     at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
     at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
     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)
#1.5#001321FC0EDF00140000000600000AF800042349427FF32E#1164697462095#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal()####BID#AMARNATH_RR                     #6AA3FE0EADF14B2593F0019B1DB52607#Thread[JCO.ServerThread-8,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Plain###java.lang.RuntimeException: com.sap.engine.services.rfcengine.RFCException: Incoming call is not authorized#
#1.5#001321FC0EDF00140000000700000AF800042349427FF40A#1164697462111#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal()####BID#AMARNATH_RR                     #6AA3FE0EADF14B2593F0019B1DB52607#Thread[JCO.ServerThread-8,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Plain###java.lang.RuntimeException: com.sap.engine.services.rfcengine.RFCException: Incoming call is not authorized
     at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:188)
     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)
Landscape:We have both BW 3.5 and EP 6.0, SP 16 on the same instance in
same physical machine. EP 6.0 works on J2EE engine as an add-in installtion.
Steps we followed for the integration of EP with BW:
1)Create RFC Destination in J2EE Engine:
Parameters:
Program ID: xyz
Gateway host: abc.ad.company.com
Gateway service: sapgw00
Application server host:abc.ad.company.com
System number: 00
Client: BID
Language: EN
User: sapjsf
Password: ********
2)Maintain RFC Destination for SAP EP 6.0
Parameters:
RFC destination: SAP_EP
Connection type: T for TCP/IP connection
Description: SAP EP RFC Destination
Technical Settings:
- Type of activation: Registered server program
- Program ID: xyz
- Gateway host: abc.ad.company.com
- Gateway service: sapgw00
Logon/Security:
- Send SAP Logon Ticket: Activated
Special Options:
Unicode
3)Maintain Portal Server Settings for SAP EP 6.0 in table RSPOR_T_PORTAL
in BW 3.5
RFC destination: SAP_EP
System name: BIDEV
Default: Checked
Portal URL prefix: http://abc.ad.company.com:50000
RM prefix for BW metadata: <empty>
KM service URL: <empty>
P.S.:We have maintained one more dummy entry as per the SAP Note 815044
in the table RSPOR_T_PORTAL.
4)Maintain Single Sign-On in SAP BW
In transaction RZ10, We have maintained following settings:
login/create_sso2_ticket=2
login/accept_sso2_ticket=1
5)Export BW Certificate to SAP BW and
6)Import BW Certificate to SAP EP 6.0
We have followed the above mentioned two steps.
7)Create BW System in SAP EP 6.0
Parameters:
Log on methods: SAPLOGONTICKET
We have created the BW system and the Connection test in WAS Connection
is working fine.
8)Configure User Management in SAP EP 6.0
This step is not maintained as our scenario does not demand it.
9)Export Portal Certificate to SAP EP 6.0 and
10)Import Portal Certificate to SAP BW
This step is also maintained as per Performance Assistant guidelines in
SPRO.
The user that we are trying to log into BeX Web Query Analyzer is
Amarnath_rr who has 'SAP ALL' rights and the same user in EP is assigned'Super Admin' as well as 'Content Admin' role.
Can anyone throw any light on wat the error might be??

Ricky,
a couple of clarifications :
1. Does the report execute independently on the web - when you execute in Query view over IE or through a web template
2. Check if SSO is properly configured - you can check if SSO is enabled by using TCode STRUST in BW. - the status of PSE should be Green.
Arun
Assign points if useful

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

Multiple applications running on the same portal server

Environment : EP 7.0 SPS12
We have multiple portal applications running on the same portal with different login page for each application. On one of our employee portal, we want to put a login page link for another portal application running on the same portal which requires a different user ID and password to access that application.
The problem we are encountering is, the login page link we put in our employee portal is bypassing the login page for the other application and using the same session as the employee portal. What can I do to make sure application login page show up when accessing the link from employee portal?
Your help is really appreciated.
Thanks
Bhabesh Patel

Hi,
thanks for the clarification. I think I do understand now and the only thing I can think of is to delete the session cookie.
The problem with that is that you would not be able to use "simple" links (e.g. you could not just call the URL of the other application, but you would have to create some application (a simply JSP would probably be fine) that deletes the cookie and redirects you to the new application.
An other option would be to create DNS aliases that so that the session cookie is not sent (but depending on your setup this might have other drawbacks). Since the cookies are not valid for the other domains you would always start with a new login when you access a new application (e.g. the employee portal has the url portal.employee.company.com and the customer portal has portal.cutomer.company.com. Then (if the settings for ume.logon.security.relax_domain.level,see http://help.sap.com/saphelp_nw70/helpdata/en/5e/473d4124b08739e10000000a1550b0/frameset.htm is correct)
Hope this helps,
Holger.

How can we call Tcode from the Portal?

Senario:
2 BAPIs are developed:
1. The information say... ABC is stored into the table from the portal using the Create BAPI.
2. The change in this ABC information is done using a particular <b>Tcode</b> say xyz. This is a report that calls the change BAPI inside.
The ABC information change will be done either through the Tcode in ECC or through the EP.
3. The Tcode has been created in ECC.
Please let me know who will be responsible to call this tcode from the Portal and how?
I am very very new to EP field so please help...

Hi Jignesh,
If you have already performed these steps and are able to see the iview that you have created. Then I think your issue has been sorted out.
To explain it to you in detail.
Let us suppose, you have created a SAP Transactional iview to access the TCODE-SE38.
Now, as soon as the user clicks on the iview, it will authenticate by asking for the username and password for the backend system...if your SSO is not in place.
Now, if your asking me how to make the iview visible.
You can add assign this SAP transactional iview to a page,a workset or a role and add the corresponding page, workset or role to the user in USER ADMINISTARTION by making it an entry point.
Or to make the iview as an entry point, right click on the iview that you have created and open the properties, then for the option that says entry point choose yes.
I guess that answers your question.
Let me know if you have need any further clarifications on the same.
Regards,
Sandeep

Portal PPE Clarification

Similar Messages

Maybe you are looking for