Set the following properties in install.xml:
Property | Description | ||
---|---|---|---|
install.str.container-type | Default value: This property determines the type of installation that is to be performed:
Set the value of | ||
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:
When you use the default value ( | ||
install.str.mz_platform | Default value: 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 |
Note |
---|
This allows the holder of the platform key to log in to this host via SSH |
- 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.
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 Setting Environment Variables for Platform.
Default value: " "
Example value: execution1
ec1
This property specifies an identifier for the installed container. Each container in your system must have a unique identifier.
Typical values for The typical value of the 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 '-'.
Default value: "true"
Use the same value for this property as in the Platform Container installation. Set the value totrue
if HTTPS is used for communication with the Platform, otherwise false
.
Default
value: MZExamplevalue:
MZ8
/opt/mz
This property specifies the
nametarget directory of the
system that the container belongs to.mz.3pp.dirinstalled container and is automatically set to the environment variable you specified for MZ_HOME when Setting Environment Variables for Platform.
install.types
Default value:
/opt/3pp
platform,ec
This property
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 /wiki/spaces/MD82/pages/3778807
Property | Description | ||
---|---|---|---|
| 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 specifies which parts of the system you want to install. For the Execution container installation, you should set this to only ec. | |||
install.admin.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 This property specifies the password of the administrative user mzadmin. The value must be | ||
install.security | 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
This property specifies if the password of the mzadmin user must be changed during the installation and if enhanced security user control will be used. A valid certificate in a keystore is required for the installation. If it is not already prepared, the installation process will create a new one when prompted. More information can be found in Network Security. |