Securing Database Communications

The following sections explain how to secure communications for the databases supported with gWLM.

No steps are needed to secure Postgres communications.

Oracle communications are not secure by default in the HP-UX environment. To secure communications:




	NOTE: This procedures affects gWLM, HP Capacity Advisor, and HP Virtualization Manager as they all communicate with the Oracle database in the same manner.

Open /etc/opt/gwlm/conf/gwlmcms.properties in a text editor.
Set the property com.hp.gwlm.jdbc.oracle.secure to 'on'.
Set the following properties as desired:
- oracle.net.encryption_types_client
- oracle.net.crypto_checksum_types_client
For more information on these properties, read their associated comments in the gwlmcms.properties file.
Ensure the Oracle listener and port being used by HP SIM is configured to accept secure communication for the encryption and checksum types specified in the previous step.
The Oracle database administrator can use netmgr to configure settings on the Oracle server.
Restart the gWLM CMS daemon (/opt/gwlm/bin/gwlmcmsd)

To disable secure Oracle communications:

Technical documentation