Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Clipboard Access through Requestor Management



User reports that whenever user is trying to access clipboard through System Management Application (SMA), user is facing an error.

Error Messages

Access to the MBean operation or attribute RequestorManagement.Clipboard[java.lang.String] has been denied.
To have access to this operation or attribute, check your MBean security settings or contact System Administrator.

Steps to Reproduce

Go to SMA > Requestor Management > Clipboard.



Below are steps to alter security permissions related to requestor management:
1. Navigate to <PRPC_distribution_dir>\archives and extract the "" to a temp folder.
2. Locate and extract the "" file under the temp/lib/pega/prresources.jar.

3. Modify the file values as per your requirement and recreate the prresources.jar with this newly modified (following values are modified according to the requirement).
#Default MBean security configuration.
deny.DatabaseManagement.DatabaseConnectionDetails = false
deny.RequestorManagement.RequestorDetails = false
deny.RequestorManagement.Clipboard = false

By default, the value is a "true", denying you access to the Clipboard / Details.
4. Login to the PRPC Developer portal, navigate to Pega > Application > Distribution > Import menu.
5. Click Browse and select the prresources.jar modified in Step 3 above and click Next.
6. In the Codeset Name/Version screen, specify Codeset Name as "Customer" and Codeset Version as "07-10-15" and click "Next". To complete the installation click "Done".
7. Stop the PRPC server/JVM.

8. Login to the PRPC database as the PRPC schema owner and execute the following SQL command.
SQL > update pr_engineclasses set pzcodeset='pega-enginecode' where pzclass like 'prmbeans%' and pzcodeset='Customer';
SQL > commit;

9. Restart the PRPC server/JVM.

If still not able to use the updated file, then you can perform the following steps.

1. Run below query:

SQL > select * from pr_engineclasses where pzcodeset='pega-enginecode' and pzclass like 'prmbeans%';

2. If one witness mutiple entries of 'prresources.jar' file with pzcodeset name as 'pega-enginecode' from the above query, filter out the latest prresources.jar entry by running select statement for 'pzlastmodified' , check the latest date entered in 'pzlastmodified' (it should be the one when you have imported prresources.jar file newly with the updated

3. Use the same last modified date as filter to pick the other prresource.jar entries other than your latest prresource.jar one.

For example, if the date  imported the prresources.jar file was '19-05-2015', one can run update statement as follows, which will pick and update the other prresource.jar entries other than your latest prresource.jar one.

SQL> select * from pr_engineclasses  where pzclass like 'prmbeans%' and pzlastmodified < To_Date('19-05-2015','dd-mm-yyyy'); 
SQL > update pr_engineclasses set pzcodeset='Customer' where pzclass like 'prmbeans%' and pzlastmodified < To_Date('19-05-2015','dd-mm-yyyy');
SQL > commit;

4. Restart the PRPC server/JVM.



Published June 7, 2016 - Updated October 8, 2020

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.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us