Installation guide

24 PegaRULES Process Commander Installation Guide v6.1 SP2
# mkdir prsysmgmt_jboss4
3. Copy the application archive, for example prsysmgmt_jboss4.war, to the
directory:
# cp /PegaRULES/archives/prsysmgmt_jboss4.war $JBOSS_HOME/server/pega/deploy
4. Extract the application archive into the folder.
# jar -xvf
prsysmgmt_jboss4.war
For more details on the System Management Application, refer to the System
Management Application Reference Guide.
Deploying the Online Help Application
Deploy the online help application (prhelp.war) in the same manner as the
System Management Application (prsysmgmt_jboss4.war).
Assigning the PegaDiagnosticUser Role to your System
Management Application Users
Users accessing the System Management Application in Process Commander must be assigned
the role PegaDiagnosticUser. If the user does not have this role they will be challenged for
authentication when they attempt to access the System Management Application from Process
Commander.
The role PegaDiagnosticUser is associated with the System Management
Application through a security-constraint element on the Diagnostic Data servlet
defined in the prweb.war application’s web.xml file:
- <security-constraint>
- <web-resource-collection>
<web-resource-name>Diagnostic Data</web-resource-name>
<description>Serves diagnostic files generated by the JMX
client</description>
<url-pattern>/DiagnosticData</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
- <auth-constraint>
<role-name>PegaDiagnosticUser</role-name>
</auth-constraint>
</security-constraint>
If you do not want to restrict access to the System Management Application, edit the web.xml file
in the WEB-INF directory of the prweb.war deployment in your application server and delete this
security constraint element.