New Patch Release 3.0.9.8.1 for Oracle9iAS Portal 3.0.9.8.0

Question

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

Answer 1

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