I have a customer who employ a number of reps / engineers / collectors all of whom need processing capability.

A number of their operational areas are rural where sheep outnumber people 10:1, ergo no signal for direct links.

I am looking at using remote laptops with a sub set of the main Ffenics application and "pushing" data out to them from the centre, doing the local processing then "pushing" back completed data back, importing and processing.

Has anybody got practical experience of really good push / pull infrastructure and methodology.

Paul,

Interesting problem.

The main problem I see is identifying each person's data. A business rule ought to be that once data has been sent out it may not be changed in the home system. So, each person has to have his/her identifiable set of data.

Once it is sent back, it would need to be imported into a holder file and then processed via DQL to add or update records. After which a new file is sent out to them.

The timing of all this is critical of of course and proper unique fields are also critical.

Does this help?

Hi Phil

Thank you for the pointers. I have just about got a grip of those essentials. In this case the engineering call, collection data will be very specific to the engineer / collector so will not change in the cente betewwn transmission and data returning.

What I am most concerned about is the methodology of data transmission. I don't want to use email with attachments so I am guessing that FTP or perhaps some 3rd party service will do. I just wonder if anybody has specific experience and is able to recommend or perhaps warn against particular approaches.

Paul

I'd consult a web expert, but I don't see why FTP wouldn't work.

I have one client where I have set up a nightly job that runs and creates and export file. A scheduled task on the server uploads that file to a remote FTP address at around 3am.

The one drawback to this approach is that it uses the FTP facility in Windows and is run from a batch file; so both the address and the password are visible to anyone who can look at the batch file. The only security, and the reason for running it from the server, is that the batch file resides on the C: partition which is not accessible to anyone logged onto the server.

And what part of the World is this where FTP is possible, but not piping?

John
ShopEase

What the heck is piping?

“Piping” is generic term to express the most efficient route / method of connecting PCs via a WAN / Internet etc.

For example, AT&T have recently completed a 100-Gigabit pipe between New Orleans and Miami replacing the 2008 40-Gigabit version which is already showing oversubscribing as more and more people use the Internet for visual media.

I just found it strange that Paul’s users are (seemingly) able to transfer files (import / export), but not access the application / server directly. This is, after all 2010. There are some marvellous bits of software (Citrix, Blue Coat, Silver Peak) that can enhance even a mediocre pipe these days – so file transfer seems a tad old fashioned?

John
ShopEase

Ah...good points. Yes, I agree.

One client has a plant down near Brighton and another in Stone. Each Stone user has his/her own RDP pc in Brighton over a T1 or DSL connection and it works fine.

I don't know how many engineers are out in the field, but having a rack mounted pc for each would not seem to be cost prohibitive nowadays.

My problem is for those areas where there is no broadband / mobile signal / wifi at all and on site processing is essential.

For these we have to transfer data down in advance of the visit and receive completed data back.

Where we have site that are "on line" the processing is done in real time using RDP to a Terminal Services server.

Paul

And does the guy 'stay' in the area with the dead zone or is he just visiting? My first thought was he needed processing capability until he returned to a wired zone where he would upload his data.

It sounds like you're doing the right things already.

Phil

We are actually doing what you suggest with engineers. Thay can make their notes etc when back in signal area and do it using RDP direct to the server.

The on site stuff is for collectors who are emptying amusement machines, counting the money and allocating to different parties and leaving a printed receipt on site. It has to be processed there and then so no choice but to transfer data around the place.

Paul

I’m even more confused.

Areas “where sheep outnumber people” wouldn’t seem to be first choice sites, commercially, for slot machines???

And why all the overhead of RDP?????

Must be missing some insider knowledge.

John
ShopEase

why do i get a mental image of a vending machine designed for sheep ?

Perhaps you can win the sheepstakes ...

(Running very, very fast..)