Using system properties instead of pulse.properties

Products

• VMware Tanzu Gemfire

Issue/Introduction

This articles describes about using system properties instead of pulse.properties.

Resolution

If using the pulse properties there are no issues. Using system properties hardcoding the pulse.properties can be avoided. But what system properties is Pulse expecting? When removing the pulse.properties the following error is logged:

[INFO 2015/04/22 11:08:43.387 EDT localhost-startStop-1 tid=0x15] (msgTID=21 msgSN=5) [PULSE] 
[com.vmware.gemfire.tools.pulse.internal.log.PulseLogWriter] 
Getting locator/manager details through System Properties..
[INFO 2015/04/22 11:08:43.387 EDT localhost-startStop-1 tid=0x15] (msgTID=21 msgSN=6) [PULSE] 
[com.vmware.gemfire.tools.pulse.internal.log.PulseLogWriter] 
Locator/Manager Properties NOT Found..Reason: System Properties Not Found..

Solution

Pulse is looking for the following system properties and gives the error if any of them are not found:

-Dpulse.embedded=true/false
-Dpulse.useLocator=true/false
-Dpulse.host=IP or host name 
-Dpulse.port=port

Additional Information

Applies to

GemFire 7 and later
Pulse running in non-embedded mode