TWiki> FipDoc Web>NewTrainingCourse>CopyFlow (17 Mar 2005, DotFingerPost? )EditAttach

Incoming Copy Flow

Stage

Program

Queue Used

Remarks

Syntax Used - with examples

Incoming Feed: In general a feed is received from a device such as a terminal server or from an virtual port delivered by a router.

 


wire
vwire
zwire
pwire
iimwire
smtpwire

incoming feed placed in ~/spool/2brouted
WIRE - standard ANPA / IPTC
VWIRE - variable format (user specifiable)
ZWIRE - IATA format
PWIRE - precedent character (CCM style)
BKWIRE - record based broker feed
IIMWIRE - ANPA/ IPTC IIM model
SMTPWIRE - smtp model

An entry in the ~tables/sys/SYSTEM parameter file for AP

name group wire -s spider1 -p110 -a -n AP

Check WEB page for swiches: options include running duplicate services, specifying non-default routing and archiving or seperate output formats
Routing (Where should it go) iproute and sent to /fip/spool/2go Parameter file in /fip/tables/route/NAME. From this file you match conditions in the source file to generate :
*DU* - destination user
*SC* - Source character set
*SZ* - defining which of a pair of redundant systems is primary for this service. NB every destination in the route file MUST have a corresponding entry in the ~tables/sys/USERS file

 ~tables/route/AP 
 
%SZ:primary,secondary
%SC:ANPA
%DU:spike
      1 c=X > queue2 + spike
      1 c=B >racing
      1 p=w > logdel ; (archive don't send on)
      1 p=e > delete ;(delete, don't archive, do mark in item log)
DISTRIBUTION (find its destination) ipwheel files read from _~spool/2go_ parameter file in ~tables/sys/USERS: 
DP: physical destination
DQ: destination queue
DC: destination character set
Can also change SC (source character set), and DF (output Format), over-ride any earlier settings and add further flags as necessary to determine the behaviour of the file for later programs.

in ~sys/USERS

DU         DP               DQ               DC        others
spike      DP:atex1         DQ:spike-wir     DC:atex
racing     DP:sun1          DQ:2edsys        DC:html   DF:newsys    SC:race   
queue2     DP:nt1           DQ:2edsys        DC:sgml   DF:news 
web        DP:apache_server DQ:2w4           DC:html
local_dir  DP:localhost     DQ:2edsys        DC:sun
CONTENT FORMATTING ipxchg files read from ~spool/xchg SC &DC are compared; if they are the same no xchg is used; if they differ ipxchg uses a parameter file ~/tables/xchg/SC2DC to xchg strings and characters. If there is a CX set in the header, an exchange of that name will be used instead. This will also call in a character set file from ~tables/chrset for single character substitution.

eg : for DU queue 2 above, SC is ANPA, DC is HTMl so the xchg parameter file is ~tables/xchg/ANPA2HTML; the character set used is ~tables/chrset/AP

~tables/xchg/ANPA2HTML 
; use AP character set
c:AP
; change carriage returns to para
x:\r\n:<P>\n
; change abc to def
x:abc:def

OUTPUT FILE STRUCTURE And Delivery
ipedsys
ipw4
ipftp
ip2db
ipsmtp
ipout 		  files are sent to editorial systems via programs such as:

ipedsys - a generic parameter driven file formatter that will top, tail and name the file

ipw4 - generates the FingerPost web based wire browser feeds

ip2db - feeds an Oracle, Sybase, MySql or MSQL database.

ip2ftp - ftp file somewhere

ipsmtp - email file

ipout and ipgtw - the J11 - adds full atex header ad formats the file. Feed an Atex J11 based system via SCP, Excelan, mpb gateway connection.*

 
OUTPUT DELIVERY (where necessary)
ipprint
ipftp
sffport
ipbdcast
ipsmtp 		  Where delivery is not part of the above programs (ie ipedsys has been used to describe the output file, but it still needs to be delivered to a further output system). In general all these programs can both format and deliver ... and it is rare for the two tasks to be separated.

ipprint can be used to deliver to a serial device, or terminal server

ipftp can be used to ftp to a remote system. ipbdcast to Broadcast files. ipsmtp can be used to email ...

 

 
Edit | Attach | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r2 - 17 Mar 2005 - 15:45:09 - DotFingerPost?
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback