<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Packet size determination in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/packet-size-determination/m-p/2253533#M487578</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can change the packet size at SAP, and there is no harm in it.&lt;/P&gt;&lt;P&gt;Only the problem is it will send more no. of packets than before, but it should not be an issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And reducing the packet size is totally depend on your system load and you have to take the decision between performance in the SAP system and TIBCO stack.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can try by just reducing it to 30 or may be 40.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Atish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 May 2007 03:45:12 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-05-18T03:45:12Z</dc:date>
    <item>
      <title>Packet size determination</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/packet-size-determination/m-p/2253532#M487577</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt; The flow of material data is &lt;/P&gt;&lt;P&gt;SAP - &amp;gt; TIBCO -&amp;gt; non-R/3 system&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The packet size for port defined to send to TIBCO is 50 for ITEM_JA( outbound mode is collect idocs) and for english language is ITEM_EN is 1( Outbound mode is tranfer immediately).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP publisher stack size at TIBCO is 3000000 bytes.&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;b&amp;gt;&lt;/P&gt;&lt;P&gt;Issue:&amp;lt;/b&amp;gt;&amp;lt;/u&amp;gt; During mass publishing of materials 500/ hour, the issue is coming while sending japaneese idocs for which segments are more for 50 idocs and TIBCO stack size is not able to accomodate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it fine to reduce the pocket size at SAP side? If so howmuch do we need to reduce and what basis it is determined.&lt;/P&gt;&lt;P&gt;Is it fine to change the properties of ITEM_JA same as ITEM_EN?&lt;/P&gt;&lt;P&gt;Will there be any performance issues?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Sree&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 May 2007 19:06:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/packet-size-determination/m-p/2253532#M487577</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-17T19:06:15Z</dc:date>
    </item>
    <item>
      <title>Re: Packet size determination</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/packet-size-determination/m-p/2253533#M487578</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can change the packet size at SAP, and there is no harm in it.&lt;/P&gt;&lt;P&gt;Only the problem is it will send more no. of packets than before, but it should not be an issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And reducing the packet size is totally depend on your system load and you have to take the decision between performance in the SAP system and TIBCO stack.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can try by just reducing it to 30 or may be 40.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Atish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2007 03:45:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/packet-size-determination/m-p/2253533#M487578</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-18T03:45:12Z</dc:date>
    </item>
    <item>
      <title>Re: Packet size determination</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/packet-size-determination/m-p/2253534#M487579</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  &amp;lt;b&amp;gt;As per packet size is consider, it not restricted , you can change the packet size. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I can just you two ways, to overcome the performance issues, if there are any.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.  You are updation is mass updation. If you are using mass updation, try to maitain the properties of both ITEM_JA and ITEM_EN as same, then there won't be any performance issuse. &lt;/P&gt;&lt;P&gt;Note : If they are both are interrelated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.If not , both there properties should be same as present, try to update with Indivival update. Cent % it won't give ant trouble either for any idocs.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Manju&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2007 06:55:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/packet-size-determination/m-p/2253534#M487579</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-18T06:55:44Z</dc:date>
    </item>
  </channel>
</rss>

