Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Set the platform related properties described below in the install.xml file. The properties are described in the order they appear in the install.xml file.

General Database Properties

PropertyDescription
mz.jdbc.type

Default value: derby

This property specifies the platform database you want to use.

The supported options are derby, oracle, postgresql, or saphana. double check if this is how it's stated when sapahana has been added

mz.jdbc.user

Default value: mzadmin

This property specifies the username of the database that the Platform will be using during runtime.

Note!

The installation will fail if the same username is configured for both the Oracle database owner, install.ora.owner, and the runtime (jdbc) user. If it is necessary to have the same username for both users, then the oracle_user.sql file must be manually updated prior to creation of the database.

mz.jdbc.password

Default value: mz

This property specifies the password for the jdbc user, described above.

The password can be changed at a later stage by using the mzsh changedbpw commmand. See mzsh  Command Line Tool User's Guide for further information. 

mz.jdbc.url

Default value: ""

This property can be used for explicitly specifying the JDBC URL. If it is not specified, then it will be calculated based on the other database parameters described below.

install.db.jdbc.user

Default value: mzadmin

Check on input for this property

install.db.jdbc.password

Default value: mz

Check on input for this property

install.db.owner

Default value: mzowner

Check on input for this property

install.db.password

Default value: mz

Check on input for this property

3pp Properties

PropertyDescription

mz.3pp.dir

Default value: /opt/3pp

This property specifies the directory where to store 3pp files required by various parts of the system, such as jar files for Oracle, the SAP RFC agent, the SAP JCo agent, the SAP CC agents, the JMS agents  Data Veracity, the Kafka profile, the various DB connectors. Double check if all of these are included

The files will be moved to the $MZ_HOME/3pp directory during installation.

Note!

Make sure that the /opt/3pp directory does not reside in the installation directory, MZ_HOME, during installation.

Common Properties

PropertyDescription

pico.rcp.platform.host

Default value: ""

Example value: 192.168.0.190

This property specifies the IP address or the hostname of the Platform to be used by other pico instances such as Execution Contexts, Service Contexts or Command Line.

If a failover occurs and you have entered a hostname as the value for this property, the hostname will be retrieved from the DNS enabling reconnection. If you have entered a static IP address as the value for this property, reconnection issues may occur after a failover, if the IP address has changed.

pico.rcp.platform.port

Default value: 6790

This property specifies the port for connecting the Execution Contexts to the Platform.

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.

If a failover occurs and you have entered a hostname as the value for this property, the hostname will be retrieved from the DNS enabling reconnection. If you have entered a static IP address as the value for this property, reconnection issues may occur after a failover, if the IP address has changed.

When the value for 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. For information about high availability, see 2.6.6 High Availability Properties.

mz.webserver.port

Default value: "9000"

This property specifies the port for connecting the Desktop to the Platform. If you install a second  instance, this port value must be different in order to not clash with the first instance.

Config Properties

PropertyDescription
mz.name

Default value: DR

This property specifies the name of the  deployment.

Notification Properties

PropertyDescription

mz.notifier.mailfrom

Default value: ""

Example value: mzadmin@company.com

This property specifies the sending signature that will be used for event generated e-mails, presented as a label.

mz.mailserver.host

Default value: ""

Example value: SMTP.server

This property specifies the name or IP address of the mail server that will be used for event generated e-mails. check if this is the property name to be used, in PE it is only called mz.mailserver

Execution Context Properties - Not Used in Platform Only Installations

PropertyDescription

mz.eclist

Default value: ec1

This property specifies the EC(s) to be installed. Only applicable if install.types includes ec.

ec.backlog.dir

Default value: ${mz.home}/tmp

This property specifies the directory where ECs can store their backlogged events. If this parameter is removed, the EC's events will not be logged. Only applicable if install.types includes ec.

ec.webserver.enabled

Default value: true

This property specifies if the web server for Execution Contexts should be active. Only applicable if install.types includes ec.

ec.webserver.port

Default value: 9090

This property specifies the port for the EC web server. Only applicable if install.types includes ec.

Note!

If using several ECs, the executioncontext.xml file needs to be modified to use separate ports for each EC, once the installation has been completed.

  • No labels