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.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
No comments:
Post a Comment