| Author |
Message
|
| TBS |
 Posted: Tue Jun 23, 2009 1:14 am Post subject: WMQFTE and Pause the transmition |
 |
|
Centurion
Joined: 29 Jan 2007
Posts: 143
Location: Hillerød / Denmark
|
Hi !
Is it passible to pause the transmission end then start it again ? |
|
| Back to top |
|
 |
| PeteVerdon |
| Posted: Tue Jun 23, 2009 3:00 am Post subject: |
|
|
Apprentice
Joined: 11 Feb 2009
Posts: 33
Location: Hursley, UK
|
Hi,
There is no specific pause functionality - once a transfer starts it will run to completion as long as both agents are available. If you really need to temporarily halt traffic you could possibly experiment with stopping one or both of the agents, since when they are restarted the transfer will continue from where it stopped. To stop an agent in the middle of a transfer you will need to use the -i ("immediate") option on fteStopAgent. |
|
| Back to top |
|
|
| TBS |
| Posted: Tue Jun 23, 2009 3:56 am Post subject: |
|
|
Centurion
Joined: 29 Jan 2007
Posts: 143
Location: Hillerød / Denmark
|
Hi !
Yep I did that .. Thanks  |
|
| Back to top |
|
|
| kodiakk |
| Posted: Mon Jul 27, 2009 10:38 am Post subject: |
|
|
Acolyte
Joined: 04 Dec 2007
Posts: 58
Location: Jacksonville, Fl.
|
Hi there,
I've discovered that in this scenario, FTE doesn't always pick up where it left off. In one of the tests I ran, it successfully picked up where it left off only 2 out of 3 times. I repeated the process, with similar results, but a different file was "orphaned" this time. At the end of the testing, I had about 6 .part files out there that were never picked up.
The next time the files were sent, the .part files that were left were simply ignored, and a .part1 was created until the file was fully finished.
Ultimately, the files all got to their destinations as intended, but I had .part files left over.
Any thoughts?
_________________
"Don't take life too seriously... you won't get out of it alive..." |
|
| Back to top |
|
|
| TBS |
| Posted: Mon Jul 27, 2009 10:48 pm Post subject: |
|
|
Centurion
Joined: 29 Jan 2007
Posts: 143
Location: Hillerød / Denmark
|
| The funktionality of pause the transmision soud be a part of the produkt with a botton |
|
| Back to top |
|
|
| PeteVerdon |
| Posted: Wed Aug 05, 2009 9:08 am Post subject: |
|
|
Apprentice
Joined: 11 Feb 2009
Posts: 33
Location: Hursley, UK
|
| kodiakk wrote: |
Ultimately, the files all got to their destinations as intended, but I had .part files left over.
|
I haven't seen this behaviour before, although I wasn't personally involved in the restart / recovery development or testing. The best way to get to the bottom of this is probably a formal problem report, as debugging it is likely to need trace files and so on.
| TBS wrote: |
The funktionality of pause the transmision soud be a part of the produkt with a botton
|
Like any other software project, we have far more ideas and feature requests than we could possibly implement, so things have to be prioritised. We can prioritise better if we understand how and why people want to use a feature. Under what circumstances do you need to pause a transfer?
Pete |
|
| Back to top |
|
|
| TBS |
| Posted: Fri Aug 07, 2009 2:44 am Post subject: |
|
|
Centurion
Joined: 29 Jan 2007
Posts: 143
Location: Hillerød / Denmark
|
| Under the test of WMQFTE we did have some problem with a disk that was close to running full and we liked to pause the file-transfer while we did some disk clean up. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Aug 07, 2009 4:21 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
| TBS wrote: |
| Under the test of WMQFTE we did have some problem with a disk that was close to running full and we liked to pause the file-transfer while we did some disk clean up. |
As I was reading this thread I was thinking what possible reason could there be to pause a file push. But this is a very good reason. I haven't used MQFTE yet, just read the Red book and paper, but I would hope this feature fins its way into the product.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| PeteVerdon |
| Posted: Fri Aug 07, 2009 6:23 am Post subject: |
|
|
Apprentice
Joined: 11 Feb 2009
Posts: 33
Location: Hursley, UK
|
I can see the convenience of an easy button to do this kind of thing, but I don't think the current solution of stopping the agent while you tidy up around it is a terrible one.
Better visibility and control of the FTE infrastructure from the GUI (which might include stopping and restarting of agents) is certainly on our long-range radar. Personally, I'd love to be able to configure and administer and generally fly around the FTE network graphically as I can for MQ using MQ Explorer. However, this is not something that will be added overnight. |
|
| Back to top |
|
|
| kodiakk |
| Posted: Fri Aug 07, 2009 7:00 am Post subject: |
|
|
Acolyte
Joined: 04 Dec 2007
Posts: 58
Location: Jacksonville, Fl.
|
One simple update to the FTE GUI that would go a LONG way in my book, is to add date/time stamps in the TRANSFER LOG (as opposed to the progress log). I have a couple of templates that run overnight, when the applications using the files are stopped, so I get a lot of "failed" messages during that time, as well as a lot of "success" messages, because no files were found to transfer. Being able to see WHEN each of those occurred would help a lot.
P.S. I know that you can look into the "properties" of each and the date and time are there in the XML properties, but that's usually more time-consuming than it's worth. Also, the properties show the transfers at GMT, instead of my timezone, which is EST.
_________________
"Don't take life too seriously... you won't get out of it alive..." |
|
| Back to top |
|
|
| PeteVerdon |
| Posted: Fri Aug 07, 2009 7:59 am Post subject: |
|
|
Apprentice
Joined: 11 Feb 2009
Posts: 33
Location: Hursley, UK
|
Kodiakk - I'll mention that to my GUI developer colleague, but as always no promises that it'll make it into any particular release.
I do wonder whether there's something you could do to avoid getting the failure messages at all. The slightly-misnamed "trigger" functionality that was in v7.0.0 (and is now largely replaced by Monitors) is really a conditional check that happens before a transfer is initiated. Could you add a trigger so that if the relevant files aren't there the transfer isn't attempted?
Pete |
|
| Back to top |
|
|
| kodiakk |
| Posted: Fri Aug 07, 2009 8:05 am Post subject: |
|
|
Acolyte
Joined: 04 Dec 2007
Posts: 58
Location: Jacksonville, Fl.
|
Pete,
I probably could get away with using triggering instead of just sending on an hourly basis, since the template depends on the file "consumption" at the destination... for our test environment, however, we thought hourly might give us a good idea of just the functionality.
I can still see the use of putting date/time in the transfer even with triggering enabled, though. 
_________________
"Don't take life too seriously... you won't get out of it alive..." |
|
| Back to top |
|
|
| dnwe |
| Posted: Sun Aug 09, 2009 11:48 pm Post subject: |
|
|
Newbie
Joined: 09 Aug 2009
Posts: 1
|
| @kodiakk GUI developer colleague here. Are you asking for a date and time stamp for when each transfer log entry was updated (as opposed to when the transfer started)? If so, follow the 'configure columns' information in the infocenter here and enable the 'state recorded' column (it is disabled by default) |
|
| Back to top |
|
|
| PeteVerdon |
| Posted: Mon Aug 10, 2009 1:15 am Post subject: |
|
|
Apprentice
Joined: 11 Feb 2009
Posts: 33
Location: Hursley, UK
|
| kodiakk wrote: |
| I probably could get away with using triggering instead of just sending on an hourly basis |
Just to be clear, it's not an either/or choice, since the "triggering" support in version 7.0.0 isn't quite what the name suggests. It doesn't observe the directory and kick off a transfer as soon as something happens; rather it is a check that takes place early in the process of starting a transfer, and aborts it (with or without a log message saying so) if the trigger condition isn't satisfied. In your situation you'd keep the hourly schedule, but add the trigger so that the transfer doesn't take place if the file isn't present.
(The functionality of watching a directory and acting as soon as something changes is included in version 7.0.1 under the name "directory monitoring".)
Pete |
|
| Back to top |
|
|
| kodiakk |
| Posted: Wed Aug 12, 2009 8:07 am Post subject: |
|
|
Acolyte
Joined: 04 Dec 2007
Posts: 58
Location: Jacksonville, Fl.
|
Hi dnwe,
I'm actually starting to see a few different things in my environments as far as the date/time stamp display is concerned.
Just a couple of days ago, I set up a template to run at 10 minutes to the hour, every hour. No trigger settings were used, nor any monitoring settings. This template DOES display the date/time stamp of when the transfer was STARTED. (Successful delivery or failed delivery time would also be helpful, I'm thinking.)
In one of my first templates, I set up a scheduled AND triggered delivery, and there is NO display of date/time stamp anywhere in the GUI transfer log, just in the "log status" window at the bottom.
I'll check out your link in the info center, and see about getting that set up.
Thanks!
_________________
"Don't take life too seriously... you won't get out of it alive..." |
|
| Back to top |
|
|
|
|
