Oracle WebCenter Portal 11.1.1.8 Spaces Admin Page (Portal Builder) throws "Page Not Found" error on browser post patching.

Oracle WebCenter Portal 11.1.1.8 Spaces Admin Page (Portal Builder) throws "Page Not Found" error on browser post patching.

Oracle WebCenter Portal 11.1.1.8 Spaces Admin page throws "Page Not Found" error after patching

Have you patched your Oracle WebCenter Portal instance from 11.1.1.7 to 11.1.1.8 & ended up getting error mesage as above in the browser on accessing WebCenter Portal Spaces Admin page ( Portal Builder)?

If you are patching from 11.1.1.7 to 11.1.1.8, you will normally run into this issue if one of the mandatory steps as below is missed during patching.

- After applying 11.1.1.8.0 patch on WebCenter Portal instance, start Admin & Managed Server.

- Run the upgradeWebCenterPermissions() command as below:

cd <WC_ORACLE_HOME>/common/bin
./wlst.sh

connect()
Enter Admin username:
Enter Admin password:
Enter connecting url: t3://<Admin_host>:<Admin_Port


- Once connected, run below in WLST

upgradeWebCenterPermissions()


- Verify if you get message that the command completed successfully.

- Restart the WebCenter managed servers.


- Test if you can now access the Spaces Admin page: http://<Admin_host>:<WC_Spaces_Port>/webcenter/spaces/admin

OracleJSP error: oracle.jsp.parse.JavaCodeException: Line # 13, oracle.jsp.parse.JspParseTagScriptlet@18a5b0d0 Error: Java code in jsp source files is not allowed in ojsp.next mode.

OracleJSP error: oracle.jsp.parse.JavaCodeException: Line # 13, oracle.jsp.parse.JspParseTagScriptlet@18a5b0d0
Error: Java code in jsp source files is not allowed in ojsp.next mode.

You may observe an issue accessing /webcenter portal login page due to custom deployments made. Everytime you attempt to access /webcenter url, it fails to load the login page. Instead, it returns below error on the browser.

OracleJSP error: oracle.jsp.parse.JavaCodeException: Line # 13, oracle.jsp.parse.JspParseTagScriptlet@18a5b0d0

Error: Java code in jsp source files is not allowed in ojsp.next mode.

To resolve,

Stop Webcenter Spaces managed server and delete conflicting custom deployments.

You may also try setting Java option -Dadfvdt.disableOjspDeployment=true in setDomainEnv.sh (for all managed servers) or in startManagedWeblogic.sh (for specific managed server) 

Applying Oracle Webcenter Portal 11.1.1.6.6 Bundle Patch 16269470

Applying Webcenter Portal 11.1.1.6.6 Bundle Patch 16269470

1. This patch is applicable to two ORACLE_HOMEs:

      -> [MW_HOME]/oracle_common (JRF Home)
      -> [MW_HOME]/Oracle_WC1    (Webcenter Home)


2. Run the following WLST commands and save the output (this will be needed during the post-install instructions):

   Using WLST:
   cd [MW_HOME]/Oracle_WC1/common/bin
   ./wlst.sh
   
   $> connect()

  $> listWebServicePolicies('/wcp_domain/WC_Spaces/webcenter', 'webcenter', 'web', 'SpacesWebService', 'SpacesWebServiceSoapHttpPort')

  $> listWebServicePolicies('/wcp_domain/WC_Collaboration/owc_discussions', 'owc_discussions', 'web', 'OWCDiscussionsServiceAuthenticated', 'OWCDiscussionsServiceAuthenticated')

3. Stop all servers (Admin Server and all Managed Server(s))

4. Run OPatch to apply the patch.

   Proceed as below:

   4.1. Set the ORACLE_HOME environment variable to "[MW_HOME]/oracle_common" directory.

       Run following command:
       - opatch apply

   4.2. Set the ORACLE_HOME environment variable to "[MW_HOME]/Oracle_WC1" directory.
  
       Run following command:
       - opatch apply 

You should see below at the end of opatch.
-------------------
Verifying the update...
Inventory check OK: Patch ID 16269470 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 16269470 are present in Oracle Home.

The local system has been patched and can be restarted.

--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1) OUI-67644:
Given patch "16269470" is a bug superset of patch "14361677" but is not a file superset.

--------------------------------------------------------------------------------
OPatch Session completed with warnings.


OPatch completed with warnings.
-----------------------

5. Start all servers (Admin Server and all Managed Server(s))

6. Prior to this patch, the WebCenter Spaces & WebCenter Discussions web service end points were seeded with a fixed policy - i.e., 
wss11_saml_token_with_message_protection_service_policy and wss10_saml_token_service_policy respectively. 

Post application of this patch, there is no security policy assigned to the WebService end points thereby resulting in a potential loss of functionality. 

To  fix this, you will need to reapply the policies that were set earlier on these services. This can be achieved either via WLST or the Enterprise Manager console. 

Using WLST:
cd [MW_HOME]/Oracle_WC1/common/bin
./wlst.sh
   
   $> connect()

   $> attachWebServicePolicy('webcenter', 'webcenter', 'web', 'SpacesWebService', 'SpacesWebServiceSoapHttpPort', 'oracle/wss11_saml_or_username_token_with_message_protection_service_policy')
   ... where oracle/wss11_saml_or_username_token_with_message_protection_service_policy is the policy you want to restore. 
  
   Note that this is the value you obtained by running listWebServicePolicies in the section '2 Pre-Installation Instructions'
   against WebCenter Spaces web service end point.

   $> attachWebServicePolicy('owc_discussions', 'owc_discussions', 'web', 'OWCDiscussionsServiceAuthenticated', 'OWCDiscussionsServiceAuthenticated', 'oracle/wss10_saml_token_service_policy')
   ... where oracle/wss10_saml_token_service_policy is the policy you want to restore. 

   $> exit()

   Failure to perform these steps will cause the connection between Spaces and the Discussions server to fail with an "Error while invoking endpoint" message.

7. Restart Spaces and Collaboration managed server(s).

8. Due to the fixes installed, the following is mandatory:

   8.1. Update the WebCenter Portal Extension Bundle for JDeveloper.
      
   8.2. Clear the browser cache.

9. Run opatch lsinventory to verify the patch applied. 

Webcenter Spaces - Warning: The file upload failed. The file could not be uploaded because it is too large. Enter the file name and location. Files must be less than 2GB

Webcenter Spaces - Warning: The file upload failed. The file could not be uploaded because it is too large. Enter the file name and location. Files must be less than 2GB


Webcenter Spaces 

Warning: The file upload failed.
The file could not be uploaded because it is too large.
--------------------------------------------------------
Enter the file name and location. Files must be less than 2GB


This is a known bug which is now resolved in 11.1.1.6. 

In case facing issue uploading documents over 2 MB in size, you can follow below steps to increase upload size upto 2 GB.


1. On the WebCenter ORACLE_HOME and via WLST, do the following:

cd FMW_HOME/WEBCENTER_ORACLE_HOME/common/bin
./wlst.sh

connect()
exportMetadata(application='webcenter',server='WC_Spaces',toLocation='/tmp',docs='/oracle/webcenter/webcenterapp/metadata/webcenter-config.xml')

Leave this window pending...

2. Edit webcenter-config.xml and assign the desired max file size to - uploadedFileMaxDiskSpace. The size is in bytes.

Example (2Gb):
cd /tmp
vi oracle/webcenter/webcenterapp/metadata/webcenter-config.xml

(...)
<webcenter:custom-attributes/>
<webcenter:uploadedFileMaxDiskSpace>2147483648</webcenter:uploadedFileMaxDiskSpace>
</webcenter:webcenter>
(...)

3. On the WebCenter ORACLE_HOME and via WLST (using the same screen as in step 1):

From Step 1... 

importMetadata(application='webcenter',server='WC_Spaces',fromLocation='/tmp',docs='/oracle/webcenter/webcenterapp/metadata/webcenter-config.xml')
disconnect()
exit()

4. Restart the WC_Spaces managed server, for the changes to be picked up.


5. Verify that you are now able to upload a file with more than 2Mb.

More details on Changing maximum file upload size

Webcenter 11g - 'Administration' link does not appear in /webcenter url when logged in as super user other than 'weblogic'

Webcenter 11g - 'Administration' link does not appear in /webcenter url when logged in as super user other than 'weblogic'

If you have installed Webcenter 11g as a super user other than 'weblogic', when you login to /webcenter url, 'Administration' link does not appear.

However if you login to /webcenter url as 'weblogic' super user, 'Administration' link can be seen as below.

In Enterprise Manager (/em), there are many Application Roles that are created from a base install.

For webcenter two roles below are important:

• Webcenter#-#defaultadministrator
• S8bba98ff_4cbb_40b8_beee_296c916a23ed#-#Administrator

The base installation using super user ‘weblogic’ seems to automatically add them to these Application Roles. However, when using/creating different super users it does not.

To fix the 'Administration' link issue you can try two workarounds below:

1) Create additional user 'weblogic' in weblogic console under security realms & assign it to Administrators group. Now access /webcenter url as weblogic user and you should be able to see the 'Administration' link.

2) Adding Administrators group to below Application Roles will make the Administration Link appear even when logged in to /webcenter as a super user other than 'weblogic'.

• Webcenter#-#defaultadministrator
• S8bba98ff_4cbb_40b8_beee_296c916a23ed#-#Administrator