|
FRONT
END PROCESSOR |
|
Espańol Castellano Portuguese |
|
 |
The
Front End Processor |
|
Joining
a Windows NT Server Domain or A Novell Netware Server |
|
Drive
Mappings and Folders on the FEP |
|
Front End
Processor Environment Variables |
| |
| The
Front End Processor
|
|
The Front End Processor is the interface between
the Adjudicator and the network equipment. Two types of Front End
Processor now exist on the DPRX Teleclaim System. One is running on
Windows 98 with multi-port serial communications installed on the
system which is connected to the TeleGlobe x.25 PAD. A total of 8
ports can be accommodated on this machine. The X.25 PAD is an
interface with a modem directly connected to NDC. See Figure 10. |
|
|
|
Figure 10 (Front End Processor
running on X.25 network) |
| The other
type of Front End Processor runs on Windows NT Workstation 4.0. The
machine is equipped with two network cards, one connected to the
network hub where the file server, adjudicator and other peripherals
are connected and the other network card is connected to a router.
The router in return is connected to an ISDN modem link to NDC. See
Figure 11. Thus the DPRX Teleclaim System is currently capable of
handling X.25 and TCP/IP packets sent from NDC. |
|
|
|
Figure 11 (Front End Processor
running on TCP/IP network) |
| Joining
a Windows NT Server Domain or A Novell Netware Server |
| For a Front
End Processor running on Windows NT 4.0 workstation to join a
Windows NT Server domain, see the previous section on the
Adjudicator machine. The same process is used as the two machines
are running the same operating system.
For a Front End Processor running on Windows 98
operating system, follow this procedure:
It is assumed that a network card is already
installed on the system. For installation instructions of network
cards, read your network card manual or ask assistance from your
network administrator.
On the FEP machine (Windows 98), click on Start
> Settings > Control Panel. Click on the network icon. The
network dialog box open up ready for your next configuration. See
Figure 13. |
|
|
|
Figure 13. (Win 98 Network Dialog
Box) |
| In the box,
"The following Network Components are installed", be sure
that the "Client for Microsoft Networks" is installed. If
you are joining a Novell Netware Server, the "Client for
Netware Networks" should be installed. If it is not installed,
click on the "Add…" button. The "Select Network
Component Type" dialog box open up. See Figure 14. |
|
|
|
Figure 14 |
| Select the
"Client" entry and click the "Add…" button.
The "Select Network Client" dialog opens up. See Figure
15. |
|
|
|
Figure 15 (Select Network Client Dialog Box) |
| On the
"Manufacturers" list box, select Microsoft. On the
"Network Clients" list box (right side) select
"Clients for Microsoft Networks" if you are joining a
Windows NT Server or "Clients for Netware Networks" if you
are joining a Novell Netware Server. Click on "Ok" button.
You may be prompted to insert the Win98 installation CD. You will
need to reboot your machine for the changes to take effect. For
other functions such as optimizing/running your network card in 100
Mbps Full Duplex mode, the Network dialog box is use to do this.
Please note also that if you are joining a Novell
Netware Server, you must set the "Primary Network Logon"
drop down list box to "Clients for Netware Networks" in
Figure 13. |
| |
| Drive
Mappings and Folders on the FEP |
| During login
of the Front End Processor (FEP) machine to the server, the login
script intended for the FEP machine will be executed.
In any case, whether you are using a Windows NT
workstation or a Windows 98 to connect to a Windows NT Server or a
Novell Netware Server, the network drive mappings and environment
variables should be the same as shown below. The execution of the
script will mapped Network drives to this machine. The mapping of
network drives to this machine is a requirement for the FEP to work
properly. The drive mappings is shown in Figure 16. |
|
|
|
Figure 16 (Front End Processor
drive mappings) |
| |
| Front
End Processor Environment Variables |
| Aside the
network drive mappings, environment variables are also set for this
machine. The environment variables are required to make the
application work properly. See Figure 17 for the environment
variables. |
|
|
|
Figure 17 (Front End Processor
environment variables) |
The following
environment variables are set by the server during the execution of
the login script:
- PSTATIONID=PBM_FEP
- FEPPATH=g:\;g:\
- DURPATH=k:\
- LOGDATA=Q:\log.dbf
- PATH=C:\Windows;C:\Windows\Command;Z:\;y:\;
For the PATH environment variable, only the
"Z:\" and "y:\" are added by the script as the
other two entries are added by Windows itself.
The Front End Processor application, library and
other files are located on the local drive of this machine. See
Figure 18. |
|
|
|
Figure 18 (Front End Processor
Application, library, config files) |
| The FEP
application can be run by double clicking on the FEP application
named FEP.exe. The application is discuss in more detail in the User’s
Manual. |
| |
|