Installation guide

# jar -xvf prweb.war

Specify explicit temp directory in prconfig.xml

1. In the application directory, open the Process Commander configuration

file, $JBOSS_HOME/server/pega/deploy/prweb.war/WEB-

INF/classes/prconfig.xml.

2. Find the env element for the temporary directory:

3. Replace $(pega.tmpdir) with the complete path to a directory that Process

Commander can use for static content and other temporary storage, for

example:

Note: If the directory you specify does not exist, Process Commander will

attempt to allocate it. It is good practice to allocate the directory on the

system before specifying it here.

The directory names you enter here are case sensitive. Be sure to enter the

names of the directories exactly as they have been created on your system.

It is also important to make sure that the Process Commander user on the

system has the appropriate permissions, including write access, to use this

directory. In particular, if you have J2SE security enabled, ensure that this

directory is accessible under your security policy.

Deploying prsysmgmt_jboss4.war or .ear

The System Management Application is distributed both as a WAR file and an EAR file and in two

versions:

– prsysmgmt_jboss.war or .ear for JBoss EAP 5 deployments

– prsysmgmt_jboss4.war or .ear for JBoss EAP 4 deployments

Be sure to use prsysmgmt_jboss4.war or prsysmgmt_jboss4.ear for JBoss EAP 4 deployments.

The System Management Application must be deployed in an expanded deployment.

1. Make sure the server is stopped.

2. Create a folder with the name of the application file, for example

‘prsysmgmt_jboss4.war’ in <jboss_home>\ server\ <your_server_name>\

deploy\

# cd $JBOSS_HOME/server/pega/deploy