Hi there, 

What should be done in case if the message is really big. 

For example if it is 512 MB in size. 

Can I avoid sending it to the message box, how do we deal with that scen

All depends on what you want to achieve with large message size . If it is data update to any SQL or Oracle then I would suggest to use SSIS or Informatica  .

Now if these 500 MB requires any business process   and these message data can be broken down to smaller chunks .

In that case i would break the message into smaller parts and then publish it to message box.

Thanks

Abhishek

Can I avoid sending it to the message box, how do we deal with that scenario ?--> I would avoid passing that big message into BizTalk server. Why do you need it?

It depends what you want? What is your Integration requirement here? Please tell us more details.

Hi

What type of  message you are trying receive.

EDI or FlatFile or XML File.

Is there any business process needs to executed on this file?

you need to identify whether it is detachable or not? If debataching is possible then debatch the message before it reaches to message box and Process each de batched message individually.

If message is not able to Debatch--Dont publish the complete message into message Box,Create Metadata of the message and Route Meta data and finally send Actual file.

Please click on Proposed as answer if it answered your question

Thanks,

Ammu4Biz.

• Proposed as answer by Ammu4biz 12 hours 38 minutes ago
• Unproposed as answer by Ammu4biz 12 hours 38 minutes ago

Hi,

You can use a custom pipeline component and give the size property of message in the property bag read it at runtime, compare it in the execute stage if it exceeds the mentioned size then in the execute stage itself you can write few lines of code to by-pass message box.

Regards,

Sharad

Hi

What type of  message you are trying receive.

EDI or FlatFile or XML File.

Is there any business process needs to executed on this file?

you need to identify whether it is detachable or not? If debataching is possible then debatch the message before it reaches to message box and Process each de batched message individually.

If message is not able to Debatch--Dont publish the complete message into message Box,Create Metadata of the message and Route Meta data and finally send Actual file.

Please click on Proposed as answer if it answered your question

Thanks,

Ammu4Biz.

• Proposed as answer by Ammu4biz Tuesday, June 23, 2015 6:25 PM
• Unproposed as answer by Ammu4biz Tuesday, June 23, 2015 6:25 PM

Hi

What type of  message you are trying receive.

EDI or FlatFile or XML File.

Is there any business process needs to executed on this file?

you need to identify whether it is detachable or not? If debataching is possible then debatch the message before it reaches to message box and Process each de batched message individually.

If message is not able to Debatch--Dont publish the complete message into message Box,Create Metadata of the message and Route Meta data and finally send Actual file.

Please click on Proposed as answer if it answered your question

Thanks,

Ammu4Biz.

• Proposed as answer by Ammu4biz Tuesday, June 23, 2015 6:25 PM
• Unproposed as answer by Ammu4biz Tuesday, June 23, 2015 6:25 PM

Consider, size is relative and 512MB may or may not be considered large depending on the circumstances.

First, do you have a specific reason to worry about this? Meaning is there an actual problem you are facing with a 512MB message?

If not, then don't worry about it, including the MessageBox.

Before anyone can give advice, you have to explain a little about the file. Is it Xml, EDI, flat file?  Is it one transaction or many transactions?