Installation Parameters

The installation parameters are organized under the following sections:

silent.cfg Parameters

The following table lists the parameters supported in the silent.cfg file.

Parameter Description
AcceptEula

Defines whether you have accepted the EULA (End User License Agreement).

  • Yes: You have read and accepted the EULA.

  • No: You have not accepted the EULA. The installation is terminated.

InstallDirectory

Defines the installation directory for the Platform Server.

SaveAndRestoreConfig

When installing over an existing Platform Server installation, it defines whether to save and restore the configuration files.

  • Yes: Saves and restores configuration files.

  • No: Overwrites the configuration files.

CreateSoftLinks

Defines whether you want to create soft links for the run-time libraries in the /usr/lib directory.

  • Yes: Creates soft links for the run-time libraries in /usr/lib. This parameter is only allowed when installing in root mode.

  • No: Does not create soft links. Use the LD_LIBRARY_PATH (or LIBPATH on AIX) to define where the runtime libraries are located.

AdminGroup Defines the name of the admin group. The default admin group name is cfadmin.
BrowseGroup Defines the name of the browse group. The default admin group name is cfbrowse.
TransferGroup Defines the name of the transfer group. The default transfer group name is cftransfer.
CCNodeName

Defines the name of the CC node that is created at the end of the installation. When this parameter is not defined, the CC node is not created.

Note: Ensure that CCNodeName does not have spaces in it.
CCNodeIPName Defines the IP name or IP address of the CC node that is created at the end of the installation.
CCNodeIPPort Defines the IP port of the CC node that is created at the end of the installation.
CCCollector

Defines whether Command Center (CC) is already collecting Log.txt transaction history from this machine. cccollector must be defined on upgrade, when there is already another PSU instance installed on the machine. If this is a brand new installation or an upgrade into an existing folder, the cccollector parameter can be omitted altogether because there is no potential issue with CC collecting Log.txt transaction history from this machine.

  • Yes: CC Collector is already collecting log records from this machine. If a user is already collecting logs from the machine but installing version 8.1.1 in a different folder, the cccollector value should be yes. In this case, at the end of installation, there is a message to reset CC Collector server for the machine.

  • No: CC Collector is not collecting log records from this machine. If a user is not collecting logs from the machine, but installing version 8.1.1 in a different folder, the cccollector value should be no. In this case, there is no collector messages at the end of installation.

Note: This parameter is defined to let the silent installer know that collection is being performed and that the user may need to copy the Log.txt files to the new log file directory.
HAMode

Defines whether HA is enabled by this installation.

  • Yes: HA mode is enabled.

  • No: HA mode is not enabled (Default).

Note: HA Mode can be configured via hainstall script after the installation is over. When Yes is defined, the HA parameters below must be defined.
HASharedDirectory Defines the name of the HA shared directory. This directory must be accessible for read/write access to all Platform Server instances in the HA cluster.
HAPrimaryRPCIPName Defines the IP name or IP address of the primary CyberMgr daemon. When running in an HA cluster, the HAPrimaryRPCIPName and HASecondaryRPCIPName parameters must be defined in the same order for all Platform Server instances in a cluster.
HASecondaryRPCIPName Defines the IP name or IP address of the secondary CyberMgr daemon. When running in an HA cluster, the HAPrimaryRPCIPName and HASecondaryRPCIPName parameters must be defined in the same order for all Platform Server instances in a cluster.
HAPrimaryRPCPort Defines the IP port of the primary CyberMgr daemon.
HASecondaryRPCPort Defines the IP port of the secondary CyberMgr daemon.
HAUseMyConfigFiles

Defines whether to copy the configuration files in the local installation to the shared configuration directory.

  • Create: Copies the configuration files but does not replace existing files. (Default)

  • Replace: Copies the configuration files to the shared directory. If there are already files in the shared directory, they are replaced. Backup of replaced files is available.

  • No: Does not copy the configuration files to the shared directory.

Command-Line Parameters

The following table lists the parameters supported by the install command in alphabetical order.

Parameter Usage
-accepteula Accepts the End User License Agreement.
-agr Defines the name for the Admin group.
-bgr Defines the name for the Audit Browse group.
-c Saves and restores configuration files during a re-installation.
-ccnode Defines the Command Center node. You must enter the fields in the following format:
-ccnode 
							cc_node_namecc_node_host cc_node_port
-cfiles

Defines the configuration files. Only one of the options below can be set.

c - Copies the configuration files but does not replace existing files. (Default)" " ( use this server's configuration files only if there are no existing configuration files in the shared HA environment).

r - Replaces the configuration files. The server configuration files are used in the shared HA environment.

n - Does not copy the server configuration files. The server configuration files are not used in the shared HA environment.

-d Defines the directory where TIBCO MFT Platform Server for z/Linux is installed.
-dshared Defines the directory path accessible by all machines.
-h or -? Displays help.
-hprimary Defines the host name for the primary RPC service.
-hsecondary Defines the host name for the secondary RPC service.
-n Saves but does not restore configuration files during a re-installation.
-q Uses the default installation options. Does not ask any questions. Runs the script in silent mode without user input.
-tgr Defines the name for the Transfer group.
-ugr Configures special group names.
-ulnk Creates links in the /usr/lib directory for files in the $CFROOT/libs directory.
Note:  

When using the ulnk parameter:

  • The install.noroot script does not support the ulnk parameter because root rights are required to create these links.
  • Soft links are created in the /usr/lib directory for each file in the $CFROOT/libs directory.
  • If a soft link that points to the files in the $CFROOT/libs directory already exists in the /usr/lib directory, a link is not created. In this case, you have to set the LD_LIBRARY_PATH environment variable before using TIBCO MFT Platform Server for z/Linux.
  • You must be careful when you create links for different versions of TIBCO MFT Platform Server for z/Linux. If the lib files are not in the /usr/lib directory, you can require LD_LIBRARY_PATH for different versions of TIBCO MFT Platform Server for z/Linux.

-cccollector

Defines whether Command Center (CC) is already collecting Log.txt transaction history from this machine. cccollector must be defined on upgrade, when there is already another PSU instance installed on the machine. If this is a brand new installation or an upgrade into an existing folder, the cccollector parameter can be omitted altogether because there is no potential issue with CC collecting Log.txt transaction history from this machine.

  • Yes: CC Collector is already collecting log records from this machine. If a user is already collecting logs from the machine but installing version 8.1.1 in a different folder, the cccollector value should be yes. In this case, at the end of installation, there is a message to reset CC Collector server for the machine.

  • No: CC Collector is not collecting log records from this machine. If a user is not collecting logs from the machine, but installing version 8.1.1 in a different folder, the -cccollector value should be no. In this case, there is no collector message at the end of installation.

Note: This parameter is defined to let the silent installer know that collection is being performed and that the user may need to copy the Log.txt files to the log file directory.
-hamode

Defines that HA mode is enabled for this installation. You must enter the fields in the following format.

-hamode      -dshared shareddirectory
             -hprimary primaryrpcipname
             -hsecondary secondaryrpcipname
             -cfiles c|r|n  

The -cfiles option is the same as HAUseMyConfigFiles in the silent.cfg file.