When you start a Hazelcast member without passing a
Config object, as explained in the Configuring Programmatically section, Hazelcast checks the member's configuration as follows:
First, it looks for the
hazelcast.configsystem property. If it is set, its value is used as the path. This is useful if you want to be able to change your Hazelcast configuration; you can do this because it is not embedded within the application. You can set the
configoption with the following command:
<path to the hazelcast.xml>.
The path can be a regular one or a classpath reference with the prefix
If the above system property is not set, Hazelcast then checks whether there is a
hazelcast.xmlfile in the working directory.
If not, it then checks whether
hazelcast.xmlexists on the classpath.
If none of the above works, Hazelcast loads the default configuration (
hazelcast.xml) that comes with your Hazelcast package.
Before configuring Hazelcast, please try to work with the default configuration to see if it works for you. This default configuration should be fine for most of the users. If not, you can consider to modify the configuration to be more suitable for your environment.