WebCenter Capture 11.1.1.8 Cluster - Creating OPSS schema for using Database Based Security Store

WebCenter Capture 11.1.1.8 Cluster - Creating OPSS schema for using Database Based Security Store

When using Database Based Security Store, follow steps below for OPSS schema creation.

- Download 11.1.1.8 RCU Patch 17068284
- Invoke RCU from /SID/fmw/product/111/oracle_common/bin ) and create OPSS schema

OPSS schema creation

i) Select Create

ii) DB connection Details:
- Host:
- Port:
- Service type:
- Username: system
- PASS: system_password
- Role: SYSDBA.

iii) On Select Components:


- Select "Select an existing Prefix" and verify SID is selected.
- Components:
Open "As Common Schemas" and select "Oracle Platform Security Services"


iv) On Schema Password, select "Use same passwords for all schemas" and enter password of "SID_MDS" schema

v)  Proceed further till OPSS schema gets created.

Related Posts:

WebCenter Capture 11.1.1.8 Cluster - Using Database Based Security Store

WebCenter Capture 11.1.1.8 Cluster - Workspace created or imported on one node is not visible on the other node and workspace gets deleted on restart of cluster node

WebCenter Capture 11.1.1.8 Cluster - Using OID Based Policy Store

WebCenter Capture 11.1.1.8.0 - reassociateSecurityStore(domain="your_domain", servertype="DB_ORACLE",datasourcename="jdbc/opss-ds", jpsroot="cn=jpsTestNode", join="false") fails with error JPS-00027: There was an internal error: java.sql.BatchUpdateException: ORA-00904: "ATTRKIND": invalid identifier

WebCenter Capture 11.1.1.8 Cluster - Using Database Based Security Store

WebCenter Capture 11.1.1.8 Cluster - Using Database Based Security Store


If facing an issue in WebCenter Capture 11.1.1.8 cluster with workspace imported / created on one node not being available on the other node of cluster as detailed in this post, one of the ways to resolve the issue is using Database Based Security Store.

Using Database Based Security Store

1) Create OPSS schema

2) Create Data Source

- Create a non-XA data source with support for global transactions disabled / unchecked (Configuration -> Transactions) in WebLogic console (JNDI name should be of format "jdbc/opss-ds" or "jdbc/cap-opss-ds") 

- Target this data source to the cluster & admin server. If other managed servers are to use the data source, the OPSS source must also target those managed servers / clusters.

- Restart MT services

3) Re-associate to OPSS Security Store

cd ORACLE_COMMON_HOME\common\bin
./wlst.sh
connect("Admin_User","Admin_User_Password","t3://hostname:port")

reassociateSecurityStore(domain="your_domain", servertype="DB_ORACLE",datasourcename="jdbc/opss-ds", jpsroot="cn=jpsTestNode", join="false") 

4) Restart the complete domain.

Now from the other cluster node (say Node 2) try accessing workspace that was created / imported on one of the WebCenter Capturecluster nodes (say Node 1). Workspace should now be visible from both the cluster nodes.

Related Posts:

WebCenter Capture 11.1.1.8 Cluster - Workspace created or imported on one node is not visible on the other node and workspace gets deleted on restart of cluster node

WebCenter Capture 11.1.1.8 Cluster - Using OID Based Policy Store

WebCenter Capture 11.1.1.8 Cluster - Creating OPSS schema for using Database Based Security Store

WebCenter Capture 11.1.1.8.0 - reassociateSecurityStore(domain="your_domain", servertype="DB_ORACLE",datasourcename="jdbc/opss-ds", jpsroot="cn=jpsTestNode", join="false") fails with error JPS-00027: There was an internal error: java.sql.BatchUpdateException: ORA-00904: "ATTRKIND": invalid identifier

WebCenter Capture 11.1.1.8 Cluster - Using OID Based Policy Store

WebCenter Capture 11.1.1.8 Cluster - Using OID Based Policy Store

If facing an issue in WebCenter Capture 11.1.1.8 cluster with workspace imported / created on one node not being available on the other node of cluster as detailed in this post, one of the ways to resolve the issue is using an OID Based Policy Store.


- On MT Host 1, invoke WLST

cd ORACLE_COMMON_HOME/common/bin
./wlst.sh

- Run connect() as below

connect("Admin_User","Admin_User_Password","t3://hostname:port")

- Execute   reassociateSecurityStore command as below using correct domain name and LDAP details 

reassociateSecurityStore(domain="your_domain",admin="cn=orcladmin",password="orclPassword",ldapurl="ldap://LDAP_HOST:LDAP_PORT",servertype="OID",jpsroot="cn=jpsroot_ecm")


- Restart the complete domain once reassociateSecurityStore is executed without any errors.

- Now from the other cluster node (say Node 2) try accessing workspace that was created / imported on one of the WebCenter Capturecluster nodes (say Node 1). Workspace should now be visible from both the cluster nodes.

Related Posts:

WebCenter Capture 11.1.1.8 Cluster - Workspace created or imported on one node is not visible on the other node and workspace gets deleted on restart of cluster node

WebCenter Capture 11.1.1.8 Cluster - Using Database Based Security Store

WebCenter Capture 11.1.1.8 Cluster - Creating OPSS schema for using Database Based Security Store

WebCenter Capture 11.1.1.8.0 - reassociateSecurityStore(domain="your_domain", servertype="DB_ORACLE",datasourcename="jdbc/opss-ds", jpsroot="cn=jpsTestNode", join="false") fails with error JPS-00027: There was an internal error: java.sql.BatchUpdateException: ORA-00904: "ATTRKIND": invalid identifier

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

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