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

Modifying prmbeans.properties file

SA-9021

Summary



You need to modify the prmbeans.properties file.

The instructions on how to use the runPega.sh to extract the prmbeans.properties from the database and then how to use the script to put the updated file back is confusing.



Resolution



The clipboard is inaccessible due to the security restraints. 

This issue is resolved through the following Local-change:

There are two options to resolve the issue without using runPega script.

Option 1

1. From <EAR-Dir>/APP-INF/lib/prresources.jar file, extract the prmbeans.properties file.
2. Modify the prmbeans.properties file:

  #Default MBean security configuration

  deny.DatabaseManagement.DatabaseConnectionDetails = true

  deny.RequestorManagement.RequestorDetails = true

  deny.RequestorManagement.Clipboard = false

3. Import the file back into the prresources.jar file.

Option 2

The other option is for the websphere team to create a jvm property called prmbeans.security with the path to a prmbeans.properties files somewhere.

1. From <EAR-Dir>/APP-INF/lib/prresources.jar file, extract the prmbeans.properties file.
2. Modify the prmbeans.properties file.

  #Default MBean security configuration

  deny.DatabaseManagement.DatabaseConnectionDetails = true

  deny.RequestorManagement.RequestorDetails = true

  deny.RequestorManagement.Clipboard = false

3. Place the prmbeans.properties in an area accessible by the application and note the path, for example, /opt/myprpcinstall/prmbeans.properties.

4. Create a prmbeans.security java property which has the value of the path /opt/myprpcinstall/prmbeans.properties.
Suggest Edit

Published June 12, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

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.

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