If you are doing large payload testing, set Show Payload on the Administration

Setting B2B Configuration Properties in Fusion Middleware Control B-3 b2b.FACorrelatedByInterchangeId To correlate inbound and outbound FAs correctly if the same control numbers are used between the same trading partners, set this property to true. By default Oracle B2B does not correlate inbound and outbound FAs correctly if the same control numbers are used between the same trading partners. Set this property to true so that Oracle B2B will correlate based on Control Number + Interchange Sender ID + Interchange Receiver ID for both Inbound and Outbound messages. b2b.FailedMessagesDirectory To change the location of the failed application message that is written to the file system, when b2b.jmsRedeliveryLimit is reached, set this property. The location can be changed from the default to another location by setting this property to another folder. b2b.HAInstance To enable File, FTP, or Email transports in an HA environment, set this property to true. The default value is false. b2b.hl7.ignoreValidation To turn off the hl7 envelope validation, you can set comma separated enveloper header with this property. For example: b2b.hl7.ignoreValidation = MessageReceivingFacility, MessageSendingApp or set it to ALL to turn off the complete envelope header validation. b2b.inboundThreadCount b2b.inboundThreadSleepTime b2b.outboundThreadCount b2b.outboundThreadSleepTime b2b.defaultThreadCount b2b.defaultThreadSleepTime To set the number of threads and thread sleep time to improve message processing, set these properties. The recommended values for b2b.inboundThreadCount and b2b.outboundThreadCount depend on your system. For a 2 GB computer, a setting of 3 to 5 is recommended. If Oracle B2B is running in a single thread mode default, then a blocked outbound HTTP message could cause failure in Oracle B2B to process the subsequent message. The HTTP delivery has a default timeout of 60 seconds, and the timeout would push the message to error and unblock the processing. To avoid delays in processing, it is recommended that you increase the thread count property b2b.outboundThreadCount to 3 or 4 threads. The b2b.inboundThreadSleepTime and b2b.inboundThreadSleepTime properties put a thread to sleep after message processing. A setting between 10 and 1000 milliseconds is recommended. b2b.jmsRedeliveryLimit You can change the retry limit for reading messages from the JMS queue by setting this property, causing Oracle B2B to retry reading the message for the number of times specified there. The default retry limit is 5. When the limit count expires, the message and the header contents are written into the file system the default location is the tmp folder. Oracle B2B also sends an exception message to the JMS - B2B_IN_QUEUE, reporting the error and providing the location of the saved message. You can specify the location for failed messages by setting b2b.FailedMessagesDirectory. b2b.listening.channel.restart.wait Sometimes Oracle B2B creates multiple file monitor threads for a listening channel. Setting a longer interval using this property helps to avoid the race condition of threads during initialization. Table B–1 Cont. Oracle B2B Properties in Oracle Enterprise Manager Fusion Middleware Control Property Description