Installation Instructions for the Sun MTP Client for Unix
---------------------------------------------------------


Unloading the Tar Image
-----------------------

The Sun MTP Client for Unix is supplied as a 'tar' format archive.

The tar image may be installed anywhere convenient on your machine, but
for your convenience, it is recommended that you use the following 
directory name as your installation root:

On AIX:		/usr/lpp/kixcli
On HP-UX:	/opt/kixcli
On Solaris:	/opt/kixcli

This directory will be referred to as $INSTROOT

As root perform the following:

mkdir $INSTROOT
cd $INSTROOT
tar -xvf kixcli.tar

It is recommended that you reserve a unix User and Group from 
which the MTP Client can be run. For the purposes of this document
it is proposed that you use the UserID 'kixcli' and GroupID 'kixcli'.

Ensure that this User and Group exist and then:

chgrp -R kixcli $INSTROOT
chown -R kixcli $INSTROOT

The files comprising the MTP Client are now installed.

Accessing Binaries
------------------

At this point is is recommended that you cease being root, and log
on again as the user defined to run the MTP Client (e.g. kixcli).

The environment of this user must be modified to access to the following
directory which containes the product binaries:

$INSTROOT/bin

e.g. using korn shell

export PATH=$PATH:$INSTROOT/bin

Accessing Libraries
-------------------

If you installed the MTP Client under the recommended $INSTROOT for
your platform, then no explicit action is required to allow access to the 
product shared libraries.

If however, you installed the MTP Client in some other directory, then
you must modify the environment of the user who is to run the MTP Client
to allow access to these libraries.

		
On AIX:
	export LIBPATH=$LIBPATH:$INSTROOT/lib

On HP-UX:
	export SHLIB_PATH=$SHLIB_PATH:$INSTROOT/lib

On Solaris:
	export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$INSTROOT/lib


Configuring the MTP Client
--------------------------

It is possible to run one or more instances of the MTP Client on a single
machine. Each instance of the client requires a directory reserved for its
use. If you are only planning on running a single instance of the MTP Client
then the home directory of the 'kixcli' user, or a subdirectory thereof,
might be a sensible place.

This directory will contain:

1) The Client configuration file 'kixcli.ini'
2) The Client message file 'kixcli.msg'
3) Any diagnostic trace or dump files


You must set the environment variable KIXCLI to refer to this directory, e.g.:

export KIXCLI=/home/kixcli

This variable must be set before the MTP Client can be started, and before
running any ECI/EPI Applications.

You must then copy the default configuration file to this directory:

cp $INSTROOT/config/kixcli.ini $KIXCLI

You must then edit this file, e.g.

vi $KIXCLI/kixcli.ini

and define system entries for the MTP systems you wish to access.

Starting the MTP Client
---------------------------

Once all this has been done, you can start the MTP Client. e.g.

kixcli &

This executable is designed to be run as a background daemon (so that it
can be started at machine boot time from 'inittab'). It therefore writes
its messages to a file, $KIXCLI/kixcli.msg, rather than to standard output
or standard error.

In the event of any problems, you should inspect the contents of this file.

Using the Control Program 'kixctl'
----------------------------------

Once the client has been started the client control program, kixctl,
can be used. First ensure that you have the KIXCLI environment variable
set, then you can perform the following commands:

kixctl -l		(list defined MTP systems and their states)
kixctl -c <system>	(manually connect to system <system>)
kixctl -d <system>	(manually disconnect to system <system>)
kixctl -m		(monitor state changes of defined systems)
kixctl -s		(shut down the MTP Client)
kixctl -D		(perform dump of the Client)
kixctl -t <mask>	(change the Trace Mask to <mask>)

Running Applications
--------------------

In order to run an ECI or EPI application, you must first set the 
KIXCLI environment variable to define which instance of the MTP Client
you wish that application to access.

With the MTP Client (kixcli) started, you can run any number of 
ECI or EPI applications.

Threading Support
-----------------

The MTP Client for Unix does not support calls to the ECI or EPI from
multiple threads in the same process concurrently. The results obtained when
doing this will be spurious, but will normally result in the application being
told that the call was on a callback.
