4.1.3 Updating the Installation Properties

Set the following properties in install.xml:

Property	Description
install.str.container-type	Default value: `platform` This property determines the type of installation that is to be performed: `platform` - All the files required to run the Platform and any other pico process are installed. `execution` - Only the files required to run EC/ECSAs and/or SCs are installed. Set the value of `install.str.container-type` to `execution.`
install.str.config-script	Default value: `-` This property specifies the path and name of a shell script that you may run after the installation of the Execution Container: The following script is available is available in the release content directory: `scripts/str-templates/basic.sh` - Adds an EC ( `ec1` ) and an ECSA (ecsa1) and SCs for Couchbase and Zookeper services (sc1-sc3 and zk1-zk3). When you use the default value ( `-` ), the installation will not include any pico configurations.
install.str.mz_platform	Default value: `http://localhost:9000` This property specifies a URL, which contains the IP address or hostname of the Platform Container and the Web Interface port. When you have entered a hostname and failover occurs, the hostname is retrieved from the DNS enabling reconnection. If you have entered a static IP address as the value of this property reconnection issues may occur if the IP address changes. The port must be unique for each system.
install.str.remote.enabled	Default value: `true` This property enables remote execution, e g you can use the mzsh command `system` to start and stop pico instances on remote container hosts. By default, this will perform the following steps: Add the Platform's public key to `~/.ssh/authorized_keys` This allows the holder of the platform key to log in to this host via SSH Add SSH connection information for this host to the STR, including: ssh-address: The hostname of this host (e.g. $(hostname)) ssh-port: 22: Default SSH port hostkeys: Discovered SSH public keys for this host in known file locations If this is not desired, or if the default values are not suitable, set this value to false. It's still possible to enable remote execution after the installation by using the mzsh command `topo setupremote.`
mz.home	Default value: `/opt/mz` This property specifies the target directory for the installed container. This value must be identical to the environment variable MZ_HOME, described in 3.1.1 Environment Variables.
mz.container	Default value: " " Example value: `execution1` This property specifies an identifier for the installed container. Each container in your system must have a unique identifier. Typical values for `mz.container` is the hostname, or a descriptive value for the purpose of the container. The permitted characters for the container identifier are 'a-z','0-9' and '-'.
install.security	Default value: "true" Use the same value for this property as in the Platform Container installation. Set the value to `true` if HTTPS is used for communication with the Platform, otherwise `false`.
mz.name	Default value: MZ Example value: `MZ8` This property specifies the name of the system that the container belongs to.
mz.3pp.dir	Default value: `/opt/3pp` This property is not applicable for installation of Execution Containers. Use the default value.

The properties for the keystore listed below are for when Platform has two way SSL authentication enabled. This is when pico.rcp.tls.require_clientauth is set to true on the Platform. For more information on how to enable SSL encryption between Platform and EC, refer to 4.2 RCP Encryption

Property	Description
`p`ico.rcp.tls.keystore	Default value: "" The absolute path to the keystore, depends on the security policy, both Platform and EC servers can share the same certificate or be using two different certificates.
pico.rcp.tls.keystore.password	Default value: "" The password to access the keystore. The password should be in encrypted format using the mzsh encryptpassword command.
pico.rcp.tls.key.password	Default value: "" The password to access the key inside the keystore. The password should be in encrypted format using the mzsh encryptpassword command.
pico.rcp.tls.keystore.alias	Default value: "" The alias of the key inside the keystore. This must be specified if there are multiple aliases present within the keystore.

Next:

4.1.4 Extracting Files