Not able to log in with FCM user in Pega 7.1.8
PRPC Users belonging to Federated Case Management (FCM) Access Groups are unable to log into Pega 7.1.8.
- Single PRPC instance, Multiple Applications, Split Schema.
- Websphere 8.0.
- Oracle 11.2
- Oracle JDBC driver 188.8.131.52.0-Production
- IBM java 1.6.0
2015-09-23 11:27:28,908 [ WebContainer : 5] [ STANDARD] [ PegaRULES:07.10] ( internal.access.DatabaseImpl) ERROR xxxx|xxxx - Encountered problem when performing a Commit
com.pega.pegarules.pub.database.ConnectionException: Database-General Problem clearing out old indexes for instance DATA-ADMIN-OPERATOR-ID-FEDERATED xxxxxxxx!PEGA, purpose RuleReference 0 enlist: caught Exception
SQL: delete from PEGA_RULES.pr_index_reference where pxInsIndexedKey = ? and pxIndexPurpose = ?
Caused by SQL Problems.
Problem #1, SQLState null, Error code 0: java.sql.SQLException: enlist: caught Exception
com.ibm.ws.Transaction.IllegalResourceIn2PCTransactionException: Illegal attempt to enlist multiple 1PC XAResources
Steps to Reproduce
Login with a user which belongs to a ‘FCM’ access group.
A defect or configuration issue in the operating environment.
Due to specific Reporting Requirements: this system differs from a standard FCM configuration in the following ways:
- The FCM tables (for instance: “PR_DATA_ADMIN_FED”) were created within the DATA schema instead of a dedicated FCM scheme.
- Two JDBC separate datasources (“PegaData” and “FCMR”) were created; but both were pointed to the same (“PegaData”) database schema.
Perform the following local-change:
For each FCM table:
Change the ‘Database Table’ rule so that the ‘Database’ field matches the ‘PegaData’ schema instead of the ‘FCMR’ schema.
Published January 31, 2016 - Updated December 2, 2021
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.