FingerPost - Pre-installation Check List

Pre-installation Check List for Fip

1.0 Overview

This document attempts to list some of the issues that occur before and during installation of a new Fip system.

If some of the information/data can be made available beforehand, the time to bring up a service can be much reduced.

2.0 Pre-installation

2.1 Which Fip modules ??

• Base
  • no of wires in?
  • no of printers?

• Mimic MailBox
  • no of connections?

• Syndication
  • no of simultaneous connections?

• Dial-Out
  • no of connections ?

• NewsAgency? Broadcast
  • no of wires in ?
  • no of wires out ?

• Telex/Fax
  • no of connections ?

• Dataformatting
  • no of inputs to be formatted ?
  • no of outputs ?

2.2 Server Hardware

• Unix - Operating System and Version number
  • Sun Solaris, SunOS4, AIX3, AIX4, DecOSF
  • Fip requires Shared Memory option (which it is by default)

• LINUX - OS release
  • Currently supporting Linux RedHat? enterprise

• NT - Version number Win2000, 4.0 or 3.5.1

• MacOSX

• RAM Fip is NOT a heavy memory user Add 16mb for a small system (up to 5 services) Add 32mb for a medium system (up to 25 services) Add 64mb for a large system (over 25 services)

• Disk Space
  • Good estimate is 100-200 mb
  • Fip programs/parameter files fit in 20mb
  • Data areas - allow 10mb more
  • Archive logs for text depends on the wire service - allow 10mb per service (2mb/day for 5 days), considerably more if processing pictures.
  • If using W4, allow 1GB for storing one months data, and again
  • more if using pictures.

• Preferably Internet access - ftp or http. Alternatively USB stick, (or as a last resort diskette) for software delivery.

• Backup - see later.

• Ethernet - for NT, Fip requires Ethernet/TCP-IP installed and running even for non-networked servers.

2.3 Communication Ports

• How many ports are required ?
  • Each wire in or out.
  • Each printer or output device.
  • Each modem for mailbox, dialout and/or syndication.

• The prefered option is to use external TerminalServers or Digi boards.

These buffer data (allowing for a smaller Host) and offer easier scalability.

• For small systems with few services at low speeds (<=2400 bps), the internal TTY or ComPorts? can be used.
• Where to locate the TerminalServers ? The TerminalServers are normally located next to the PTT line termination points and modems to keep the cable lengths as small as possible. Are enough Ethernet connections available next to the comms racks ?

2.4 For Each Wire Service

• Agency Name

• Name of service

• Is it a standard wire from that agency or is it customised for the client ?

• Is there any information on the data ? Speed ? No of Data Bits ? No of Stop Bits ? Parity ? v24/rs232 connection ? Do we need a convertor ? YES if one or more of the above attributes are not catered for by the normal settings of the Terminal Server/TTY port.

eg the Speed is lower than 300 bps or an unusual speed; connection is CurrentLoop not v24; 5 bit BAUDOT traffic.

• Is there any information on the Format ?
  • Agency (or client) Documentation that can be photocopied ?
  • Standard Formats
    • ANPA1312, IPTC7901, IATA, IIM, NITF

• • Non-standard but known
    • AFX v7, DJ via Wave4, CCM

• • Non-standard
    • Any information on the Start/End of Header/Text ?
    • header fields that are required ?

In all cases it helps if we can just check the feed beforehand. So can we have binary dump of a (large) sample of the RAW data via email or FTP ?

• Is there any information on the Character Set used ? We need this for mapping to that of each type of destination.

• Is the feed available now ?
  • Terminal Server port allocated ?
  • Modem<->Server Cable selected ?
    • (normally a crossed v24 cable as both modem and TermSvr? are comms devices)

• Modem selected ?
• Satellite link/leased Line/Phone line installed and working ?

• If no information is available, you will just have to use Fip diagnostics to try and find out during installation !

2.5 Other connections

• FTP and other TCP-IP connections
  • If to an external host, route through the Firewall agreed/tested ?

• Modems for Mailbox, Retreive, Syndication, Dialout.
  • Terminal Server? port allocated ?
  • Modem<->Server Cable selected ? (normally a crossed v24 cable as both modem and TermSvr? are comms devices)

• Modem selected ?
• Phone line installed and working ?

2.6 Data routing

• For each wire/data source, where are the individual files to be routed to ?
• All files to one destination or split between several ?
• What criteria is used to route ?
  • normally contents of certain Header Fields and/or text

• • Which files need to be sent to more than one destination ?
  • Are the destinations on more than one host ?

• For current installations, what are the actual in-use destinations ?
  • e.g. on the Editorial system, wire baskets/queues

• Source Redundancy : Running Redundant wires
  • Where multiple copies of a wire feed are received simultaneously
  • If so, remember to allocate extra port(s) on the Terminal Servers and to make/buy extra cables. This can be decided AFTER installation.

• Destination Redundancy :

• • Is there a backup route to a destination if the main, normal host dies ?
  • This can be decided AFTER installation.

2.7 Data conversion

• For current installations, what conversions are done now.
  • Check accents, pound signs, other special chrs.
  • Check end-of-line strings.

• Any information on styles used by the client ?
  • e.g. all paragraphs are CRCRLF and 5 spaces.

Most of the conversions will be done during the TUNING phase.

2.8 Backup Strategy

• What backup is required and how will it be done - tape, RCP etc.
• In most Fip systems, data is transient and any security copies are made on the source or destination machines - the Editorial system for example. So backups of the DATA is NOT required.
• Backups of binaries and parameter files can be on a regular basis or when changed.
• How to manage backups can be decided AFTER installation except where a tape/diskette drive needs to be purchased.

2.9 General Plant considerations

• access to comms lines, modems, computers.
• usual Power requirements; protected power is preferred.
• usual Ethernet connection(s).

3.0 Responsibilities - Who does what ?

Rough, suggested guidelines are :

• What is the client responsible for organising beforehand ?

Plant

• What are you responsible for organising beforehand ?
  • Software
  • Selection of

• What is the client responsible for during installation ?
• What are you responsible for during installation ?

4.0 On-site checklist

4.1 Power

4.2 Air conditioning if required

4.4 Hardware

Servers, terminal servers, modems, other adapters if required

4.5 Software

Fip, other

4.6 Network

drop leads, adapters, hubs, routers where necessary

4.7 Communications

• Telco lines installed
• Modems installed and connected
  • v24 cables.

4.8 Plan ...

• Plan which Port is to be used for which service
• Plan which data will be sent where
• Plan conversions of data
• Plan training

5.0 Actual installation - Suggested approach

5.1 Get one server working on the network first.

Load Fip Software. Load Fip customised tables where appropiate.

5.2 Get one TermSvr? working on the network.

Ping from Server ok ? if not get the client. Setup TermSvr? ports for Reverse Telnet or Slave - Speed,Bits,etc Allocate TCP-IP Port number to each port

5.3 Setup connection to destinations using test files.

This obviously depends on where/what the destination machine is!

5.4 connect one agency wire to TermSvr? port

• The wire should be reasonably busy where possible.
• Use TELNET directly to the port
  • No data - use a BreakOut? box to check the cable/data arriving (usually it is because pins 2 and 3 have been reversed !)
  • Garbled data - check the TermSvr? settings for Speed/Bits OR it might be Parity

• • Data OK - start relevant Fip program : *wire

5.5 Setup/check routing of incoming feed to the final destinations

5.6 Setup/check data conversion of incoming feed to the final destinations

5.7 Repeat points 5.4-5.6 for each wire

5.8 Tuning

• Often a good approximation of the data conversion can be attained quickly. But in some cases you may not have sufficent files to tune the feed completely - for Soccer Match results or a particular Cookery feature which arrives twice weekly for example. So at a suitable point, go on to the next wire to be setup, so you do not spend too much time on a small item.
• Use RESEND function to repeat files that have not been converted correctly.

5.9 Setup other data flows - from Editorial machine to DialOut? - etc

Notes and Comments