Command-Line Parameters

The following table lists all the parameters supported on the command line and their usage.

Parameter Usage
-d Defines the directory where TIBCO MFT Platform Server for UNIX is installed.
-q Runs the script in silent mode without user input.
-c Saves and restores configuration files during a re-installation.
-n Saves but does not restore configuration files during a re-installation.
-ulnk Creates links in the /usr/lib directory for files in the /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 /libs directory.
  • If a soft link file pointed to the files in the /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 UNIX.
  • You must be careful when you create links for different versions of TIBCO MFT Platform Server for UNIX. 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 UNIX.

-ugr Configures special group names.
-agr Defines the name for the Admin group.
-bgr Defines the name for the Audit Browse group.
-tgr Defines the name for the Transfer group.
-accepteula Accepts the End User License Agreement.
-h (-?) Displays online help for the install script.
-ccnode Defines the Command Center node. You must enter the fields in the following format:
-ccnode 
							cc_node_name cc_node_host cc_node_port
-hamode

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

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

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

-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 log file directory.