Salescard Interface Retriggering and problems observed on Event server

[snehareddy]

Hello,
On Mercator we have one interface called as Salescard interface which is time triggered.
The Mercator Version we are using: 6.7(306_1EM) on HP-UX platform.
For this Salescard interface,file will come on every Monday and we have observed that file has come but still it lead to many source not available errors on all the event servers which lead to many problems on the event servers.
The interface has lead to retriggering after the time of its receival.
The time at which the file is recieved ,at the same time the event servers have been restarted.

Please let us know the possible causes and remedy for the above problem.

Thanks in Advance!!

 

[janhes]

It's probably triggering before the whole file has arived if it is large. Best to have an empty dummy file sent after the data file has arived and trigger on the dummy file. Alternativelt have the data file sent as a .tmp file and rename it after the transfer is complete.

 

[snehareddy]

Hello,

Here in this interface the file size is normal only as we receive every week.Also map delay is also zero only.
All the properties are normal only.
Every time it got retriggered it got updated in the launcher process of the event server.
We were not able to find out what may be the exact reason.

Please let us know the possible causes and remedy for the above problem.

Thanks in Advance!!

 

[OllyC]

What do you mean by "file size is normal"?

As soon as Mercator sees the file it will try to run the transformation map. If the file is still being written to, you will get errors.

Either follow Janhes' suggestion and implement a map delay or change the delivery process of the file to do a rename or a move after the file has been written.

 

[thisismondweep]

Hi,

I have seen similar problems earlier. This happens ,when as OllyC, has rightly pointed out, the map getting triggered before the entire file is copied to the disk.

To avoid this use it as follows:-
Assume the event server system triggers when the file comes to location A

1) Let the file come to location TEMP from the external system.

2) mv file from TEMP to A

the move (mv) operation just changes the internal pointer from location TEMP to A; the file having already been copied to the disk.

Now the system should process as usual.

Do let us know if this helps.

Cheers!

 

[dstxaix]

This will work as thisismondweep menioned only if TEMP and Location are on the same filesystem. A move across filesystems is a copy and will not provide any benefit.