Patching Oracle WebCenter 5-21
a.
If this template was used in WebCenter Spaces, right-click again after creating the site resource and export the file.
b.
Log in to WebCenter Spaces and navigate to the Administration section.
c.
Select Resources Content Presenter and upload your template.
5.5.5 Updating Oracle WebCenter Portal Schemas
In Release 11.1.1.2.0 and 11.1.1.3.0, the
MW_ HOME
jdeveloperjdevextensionsoracle.webcenter.installsqlora clewc_schema.sql on UNIX Operating systems or
MW_ HOME
\jdeveloper\jdev\extensions\oracle.webcenter.install\sql\ora cle\wc_schema.sql on Windows Operating systems could be used to created
schemas used by custom WebCenter applications deployed to the custom Managed Servers. Since these schemas would not be registered in the schema version registry,
Patch Set Assistant cannot be used to update them.
To update these schemas, use the
MW_ HOME
jdeveloperjdevextensionsoracle.webcenter.installsqlora cle11.1.1.4.0RRwc_objects.sql on UNIX operating systems or
MW_ HOME
\jdeveloper\jdev\extensions\oracle.webcenter.install\sql\ora cle\11.1.1.4.0RR\wc_objects.sql on Windows operating systems script. For
example:
sqlplus
exampleuser examplepassword
examplehost
as sysdba
MW_ HOME
jdeveloperjdevextensionsoracle.webcenter.installsqloracle11.1.1.4.0RRw c_objects.sql
schemaname
5.5.6 Updating Your Configuration for WebCenter REST APIs
Before you can use the WebCenter Representational State Transfer REST APIs, you must perform the server-side configurations described in this section. You must
perform two separate configurations:
■
Section 5.5.6.1, Configuring an Identity Asserter
■
Section 5.5.6.2, Configuring the Credential Store You must configure an identity asserter and you must seed required entries in the
credential store, which enables the REST security tokens to function properly.
For more information about security tokens, see Security Considerations for CMIS REST APIs in Oracle Fusion Middleware Developers Guide for Oracle WebCenter.
5.5.6.1 Configuring an Identity Asserter
You must configure an identity asserter before using the REST APIs. For detailed instructions, see Configuring the REST Service in the Oracle Fusion Middleware
Administrators Guide for Oracle WebCenter.
5.5.6.2 Configuring the Credential Store
Run the following WLST commands to configure the credential store. Execute these commands while the server is running. You do not have to restart the server after
executing these commands.
Note:
This configuration is not required for the navigation REST APIs or for the CMIS REST APIs.
5-22 Oracle Fusion Middleware Patching Guide
createCredmap=o.webcenter.jf.csf.map, key=keygen.algorithm, user=keygen.algorithm, password=AES
createCredmap=o.webcenter.jf.csf.map, key=cipher.transformation, user=cipher.transformation, password=AESCBCPKCS5Padding
5.5.7 Updating Multi Calendar Layouts
In Release 11.1.1.3.0, the Calendar Overlay Style FULL could be used to enable multiple calendars for some events task flow and add multiple space calendars in one
events task flow. After upgrading to Release 11.1.1.4.0, the events task flow no longer displays multiple calendars only the current space calendar is displayed.
To work around this issue, go to the page editor, find the Calendar Overlay Style parameter and select Full from the list of available options.
5.5.8 Extending a Domain to Install Oracle WSM Policy Manager
When you upgrade Oracle WebCenter, existing WSM-PM applications and associated datasource are re-targeted to the WC_Collaboration managed server. If your
upgraded WebCenter domain has Oracle WebCenter Discussions Server installed, you must extend the domain to install Oracle WSM Policy Manager if not already installed.
To extend a WebCenter domain to install Oracle WSM Policy Manager:
1.
Stop the Admin server and all managed servers.
2.
Start the Configuration Wizard on the machine running the Admin server. On UNIX, run
WebCenter_ORACLE_HOME
commonbinconfig.sh. On Windows, run
WebCenter_ORACLE_HOME
\common\bin\config.cmd.
3.
Select Extend an existing WebLogic domain and click Next.
4.
Select your domain and click Next.
5.
Select the checkbox for Oracle WSM Policy Manager and click Next.
6.
Enter the connection details for OWSM MDS Schema and click Next.
7.
Click Next on the remaining screens until you get the Configuration Summary screen, then click Extend.
5.5.9 Setting the Web Context Root on the UCM Connection
Assuming that the Universal Content Management UCM and WebCenter instances are configured for access through a common Oracle HTTP server, the Web Server
Context Root property WebContextRoot on the existing UCM connection can be set either through Fusion Middleware Control or WLST using the
setJCRContentServerConnection command to make UCM features available in the WebCenter application via an iFrame:
■
To use Fusion Middleware Control, see Setting Connection Properties for the WebCenter Spaces Content Repository Using Fusion Middleware Control in
Oracle Fusion Middleware Administrators Guide for Oracle WebCenter.
Note:
If your domain is running on multiple machines, you must pack the domain on the machine running the Administration Server
and unpack on the other machines. For information, see Section 5.4.2,
Updating Oracle WebCenter Using WLST Commands.
