Assign the variable to b2b.largePayload in the Invoke activity.
B-2 Oracle Fusion Middleware Users Guide for Oracle B2B
b2b.checkDuplicate To check for duplicate messages, set this property to true.
If this property is set to false, a check for a duplicate of the incoming business message is not performed.
By default, Oracle B2B checks for duplicate messages based on the business message ID of the incoming message.
b2b.deploy.validation To turn off validation during deployment, set this property to false.
This is useful when deploying a large number of agreements where you are certain that the data is valid.
b2b.docPluginList Using this property, document plugins are loaded as per the order
specified in this property. For example, b2b.docPluginList=Custom,EDI_X12,EDI_EDIFACT,HL7,RosettaNet
ensures that document plugins are loaded as per the specified order. If no value is provided for this property, then all document plugins from
the system protocol.xml are loaded. b2b.edi.enablePreprocess
Set this property to true to pre-process data to remove the trailing CRLF new line characters andor unwanted CRLF that maybe present in file.
The default value is false. Changes to this property require a server restart for the new value to take
effect. b2b.edi.identifyToTP
To identify the toTP from the TP information present in the incoming message, use this property.
This property is used for inbound message processing. If it is set to true, the toTP is identified from the TP information present in the incoming
message. The default value is false. b2b.edi.ignoreValidation
To turn off the EDI envelope validation and ignore interchange validation errors for EDI messages, you can set comma separated
enveloper header with this property. For example:
b2b.edi.ignoreValidation=InterchangeSenderID, InterchangeReceiverID
or use the value ALL to turn off the complete envelope header validation.
Note: If you add or update this flag, a server restart is not needed.
However, if you remove the flag, the server must be restarted for the change to take effect.
b2b.encoding This property can be used to specify encoding other than default UTF-8.
b2b.errorsCumulativeReported To indicate whether reported errors are cumulative or not, set this
property to true or false. Set this property to true the default to report errors in a cumulative
fashion. If set to false, the error text and error description fields are not
concatenated with the description starting on a new line. This property is most useful with EDI batching error messages.
b2b.fa.inbound.validation b2b.fa.outbound.validation
Use these properties to control inbound and outbound FA validation. To turn off the outbound FA validation, set the
b2b.fa.outbound.validation property to false. The default value is true.
To turn off the inbound FA validation, set the b2b.fa.inbound.validation property to false. The default value
is true.
Table B–1 Cont. Oracle B2B Properties in Oracle Enterprise Manager Fusion Middleware Control
Property Description
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