OID is integrated with Oracle Webcenter 11g through a provider & integrated with Jive Forums
(WC_Collaboration managed server)
A WebCenter Spaces announcement task flow is being used in a custom portal application.
When creating groups & users in OID through the custom application from Webcenter Spaces, those users are able to login to the Portal.
But announcements are not shown in Portal.
For announcements to be shown on Portal the users need to be manually added in the Jive
Forums Admin console.
Is it possible, once the users are created in OID, for those users to be automatically added in
Jive Forums, so that when the user logs in to Portal they are able to see the announcements in
Portal?
2.
.
Hi,
Here is the steps to change the Oracle Logo.
1. Login to Webcenter Spaces an admin user (weblogic)
2. Click the Administration Link
3. Click the Configuration Tab
4. Under Global Settings notice the selected Oracle Logo.

5. Click the Browse Button to Navigate to the logo of your choice.
The changes should be immediate.
I have not found a simple way to do this yet. I do think this is controlled however at the
Page Template Level.
For example I think this needs to be changed to the Webcenter Public Pages Template located at Administration > Resources > Page Templates > WebCenter Public-Page
Template. You need to make a copy of this page and then edit the copy. Somehow we then need to make this the active page for the Weblcome page. I am just not finding where to turn this on at.
) ### Extra Details ### i registered Omni portlet by portlet producer.
After creating page in web center spaces i add omni portlet on my page.
Customize the omni portlet and add google gadgets code by code but at last i got blank screen.
2) ### Step by step instructions ###
1.Add omni portlet on my web center spaces.
2.Customize the omni portlet.
3.finaly add the google gadget code .
4.Screen becomes blank.
5.I follow the same as given in this link: both on application level and web center spaces level. http://download.oracle.com/otndocs/tech/webcenter/files/owc_r11_google_gadgets.htm
Hi,
Please configure proxy server to webcenter as in http://download.oracle.com/docs/cd/E17904_01/webcenter.1111/e12405/wcadm_rss.htm
#CIHICGBD
Either via Fusion Middleware console or via WLST.

PFB the usecase & excet scenario.
There is a requirement from our client that in the header region of the custom portal we have to show the logo and advertisement images & in the footer region branding images
& text to be shown.
Header Region - In header region, we have customized logo and a banner image
(screenshot attached) which we have built as a sitestudio template (hcsp).We are calling this template through RIDC API and made this bunch of code as custom task flow.Now added this custom taskflow in the header region of the custom page template and assigned to the custom space in the webcenter portal.
Footer Region - In footer region, we have customized footer logo, sponsor images
(screenshot attached) & cutomized text which we have built as a sitestudio template (hcsp).We are calling this template through RIDC API and made this bunch of code as custom task flow.Now added this custom taskflow in the footer region of the custom page template and assigned to the custom space in the webcenter portal.
Now problem is after login to the portal when we click on any links/top menus in the portal,It's refreshing whole page, we want header & footer region not to be refereshed.
Setting Up and Testing the Announcements and Discussions Service for use with WebCenter
Spaces

In this Document
Purpose
Scope and Application
Setting Up and Testing the Announcements and Discussions Service for use with WebCenter Spaces
Oracle WebCenter - Version: 11.1.1.3.0 to 11.1.1.3.0
Information in this document applies to any platform.
This document shows an example of how to configure the Announcements and Discussions
Service for use with WebCenter Spaces or Custom WebCenter Applications.
It assumes you already installed and configured WebCenter Domain.
In addition to the Support Note below, you can get additional information here:
Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter
11g Release 1 (11.1.1)
12 Managing the Announcements and Discussions Services
Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter
11g Release 1 (11.1.1)
28 Configuring WS-Security for WebCenter Applications and Components
28.1 Configuring WS-Security for a Simple Topology
This document is intended for WebCenter Administrators that need to Configure WebCenter.
Setting up Discussions and Announcement Service requires the following major steps:
1. Securing the connection between WebCenter and Discussions Service using WS-
Security.
This step requires: o Creating the WebCenter Spaces Domain Keystore (webcenter.jks) with a Key
Pair containing a public key and associated private key. o Exporting the certificate (orakey.cer) containing the WebCenter domain public key.

o Creating the Discussions Keystore (owc_discussions.jks) with the WebCenter domain certified public key. o Configure the Discussions Server to use the Keystore.
A keystore is a file that provides information about available public and private keys.
2. Configure WebCenter Spaces for Discussions Service.
This step includes creating a connection to the Discussions Service and securing the connection using the Discussions-Keystore.
Next you will find the detailed steps for this configuration.
Securing the connection between WebCenter and Discussions Service using WS-Security
The following diagram shows how WS-Security is implemented for the Discussions configuration:
Note:

The WebCenter Spaces documentation has an additional step to create another public key with alias webcenter_spaces_ws. This key is used when working with SOA (Worklist Service). So this other public key is not required for the Discussions Service.
To secure the connection between WebCenter and Discussions Service perform the following steps.
1. Create the WebCenter Spaces Domain Keystore (webcenter.jks) with a Key Pair containing a public key and associated private key with alias "orakey". o Connect to the WebCenter Server. o Set the environment.
For example: export MW_HOME=/refresh/oracle/fmw11g export JAVA_HOME=/refresh/oracle/fmw11g/jrockit_160_14_R27.6.5-32 export PATH=$JAVA_HOME/bin:$PATH
Note: The above values might be different in your install. o Go to the directory where you will create the keystores: cd $MW_HOME/user_projects/domains/[webcenter_domain]/config/fmwconfig
For example: cd $MW_HOME/user_projects/domains/wc_domain/config/fmwconfig o Generate a Java keystore certificate with a private key alias "orakey" by running the following command:
$JAVA_HOME/bin/keytool -genkeypair -keyalg RSA -dname "consumer_dname"
-alias orakey -keypass key_password -keystore keystore -storepass keystore_password -validity days_valid
In the above command:
 consumer_dname is the name of the consumer (for example, cn=spaces,dc=example,dc=com)
 key_password is the password for the new public key, (for example, welcome1)
 keystore is the keystore name, (for example, webcenter.jks)
 keystore_password is the keystore password, (for example, welcome1)
 days_valid is the number of days for which the key password is valid (for example, 1064).
For example:

The above command should create the keystore webcenter.jks
file if it doesn't exist and it will add a private key with alias "orakey" . If you already created the webcenter.jks keystore file before then the private key will be added to the existing file.
Note: The domain name (dname) should match your server domain. o Check the keystore webcenter.jks
file was generated properly with the keytool command.
You will be asked for the password you provided when generating the keystore certificate. The output should show the new entry for the " orakey " alias with
Entry type as " PrivateKeyEntry ".
$JAVA_HOME/bin/keytool -list -v -keystore webcenter.jks
For example:
$JAVA_HOME/bin/keytool -list -v -keystore webcenter.jks
Enter keystore password: welcome1
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 1 entry
Alias name: orakey
Creation date: Aug 5, 2010
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: CN=spaces, DC=vm, DC=oracle, DC=com
Issuer: CN=spaces, DC=vm, DC=oracle, DC=com
Serial number: 4c5b0584
Valid from: Thu Aug 05 19:40:04 BST 2010 until: Thu Jul 04
19:40:04 BST 2013
Certificate fingerprints:
MD5: EA:19:73:96:F4:F8:B4:6E:0F:ED:41:60:B5:9D:5E:2B
SHA1: C6:4A:FE:E3:39:60:4B:DC:8E:C4:0E:74:AA:03:BC:B6:DF:27:55:63
Signature algorithm name: SHA1withRSA
Version: 3
*******************************************
*******************************************
$JAVA_HOME/bin/keytool \
-genkeypair \
-keyalg RSA \
-dname "cn=spaces,dc=vm,dc=oracle,dc=com" \
-alias orakey \
-keypass welcome1 \
-keystore webcenter.jks
\
-storepass welcome1 \
-validity 1064

2. Export the certificate (orakey.cer) containing the WebCenter domain public key.
$JAVA_HOME/bin/keytool -exportcert -v -alias orakey -keystore keystore -storepass keystore_password -rfc -file orakey.cer
In the above command: o keystore is the keystore name, (for example, webcenter.jks) o keystore_password is the keystore password, (for example, welcome1)
For example:
$JAVA_HOME/bin/keytool -exportcert -v -alias orakey -keystore webcenter.jks -storepass welcome1 -rfc -file orakey.cer
Certificate stored in file <orakey.cer>
The above command generates the certificate orakey.cer
file.
This certificate will be imported in the Discussions Keystore.
3. Create the Discussions Keystore (owc_discussions.jks) with the WebCenter domain certified public key. o Create a keystore for the Discussions Service by importing the certificate containing the public key of the WebCenter domain.
$JAVA_HOME/bin/keytool -importcert -alias df_orakey_public -file orakey.cer
keystore owc_discussions.jks
-storepass keystore_password
In the above command:
 keystore_password is the keystore password, (for example, welcome1)
For example:
$JAVA_HOME/bin/keytool \
-importcert \
-alias df_orakey_public \
-file orakey.cer
\
-keystore owc_discussions.jks
\
-storepass welcome1
Owner: CN=spaces, DC=vm, DC=oracle, DC=com
Issuer: CN=spaces, DC=vm, DC=oracle, DC=com
Serial number: 4c5b0584
Valid from: Thu Aug 05 19:40:04 BST 2010 until: Thu Jul 04
19:40:04 BST 2013
Certificate fingerprints:
MD5: EA:19:73:96:F4:F8:B4:6E:0F:ED:41:60:B5:9D:5E:2B
SHA1:

C6:4A:FE:E3:39:60:4B:DC:8E:C4:0E:74:AA:03:BC:B6:DF:27:55:63
Signature algorithm name: SHA1withRSA
Version: 3
Trust this certificate? [no]: yes
Certificate was added to keystore
When prompted "Trust this certificate?" say "Yes" to trust the certificate
The above command should create the keystore owc_discussions.jks
file with the self-certified public key with alias " df_orakey_public ".
This certificate will be used by Discussions Server to determine that Spaces is a trusted application. o Check the keystore to be sure the WebCenter domain public key was added.
You will be asked for the password you provided when generating the keystore certificate. The output should show 1 entry for the " df_orakey_public " alias with
Entry type as " trustedCertEntry ".
$JAVA_HOME/bin/keytool -list -v -keystore owc_discussions.jks
For example:
$JAVA_HOME/bin/keytool -list -v -keystore owc_discussions.jks
Enter keystore password: welcome1
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 1 entry
Alias name: df_orakey_public
Creation date: Aug 5, 2010
Entry type: trustedCertEntry
Owner: CN=spaces, DC=vm, DC=oracle, DC=com
Issuer: CN=spaces, DC=vm, DC=oracle, DC=com
Serial number: 4c5b0584
Valid from: Thu Aug 05 19:40:04 BST 2010 until: Thu Jul 04
19:40:04 BST 2013
Certificate fingerprints:
MD5: EA:19:73:96:F4:F8:B4:6E:0F:ED:41:60:B5:9D:5E:2B
SHA1: C6:4A:FE:E3:39:60:4B:DC:8E:C4:0E:74:AA:03:BC:B6:DF:27:55:63
Signature algorithm name: SHA1withRSA
Version: 3
*******************************************
*******************************************
4. Configure the Discussions Server to use the Keystore. o Connect to the WebCenter Server.

o Set the environment.
For example: export MW_HOME=/refresh/oracle/fmw11g export JAVA_HOME=/refresh/oracle/fmw11g/jrockit_160_14_R27.6.5-32 export PATH=$JAVA_HOME/bin:$PATH
Note: The above values might be different in your install. o Change to the following directory: cd $MW_HOME/user_projects/domains/[webcenter_domain]/lib
For example: cd $MW_HOME/user_projects/domains/wc_domain/lib o Create a keystore certificate properties file named keystore.properties.
The following example shows properties for a sample certificate: org.apache.ws.security.crypto.provider=org.apache.ws.security.components.cryp
to.Merlin org.apache.ws.security.crypto.merlin.keystore.type=jks org.apache.ws.security.crypto.merlin.keystore.password=welcome1 org.apache.ws.security.crypto.merlin.keystore.alias=df_orakey_public org.apache.ws.security.crypto.merlin.file=/<replace dir path where you run keytool>/owc_discussions.jks
For example: org.apache.ws.security.crypto.provider=org.apache.ws.security.comp
onents.crypto.Merlin org.apache.ws.security.crypto.merlin.keystore.type=jks org.apache.ws.security.crypto.merlin.keystore.password=welcome1 org.apache.ws.security.crypto.merlin.keystore.alias=df_orakey_publ ic org.apache.ws.security.crypto.merlin.file=/refresh/oracle/fmw11g/u ser_projects/domains/wc_domain/config/fmwconfig/owc_discussions.jk
s
Note: Be sure the keystore.properties file doesn't contain any trailing spaces or special characters on any of the lines. All should be plain text with no trailing spaces.
Tip for Unix systems:
On Unix systems edit the keystore.properties file with "vi" editor.
On each line of the file enter the "$" command. This should take you to the end of the line with the cursor positioned in the last character of the line (if it is after the

last character then you have a trailing space).
It was observed that in some cases when you create the file in other systems like windows and then copy the file to Unix for some reason all carry returns were removed from the file. So ensure you have one "org.apache.ws.security.crypto" value per line and that the "$" command doesn’t go to the end of the file. o Create a jar file containing the keystore.properties using the following command: jar cvf jive_crypto.jar keystore.properties
For example: jar cvf jive_crypto.jar keystore.properties adding: META-INF/ (in=0) (out=0) (stored 0%) adding: META-INF/MANIFEST.MF (in=56) (out=56) (stored 0%) adding: keystore.properties (in=409) (out=173) (deflated 57%)
Total:
------
(in = 453) (out = 563) (deflated -24%)
The above command should create the jive_crypto.jar
file. o Log on to the Oracle WebCenter Discussions admin console.
The URL should look like this: http://server:port/owc_discussions/admin
For example: http://fmw11g.vm.oracle.com:8890/owc_discussions/admin
Login as a user with admin privileges. For example with weblogic user.

o Click "System Properties" in the Oracle WebCenter Discussions admin console. o Change the following property value: webservices.soap.custom.crypto.fileName=keystore.properties

Configure WebCenter Spaces for Discussions Service
1. Create a connection to Oracle WebCenter Discussions. o Login to the Enterprise Manager 11g Fusion Middleware Control.
The URL should look like this: http://server:port/em
For example: http://fmw11g.vm.oracle.com:7001/em o Navigate as follows:
Farm -> WebCenter -> WebCenter Spaces -> webcenter (WLS_Spaces)

o In the Right panel select the following menu option: webcenter -> Settings -> Service Configuration

o Click on the "Discussion and Announcements" Link. o Click Add to create the discussions connection. o Provide the following information:
Connection Name: Enter a unique name for the connection.
Active Connection: Checked
Server URL: URL for Discussions Service. e.g. http://server:8890/owc_discussions
Administrator User Name: Discussions Server user that has System Admin permissions (weblogic initially).
Connection Secured: Checked
Additional Properties:
keystore.location: location of the keystore file
group.mapping=Set to forum or category.
- When set to forum (the default), a single forum is created under the application
root category per group space.
- When set to category, a subcategory is created under the application

root category per group space.
keystore.type: jks
encryption.key.alias: key alias to be used for encryption
keystore.password: password for the keystore - check Is Property Secured.
encryption.key.password: password for accessing the encryption key - check
Is Property Secured.
For example:
Connection Name: JIVE
Active Connection: Checked
Server URL: http://fmw11g.vm.oracle.com:8890/owc_discussions
Administrator User Name: weblogic
Connection Secured: Checked
Additional Properties:
keystore.location:
/refresh/oracle/fmw11g/user_projects/domains/wc_domain/config/fmwc onfig/webcenter.jks
group.mapping= category
keystore.type: jks
encryption.key.alias: orakey
keystore.password: welcome1 ( Is Property Secured? - Checked )
encryption.key.password: welcome1 ( Is Property Secured? -
Checked )

o Restart the WLS_Spaces and the WLS_Services managed servers.
2. Connect to WebCenter Spaces and test the Discussions Service.

Installation and Configuration of Oracle WebCenter Discussions 10g Release 3 (10.1.3.4.0)
In this Document
Purpose
Scope and Application
Installation and Configuration of Oracle WebCenter Discussions 10g Release 3 (10.1.3.4.0)
Preparation of Oracle WebLogic Server (WLS)
Installation of Oracle WebCenter Discussions 10g R3
References
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.
Oracle WebCenter - Version: 10.1.3.4.0 to 10.1.3.4.0
Information in this document applies to any platform.
This document provides step-by-step details to install and configure Oracle WebCenter
Discussions 10g Release 3 (10.1.3.4.0) on the Oracle WebLogic Server 10.3 platform.
The following assumptions are made:
- You already have an installation of Oracle WebLogic Server 10.3. If not, you may download the production version from the Oracle BEA Product Downloads website and install it.
- You have already downloaded the Oracle WebCenter Discussions 10g Release 3 (10.1.3.4.0). If not, you may download this from Oracle WebCenter Additional Services 10g Release 3
(10.1.3.4.0) website .
Installation of Oracle WebCenter Discussions 10g Release 3 (10.1.3.4.0) is only supported on
Oracle WebLogic Server 10.3.
ORACLE_HOME
(Middleware)
Oracle WebLogic Server
Test Environment /Oracle/Middleware $ORACLE_HOME/wlserver_10.3
My Environment
Default WebLogic Server Administration Console accessed as follows (on Test environment):

http://myHostName:7001/console
1. Create a new WebLogic domain "WebCenterDomain". If you already have a domain you would like to work with, then skip this step.
[Middleware]$ $ORACLE_HOME/wlserver_10.3/common/bin/config.sh

Select Generate a domain configured automatically to support the following products option

Configure administrator username and password for this domain

Choose the domain's start up mode (Development or Production) and the JDK to use.
Sun SDK 1.6 and JRockit SDK 1.6 are used for Development and Production modes respectively.

Accept default settings for Server and Cluster configuration

Accept default settings for Store configuration

Review the domain details and click Next

Domain Name: WebCenterDomain Domain Location:
$ORACLE_HOME/user_projects/domains (default)

Create the domain
* Product mode was selected as the domain start up mode at the time of creation of this Note.
After completion of domain creation by the wizard, verify its creation by navigating to
$ORACLE_HOME/user_projects/domains directory. You will find a new WebCenterDomain directory.
2. Start the Node Manager, if not already started. The assumption here is that you have the Node
Manager installed. If you have not the Node Manager installed, then you will start the Managed
Server (DiscussionServer) using a script in Step 7
[Middleware]$ $ORACLE_HOME/wlserver_10.3/server/bin/startNodeManager.sh
3. Start the AdminServer of the newly created "WebCenterDomain" using the username/password specified during its creation:
[Middleware]$
$ORACLE_HOME/user_projects/domains/WebCenterDomain/common/bin/startWebLogic.sh
4. Access the WebLogic Server Administration Console in the browser: http://myHostName:7001/console
Login using the username/password specified during the creation of "WebCenterDomain". After authentication, ensure you are connected to the "WebCenterDomain" at the top right of the page.
5. Create a machine (a logical representation of the computer that will host the WebLogic Server instance, "DiscussionServer" in this case):
+ Go to the home page of WebLogic Server Administration Console
+ Under "Domain Configurations", click on "Machines" (Environment).
+ Click on "Lock & Edit" button in the Change Center (top left of page). Now, choose to create a
Machine.
+ In the "Create a New Machine" screen:
++ Name: myHostName
++ Machine OS: Unix
6. Create a Managed Server "DiscussionServer" to host the Oracle WebCenter Discussions 10g
R3
+ Expand "Environment" menu in the "Domain Structure" portlet (left menu) on the WebLogic
Server Administration Console.
+ Click on "Servers" to display a Summary of Servers. Notice the default "AdminServer" is

displayed in RUNNING state.
+ Click on "Lock & Edit" button in the Change Center (top left of page). Now, choose to create a new Server.
+ In the "Create a New Server" screen
++ Server Name: DiscussionServer
++ Server Listen Port: 17001
++ Choose this to be a stand-alone server
++ Finish
+ Click on the "DiscussionServer" link to go to its settings screen
++ Change the "Machine" value from "(None)" to "myHostName" as created in step 5 above.
++ Save the settings
Finally, click on "Activate Changes" button in the Change Center (top left of page).
7. Start the newly created "DiscussionServer":
+ Go to the Summary of Servers screen. Notice the default "AdminServer" is displayed in
RUNNING state while the "DiscussionServer" is in UNKNOWN state.
+ Click on "Lock & Edit" button in the Change Center (top left of page).
+ Go to the "Control" tab and start the "DiscussionServer"
Refresh the page to confirm the state of "DiscussionServer" is RUNNING.
If you do not have the Node Manager installed, you may start the "DiscussionServer" as below.
Use the username/password specified during the creation of the Domain.
[Middleware]$ $ORACLE_HOME/user_projects/domains/WebCenterDomain/common/bin/sta rtManagedWebLogic.sh DiscussionServer
8. Unzip Oracle WebCenter Discussions 10g Release 3 (10.1.3.4.0) file downloaded from Oracle
WebCenter Additional Services 10g Release 3 (10.1.3.4.0) website .
Install Home
(Unzip Directory)
Test
Environme nt
Oracle/software/WC10134/Discus sions
$MW_HOME/user_projects/domains/WebCenter
Domain
DOMAIN_HOME
(WebCenterDomain)
My
Environme nt
[Discussions]$ ls deploy-discussions-sso.jar jive_forums_silver_5_5_20_oracle_01092009.zip oracle-discussions-sso.zip
[Discussions]$ unzip jive_forums_silver_5_5_20_oracle_01092009.zip
[Discussions]$ cd jive_forums_silver_5_5_20_oracle
[jive_forums_silver_5_5_20_oracle]$ ls -l
-rw-r--r-- 1 oracle oinstall 29215 Jan 9 16:46 changelog.html drwxr-xr-x 4 oracle oinstall 4096 Jan 9 16:46 client drwxr-xr-x 3 oracle oinstall 4096 Jan 9 16:49 database drwxr-xr-x 6 oracle oinstall 4096 Jan 9 16:49 documentation

-rw-r--r-- 1 oracle oinstall 4525 Jan 9 16:46 EditWAR.jar
-rw-r--r-- 1 oracle oinstall 5618 Jan 9 16:46 issues.html
-rw-r--r-- 1 oracle oinstall 36909777 Jan 9 16:49 jiveforums.war drwxr-xr-x 9 oracle oinstall 4096 Jan 9 16:49 jiveHome
-rw-r--r-- 1 oracle oinstall 7547 Jan 9 16:46 LICENSE.html
-rw-r--r-- 1 oracle oinstall 4253 Jan 9 16:46 README.html
9. Move the "jiveHome" directory from the unzipped location to a permanent location. In the test environment, the "jiveHome" directory is placed in the same directory level as the
$ORACLE_HOME.
[jive_forums_silver_5_5_20_oracle]$ mv jiveHome/ /Oracle/
[jive_forums_silver_5_5_20_oracle]$ ls /Oracle/ jiveHome Middleware jiveHome
MW_HOME
(Middleware)
Test Environment /Oracle/jiveHome /Oracle/middleware
My Environment
10. Update the "jiveforums.war" file in the Discussions Install Home with the new "jiveHome":
[jive_forums_silver_5_5_20_oracle]$ export PATH=$ORACLE_HOME/jdk160_11/bin:$PATH
[jive_forums_silver_5_5_20_oracle]$ which java
/Oracle/Middleware/jdk160_11/bin/java
[jive_forums_silver_5_5_20_oracle]$ java -version java version "1.6.0_11"
Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
Java HotSpot(TM) Client VM (build 11.0-b16, mixed mode)
[jive_forums_silver_5_5_20_oracle]$ ls changelog.html database EditWAR.jar jiveforums.war README.html client documentation issues.html LICENSE.html
[jive_forums_silver_5_5_20_oracle]$ java -jar EditWAR.jar jiveforums.war
This utility will modify your WAR file to correctly point to your jiveHome directory by editing WEB-INF/classes/jive_init.xml
Enter the full path to your jiveHome directory:
> /Oracle/jiveHome
Setting jiveHome to: /Oracle/jiveHome
...................................................................
[jive_forums_silver_5_5_20_oracle]$
11. Create "owc_discussions" deployment directory by extracting the contents of updated
"jiveforums.war" into it.
[jive_forums_silver_5_5_20_oracle]$ ls changelog.html database EditWAR.jar jiveforums.war README.html client documentation issues.html LICENSE.html
[owc_discussions]$ unzip jiveforums.war -d owc_discussions/
12. Create "jive" schema connected to the database as a DBA from any SqlNet client.

SQL> SHOW USER
USER IS "SYS"
SQL> CREATE USER jive IDENTIFIED BY jive;
SQL> GRANT CONNECT, RESOURCE TO jive;
SQL> EXIT
13. Use "jive_forums_oracle.sql" script to create the repository tables in the newly created schema. This script is located in the "database" in the Install Home
(Oracle/software/WC10134/Discussions/database). Execute the script connected to the database as "jive" user from any SqlNet client.
SQL> SHOW USER
USER IS "JIVE"
SQL> START /Oracle/software/WC10134/Discussions/database/jive_forums_oracle.sql
SQL> EXIT
14. Access the WebLogic Server Administration Console in the browser: http://myHostName:7001/console
Login using the username/password specified during the creation of "WebCenterDomain".
After authentication, ensure you are connected to the "WebCenterDomain" at the top right of the page.
Start the "DiscussionServer" if not already in RUNNING state.
15. Create a JDBC data source to connect to the "jive" schema in the database (created in steps
12 & 13). Skip this step if you intend to provide database connection information during Oracle
Discussions setup (step 19) .
+ Expand "Services" menu in the "Domain Structure" portlet (left menu) on the WebLogic Server
Administration Console
++ Expand "JDBC" and click on "Data Sources" to display a Summary of Data Sources
+++ Create a new JDBC Data Source
++++ Name: jdbc/OwcDiscussionsDS
++++ Database Type: Oracle
++++ Database Driver: *BEA's Oracle Drive (Type4 XA) Versions:
9.0.1,9.2.0,10,11 (WLS 10.3.0)
*Oracle's Driver (Thin) for Instance Connections; Versions:
9.0.1,9.2.0,10,11 (WLS 10.3.1)
++++ Next
++++ Next
++++ Database Name: orcl (Note: Use database SID, not Service
Name)
++++ Host Name: acme.us.oracle.com
++++ Port: 1521
++++ Database User Name: jive (Note: Schema created in step 12)
++++ Password: jive
++++ Confirm Password: jive
++++ Next
++++ Test Configuration
++++ Next
++++ Target Server: DiscussionServer
++++ Finish
"Activate Changes" in the Change Center (top left of page).
16. Deploy "owc_discussions" application to "DiscussionServer".
+ Go to the Summary of Servers page (WebCenterDomain => Environment => Servers). Ensure
"DiscussionServer" is in RUNNING state. Start the Server if otherwise
+ Go to the Summary of Deployments page (WebCenterDomain => Deployments)

+ "Lock & Edit" in the Change Center (top left of page) and choose to "Install" and application
+ In the "Install Application Assistant" screen, navigate using the links to the
"jive_forums_silver_5_5_20_oracle" directory under the Install Home
Path: /Oracle/software/WC10134/Discussions/jive_forums_silver_5_5_20_oracle/
+ Select " owc_discussions (open directory) "
+ Next
+ Install this deployment as an application
+ Next
+ Deployment Target: DiscussionServer
+ Next
+ Next
+ Finish
+ Save
"Activate Changes" in the Change Center (top left of page).
17. Start the deployed "owc_discussions" application
+ Go to the Summary of Deployments page (WebCenterDomain => Deployments). Notice the deployed application is in "Prepared" state.
+ Start the "owc_discussions" deployment (to service all requests)
Refresh page to confirm the state of the deployment is "Active" and health is "OK"
18. Test the installation:
+ Go to the Summary of Deployments page (WebCenterDomain => Deployments). Ensure
"owc_discussions" is in "Active" state.
+ Click on "owc_discussions" link to review its settings
+ Go to "Testing" tab
owc_discussions
Default URL : http://myHostName:17001/owc_discussions
Welcome (html): http://myHostName:17001/owc_discussions/index.html
Welcome (jsp) : http://myHostName:17001/owc_discussions/index.jsp
19. Oracle Discussion Setup:
+ Access the Oracle Discussion Setup page using the default URL:
http://myHostName:17001/owc_discussions
+ Review the Installation Checklist for success.
+ Continue
If you created a JDBC Datasource (step 15), then choose JNDI Datasource as an option
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ Database Settings: JNDI Datasource
+ Continue
+ JNDI Datasource Name: jdbc/OwcDiscussionsDS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ Continue
+ User, Group and Authentication Systems: Default
+ Continue
+ Other Settings: Update Community Name, if needed
+ Continue
+ Admin Account Setup.
Current Password: admin (default password for admin user upon installation)
New Password: manager1
+ Continue to completion
Oracle Discussions Setup screen can again be accessed using the following URL:
http://myHostName:17001/owc_discussions/admin

20. Upgrade the installation (required one-time task):
+ Access the Oracle Discussions default URL to display the Upgrade Console:
http://myHostName:17001/owc_discussions
+ Review the details on the Upgrade Console and confirm
+ Start Upgrade
21. Restart the "owc_discussions" application after a successful upgrade
+ Go to the Summary of Deployments page (WebCenterDomain => Deployments) on the
WebLogic Server Administration Console.
+ Stop (force) the "owc_discussions" application.
+ Start the application (to service all requests)
Refresh page to confirm the state of the deployment is "Active" and health is "OK"
22. Access Oracle WebCenter Discussions http://myHostName:17001/owc_discussions
Login as "admin" / "manager1"
How to Configure WebCenter Spaces and WebCenter Discussions (Jive) for Active
Directory External LDAP
In this Document
Goal
Solution
Platforms: 1-914CU;
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
Oracle WebCenter - Version: 11.1.1.1.0 to 11.1.1.2.0
Information in this document applies to any platform.
This article covers the configuration steps required to allow WebCenter Spaces and WebCenter
Discussions to connect to Active Directory LDAP server.
Pre-requisites
1. Ensure the username and password for the administrative user on AD is correct.
Note that the administrative user CN is required, not the full DN,

i.e. administrator as opposed to cn=administrator,cn=Users,dc=webcenter,dc=au,dc=oracle,dc=com.
2. To test the username and password (set PATH to use ldapbind from an ORACLE_HOME)
Using ldapbind, test you can bind as the administrative user which will be used as username in the PRINCIPLE field e.g. ldapbind -h ActiveDirectory_Host.au.oracle.com -p 389 -D "administrator@support.local" -w password1
Configure WebCenter Spaces for AD
The configuration is done via the WebLogic Server administration console, located at
http://machine:7001/console.
Follow the steps documented in (With the following changes/steps):
Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter
11g Release 1 (11.1.1)
Part Number E12405-04
Chapter 23.3.1 Reassociating the Identity Store with an External LDAP
1 . Additional Changes/Steps
Step 5
Field
Type
Step 10 Control
Flag
Value
ActiveDirectoryAuthenticator
SUFFICIENT
Description
Ensure that the Control Flag to SUFFICIENT.
Step 13 Principal administrator@support.local
User
Base DN cn=users,dc=support,dc=local
Group
Base DN dc=support,dc=local
Step 13 Use
Retrieved
User
Name as
Principal
Checked
The LDAP user administrative account. Refer pre-requisite 1 & 2 above.
Specify the DN under which your Users exist for example
Update the Group Base DN to reflect where you want to search for groups in Active
Directory
Ensure "Use Retrieved User Name as Principal" is checked.
Step 13 All Users
Filter
Can be left blank, or you can specify a query like (objectclass=user)
User
From
Name
Filter
User
Name
Attribute
&(sAMAccountName=%u)(objectclass=user)) Point to NOTE: Active Directory uses "sAMAccountName" to look up user account names. cn This is the attribute active directory uses to store the user account name.
Step 13 (
Important)
Edit
MIDDLEWARE_HOME/user_projects/domains/<DOMAIN_NAME>/config/fmwconfig/jpsconfig.xml file. Refer below.
Step 15 Ensure that the new authentication provider is on top of the list, followed by any other authenticators and

the DefaultAuthenticator placed at the end of the list.
All should have their Control Flags set to SUFFICIENT.
2. Important: Edit
MIDDLEWARE_HOME/user_projects/domains/<DOMAIN_NAME>/config/fmwconfig/jpsconfig.xml file
<!-- JPS WLS LDAP Identity Store Service Instance -->
<serviceInstance name="idstore.ldap" provider="idstore.ldap.provider">
<property name="idstore.config.provider" value="oracle.security.jps.wls.internal.idstore.WlsLdapIdStoreConfigProvider"/>
<property name="CONNECTION_POOL_CLASS" value="oracle.security.idm.providers.stdldap.JNDIPool"/>
<property name="username.attr" value="cn"/> <=== ADDED ======
<property name="user.login.attr" value="sAMAccountName"/> <=== ADDED =====
</serviceInstance>
3. Restart Admin Server and WLS_Spaces.
4. Log back into Administration console AFTER restarting and go to the myrealm, security realm ,
"Users and Groups tab" . On the Users and Groups tab, :
- the Active Directory users are listed in the Users table.
- the provider column indicates where the users came from.
If the active directory users are not listed, that indicates the configuration problem.
Configure WebCenter Discussions for AD
WebCenter Discussions (Jive) is configured for LDAP using the Jive Setup tools.
1. Stop the WLS_Services managed server.
2. Locate the file jiveHome/jive_startup.xml .
JiveHome is usually in middleware_home/user_projects/domains/<Your_Domain_Name>/config/fmwconfig/servers/WLS
_Services/owc_discussions_11.1.1.2.0
3. Backup the existing jive_startup.xml.
4. Edit jive_startup.xml and set the value to "false":
<setup>false</setup>
5. Start your WLS_Services managed server.
6. Access the Jive Forums Setup page using the url: http://machine:port/owc_discussions/admin
7. On the "Installation Checklist" page , ensure all checks are successful.
8. On the "Database Settings" page, select "JNDI Datasource"
9. On the "Datasource Settings" page: "JNDI Datasource: /jdbc/OWC_DiscussionsDS

10. On the "User, Group and Authentication Systems" page: select "LDAP"
11. On the "LDAP User System" page:
Field Value Description
Ldap Host ActiveDirectory_Host.au.oracle.com LDAP server host
Ldap Port
Base DN
389 cn=users,dc=support,dc=local
Admin DN
Admin Password
Username Field
Name Field
User Search Filter administrator@support.local xxxxxxxxxx sAMAccountName cn
(sAMAccountName={0})
LDAP server port
Specify the DN under which your
Users exist.
The LDAP user administrative account. Refer pre-requisite 1 & 2 above.
The directory administrator password.
The field name on which to perform username lookups.
The field name that holds the user's name
The filter used to query the ldap repository for users.
12: On the "LDAP User Data Storage Mode" page, Enter the same admin name used in step 11. i.e administrator
13. Finish the setup.
14 Restart WLS_Services managed server.
Troubleshooting
1. To check if the filters work correct: e.g. (&(sAMAccountName=%u)(objectclass=user))" ldapsearch -h ActiveDirectory_Host.au.oracle.com -p 389 -D "administrator@support.local" -w password1 \
-b "cn=users,dc=support,dc=local" -s sub "(&(sAMAccountName=*)(objectclass=person))" ldapsearch -h ActiveDirectory_Host.au.oracle.com -p 389 -D "administrator@support.local" -w password1 \
-b "cn=users,dc=support,dc=local" -s sub "(&(sAMAccountName=sapatelad))"
2. Refer Note:1070493.1
Active Directory Users Cannot Login to Custom WebCenter/ADF
Applications
3. WebCenter Discussions (Jive) LDAP properties can be viewed :
a. In browser on "Jive Forums Admin Console" ( http://machine:port/owc_discussions/admin)
"System" tab, then "System Properties" on the left hand menu.
b. Login to sqlplus <prefix>_discussions/password
set linesize 200

column name format a40;
column propvalue format a50;
select * from jiveproperty;
4. Jive users are in : select * from jiveuser
5. Debug Jive LDAP - enabled via "Jive Forums Admin Console" :
a. Login to "Jive Forums Admin Console", "System" tab.
On the left hand menu under "Monitoring" click on "Logs"
b. Click on Debug Tab.
c. Select Radio button enabled for " Debug Log:" and click on update button.
d. Note the location of the logs : e.g.
Log dir:
/u01/app/oracle/11g/mw11.1/user_projects/domains/WebCenter/config/fmwconfig/servers/WLS_
Services/owc_discussions_11.1.1.2.0/logs/
e. Login to "Jive Forums Admin Console", "System" tab, then "System Properties" on the left hand menu.
f. Scroll to the bottom, Add new property
Property Name: ldap.ldapDebugEnabled
Value : true
f. Restart WLS_Services.
6. Debug Jive LDAP - when "Jive Forums Admin Console" cannot be accessed :
a. Locate the file jiveHome/jive_startup.xml. Refer above for what JiveHome is.
b. Backup the existing jive_startup.xml.
c. Edit jive_startup.xml and add/edit the tags to the bottom of the file:
<log>
<debug>
<enabled>true</enabled>
</debug>
</log>
d. sqlplus <prefix>_discussions/password
insert into jiveproperty values ('ldap.ldapDebugEnabled','true');
commit;

How to Configure Webcenter 11g (PS2) with UCM 11g
Oracle WebCenter - Version: 11.1.1.3.0 and later [Release: and later ]
Information in this document applies to any platform.
Use the existing instances of WebCenter and configure them appropriately to interact with the
UCM 11g.
This documented is intended for users who are installing Oracle Enterprise Content Management
Suite for the first time and have the basic knowledge about Weblogic server administration.
This document assumes the WebCenter 11g SP2 (11.1.1.3) is installed and configured correctly.
For downloading Universal Content Management (11.1.1.3.0) access the following url: http://www.oracle.com/technetwork/middleware/downloads/fmw-11-download-092893.html
1. Create Schemas for Oracle Enterprise Content Management. (ECM)

Execute the "rcu" executable from the RCU_HOME, like this: cd rcuHome/bin
./rcu
Note:
RCU_HOME is the home where the rcu software was uncompressed.

Choose "Create" option and select all the components for Enterprise Content
Management

2. Install Oracle Enterprise Content Management

Execute the "runInstaller" from the path where the ECM software was uncompressed. like this:

Follow the screens until the installation is completed.
3. Configure Oracle Enterprise Content Management.

Execute the "config" executable from the ECM path (given in the previous step). Like this: cd $FMW_HOME/ECM_Directory/common/bin
./config.sh

You can created or Extend a domain for ECM.
If you create a new domain, be sure on the " Select Optional Configuration" step, choose the "Configure the Administration Server" option and change the default administration port. For instance 7002


Start the new Domain and the managed Servers, like this:
./startWebLogic.sh
./startManagedWeblogic.sh <UCM_Managed_Server> <admin_url> like:
./startManagedWeblogic.sh UCM_server1 http://mymachine.oracle.com:7002

Verify you can access:
http://server:16200/cs/
4. Post Steps on the Configuration of ECM 11g

Start the Oracle Content Server (if not started yet)
1. Login to the Enterprise Manager Console.
2. In the navigation tree, expand the appropriate domain name (for example,
UCM_ucm_domain).
3. Expand Content Management, then Universal Content Management, then Content
Server.
4. Select the Oracle Universal Content Management content server name (for example,
Oracle Content Server (UCM_server1)). The home page for your Oracle Content Server instance displays.
5. From the UCM menu on the Oracle Content Server page, select Control, then Start. The
Oracle Content Server is started.

Configure the Oracle Content Server Instance:
1. As the first time you access:

http://server:16200/cs/
The "Content Server Configuration" screen should appears. Like this:
The diagram above, shows the fields that should be changed according to the instance.

Server Socket Port is set to port used for socket connections on server.

Incoming Socket Connection Address needs to have IP address of server that will open up the socket connection.
Note:
If you do not see the initial configuration screen after access:
" http://server:16200/cs/", then modify the values through the Enterprise Manager Console:
Content Management
> Universal Content Management
> Content Server
>Oracle Universal Content Management.
> Right click "Oracle Universal Content Management" and select configuration
> Add Intradoc ServerPort, that is the same as Server Socket Port
> Add IP Address Filter, that is the same as Incoming Socket Connection Address
Security Filter
For additional information about how to modify those values manually, check the

Note: 1277150.1 How to Update the Content Server Parameters for UCM 11g Post initial
Configuration
2. Restart the UCM server.
5. Enable the Components Required for Integrating UCM 11g in WebCenter.

Login to http://server:16200/cs/

Expand the "Administration" Section > Select Admin Server

From the "Component Manager" window, check in:
1. Folders_g
2. WebCenterConfigure

Configure the Folders Components.

Expand the "Administration" Section > Expand the "Folder Configuration" > Select
Information Field Inherit Configuration.

Check Type, Security Group and Account


Expand the "Administration" Section > Expand the "Folder Configuration" > Select
System Default Information Field Configuration,

Ensure that the Type and Security Group have the following values:

Click on the "General Configuration" link and be sure the option: "Automatically assign a content ID on check-in" is checked it.

Restart UCM Server
6. Create the Connection from WebCenter to UCM 11g.
Once you have completed the steps mentioned above, the next step is to establish the connection from WebCenter to UCM 11g.

Access the Fusion Middleware Control ( Example: http://host:port/em)

Login as the admin user.

From the Farm Webcenter > Webcenter Spaces > Choose webcenter(WLS_Spaces)

From the popup webcenter Menu > Settings>Service Configuration


Be sure "Content Repository" is chosen and select "Add"


Fill out the fields into red square as shown in the below example:
Note:
For additional information about the parameters filled out in above example, review the following documentation:
Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter

11 Managing Content Repositories
11.3.2 Registering Content Repositories Using Fusion Middleware Control

Restart the WebCenter Spaces instance for the changes to take effect.
Note:
If the changes on an existing connection are not saved, create a new one and try again.
7. Validate the Connection from Webcenter to UCM 11g.

Personal Space : Ensure that appropriate folders are created on the UCM side for the user authenticated on WebCenter.
- Access http://servername.domain:16200/cs
- Select "Browse Content".
Notice:

You will see folder called PersonalSpaces, with the user weblogic and selecting its name will show any documents created in personal space.

Also notice folder called MyWebCenterSpaces, this is the root folder used when registering the UCM Server with WebCenter. Under here will be a folder for each Group
Space using the Document Service, and selecting on them will see the folders and documents created

Personal Space : The user can upload a document to UCM from WebCenter

Personal Space : The user can retrieve and open the documents in UCM from
WebCenter

Group Space : Created a group space and ensured that appropriate folder is created on the UCM backend
8. Configure the credential store to use LDAP.

If WebCenter and UCM11g are configured in different domains, you need to ensure both domains are setup to share the same Identity Store.
If using the same domain, then only you need to configure that domain to use the desired
Identity Store if not already done.
To be safe, before you create the LDAP authenticator, back up the the following configuration files:
FMW_HOME/user_projects/domains/domain_name/config/config.xml
FMW_HOME/user_projects/domains/domain_name/config/fmwconfig/jps-config.xml
FMW_HOME/user_projects/domains/domain_name/config/fmwconfig/system-jazn-data.xml
FMW_HOME/user_projects/domains/domain_name/AdminServer/security/boot.properties
1. Log in to the WebLogic Server Console.
2. Click the Security Realms link on the left navigational bar.
3. Click the myrealm default realm entry to configure it.
4. Open the "Providers" tab within the realm.
5. Observe that there is a DefaultAuthenticator provider configured for the realm.
6. Click the "New" button to add a new provider.
7. Enter a name for the provider such as OIDAuthenticator or OVDAuthenticatordepending on whether Oracle Internet Directory or Oracle Virtual Directory will be used.
8. Select the OracleInternetDirectoryAuthenticator or OracleVirtualDirectoryAuthenticator type from the list of authenticators depending on whether Oracle Internet Directory or
Oracle Virtual Directory will be used.
9. Click OK.
10. In the Providers screen, click the newly created Authenticator.
11. Set the control flag to SUFFICIENT. This indicates that if a user can be authenticated successfully by this authenticator, then it should accept that authentication and should not continue to invoke any additional authenticators. If the authentication fails, it will fall through to the next authenticator in the chain.
Make sure all subsequent authenticators also have their control flag set to SUFFICIENT; in particular, check the DefaultAuthenticator and set that to SUFFICIENT.
12. Click Save to save this setting.
13. Open the "Provider Specific" tab to enter the details for the LDAP server.
14. Click "Activate Changes" to propagate the changes
Setting the Order of Providers Reorder the OID/OVD Authenticator and Default
Authenticator and ensure that the control flag for each authenticator is set as follows:
■ OID LDAP Authenticator: SUFFICIENT
■ Default Authenticator: SUFFICIENT
15. The Admin Server and the Managed Servers need to be restarted for the changes to take effect.
Note:
For detail information about Configuring the Identity Store, review the following documentation:
Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter
24 Configuring the Identity Store
9. Validate the Instances with the new identify store. Repeat the steps mentioned in Task 7, in previous step.

When an Announcement component to a page in a Group Space, the default behaviour is for this component to display announcements from the Announcement Manager associated with this
Group same Space.
It's possible to edit the properties of this component to point to an Announcement Manager in another Group Space. This is done by editing the component properties and setting the Forum ID to point to the Forum Id associated with that other Group Space.
This works as expected for the announcements themselves.
However, other icons do not work as expected - Announcement Manager and RSS Feed icons on this component still point to the original default Announcement manager for the current space.
The announcement messages and the edit icons point to different places.
Is there a way to get these icons to point to the announcements from a different space?
The ultimate aim is to have three different announcements portlets on a single page pointing to three different announcements from different group spaces.
There is information on Announcements in the Oracle
�
Fusion Middleware User's Guide for
Oracle WebCenter
11g Release 1 (11.1.1)
Part Number E10149-02
13.1 What You Should Know About the Announcements Service
This is explained in this documentation:
In group spaces, announcements are scoped to the group space where you create them. In personal space pages, announcements are scoped application-wide, to all logged-in
(authenticated) users.
> The behavior we see is intended behavior. In a Group Spaces, the announcements taskflow has been designed to show the group spaces announcement and not the other group spaces ones.
The situation is different for Personal Spaces, so depending on your requirements, it may be possible to use Personal Space instead of Group Space.

Webcenter Announcement Viewer Task Flow Not Able To Show More Then 10
Announcements
Oracle WebCenter - Version: 11.1.1.2.0 to 11.1.1.4.0 - Release: 11g to 11g
Information in this document applies to any platform.
The current WebCenter 11.1.1.3 PS2 Bundle Patch 3 instance of Spaces has Announcement taskflow which always displays fixed number of 10 announcements in the taskflow all the time. Is there a taskflow parameter we can set in to the taskflow to tune in the display on number of
Announcements to be displayed in the taskflow?
The feature is implemented in WebCenter 11.1.1.4.0 (PS3).
Till WebCenter 11.1.1.3 release (PS2) does not have this parameter for Announcement Viewer taskflow.
However, the WebCenter PS3, which was not released at the time this note was written, has the parameter under Announcement viewer taskflow parameter called "Number of Announcements to show".
Perform below steps in PS3 to incorporate the requirement:
1. Edit the Announcement region
2. In the Component Properties: Announcements --> Go to "Parameters" --> "Number of
Announcements to show"
Please specify the number of Announcements you want to show in the parameter field.
There are other enhanced parameters as below:

Expand All Announcements in Extended Mini View

Number of Expanded Announcements

Content View Only

Hide Toolbar
 Navigate to Announcement Viewer

Number of Announcements on Extended Mini View

Forum ID

Announcement Length

Number of Announcements to show

Fixed Bugs List

11g Release 1 (11.1.1.2.0) Bundle Patch 1 - Patch 9313626

11g Release 1 (11.1.1.2.0) Bundle Patch 2 - Patch 9377463

11g Release 1 (11.1.1.2.0) Bundle Patch 3 - Patch 9573913

11g Release 1 (11.1.1.2.0) Bundle Patch 4 - Patch 9701496
Last Updated : August 2010
This document lists all bugs that are fixed in Oracle WebCenter 11 g Release 1 Patch Set 1
(11.1.1.2.0) Bundle Patches. Bugs are sorted by bug number, as well as by component area.
This section contains the following bug lists:

Section 1.1, "Bugs Fixed by Number"

Section 1.2, "Activity Streaming"

Section 1.3, "Annoucements"

Section 1.4, "Blogs"

Section 1.5, "Composer"

Section 1.6, "Content Integration"

Section 1.7, "Design-Time"

Section 1.8, "Events"

Section 1.9, "Lifecycle"

Section 1.10, "Lists"

Section 1.11, "Mail"

Section 1.12, "People Connection"

Section 1.13, "Portlet Services"

Section 1.14, "Search"

Section 1.15, "Spaces"

Section 1.16, "Tagging"

Section 1.17, "Wiki"

The following table lists all bugs that were fixed for all components in this release of Oracle
WebCenter Patchset 1 (11.1.1.2.0), in numerical order.
Bug
Numbe r
853255
3
Component
Annoucement s
863229
9
884791
2
901593
0
907662
4
911475
7
911593
5
Portlet
Services
Search
Spaces
Tagging
Lifecycle
Lifecycle
Bundle
Patch
Inclusio n
11.1.1.2.
4
11.1.1.2.
1
11.1.1.2.
4
11.1.1.2.
3
11.1.1.2.
2
11.1.1.2.
1
11.1.1.2.
1
Version
Fixed Description
11.1.1.4.
0
When an Announcement is created for a future date it will not be listed on the Announcement main view page.
11.1.1.3.
0
When using Portlets that use UIX rendering technology, such as E-Business Suite Portlets, in
WebCenter, there can be collisions between the definitions of styles used by the Portlet and those used in the consuming page. If the portlet is rendered in-line (i.e. not in an iframe) this can adversely affect the appearance and behaviour of the page. If the portlet is in an iframe, this can adversely affect the appearance of the portlet but will not affect the consuming page.
11.1.1.4.
0
From content from various data sources contained in the UCM, only WebCenter Spaces content should be return in the search results of
Search service.
Note 1102904.1 - WebCenter Spaces: How to
Search the Whole UCM Repository or Limit the
Search onto the WebCenter Spaces within UCM
11.1.1.3.
0
11.1.1.3.
0
There is a problem caused within Group Spaces metadata being not refreshed during the upgrade from 11.1.1.2.0 to 11.1.1.3.0. The fix adds an new WLST command to do it so - refreshGroupSpaceCache . Refer to Bug
9278002.
Note 1077490.1 - After Upgrade to WebCenter
11.1.1.2.0, Group Spaces Are Not Displayed in
MyGroupSpaces
In the document tagging-personalview.xml
there are multiple elements with the same ID tagging-personal-view. This error made
Taskflow customization in JDeveloper unusable.
11.1.1.3.
0
Changed the Portlet Container template name to wsrp minimal to better support SES integration and patching.
11.1.1.3.
0
Apply the Portlet Container template. The
Managed Server WLS_Portlet will be created.
This will better support SOA integration.

Bug
Numbe r
914395
7
Component
Design-Time
918766
8
925816
1
925910
7
925954
6
926264
9
926334
4
926368
1
927144
4
927445
6
Design-Time
Spaces
People
Connection
Spaces
Events
Mail
Mail
Mail
Spaces
Bundle
Patch
Inclusio n
11.1.1.2.
1
11.1.1.2.
1
11.1.1.2.
1
11.1.1.2.
1
11.1.1.2.
1
11.1.1.2.
1
11.1.1.2.
1
11.1.1.2.
1
11.1.1.2.
1
11.1.1.2.
1
Version
Fixed Description
11.1.1.3.
0
The customization extension bundle includes some webcenter framework jars. These jars no longer need to be included in this bundle because they are already included in the webcenter extension bundle.
11.1.1.3.
0
List and event service taskflows are not available to customize. Made them available within the customization extension bundle.
11.1.1.3.
0
Creating a Group Space containing a turkish 'I' within its name with the browser locale set to
"turkish", it throws an error.
11.1.1.3.
0
Add a second message to someone's message board, the text from the the first message is retained.
11.1.1.3.
0
After login to Spaces, when going to Discussions,
Announcements or UCM you'll see the username instead of first name and last name.
11.1.1.3.
0
Error dialog popped when add an all day event of a Group Space to the Personal calendar.
11.1.1.3.
0
When replying to emails from WebCenter Spaces a new window opens but does not have the To: field populated with the email address of the person that sent the email. It is blank.
11.1.1.3.
0
Adding the email component to a spaces page is only showing messages when the provided dropdown list is set to all. If the dropdown is changed to today, or another value, it does not show messages.
11.1.1.3.
0
This issue only occurs when using Outlook and the e-mail server is setup to have email addresses in the form: lastname, firstname. To avoid this issue, semi-colon should be used as email address separator, by setting the property named 'address.delimiter' to ";".
Note 1057384.1 - E-Mail To: List for WebCenter?
Spaces is Restricted to Comma for the Delimiter
11.1.1.3.
0
When a WebCenter R1 instance is migrated to
PS1 there are issues which can be seen.
Performing a refresh from WebCenter Spaces over the Administration > Group Space, the refresh does not update the tables and no group spaces are seen in the screen.
Creating a Group Space or adding members in
Group Space throws the following error: "Errors were encountered in creating group space.".

Bug
Numbe r Component
927494
5
927800
2
928000
1
928288
6
930325
4
People
Connection
Spaces
Spaces
Spaces
Mail
Bundle
Patch
Inclusio n
11.1.1.2.
2
11.1.1.2.
1
11.1.1.2.
2
11.1.1.2.
3
11.1.1.2.
1
Version
Fixed Description
When logged in as WebCenter Spaces administrator in Administration > Group Spaces screen, the export/import, bulk delete, setting the
Group Spaces active/closed, online/offline options are not available. Also none of the Group
Spaces are visible in the My Group Spaces or
WebCenter Spaces over the Administration >
Group Spaces screen.
11.1.1.3.
0
Places in PeopleConnections & Spaces that show a list of several items, and which were earlier showing only upto 25 items even if there were more items, (viz. list of reportees in User
Profile taskflows, list of services & connection lists & group spaces in Activity Stream settings, list of invitations & list of connection lists in the
Connections Main View taskflow), will now show all the items instead of just upto 25.
11.1.1.3.
0
After migrating a WebCenter Spaces R1 instance to PS1 the Group Space metadata should be refreshed. The webcenter administrator should click the Refresh button in the Administration >
Group Space screen.
To refresh the security-related data, the webcenter administrator should navigate to individual Group Space > Settings > Members screen and click on the Refresh button.
A WLST command has been created for this case - refreshGroupSpaceCache .
11.1.1.3.
0
After configuring the Personal Spaces tab to be labeled Home it sometimes shows as
#{'Home'} . When this happens it remains that way till you logout the session. After logout and login it changes back to the normal display of
Home.
11.1.1.3.
0
In the getGroupSpaceMetadataWithoutSecurity
() method, there were some issues with populating the customAttribute and not flushing the changes. So, when tests performed, like create Group Space and fetch all the Group
Space metadata, for the last group whose data was not flushed was resulting in
ConcurrantMOChangeException .
11.1.1.3.
0
Mail messages coming from the server based on received date may be wrong. We need to use a comparator to compare against the received date rather than assuming the server is giving us the message based on the received date which may

Bug
Numbe r Component
930542
2
930583
8
935864
3
937464
6
937857
7
938008
4
948685
7
949545
9
949888
7
Activity
Streaming
Spaces
Mail
Spaces
Mail
Lifecycle
Wiki
Blogs
Spaces
Bundle
Patch
Inclusio n
11.1.1.2.
1
11.1.1.2.
2
11.1.1.2.
3
11.1.1.2.
2
11.1.1.2.
2
11.1.1.2.
3
11.1.1.2.
3
11.1.1.2.
4
11.1.1.2.
4
Version
Fixed Description
11.1.1.3.
0 be incorrect.
Create a Group Space GS1 and add user A and enterprise role X as members of Group Space
GS1. User B is a member of Enterpise Role X and is member of Group Space GS1 via this role.
User B is not able to see any data related to
Activity Stream for the Group Space GS1.
11.1.1.3.
0
After login to Spaces, when going to My Group
Spaces, you'll see the user name instead of first name and last name. With this fix you will see a person's display name instead of his user id.
11.1.1.3.
0
If you configure WebCenter with MS Exchange
Server 2007 and you try to send an email, It will fail with error "connection to server failed". With this fix, it uses now the authentication with SMTP protocol to get through this failure.
11.1.1.3.
0
When the WebCenter Spaces application is redeployed in a later release the seeded businessRolePages/pages.xml in the MAR gets overwriten. Refer to Bug 9380084.
11.1.1.3.
0
11.1.1.3.
0
When older messages are moved into the mail folder i.e inbox, it will get moved to the top of the list. To re-sort it based on receiving date, you need to logout and relogin again onto
WebCenter.
The MAR file within the EAR ( webcenter.ear
) should only change the checksum if its contents changes.
11.1.1.3.
0 (*)
When a wiki or blog page is created with special characters in the name, the text is not encoded properly.
11.1.1.4.
0 (*)
This fixes the acces to Blog RSS links with basic authentication set up, when trying to use external readers.
Note 1108910.1 - Wiki Blog RSS Are Not
Displayed Correctly in WebCenter Spaces with
SSO Enabled
11.1.1.4.
0
This is a new behavior introduced through which customers can decide to disable the remembrance of last accessed page behavior within a session.
Note 1102606.1 - WebCenter Spaces: disableLastAccessPageBehavior & disableLastAccessPageBehavior.withinSession

Bug
Numbe r
950039
4
950104
0
950158
3
Spaces
950178
2
Annoucement s
950973
4
Component
Content
Integration
Spaces
Annoucement s
Bundle
Patch
Inclusio n
11.1.1.2.
3
11.1.1.2.
4
11.1.1.2.
4
11.1.1.2.
4
11.1.1.2.
4
Version
Fixed Description
11.1.1.3.
0
When adding an Enterprise Role to a Group
Space, if all services support Enterprise Roles, the group will be added to the Group Space. If one of the services does not support Enterprise
Roles, the users in the group will be added onto the Group Space and it will be logged that the service does not support Enterprise Roles.
Due to this, the user may encounter the issue that on one attempt the group is added to the
Group Space, yet another time, the users in the group are added, yet nothing in the system has changed.
Looking at the logs, there will be contradicting entries indicating that Document Library does support Enterprise Role Mapping (when the group is added to the Group Space), and also that it does not (when the users of the group are added to the Group Space).
11.1.1.4.
0
The delete message used when deleting a Group
Space page added onto a Personal Space
(cross-scoped page) was the same as which gets displayed when deleting any other page (scoped page). Deleting the Group Space page added onto Personal Spaces actually doesn't delete the page but just deletes the link from Personal
Spaces, so the delete message was misleading.
The fix corrects the message to indicate that the delete will just remove the link from Personal
Spaces.
11.1.1.4.
0
Creating a page with the same name is possible, hence the URL is the same for all pages with the same name. The fix verifies if the name entered is already used by an existing page before creating and if yes, it pops up an error message and let the user to choose another name. The same for renaming a page and copy a page.
11.1.1.4.
0
When opening the Announcement Manager from the Announcements portlet within the Home page
(from a Group Project template), it opens a page named Announcement Viewer instead of
Announcements, which is misleading.
11.1.1.4.
0
Listing expired announcements is not possible.
Eg, users may not realise that choosing an announcement to expire means that there will be no record of that announcement after the chosen date. This fix allows expired announcements to be queried and be seen.
Note 1106903.1 - Announcement with future date

Bug
Numbe r Component
952369
1
952777
1
953023
1
953439
5
954096
8
957718
3
957738
4
958777
2
961234
4
Blogs
Wiki
Wiki
Content
Integration
Spaces
Spaces
Composer
Lists
Wiki
Bundle
Patch
Inclusio n
11.1.1.2.
3
11.1.1.2.
3
11.1.1.2.
3
11.1.1.2.
4
11.1.1.2.
4
11.1.1.2.
4
11.1.1.2.
4
11.1.1.2.
4
11.1.1.2.
4
Version
Fixed Description
11.1.1.3.
0 (*) could not be edit/delete/modify
The URLs need to have the domain/page names encoded when the links are created. New methods were added to encode the names and the they are now used to create the href links.
Refer to Bug 9486857.
11.1.1.3.
0 (*)
When the wiki page is created and the user clicks on the link in the menu an error page appears in
Internet Explorer. The user is not able to access the wiki page. This is for the page name encoding.
11.1.1.3.
0 (*)
When the wiki page is created and the user clicks on the link in the menu an error page appears in
Internet Explorer. The user is not able to access the wiki page. This is for the domain encoding.
11.1.1.4.
0
The Document Library "Recent Documents" taskflow groupSpace parameter default value was not being set properly when the taskflow was dropped onto a page in a Group Space.
11.1.1.4.
0
In IE7/8 some connection names were getting cut off with some specific skins. This fix solves the issue so that the display name for the connections is not truncated for all skins.
11.1.1.4.
0
Users matching a specified search criteria (First
Last* / Fir Las / First Last / First/Last/Fi*/Las*) returned different set of users across "Global
Search Bar", in "Find and Invite Connections", in
"My Connections" and in "People Picker". This fix solves the issue so that the people search across the four components returns a consistent set of results.
11.1.1.4.
0
When editing a "rich text" component added to a page using Oracle Composer, the background color of the editable area is always white, obscuring the background of the page behind the text component. Now, with this change, the background color of the rich text editor is transparent, which lets the page color to come through.
11.1.1.4.
0
Adhoc filtering in the list view now allows filtering on columns with data type Person, as well as data type String.
11.1.1.4.
0 (*)
The import domain from a Wiki is failing because it is not finding a query that it is expecting
( getVersionsByNodeAndNumber ).

Bug
Numbe r
961249
3
Component
Wiki
Bundle
Patch
Inclusio n
11.1.1.2.
4
Version
Fixed Description
11.1.1.4.
0 (*)
After upgrading from a file-based repository onto a database repository it is needed to run a script to update the METADATA table, in order to see the text in the Rich Text Editor.
Note 1105862.1 - For Imported Wiki Domains its
Imported Pages do NOT have the Rich Text
Editor (RTE) Bar Enabled
966467
1
Wiki 11.1.1.2.
4
11.1.1.4.
0 (*)
Using WebCenter Spaces and searching for a
Wiki page within the right upper corner, nothing is returned within the UI, eg, the popup is shown, but it seems the search on Wikis is not working.
967726
1
Content
Integration
11.1.1.2.
4
11.1.1.4.
0
When searching for content in UCM which has accounts other than those created by
WebCenter, you may see "Results not currently available" instead of search results.
(*) - The functionality will be changed in Oracle WebCenter 11.1.1.4.0.
The following table lists all Activity Streaming bugs that are fixed within Oracle WebCenter
Patchset 1 (11.1.1.2.0) Bundle Patches.
Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description
11.1.1.2.1 11.1.1.3.0 9305422 Create a Group Space GS1 and add user A and enterprise role X as members of Group Space GS1. User B is a member of Enterpise Role X and is member of Group
Space GS1 via this role. User B is not able to see any data related to Activity Stream for the Group Space GS1.
The following table lists all Annoucements bugs that are fixed within Oracle WebCenter Patchset
1 (11.1.1.2.0) Bundle Patches.
Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description
11.1.1.2.4 11.1.1.4.0 8532553 When an Announcement is created for a future date it will not be listed on the Announcement main view page.
11.1.1.2.4 11.1.1.4.0 9501782 When opening the Announcement Manager from the
Announcements portlet within the Home page (from a

Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description
Group Project template), it opens a page named
Announcement Viewer instead of Announcements, which is misleading.
11.1.1.2.4 11.1.1.4.0 9509734 Listing expired announcements is not possible. Eg, users may not realise that choosing an announcement to expire means that there will be no record of that announcement after the chosen date. This fix allows expired announcements to be queried and be seen.
Note 1106903.1 - Announcement with future date could not be edit/delete/modify
The following table lists all Blogs bugs that are fixed within Oracle WebCenter Patchset 1
(11.1.1.2.0) Bundle Patches.
Bundle
Patch
Inclusion
11.1.1.2.4
Version
Fixed
11.1.1.4.0
(*)
Bug
Number Description
9495459 This fixes the acces to Blog RSS links with basic authentication set up, when trying to use external readers.
Note 1108910.1 - Wiki Blog RSS Are Not Displayed
Correctly in WebCenter Spaces with SSO Enabled
11.1.1.2.3
11.1.1.3.0
(*)
9523691 The URLs need to have the domain/page names encoded when the links are created. New methods were added to encode the names and the they are now used to create the href links. Refer to Bug 9486857.
(*) - The functionality will be changed in Oracle WebCenter 11.1.1.4.0.
The following table lists all Composer bugs that are fixed within Oracle WebCenter Patchset 1
(11.1.1.2.0) Bundle Patches.
Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description
11.1.1.2.4 11.1.1.4.0 9577384 When editing a "rich text" component added to a page using
Oracle Composer, the background color of the editable area is always white, obscuring the background of the page behind the text component. Now, with this change, the background color of the rich text editor is transparent, which lets the page color to come through.

The following table lists all Content Integration bugs that are fixed within Oracle WebCenter
Patchset 1 (11.1.1.2.0) Bundle Patches.
Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description
11.1.1.2.3 11.1.1.3.0 9500394 When adding an Enterprise Role to a Group Space, if all services support Enterprise Roles, the group will be added to the Group Space. If one of the services does not support
Enterprise Roles, the users in the group will be added onto the Group Space and it will be logged that the service does not support Enterprise Roles.
Due to this, the user may encounter the issue that on one attempt the group is added to the Group Space, yet another time, the users in the group are added, yet nothing in the system has changed.
Looking at the logs, there will be contradicting entries indicating that Document Library does support Enterprise
Role Mapping (when the group is added to the Group
Space), and also that it does not (when the users of the group are added to the Group Space).
11.1.1.2.4 11.1.1.4.0 9534395 The Document Library "Recent Documents" taskflow groupSpace parameter default value was not being set properly when the taskflow was dropped onto a page in a
Group Space.
11.1.1.2.4
11.1.1.4.0 9677261 When searching for content in UCM which has accounts other than those created by WebCenter, you may see
"Results not currently available" instead of search results.
The following table lists all Design-Time bugs that are fixed within Oracle WebCenter Patchset 1
(11.1.1.2.0) Bundle Patches.
Bundle
Patch
Inclusion
11.1.1.2.1
11.1.1.2.1
Version
Fixed
Bug
Number Description
11.1.1.3.0 9143957 The customization extension bundle includes some webcenter framework jars. These jars no longer need to be included in this bundle because they are already included in the webcenter extension bundle.
11.1.1.3.0 List and event service taskflows are not available to customize. Made them available within the customization extension bundle.

The following table lists all Events bugs that are fixed within Oracle WebCenter Patchset 1
(11.1.1.2.0) Bundle Patches.
Bundle Patch
Inclusion
11.1.1.2.1
Version
Fixed
Bug
Number Description
11.1.1.3.0 9262649 Error dialog popped when add an all day event of a
Group Space to the Personal calendar.
The following table lists all Lifecycle bugs that are fixed within Oracle WebCenter Patchset 1
(11.1.1.2.0) Bundle Patches.
Bundle Patch
Inclusion
11.1.1.2.1
Version
Fixed
Bug
Number Description
11.1.1.3.0 9114757 Changed the Portlet Container template name to wsrp minimal to better support SES integration and patching.
11.1.1.2.1
11.1.1.2.3
11.1.1.3.0 9115935 Apply the Portlet Container template. The Managed
Server WLS_Portlet will be created. This will better support SOA integration.
11.1.1.3.0 9380084 The MAR file within the EAR ( webcenter.ear
) should only change the checksum if its contents changes.
The following table lists all Lists bugs that are fixed within Oracle WebCenter Patchset 1
(11.1.1.2.0) Bundle Patches.
Bundle Patch
Inclusion
11.1.1.2.4
Version
Fixed
Bug
Number Description
11.1.1.4.0 9587772 Adhoc filtering in the list view now allows filtering on columns with data type Person, as well as data type
String.
The following table lists all Mail bugs that are fixed within Oracle WebCenter Patchset 1
(11.1.1.2.0) Bundle Patches.
Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description
11.1.1.2.1 11.1.1.3.0 9263344 When replying to emails from WebCenter Spaces a new

Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description window opens but does not have the To: field populated with the email address of the person that sent the email. It is blank.
11.1.1.2.1 11.1.1.3.0 9263681 Adding the email component to a spaces page is only showing messages when the provided dropdown list is set to all. If the dropdown is changed to today, or another value, it does not show messages.
11.1.1.2.1 11.1.1.3.0 9271444 This issue only occurs when using Outlook and the e-mail server is setup to have email addresses in the form: lastname, firstname. To avoid this issue, semi-colon should be used as e-mail address separator, by setting the property named 'address.delimiter' to ";".
Note 1057384.1 - E-Mail To: List for WebCenter? Spaces is
Restricted to Comma for the Delimiter
11.1.1.2.1 11.1.1.3.0 9303254 Mail messages coming from the server based on received date may be wrong. We need to use a comparator to compare against the received date rather than assuming the server is giving us the message based on the received date which may be incorrect.
11.1.1.2.3 11.1.1.3.0 9358643 If you configure WebCenter with MS Exchange Server 2007 and you try to send an email, It will fail with error
"connection to server failed". With this fix, it uses now the authentication with SMTP protocol to get through this failure.
11.1.1.2.2 11.1.1.3.0 9378577 When older messages are moved into the mail folder i.e inbox, it will get moved to the top of the list. To re-sort it based on receiving date, you need to logout and relogin again onto WebCenter.
The following table lists all Page Service bugs that are fixed within Oracle WebCenter Patchset 1
(11.1.1.2.0) Bundle Patches.
Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description
11.1.1.2.1 11.1.1.3.0 9259107 Add a second message to someone's message board, the text from the the first message is retained.
11.1.1.2.2 11.1.1.3.0 9274945 Places in PeopleConnections & Spaces that show a list of several items, and which were earlier showing only upto 25 items even if there were more items, (viz. list of reportees in
User Profile taskflows, list of services & connection lists & group spaces in Activity Stream settings, list of invitations & list of connection lists in the Connections Main View

Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description taskflow), will now show all the items instead of just upto 25.
The following table lists all Portlet Services bugs that are fixed within Oracle WebCenter Patchset
1 (11.1.1.2.0) Bundle Patches.
Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description
11.1.1.2.1 11.1.1.3.0 8632299 When using Portlets that use UIX rendering technology, such as E-Business Suite Portlets, in WebCenter, there can be collisions between the definitions of styles used by the
Portlet and those used in the consuming page. If the portlet is rendered in-line (i.e. not in an iframe) this can adversely affect the appearance and behaviour of the page. If the portlet is in an iframe, this can adversely affect the appearance of the portlet but will not affect the consuming page.
The following table lists all Search bugs that are fixed within Oracle WebCenter Patchset 1
(11.1.1.2.0) Bundle Patches.
Bundle Patch
Inclusion
11.1.1.2.4
Version
Fixed
Bug
Number Description
11.1.1.4.0 8847912 From content from various data sources contained in the
UCM, only WebCenter Spaces content should be return in the search results of Search service.
Note 1102904.1 - WebCenter Spaces: How to Search the Whole UCM Repository or Limit the Search onto the
WebCenter Spaces within UCM
The following table lists all Spaces bugs that are fixed within Oracle WebCenter Patchset 1
(11.1.1.2.0) Bundle Patches.
Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description

Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description
11.1.1.2.3 11.1.1.3.0 9015930 There is a problem caused within Group Spaces metadata being not refreshed during the upgrade from 11.1.1.2.0 to
11.1.1.3.0. The fix adds an new WLST command to do it so - refreshGroupSpaceCache . Refer to Bug 9278002.
Note 1077490.1 - After Upgrade to WebCenter 11.1.1.2.0,
Group Spaces Are Not Displayed in MyGroupSpaces
11.1.1.2.1 11.1.1.3.0 9258161 Creating a Group Space containing a turkish 'I' within its name with the browser locale set to "turkish", it throws an error.
11.1.1.2.1 11.1.1.3.0 9259546 After login to Spaces, when going to Discussions,
Announcements or UCM you'll see the username instead of first name and last name.
11.1.1.2.1 11.1.1.3.0 9274456 When a WebCenter R1 instance is migrated to PS1 there are issues which can be seen.
Performing a refresh from WebCenter Spaces over the
Administration > Group Space, the refresh does not update the tables and no group spaces are seen in the screen.
Creating a Group Space or adding members in Group Space throws the following error: "Errors were encountered in creating group space.".
When logged in as WebCenter Spaces administrator in
Administration > Group Spaces screen, the export/import, bulk delete, setting the Group Spaces active/closed, online/offline options are not available. Also none of the Group Spaces are visible in the My Group Spaces or WebCenter Spaces over the
Administration > Group Spaces screen.
11.1.1.2.1 11.1.1.3.0 9278002 After migrating a WebCenter Spaces R1 instance to PS1 the
Group Space metadata should be refreshed. The webcenter administrator should click the Refresh button in the
Administration > Group Space screen.
To refresh the security-related data, the webcenter administrator should navigate to individual Group Space >
Settings > Members screen and click on the Refresh button.
A WLST command has been created for this case - refreshGroupSpaceCache .
11.1.1.2.2 11.1.1.3.0 9280001 After configuring the Personal Spaces tab to be labeled Home it sometimes shows as #{'Home'} . When this happens it remains that way till you logout the session. After logout and login it changes back to the normal display of Home.
11.1.1.2.3 11.1.1.3.0 9282886 In the getGroupSpaceMetadataWithoutSecurity() method, there were some issues with populating the customAttribute and not flushing the changes. So, when tests performed, like create Group Space and fetch all the Group
Space metadata, for the last group whose data was not flushed was resulting in ConcurrantMOChangeException .
11.1.1.2.2 11.1.1.3.0 9305838 After login to Spaces, when going to My Group Spaces, you'll see the user name instead of first name and last name. With this fix you will see a person's display name instead of his user

Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description id.
11.1.1.2.2 11.1.1.3.0 9374646 When the WebCenter Spaces application is redeployed in a later release the seeded businessRolePages/pages.xml in the
MAR gets overwriten. Refer to Bug 9380084.
11.1.1.2.4 11.1.1.4.0 9498887 This is a new behavior introduced through which customers can decide to disable the remembrance of last accessed page behavior within a session.
Note 1102606.1 - WebCenter Spaces: disableLastAccessPageBehavior & disableLastAccessPageBehavior.withinSession
11.1.1.2.4 11.1.1.4.0 9501040 The delete message used when deleting a Group Space page added onto a Personal Space (cross-scoped page) was the same as which gets displayed when deleting any other page
(scoped page). Deleting the Group Space page added onto
Personal Spaces actually doesn't delete the page but just deletes the link from Personal Spaces, so the delete message was misleading. The fix corrects the message to indicate that the delete will just remove the link from Personal Spaces.
11.1.1.2.4 11.1.1.4.0 9501583 Creating a page with the same name is possible, hence the
URL is the same for all pages with the same name. The fix verifies if the name entered is already used by an existing page before creating and if yes, it pops up an error message and let the user to choose another name. The same for renaming a page and copy a page.
11.1.1.2.4 11.1.1.4.0 9540968 In IE7/8 some connection names were getting cut off with some specific skins. This fix solves the issue so that the display name for the connections is not truncated for all skins.
11.1.1.2.4 11.1.1.4.0 9577183 Users matching a specified search criteria (First Last* / Fir Las /
First Last / First/Last/Fi*/Las*) returned different set of users across "Global Search Bar", in "Find and Invite Connections", in
"My Connections" and in "People Picker". This fix solves the issue so that the people search across the four components returns a consistent set of results.
The following table lists all Tagging bugs that are fixed within Oracle WebCenter Patchset 1
(11.1.1.2.0) Bundle Patches.
Bundle
Patch
Inclusion
11.1.1.2.2
Version
Fixed
Bug
Number Description
11.1.1.3.0 9076624 In the document tagging-personal-view.xml
there

Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description are multiple elements with the same ID tagging-personalview. This error made Taskflow customization in
JDeveloper unusable.
The following table lists all Wiki bugs that are fixed within Oracle WebCenter Patchset 1
(11.1.1.2.0) Bundle Patches.
Bundle
Patch
Inclusion
Version
Fixed
Bug
Number Description
11.1.1.2.3 11.1.1.3.0
(*)
9486857 When a wiki or blog page is created with special characters in the name, the text is not encoded properly.
11.1.1.2.3 11.1.1.3.0
(*)
9527771 When the wiki page is created and the user clicks on the link in the menu an error page appears in Internet Explorer. The user is not able to access the wiki page. This is for the page name encoding.
11.1.1.2.3 11.1.1.3.0
(*)
9530231 When the wiki page is created and the user clicks on the link in the menu an error page appears in Internet Explorer. The user is not able to access the wiki page. This is for the domain encoding.
11.1.1.2.4 11.1.1.4.0
(*)
9612344 The import domain from a Wiki is failing because it is not finding a query that it is expecting
( getVersionsByNodeAndNumber ).
11.1.1.2.4 11.1.1.4.0
(*)
9612493 After upgrading from a file-based repository onto a database repository it is needed to run a script to update the
METADATA table, in order to see the text in the Rich Text
Editor.
Note 1105862.1 - For Imported Wiki Domains its Imported
Pages do NOT have the Rich Text Editor (RTE) Bar Enabled
11.1.1.2.4 11.1.1.4.0
(*)
9664671 Using WebCenter Spaces and searching for a Wiki page within the right upper corner, nothing is returned within the
UI, eg, the popup is shown, but it seems the search on Wikis is not working.
(*) - The functionality will be changed in Oracle WebCenter 11.1.1.4.0.
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in

HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other marketleading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program
Web site at http://www.oracle.com/accessibility/ .
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that
Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html
or visit http://www.oracle.com/accessibility/support.html
if you are hearing impaired.
Oracle WebCenter Fixed Bugs List, 11 g Release 1 Patch Set 1 (11.1.1.2.0) Bundle Patches.
Copyright 2010 Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or
"commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable
Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December
2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
The following products are included with Oracle Fusion Middleware 11g R1 (11.1.1.4.0):

Oracle WebLogic Server 11g R1 (10.3.4)

Oracle Repository Creation Utility 11g R1 (11.1.1.4.0)

Oracle SOA Suite 11g R1 (11.1.1.4.0)

Oracle WebCenter 11g R1 (11.1.1.4.0)

Oracle Identity Management 11g R1 (11.1.1.4.0)

Oracle Forms, Reports, Portal & Discoverer 11g R1 (11.1.1.4.0)

Oracle Web-Tier Utilities 11g R1 (11.1.1.4.0)

Oracle JDeveloper & Application Development Runtime 11g R1 (11.1.1.4.0)

Oracle Enterprise Content Management 11g R1 (11.1.1.4.0)

Oracle Enterprise Repository 11g R1 (11.1.1.4.0)

Oracle Business Process Management 11g R1 (11.1.1.4.0)

Oracle Complex Event Processing 11g R1 (11.1.1.4.0)

Oracle Application Integration Architecture Foundation Pack 11g R1 (11.1.1.4.0)

Oracle Service Bus 11g R1 (11.1.1.4
Oracle Fusion Middleware11g R1 (11.1.1.5.0) has been made available for the following products:

!! Click Here for All Patch Set and Full Media Downloads !!

Oracle WebLogic Server 11g R1 (10.3.5)

Oracle Fusion Middleware Repository Creation Utility 11g R1 (11.1.1.5.0)

Oracle SOA Suite 11g R1 (11.1.1.5.0)

Oracle WebCenter 11g R1 (11.1.1.5.0)

Oracle Fusion Middleware Web-Tier Utilities 11g R1 (11.1.1.5.0)

Oracle JDeveloper 11g R1 (11.1.1.5.0)

Oracle Application Development Runtime 11g R1 (11.1.1.5.0)

Oracle Application Development Framework 11g R1(11.1.1.5.0)


Oracle Enterprise Content Management 11g R1 (11.1.1.5.0)
Oracle Enterprise Repository 11g R1 (11.1.1.5.0)

Oracle Business Process Management Suite11g R1 (11.1.1.5.0)

Oracle Application Integration Architecture Foundation Pack 11g R1 (11.1.1.5.0)


Oracle Service Bus 11g R1 (11.1.1.5.0)
Oracle Identity Management 11g R1 (11.1.1.5.0) - Released May 6, 2011 o Oracle Internet Directory 11gR1(11.1.1.5.0) o Oracle Directory Integration Platform 11gR1(11.1.1.5.0) o Oracle Virtual Directory 11gR1(11.1.1.5.0) o Oracle Directory Services Manager 11gR1(11.1.1.5.0) o Oracle Identity Federation 11gR1(11.1.1.5.0)

Oracle Identity and Access Management (11.1.1.5.0) - Released May 23, 2011 o Oracle Identity Manager 11gR1(11.1.1.5.0) o Oracle Identity Manager Connectors 11g o Oracle Access Manager Server 11gR1(11.1.1.5.0) o Oracle Access Manager WebGate 11gR1(11.1.1.5.0) o Oracle Adaptive Access Manager 11gR1(11.1.1.5.0) o Oracle Security Token Service 11gR1(11.1.1.5.0) o Oracle Entitlements Server 11gR1(11.1.1.5.0) o Oracle Entitlements Server Security Module11gR1(11.1.1.5.0) o Oracle Identity Navigator 11gR1(11.1.1.5.0)
Master Note for Maintaining / Upgrading Oracle Webcenter 11g]
In this Document
Goal
Solution
Understanding Valid Migration Paths
Updating to Webcenter 11.1.1.5.0 (PS4):
Updating to Webcenter 11.1.1.4.0 (PS3):
Updating to WebCenter 11.1.1.2.0 (PS1):
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
Oracle WebCenter - Version: 11.1.1.1.0 to 11.1.1.5.0 - Release: 11g to 11g
Information in this document applies to any platform.

This document is for WebCenter Administrators that need to maintain Oracle WebCenter 11g.
In this document you will find information to upgrade WebCenter 11g to the latest release.
An Oracle Fusion Middleware environment can consist of different components like:

Oracle WebLogic Server

Web Logic Server domain (for Webcenter, SOA, etc.)

Java components, such as Oracle Webcenter, Oracle SOA Suite.

Oracle instances containing system components such as Oracle HTTP Server.
 etc.
At the time of writing this note the latest version of WebCenter is 11.1.1.5.0.
Depending on your current WebCenter version moving to a later release could require upgrading/patching to an intermediate release.
WebCenter is just part of a more complete set of Products that are part of a Fusion Middleware install. So upgrading or patching WebCenter involves upgrading or patching all components under the Fusion Middleware environment.
Valid upgrade/migration paths are as follows:

Starting with R1 (11.1.1.1.0) these are valid migration paths:
R1 (11.1.1.1.0) --> PS1 (11.1.1.2.0)
Note: The only valid migration path from R1 is to go to PS1. Once you upgrade to PS1 release then you can migrate to a later release.

Starting with PS1 (11.1.1.2.0) these are valid migration paths:
PS1 (11.1.1.2.0) --> PS4 (11.1.1.5.0)
PS1 (11.1.1.2.0) --> PS3 (11.1.1.4.0)
PS1 (11.1.1.2.0) --> PS2 (11.1.1.3.0)

Starting with PS2 (11.1.1.3.0) these are valid migration paths:
PS2 (11.1.1.3.0) --> PS4 (11.1.1.5.0)
PS2 (11.1.1.3.0) --> PS3 (11.1.1.4.0)

Starting with PS3 (11.1.1.4.0) these are valid migration paths:
PS2 (11.1.1.4.0) --> PS4 (11.1.1.5.0)
The above shows valid migration paths. Note that from a given starting release you can upgrade to different intermediate releases. However we recommend doing the upgrade to the latest release.

Note:
This document doesn't cover upgrading from WebCenter 10g to 11g.
This section explains the general process for upgrading to WebCenter 11.1.1.5.0 (PS4) from any of the following releases:

WebCenter 11.1.1.4.0

WebCenter 11.1.1.3.0

WebCenter 11.1.1.2.0
If your existing Oracle Fusion Middleware software is 11g Release 1 (11.1.1.1.0), you must first migrate your existing software and configuration data to 11g Release 1 (11.1.1.2.0), and then update the software to 11g Release 1 (11.1.1.5.0).
The following documentation contains more information on this upgrade path:
Oracle Fusion Middleware Installation Planning Guide
11g Release 1 (11.1.1)
1 Understanding Your Installation Starting Point
1.4 Starting with Oracle Fusion Middleware 11g (11.1.1.2.0), 11g (11.1.1.3.0), and 11g
(11.1.1.4.0)
So this is what you need to do to upgrade to WebCenter 11.1.1.5.0 (PS4):
1. Before starting the upgrade be sure to backup your existing Fusion Middleware.
You should back up the following: o Your entire Oracle Fusion Middleware environment with all services down. o Your domains. o The database.
More information on how to do a backup of your existing Fusion Middleware is here: o For WebCenter 11.1.1.4.0 (PS3)
Oracle Fusion Middleware Administrator's Guide
11g Release 1 (11.1.1)
16 Introducing Backup and Recovery o For WebCenter 11.1.1.3.0 (PS2)
Oracle Fusion Middleware Administrator's Guide
11g Release 1 (11.1.1)
15 Introducing Backup and Recovery o For WebCenter 11.1.1.2.0 (PS1)
Oracle Fusion Middleware Administrator's Guide
11g Release 1 (11.1.1)
15 Introducing Backup and Recovery

2. Update the Oracle WebLogic Server to Version 10.3.5.
There are two ways for you to update your WebLogic Server to 10.3.5: o Use the Smart Update tool.
Smart Update is used to patch your existing Oracle WebLogic Server installation.
This is a standalone Java application that you can run to upgrade the software installations quickly and easily with maintenance patches and maintenance packs.
Refer to the following documentation:
Oracle Smart Update Installing Patches and Maintenance Packs
Release 3.2.1
3 Downloading and Applying Patches o Or use the upgrade installers.
Refer to the following documentation:
Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server
11g Release 1 (10.3.5)
2 Preparing for Installation
Downloading an Upgrade Installer From My Oracle Support
3. Update Your Existing WebCenter software to 11.1.1.5.0.
Use the Patch Set Installer to update your existing software to the latest version.
The Oracle WebCenter installer can be used to patch an existing installation, or it can be used to install a fresh environment.
For either a fresh install or an upgrade you download the same software and run the same installer to perform both functions.
You can download the WebCenter Installer from here: http://www.oracle.com/technetwork/middleware/webcenter/downloads/index.html
More information on this here:
Oracle Fusion Middleware Patching Guide
11g Release 1 (11.1.1)
3 Applying the Latest Oracle Fusion Middleware Patch Set
Oracle Fusion Middleware Patching Guide
11g Release 1 (11.1.1)
3 Applying the Latest Oracle Fusion Middleware Patch Set
3.2 Special Instructions for Patching Oracle WebCenter
Oracle Fusion Middleware Patching Guide
11g Release 1 (11.1.1)
5 Patching Oracle WebCenter

4. If you have a WebTier (with HTTP server) installed in the same Middleware Home as
WebCenter then you also need to update the Web Tier to 11.1.1.5.0.
You can download the Oracle Fusion Middleware Patch Set 4 (11.1.1.5.0) from here:
Oracle Fusion Middleware Web Tier Utilities 11g Patch Set 4 (11.1.1.5.0)
The Patch Set Installer can be used to patch existing 11g Patch Set 1 (Release
11.1.1.2.0), Patch Set 2 (Release 11.1.1.3.0) or Patch Set 3 (Release 11.1.1.4.0) environments.
Refer to the following documentation:
Oracle Fusion Middleware Download, Installation, and Configuration ReadMe
11g Release 1 (11.1.1.5.0)
Oracle Fusion Middleware Patching Guide
11g Release 1 (11.1.1)
3 Applying the Latest Oracle Fusion Middleware Patch Set
5. If you have any other products installed in the same Fusion Middleware Home as
WebCenter you also need to update those products to 11.1.1.5.0.
More information on how to upgrade other components is here:
Oracle Fusion Middleware Installation Planning Guide
11g Release 1 (11.1.1)
1 Understanding Your Installation Starting Point
1.4 Starting with Oracle Fusion Middleware 11g (11.1.1.2.0), 11g (11.1.1.3.0), and 11g
(11.1.1.4.0)
6. Update Your Database Schemas
The Patch Set Assistant is used in patch set releases only to update the database schema of an Oracle Fusion Middleware component. This tool updates 11g Release 1 schema versions as described below:
Version 11.1.1.2.0 to version 11.1.1.5.0
Version 11.1.1.3.0 to version 11.1.1.5.0
Version 11.1.1.4.0 to version 11.1.1.5.0
If your existing schema version is earlier than 11.1.1.2.0, you must migrate to version
11.1.1.2.0 before you can run the Patch Set Assistant.
Check the following document for more information:
Oracle Fusion Middleware Patching Guide
11g Release 1 (11.1.1)
4 Updating Your Schemas with Patch Set Assistant
7. Perform the WebCenter Post-Patching Tasks.
Some of the post-patching tasks include but not limited to:

o Migrating Wiki Pages and Blogs. o Extending a WebCenter Domain to add Oracle WebCenter Analytics Collector. o Upgrading Oracle WebCenter Custom Portal Managed Servers. o Content Presenter Migration.
More information on this is here:
Oracle Fusion Middleware Patching Guide
11g Release 1 (11.1.1)
5 Patching Oracle WebCenter
5.5 Task 5: Perform Oracle WebCenter Post-Patching Tasks
8. Connect to the OS server where WebCenter is installed. o Set the ORACLE_HOME to the Webcenter Home.
For example, in my case:
MW_HOME = /refresh/oracle/fmw11g
ORACLE_HOME = /refresh/oracle/fmw11g/WebCenter o Change to the ORACLE_HOME/OPatch directory: cd $ORACLE_HOME/OPatch o Run the following command:
./opatch lsinventory
Note:
If you don't have a central inventory add this parameter to the above command:
-invPtrLoc <ORACLE_HOME_LOCATION>/oraInst.loc o Take note of the "Log file location" at the beginning of the output of the above command.
The log file name should be like:
Log file location :
/refresh/oracle/fmw11g/WebCenter/cfgtoollogs/opatch/opatch2011-05-30_11-15-
00AM.log

o Review the opatch log and confirm it says something like this to confirm
Webcenter was correctly upgraded to 11.1.1.5.0:
Installed Top-level Products (1):
Oracle WebCenter Suite 11g 11.1.1.5.0
There are 1 products installed in this Oracle Home.
9. Check the following note to verify for recommended patches for WebCenter or ADF.
Note 1087226.1
Recommended Patches for Oracle WebCenter 11g
The above note is updated with the latest recommended patches for each release.
It also contains recommended patches for JDeveloper for developing WebCenter applications.
This section explains the general process for upgrading to WebCenter 11.1.1.4.0 (PS3) from any of the following releases:

WebCenter 11.1.1.3.0

WebCenter 11.1.1.2.0
If your existing Oracle Fusion Middleware software is 11g Release 1 (11.1.1.1.0), you must first migrate your existing software and configuration data to 11g Release 1 (11.1.1.2.0), and then update the software to 11g Release 1 (11.1.1.4.0).
The following documentation contains more information on this upgrade path:
Oracle Fusion Middleware Installation Planning Guide
11g Release 1 (11.1.1)
1 Understanding Your Installation Starting Point
1.4 Starting with Oracle Fusion Middleware 11g (11.1.1.2.0) and 11g (11.1.1.3.0)
So this is what you need to do to upgrade from an existing WebCenter 11g to 11.1.1.4.0 (PS3):
1. Before starting the upgrade be sure to backup your existing Fusion Middleware.
You should back up the following: o Your entire Oracle Fusion Middleware environment with all services down. o Your domains. o The database.
More information on how to do a backup of the Fusion Middleware is here:

o For WebCenter 11.1.1.3.0 (PS2)
Oracle Fusion Middleware Administrator's Guide
11g Release 1 (11.1.1)
15 Introducing Backup and Recovery o For WebCenter 11.1.1.2.0 (PS1)
Oracle Fusion Middleware Administrator's Guide
11g Release 1 (11.1.1)
15 Introducing Backup and Recovery
2. Update the Oracle WebLogic Server to Version 10.3.4
There are two ways for you to update your WebLogic Server to 10.3.4: o Use the Smart Update tool.
Smart Update is used to patch your existing Oracle WebLogic Server installation.
This is a standalone Java application that you can run to upgrade the software installations quickly and easily with maintenance patches and maintenance packs.
Refer to the following documentation:
Oracle Smart Update Installing Patches and Maintenance Packs
Release 3.2.1
4 Downloading and Installing Maintenance Packs o Or use the upgrade installers.
Refer to the following documentation:
Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server
11g Release 1 (10.3.3)
2 Preparing for Installation
Downloading an Upgrade Installer From My Oracle Support
3. Update Your Existing WebCenter software to 11.1.1.4.0.
Use the Patch Set Installer to update your existing software to the latest version.
The Oracle WebCenter installer can be used to patch an existing installation, or it can be used to install a fresh environment.
For either a fresh install or an upgrade you download the same software and run the same installer to perform both functions.
You can download the WebCenter Installer from here: http://www.oracle.com/technetwork/middleware/webcenter/downloads/index.html
More information on this here:
Oracle Fusion Middleware Patching Guide
11g Release 1 (11.1.1)
3 Applying the Latest Oracle Fusion Middleware Patch Set

Oracle Fusion Middleware Patching Guide
11g Release 1 (11.1.1)
5 Patching Oracle WebCenter
4. If you have a WebTier (with HTTP server) installed in the same Middleware Home as
WebCenter then you also need to update the WebTier to 11.1.1.4.0.
You can download the Oracle Fusion Middleware Patch Set 3 (11.1.1.4.0) from here:
FMW 11G PS3 (11.1.1.4) FOR WETIER UTILITIES
The Patch Set Installer can be used to patch existing 11g Patch Set 1 (Release
11.1.1.2.0) or Patch Set 2 (Release 11.1.1.3.0) environments.
Refer to the following documentation:
Oracle Fusion Middleware Download, Installation, and Configuration ReadMe
11g Release 1 (11.1.1.4.0)
Oracle Fusion Middleware Patching Guide
11g Release 1 (11.1.1)
3 Applying the Latest Oracle Fusion Middleware Patch Set
5. If you have any other products installed in the same Fusion Middleware Home as
WebCenter you also need to update those products to 11.1.1.4.0.
More information on how to upgrade other components is here:
Oracle Fusion Middleware Installation Planning Guide
11g Release 1 (11.1.1)
1 Understanding Your Installation Starting Point
1.4 Starting with Oracle Fusion Middleware 11g (11.1.1.2.0) and 11g (11.1.1.3.0)
6. Update Your Database Schemas
The Patch Set Assistant is used in patch set releases only to update the database schema of an Oracle Fusion Middleware component. This tool updates 11g Release 1 schema versions as described below:
Version 11.1.1.2.0 to version 11.1.1.4.0
Version 11.1.1.3.0 to version 11.1.1.4.0
If your existing schema version is earlier than 11.1.1.2.0, you must migrate to version
11.1.1.2.0 before you can run the Patch Set Assistant.
Check the following document for more information:
Oracle Fusion Middleware Patching Guide11g Release 1 (11.1.1)
4 Updating Your Schemas with Patch Set Assistant
7. Perform the WebCenter Post-Patching Tasks.
Some of the post-patching tasks include but not limited to:

o Migrating Wiki Pages and Blogs. o Extending a WebCenter Domain to add Oracle WebCenter Analytics Collector. o Upgrading Oracle WebCenter Custom Portal Managed Servers. o Content Presenter Migration.
More information on this is here:
Oracle Fusion Middleware Patching Guide
11g Release 1 (11.1.1)
5 Patching Oracle WebCenter
5.5 Task 5: Perform Oracle WebCenter Post-Patching Tasks
8. Connect to the OS server where WebCenter is installed. o Set the ORACLE_HOME to the Webcenter Home.
For example, in my case:
MW_HOME = /refresh/oracle/fmw11g
ORACLE_HOME = /refresh/oracle/fmw11g/WebCenter o Change to the ORACLE_HOME/OPatch directory: cd $ORACLE_HOME/OPatch o Run the following command:
./opatch lsinventory
Note:
If you don't have a central inventory add this parameter to the above command:
-invPtrLoc <ORACLE_HOME_LOCATION>/oraInst.loc o Take note of the "Log file location" at the beginning of the output of the above command.
The log file name should be like:
Log file location :
/refresh/oracle/fmw11g/WebCenter/cfgtoollogs/opatch/opatch2011-04-20_11-24-
00AM.log

o Review the opatch log and confirm it says something like this to confirm
Webcenter was correctly upgraded to 11.1.1.4.0:
Installed Top-level Products (1):
Oracle WebCenter Suite 11g 11.1.1.4.0
There are 1 products installed in this Oracle Home.
9. Check the following note to verify for recommended patches for WebCenter or ADF.
Note 1087226.1
Recommended Patches for Oracle WebCenter 11g
The above note is updated with the latest recommended patches for each release.
It also contains recommended patches for JDeveloper for developing WebCenter applications.
This section explains the general process for upgrading to WebCenter 11.1.1.2.0 (PS1) from the following release:

WebCenter 11.1.1.1.0
The following documentation contains more information on this upgrade path:
Oracle Fusion Middleware Installation Planning Guide
11g Release 1 (11.1.1)
1 Understanding Your Installation Starting Point
1.3 Starting with Oracle Fusion Middleware 11g (11.1.1.1.0)
To do the upgrade from WebCenter 11g R1 (11.1.1.1.0) to PS1 (11.1.1.2.0) perform the following actions:
1. Before starting the upgrade be sure to backup your existing Fusion Middleware.
You should back up the following: o Your entire Oracle Fusion Middleware environment with all services down. o Your domains. o The database.
More information on how to do a backup of the Fusion Middleware is here:
Oracle Fusion Middleware Administrator's Guide
11g Release 1 (11.1.1)
13 Introducing Backup and Recovery

2. Update the Oracle WebLogic Server to Version 10.3.2
There are two ways for you to update your WebLogic Server to 10.3.2: o Use the Smart Update tool.
Smart Update is used to patch your existing Oracle WebLogic Server installation.
This is a standalone Java application that you can run to upgrade the software installations quickly and easily with maintenance patches and maintenance packs.
Refer to the following documentation:
Oracle Smart Update Installing Patches and Maintenance Packs
Release 3.2
4 Downloading and Installing Maintenance Packs o Or use the upgrade installers.
Refer to the following documentation:
Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server
11g Release 1 (10.3.3)
2 Preparing for Installation
Downloading an Upgrade Installer From My Oracle Support
3. Install WebCenter 11.1.1.2.0.
Install the software only. Make sure that you do not configure WebCenter.
WebCenter 11.1.1.2.0 can be downloaded from here:
Oracle Fusion Middleware 11gR1 Software Downloads
Download: WebCenter Suite (11.1.1.2.0)
4. If you have a WebTier (with HTTP server) installed in the same Fusion Middleware Home as WebCenter then you also need to install the Web Tier Utilities (11.1.1.2.0).
Install the software only. Make sure that you do not configure the Web Tier.
Oracle Fusion Middleware 11gR1 Software Downloads
Download: Web Tier Utilities (11.1.1.2.0)
5. If you have any other products installed in the same Fusion Middleware Home as
WebCenter you might also need to install the base 11.1.1.2.0 software for those products.
More information on how to upgrade other components is here:
Oracle Fusion Middleware Installation Planning Guide
11g Release 1 (11.1.1)
1 Understanding Your Installation Starting Point
1.3 Starting with Oracle Fusion Middleware 11g (11.1.1.1.0)

6. Migrate your 11g Release 1 (11.1.1.1.0) Configuration Data to 11g Release 1
(11.1.1.2.0).
After you have upgraded your software, you must run the Patch Assistant tool to migrate your data to the updated version.
More information is here:
Oracle Fusion Middleware Patching Guide
11g Release 1 (11.1.1)
B Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1
(11.1.1.2.0)
The Patch Assistant tool to migrates the following: o Your existing configuration of Oracle Fusion Middleware 11g Release 1
(11.1.1.1.0) components, used in conjunction with the 11.1.1.1.0 and 11.1.1.2.0 installations.
When you run Patch Assistant tool, the configuration files contained in the Oracle
Fusion Middleware 11g Release 1 (11.1.1.1.0) domain and Instance directories are copied to the new directories in the Oracle Fusion Middleware 11g Release 1
(11.1.1.2.0) installation. o Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) Domains. o Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) Oracle Instances. o Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) database schemas created using Oracle Repository Creation Utility (RCU)
7. Perform the Post-Migration Configuration steps for Oracle Fusion Middleware
Components.
More information on this is here:
Oracle Fusion Middleware Patching Guide
11g Release 1 (11.1.1)
B Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1
(11.1.1.2.0)
B.4 Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
B.4.3 Post-Migration Configuration for Oracle Fusion Middleware Components
How to Confirm if Caching is Enabled in WebCenter Spaces
Oracle WebCenter - Version: 11.1.1.1.0 to 11.1.1.5.0 - Release: 11g to 11g
Information in this document applies to any platform.

When it comes to WebCenter performance, caching in the browser is critical.
This document explains how to check if caching in the browser is properly working for 11g
WebCenter Spaces.
This document is intended for WebCenter Administrators who are responsible to operate
WebCenter Spaces with an acceptable performance for the users.
It is important to make sure that caching works properly in the browser to maintain an optimal performance for WebCenter Spaces. Caching may be validated using tools such as Fiddler,
HTTP Watch, and Firebug. Here are the steps to validate caching is working correctly using
Firebug:
1. Install the Firebug add-on for Firefox
2. Open Firebug by clicking on the Firefox Tools menu, and checking Open Firebug under the
Firebug menu item or alternatively by clicking on the Firebug icon in the status bar.
3. Once Firebug is open, enable the Net option in Firebug by selecting Net on the Firebug header and change the radio button to Enabled.
4. Under the Net item in Firebug, click the JS tab
5. Clear browser cache
6. Access a WebCenter Page, other than the login page.
7. In Firebug view the All tab to see all HTTP requests and response status.
8. The first request after clearing the browser's cache would typically look like this: