This section describes properties that are applicable to both the Platform and ECs.

For Private Cloud and AWS, the properties are stored in the values.yaml files for the Platform and ECD, where you define the systemProperties. Or in the EC Deployment web interface to configure ECs.

Installed Properties

The properties described in this section are automatically included in the values.yaml files when Usage Engine is installed.

Property	Description
pico.cache.basedir	Default value: `$MZ_HOME/pico-cache` This property specifies the directory that should be used for the pico-cache that is cashing information about all running picos, which is used by all servers and clients.
pico.rcp.platform.host	Default value: "" This property specifies the IP address or the hostname of the Platform, to be used by other pico instances (e g Desktop, Execution Context, and mzsh). When you enter the hostname as the value of this property, if a failover occurs, the hostname is retrieved from the DNS enabling reconnection. If you enter the IP address as the value of this property, if it is a static IP address, reconnection issues may occur if the IP address changes.
pico.rcp.platform.port	Default value: `6790` This property specifies the port that is used for communicating with the Platform.
pico.synchronizer.port	Default value: `6791` This property specifies the port that is used for synchronizing files from the Platform to external ECs.
pico.rcp.server.host	Default value: `""` This property specifies the IP address or hostname of the pico instances. It will be used to determine the interface that the pico instances must bind to and the IP address/hostname that will be used by connecting processes. When you enter the hostname as the value of this property, if a failover occurs, the hostname is retrieved from the DNS enabling reconnection. If you enter the IP address as the value of this property, if it is a static IP address, reconnection issues may occur if the IP address changes. When the value of this property is left blank, the pico instance will bind to all IP addresses of the host. This means that the pico will listen for inbound network traffic on all network interfaces, and may attempt to use any local IP address for outbound network traffic. Note! If there is more than one IP address for the host, this property has to be set with the correct IP address. Make sure to set the property if you use IPv6, or if a high availability environment is configured. Note! When `pico.rcp.server.host` is set in the Platform Container, the value must be identical to `pico.rcp.platform.host.`
pico.rcp.server.bind_interfaces	Default value: `""` When you set the property `pico.rcp.server.host`, pico instances will only bind to the interface associated with that IP address. Due to the network configuration, it may be required by pico instances to bind to additional interfaces. You can specify these by specifying a comma-separated list of IP address or hostnames in the property pico.rcp.server.bind_interfaces. It is also possible to set this property to the value `ALL` to ensure that the pico instances will bind to all interfaces, even though `pico.rcp.server.host` has been set. If you have not set `pico.rcp.server.host`, the property `pico.rcp.server.bind_interfaces` will have no effect. Example - Using pico.rcp.server.bind_interfaces An EC named ec1 has one external and one internal IP address. Other ECs will have to use the hostname `ec1host` to be able to connect. The name ec1host maps to either the external or internal IP address depending on the client location in the network. To ensure that all connection attempts will use the hostname, you set the property `pico.rcp.server.host` to `ec1host`. This will then cause the ec1 to only bind to ec1host which will map to the internal IP address, since this is the local context. If an other EC on the external network, ec2 in this example, tries to connect to ec1, it will use the hostname ec1host which maps to the external IP. This will fail. To ensure connectivity you need to set `pico.rcp.server.bind_interfaces` to the external IP address or `ALL` to ensure that the incoming connection attempt from ec2 will succeed.
pico.tmpdir	Default value: `MZ_HOME/tmp` This property specifies the temp directory you want to use for your picos.
java.library.path	Default value: `${mz.home}/common/lib/native` This property must be set to `${mz.home}/common/lib/native`.

Additional Properties

The properties described in this section can be added to define different aspects of security.

Property	Description
mz.httpd.security	Default value: `""` This property enables HTTP communication protected by TLS (i e HTTPS).
mz.httpd.security.keystore	Default value: `""` This property specifies the path to the keystore that is used for HTTP/TLS.
mz.httpd.security.keystore.password	Default value: `""` This property must contain the password to the keystore specified in `mz.httpd.security.keystore`.
mz.httpd.security.key.password	Default value: `""` This property must contain the password to the key to the key that is used for HTTP/TLS. By default (in `keytool`), this is the same as the keystore password.
pico.rcp.tls.keystore	Default value: `""` This property specifies the path to a keystore and enables the system to use TLS for all RCP connections that are not from the local host. If this property is not set, TLS will not be used.
pico.rcp.tls.keystore.alias	Default value: `""` This property specifies which of the keys in the keystore that should used for RCP/TLS (if there are more than one). RCP will prefer to use the key with this keystore alias. If it is not set and the keystore contains more than one private key, it is undefined which key is used.
pico.rcp.tls.keystore.password	Default value: `""` This property must contain the password to the keystore specified in `pico.rcp.tls.keystore`.
pico.rcp.tls.key.password	Default value: `""` This property must contain the password to the key that is used for RCP/TLS. By default (in `keytool`), this is the same as the keystore password.
pico.rcp.tls.require_clientauth	Default value: `false` This property specifies if client authentication is required when these are not running on the local host.

Various other Properties that can be used.

Property	Description
mz.drdate.lenient	Default value: `false` This property enables lenient interpretation of the date/time in the string parameter in the APL function `strToDate`. With lenient interpretation, a date such as "January 32, 2016" will be treated as being equivalent to the 31nd day after January 1, 2016. With strict (non-lenient) interpretation, an invalid date will cause the function to leave the submitted date variable unchanged.
mz.outputstream.use_compact	Default value: `false` This property enables compact serialization of data. Enabling the property can optimize the size of your serialized data.
mz.preset.aggregation.storage.path	Default value: `false` This property enables hardcoding of the Aggregation profile directory to the specified path. The Desktop user will still be able to see the set directory, but not change it.
mz.preset.dupUDR.storage.path	Default value: `false` This property enables hardcoding of the Duplicate UDR profile directory to the specified path. The Desktop user will still be able to see the set directory, but not change it.
mz.preset.interwf.storage.path	Default value: `false` This property enables hardcoding of the Inter Workflow profile directory to the specified path. The Desktop user will still be able to see the set directory, but not change it.
mz.httpd.security	Default value: `false` This property enables HTTP communication protected by TLS (i e HTTPS).
mz.use.search	Default value: `true` Setting this property to "false" will disable the global search function in the Desktop. This will decrease the startup time of the Platform by approximately 10%.
mz.wi.xframeoptions	This property determines if X-Frame-Options are enabled in the Platform- and EC Web Interface in order to protect from framing. The valid values are: `DENY` - The X-Frame-Options are enabled so that the Web Interface cannot be displayed in a frame. `ALLOW` - The X-Frame-Options are disabled so that the Web Interface can be displayed in a frame. `ALLOW-FROM <specific origin>` - The X-Frame-Options are disabled on a specific origin. This means that the Web Interface can only be displayed in a frame on the specified origin. `SAMEORIGIN` - The X-Frame-Options are disabled on the same origin as the Web Interface. This means that the Web Interface can only be displayed in a frame on the same origin as the Web Interface itself.
pico.rcp.connection.timeout	Default value: The value specified for `pico.rcp.timeout` This property determines the the RCP open connection timeouts in seconds. If you do not specify a value for this property, the value is the same as that set for the property `pico.rcp.timeout`.
pico.rcp.timeout	Default value: `30` This property determines the RCP handshake and heartbeat timeouts in seconds.
pico.upgrade_history	Default value: `${mz.home}/upgrade_history` This property specifies the directory where the new and old versions of Usage Engine packages patched into the system are stored.

Page tree

Common Properties[hide]2.0[/hide]

Installed Properties

Additional Properties

Various other Properties that can be used.