The following lists the main applications used at SFL. Most of these applications have various uses and are in operation across most of our servers.

(1)

SFL SOFTWARE GUIDE

Introduction

The following lists the main applications used at SFL. • SFL Program Manager

• Simulator Gateway XCEED Version (used to be known as the channel processor) • Simulator Gateway MS Version(used to be known as the channel processor) • SFL File Status Spy

• System Console Server (or Spy Server)

• Electronic Reports

Most of these applications have various uses and are in operation across most of our servers.

The rest of this document will explain how they work in further detail along with general troubleshooting.

(2)

SFL PROGRAM MANAGER

What is it?

The program manager was developed to start, monitor or stop a list of processes. To start all the monitored processes;

• This is achieved by simply double click on the blue diamond. If it is used on a server, you will find it in the middle of the desktop

Each process can be monitored for;

• Not Responding Processes

If a monitored process is shown as “not responding”, they are killed and a new process is started. • Running Program status file.

The Simulator gateway software produces a status file every time it runs through a scan stage. This status file can be monitored for common problems. Again, the process will be killed and restarted if a fault is found with the status file.

NOTE: A process can be started by the manager but configured so it is not monitored. E.g. SFL Backup process for off-sites. These processes lock up while transferring. A process which is not monitored will not be restarted when closed or is “not responding”.

To stop all processes

• To stop one. Goto the processes screen and click on the process to stop it.

• To stop ALL. Simply exit the program manager and it will prompt you to end each process individually or an “A” to end all



When the program manager is in use, it SHOULD be used to start and stop all SFL processes!!!!!! This is done from the process screen (see later).

(3)

Main Screens

The Process Log Screen

A colour codes log of what has occurred since it was started.

In this screen shot you can see that the manager has; • Run a number of commands to start various processes (see later) • That someone has manually killed the SFLBackup offsite process • Confirmation that the process has been killed and then

(4)

The Processes Screen

A list of processes which show if the process is monitored and if so, how many times it has been restarted.

It is from this screen that a process can be clicked upon for the following manual actions;

Only use this screen to;

• Start: Start the process

• End: End the process

(5)

• Start Monitoring: Restart monitoring The Configuration Screen

This screen is really for quick access to only some of the configuration. The main config is in the actual INI file. To see the INI file click on “View Config”.

(6)

The SFL_PGMmanager.ini File

The INI file contains the main configuration for the program manager. I.e. general program operation and the list of processes to Start and/or monitor.



Please only amend the INI file if you know what you are doing!

[CONFIGURATION] <<< This is the general program config

MONITOR_PROCESSES=1 TIMER_INTERVAL=10000 SYSSPY_ENABLED=0

SYSSPY_IP=10.240.150.36 SYSSPY_IPPORT=31777

DESCRIPTION=SFL File Manager Process Invoke and Update

[PROCESS**] <<< This is a commented out process

DESCRIPTION=SFLBackup AS400 Process INVOKE_PROCESS=1

MONITOR_PROCESS=1 FIND_TASKID=0

EXECUTE_SHELL_CMD="C:\Program Files\Safe Financials Limited\SFL LiveFileProcesses\Crest_Simulator_GWX.exe" 60 Y

WARNING_COUNT_B4ACTION=10 RESTART_COUNT_B4ACTION=20

[PROCESS] <<< This is a process

DESCRIPTION=LLPBackup AS400 Process INVOKE_PROCESS=1

EXECUTE_SHELL_CMD="C:\Program Files\Safe Financials Limited\SFL

LiveFileProcesses\Crest_Simulator_GWX.exe" 61 Y <<< The actual program to run

[PROCESS] <<< Another process

DESCRIPTION=Live CREST Intermediate Gateway INVOKE_PROCESS=1

[PROCESS] <<< and another one

DESCRIPTION=iSeries File Tasks INVOKE_PROCESS=1

(7)

Known Problems

Task already running

If you get a message box stating that a process is already started, it means you have either;

• You have started the program manager more than once. Stop all occurrences of the program manager and restart again

• One of the processes is still running in the background. Go to task manager (right click on the start bar) and look in the processes for the rogue process. Kill it and start again.

(8)

SIMULATOR GATEWAY

What is it?

The software’s main aim is to transfer file from a local directory across to a remote and from the remote to the local pc.

However, over the years it has been developed to handle different variations of file transfer and management. The following are the main uses;

(Note : There are two types of this application, EXCEED and MICROSOFT. The XCEED version was meant to supercede the MS one. But, it does not send large files across the internet and it is also incompatible with some SOCKS5 gateways1_.)

The software is used for the following processes across multiple servers;

•

Simulator Gateway Process

Used at both the client site and also at SFL to manage the transfer of files through FTP. It works in two main ways.

o To Remote (inbound processing). Files on the local drive are sent to the remote site using FTP.

o From Remote (Outbound processing). Files on the remote FTP server are transferred to the local machine.

All file transfers are controlled by Operators. Each operator has a set of directories configured for the transfer process.

•

AS400 Backup Gateway Process

Used to transfer Save files2_{from the AS400s across to a local server using the} “from remote” configuration of the program. This process uses the XCEED version.

It works in the same way as the simulator gateway. I.e. files are received from the AS400 and placed onto a PC. The next process, the SFL Offsite process then runs to transmit the files on the PC to the remote PC for the purpose of offsite backup.

•

SFL Off site Process

(Microsoft version)

Used to transfer Save files and other large files across to an Internet site. This process has to use the MICROSOFT version as the Xceed version has problems with large files across the net.

The main problem with the MS version is that when transferring large files, it tends to lock up. This is NOT a problem, it’s just the way it works. See SFLGateway process descriptions later in this document.

• Data File Emailing

1_{Socks 5 gateways are used by DB and some other users. They provide a secure internet channel to the internet. They}

work a little bit like a firewall router.

(9)

Used to transfer files from the LLP as400 and setup the necessary data for processing by the electronic reports software. This is mainly used by the LLP for the emailing of BACS data.

As with all of these software variations, it simply receives files from an AS400, then emails them to the address stored in one of the files.

(10)

Main Screens

The minimized Screen

When the program starts, this is the minimized display.

It shows;

File stats: This shows “0 files in the last 30m” in the example above. This can be clicked to show other stats

Process Status: This shows the current status

Progress Bar: This shows whether or not the program is scanning

Error Light: This should be GREEN, other wise there is an

Error

(RED)or a Warning (ORANGE) .

Size Light: This is red if there is a large file going through. Don’t worry about this. It is only an indicator!!! I.e. no action required.

Transit Light: This is a count of file going through the system which need a response. It is red if there are files which have not been responded to. See the files in transit screen for those files.

Start Button: When started this is green and the text “stop”. When stopped, the button is red with the text “start”. Parameters on the command to run this determines whether or not it is running when invoked.

Max/Min Button: The maximize button

The Process Log Screen