StoreGazer Setup Help
StoreGazer 4690 Installation
Introduction
EDJ StoreGazer for the 4690 Operating System consists of two separate applications:
EDJServr.286 and EDJAgent.286. It is recommended that EDJAgent is always running.
EDJServr will be called to execute when necessary.
Installation
The first step in setting up EDJ StoreGazer is to run the install package included
on the StoreGazer diskettes using the 'a:install a:' command. The installation
batch will create the required directories, define several logical filenames,
and distribute the StoreGazer files. The installation will prompt you to
determine if the EDJAgent application should automatically be configured as
a background application.
After StoreGazer is installed on your system, ensure that TCP/IP is available. If TCP/IP is not already installed on your system, please install it using the instructions provided with the TCP/IP installation diskettes.
The following files need to be modified on the 4690 for StoreGazer to work properly:
After these files are modified, the EDJAgent
configuration file must be updated. Once
this is complete, ensure the 'EDJGazer:EDJAgent.286' and
'Adx_spgm:Adxhsi9l.286' applications are configured to run in the
background. After a reboot, StoreGazer will be configured to run.
Hosts File - Adxhsihf.dat
Note: To find an IP for a particular controller, view the \ADX_SDT1\ADXIP##Z.BAT file (Replace ## with the controller ID).
Sample file: ADXIPCCZ.BAT
adxhxi2l ifconfig lan0 10.1.1.1
This file shows that the IP Address for Controller CC is 10.1.1.1. Let's assume there is also an alternate master controller DD, with an IP of 10.1.1.2. For StoreGazer to be able to perform actions on both CC and DD, they should both be defined in the hosts file. Listed below is a sample hosts file.
Sample file: ADXHSIHF.DAT
# /etc/hosts file 9.67.39.83 my4690host 9.67.39.81 fred 10.1.1.1 CC 10.1.1.2 DD
* - If hostnames are already defined for each controller in your store, this step can be skipped. If this is the case, you can use the DefineNode command in the configuration file to map each node ID to the appropriate hostname.
* - If you use dynamic IPs via a BOOTP server, you should enable the ResolveIPsByFile option.
SuperServer File - Adxhsiif.dat
Sample file: ADXHSIIF.DAT
ftp tcp ADX_SPGM:adxhsifl.286 telnet tcp ADX_SPGM:adxhsiul.286 edjserv tcp EDJGAZER:edjservr.286
Port File - Adxhsisf.dat
Sample file: ADXHSISF.DAT
# # Network services, Internet style # echo 7/tcp echo 7/udp ... nntp 119/tcp edjserv 1236/tcp # UNIX specific services ...