HP 3PAR StoreServ 7200 2-node HP 3PAR Policy Server Administrator's G - Page 70

This step depends on what you changed, Continue to the next for details.

Get HP 3PAR StoreServ 7200 2-node PDF manuals and user guides View all HP 3PAR StoreServ 7200 2-node manuals
Add to My Manuals
Save this manual to your list of manuals

Page 70 highlights

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 The installation program sets this path based on where you uses for the HSQL database 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 The default user name is ADMIN. What appears here should internally when accessing the HSQL be the name you entered during installation. The name must database. 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 Default is 5 (connections). Supports up to the maximum connections to maintain in memory. 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 Default is 150 (connections). connections to maintain in memory. com.axeda.apm.jdbc. implementation_ class Connection manager implementation Do NOT change the default, which is class. com.axeda.common.jdbc.hsql. HSQLConnectionManager. HP 3PAR Policy Server 7-6

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
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
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
.