| Author |
Message
|
| prasunad |
 Posted: Wed Jul 30, 2014 11:14 pm Post subject: |
 |
|
Novice
Joined: 10 Jul 2014
Posts: 22
|
Considering, if the target has a restriction of not receiving a file greater than certain xMB, but the source is sending x+10MB.
Any suggestion how the same can be handled. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Jul 31, 2014 4:36 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| prasunad wrote: |
Considering, if the target has a restriction of not receiving a file greater than certain xMB, but the source is sending x+10MB.
Any suggestion how the same can be handled. |
There is absolutely no way that we can answer that question.
It all depends on the file content and how you would be able to break it up, if at all?
Have fun 
_________________
MQ & Broker admin
Last edited by fjb_saper on Thu Jul 31, 2014 4:59 am; edited 1 time in total |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 31, 2014 4:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| prasunad wrote: |
| Any suggestion how the same can be handled. |
Slap someone. The requirement is nonsense. It's ridiculous to say that a file can never be greater than size x; suppose the file is the number of customer orders placed in a given day? Are you going to tell your sales & marketing people, "don't be too successful because you'll make the file too big".
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jul 31, 2014 5:01 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Vitor wrote: |
| prasunad wrote: |
| Any suggestion how the same can be handled. |
Slap someone. The requirement is nonsense. It's ridiculous to say that a file can never be greater than size x; suppose the file is the number of customer orders placed in a given day? Are you going to tell your sales & marketing people, "don't be too successful because you'll make the file too big". |
This is one scenario where you could break up the file. What about a jpeg file or a video file etc...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 31, 2014 5:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
| Vitor wrote: |
| prasunad wrote: |
| Any suggestion how the same can be handled. |
Slap someone. The requirement is nonsense. It's ridiculous to say that a file can never be greater than size x; suppose the file is the number of customer orders placed in a given day? Are you going to tell your sales & marketing people, "don't be too successful because you'll make the file too big". |
This is one scenario where you could break up the file. What about a jpeg file or a video file etc... |
My point was that if the "requirement" is that the file should never be larger than xMb, then the "requirement" has already failed to account for the structure of the file and is therefore nonsense.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| prasunad |
| Posted: Thu Jul 31, 2014 7:43 am Post subject: |
|
|
Novice
Joined: 10 Jul 2014
Posts: 22
|
I do agree on the file size restriction, but that is the principal requirement...
 |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 31, 2014 8:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| prasunad wrote: |
| that is the principal requirement... |
Who is putting this requirement in place? What's driving it? "Limit the file size" doesn't just come out of nowhere. What's the business requirement for keeping file sizes down?
For example, if the reason is that the target system (for whatever reason) reads the entire file into memory and then breaks it into transactions you can meet the "requirement" by coding to produce multiple output files for the target system each containing only one trasnacation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jul 31, 2014 8:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| What are you supposed to do with the file if it's too big? |
|
| Back to top |
|
|
| prasunad |
| Posted: Thu Jul 31, 2014 11:13 pm Post subject: |
|
|
Novice
Joined: 10 Jul 2014
Posts: 22
|
| The business requirement being, the target system cannot accept data greater than 1MB, and if ESB is getting data greater than 1 MB, ESB has to slice it. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Jul 31, 2014 11:31 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
does the requirement detail now the data should be 'sliced'?
IMHO, if it does not then the requirement is deficient.
How are you sending the data to the receiving application?
If it is MQ then you could use message grouping BUT only if the recipient understands it.
In this day and age(2014) for an application to have this sort of limitation would make me steer well clear if it in future.
Do you want to tell us who develops it unless of course, it is an internally developed application?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| prasunad |
| Posted: Fri Aug 01, 2014 12:02 am Post subject: |
|
|
Novice
Joined: 10 Jul 2014
Posts: 22
|
data is sent to target system using webservices.
your correct, the requirement does not say how the data needs to be sliced. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Aug 01, 2014 12:41 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| prasunad wrote: |
data is sent to target system using webservices.
your correct, the requirement does not say how the data needs to be sliced. |
Then you have to go back to whoever wrote the requirement and get them to fix it.
If you decide to slice it one way and the receiving application expects it another way then your flow will fail. Until you know how the receiver is expecting the data then you can't do much.
IMHO, it is a really weird webservice that has this sort of limitation.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
