Distributing the Software

Regardless of which method you choose to distribute the software (CD, network copy, etc.) be sure the original package (NFMPackage.exe) and the response file (Setup.iss) are distributed to the target system.

Step 3: Install the Software Package

Once both files (NFMPackage.exe and Setup.iss) are on the target system, you can install the NFM package with the following command:

ADMINISTRATIVE FEATURES: NFM CLIENT COMPONENT

NFMPackage.exe /s /a /s /SMS /f1”C:\<PATH>\Setup.iss” /f2”C:\<PATH>\Setup.log”

Where: /s – silent mode for package installation

/a – adds / passes remaining options to SETUP.exe /s - silent mode for SETUP.exe

/SMS - waits for SETUP.exe to finish before exiting /f1 – full path to the response file

/f2 – full path to the install log

After the package has been installed, the Setup.log will contain a “ResultCode” value that is the success or failure of the install. Here is a list of possible result codes:

0 Success. -1 General error. -2 Invalid mode.

-3 Required data not found in the Setup.iss file. -4 Not enough memory available.

-5 File does not exist.

-6 Cannot write to the response file. -7 Unable to write to the log file.

-8 Invalid path to the InstallShield Silent response file. -9 Not a valid list type (string or number).

-10 Data type is invalid.

-11 Unknown error during setup. -12 Dialog boxes are out of order. -51 Cannot create the specified folder.

-52 Cannot access the specified file or folder. -53 Invalid option selected.

** These values are not generated by NFM ** but instead by InstallShield. For additional questions related to InstallShield’s automated installs please consult

www.installshield.com

NFM Client files / directories:

<product directory>

bin NFM Client binaries / executables and config files <working directory>

logs NFM Client logs ssl SSL related files

ADMINISTRATIVE FEATURES: NFM CLIENT COMPONENT

Line added to startup script / service:

AIX (/etc/inittab): nfmclient:2:respawn:/usr/lpp/tps/nfmc/bin/nfmclient Linux (/etc/inittab): nfc:2345:respawn:/opt/tps/nfmc/bin/nfmclient

Sun (/etc/inittab): nf:234:respawn:/opt/tps/nfmc/bin/nfmclient SCO (/etc/inittab): nf:234:respawn:/opt/tps/nfmc/bin/nfmclient Windows

(The NFM Client is set to start as a Windows Service from the Windows Services Control Panel) ** When NFM Client is installed, the ‘Startup Type’ is set to Manual. It is recommended that you change this to Automatic, so the Service will start whenever the OS is started.

NFM Client Processes

Process Name Description

nfmclient _{NFM client program. One instance should always exist} while the NFM client is running which should be all the time.

ADMINISTRATIVE FEATURES: NFM CLIENT COMPONENT

nfmi _{NFM remote command line utility program. Loaded as} needed.

Removing the NFM Client package:

Removal can be done with the following commands:

OS Uninstall Command

AIX /usr/lpp/tps/nfm/bin/uninstall * Linux /opt/tps/nfm/bin/uninstall *

Windows Go to Windows Control panel, select ‘Add Remove Programs’, select ‘TPS/NFM Client”, press the “Remove” or “Uninstall” button. **

* The uninstall script will remove everything in /opt/tps/nfmc/ or /usr/lpp/tps/nfmc; however it will NOT delete anything in the /var/tps/nfmc directories. If you want NFM Client removed completely you will have to remove everything in /var/tps/nfmc manually.

** Uninstall will remove everything in C:/Program Files/TPS Systems/NFMClient except the log directory. If you want NFM Client removed completely you will have to remove these directories manually.

Creating NFM Client Backups

The following directories should be backed up regularly. These directories contain configuration files for

UNIX:

/var/tps/nfmc/* Windows:

C:\Program Files\TPS Systems\NFMClient\*

NFM Client Configuration File

NFM Client uses an optional configuration file that resides in the NFM Client’s main install directory and is usually called nfm.cfg. Settings inside this configuration file will override the default NFM settings. Some reasons for using an NFM Client configuration file include:

ADMINISTRATIVE FEATURES: NFM CLIENT COMPONENT

Want the client to use a different TCP/IP port. Want to use SSL type communications

Want the client to use multiple connections or sockets

Want the client to use a different connection type other than Listen

A configuration file looks something like this: NFMSERVER=nfmserver

NFMNODE=unknown

CONNECT=LISTEN, PORT=8008, INTERVAL=, DURATION=, SSL=0, KEY=, CERTIFICATE=,

The first part contains the following fields:

NFMSERVER=[address] This field should be set to the IP address or hostname that the NFM server is running on.

NFMNODE=[name] This field should be set to the NFM node name that represents this node.

(NOTE: These two fields are only required if a CONNECT record of type PERMANENT is defined below).

The remaining portion of the file contains one or more connection entries. These entries should equivalent to the connection entries defined in the NFM node or model definition for this node. The following fields are available:

CONNECT=[type] This field should be set to the required connection type. Currently supported values are LISTEN and PERMANENT.

PORT=[number] This field should be set to desired port for this connection.

ADMINISTRATIVE FEATURES: TROUBLESHOOTING