HP 3PAR Policy Server Administrator's Guide (QR483-96003, December 2012)

HP 3PAR Policy Server 7-6
7. This step depends on what you changed:
 If you changed the directory server configuration, you must also edit the Tomcat server.xml file.
Continue to the next section for details.
 If you decided to switch to using SSL, refer to the Tomcat document, SSL-HOW TO, at
http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html.
 If you do not need to edit the server.xml file, restart Policy Server.
Table 7-1 Properties in PolicyManager.properties
Name Description Supported values
Server Information
com.axeda.apm.
startup.name
Name of your HP 3PAR Policy
Server. This string appears in the
server console window only.
Any valid text string, up to 250 characters. For example, HP
3PAR Policy Server.
com.axeda.apm.
startup.version
Build number for this HP 3PAR
Policy Server. For example, 6.5
Build 650108 (2012/06/15
10:11 EDT)
Do NOT Change. Reference this number when contacting
Technical Support.
JDBC Settings - settings for Policy Server to communicate with the HSQL database
com.axeda.apm.jdbc.
HostURL
Address that HP 3PAR Policy Server
uses for the HSQL database
The installation program sets this path based on where you
choose to install Policy Server. For example, the default
installation path on Windows is C:\Program Files (x86)HP
3PAR\PolicyServer. and on Linux it is
/root/HP3PAR/PolicyServer The value here always uses the
forward slashes, as in the following example for a Windows
installation:
jdbc:hsqldb:hsql://localhost:9001/apm
com.axeda.apm.jdbc.user
User name for Policy Server to use
internally when accessing the HSQL
database.
The default user name is
ADMIN. What appears here should
be the name you entered during installation. The name must
be all uppercase.
com.axeda.apm.jdbc.
password
Password for Policy Server to use
with the JDBC user name for
accessing the HSQL database.
The default password is
admin. What appears here should
be the password you entered during installation. It is NOT
encrypted.
com.axeda.apm.jdbc.
initial_pool_size
The initial number of database
connections to maintain in memory.
Default is 5 (connections). Supports up to the maximum
number of database connections, which is set by the
property, com.axeda.apm.jdbc. max_pool_size).
com.axeda.apm.jdbc.
max_pool_size
The maximum number of database
connections to maintain in memory.
Default is 150 (connections).
com.axeda.apm.jdbc.
implementation_
class
Connection manager implementation
class.
Do NOT change the default, which is
com.axeda.common.jdbc.hsql.
HSQLConnectionManager
.