B Properties of b2b-config.xml

Most B2B properties are set on the Configuration tab of the Oracle B2B interface. Configuration tab settings override properties set in b2b-config.xml. See Chapter 15, "Configuring B2B System Parameters."

This appendix contains the following topics:

Note:

Changes to b2b-config.xml require a server restart.

B.1 Turning off Validation During Deployment

You can turn off validation during deployment by setting the property b2b.deploy.validation=false in b2b-config.xml. This is useful when deploying a large number of agreements where you are certain that the data is valid. Restarting the SOA Server is required.

B.2 MDS Cache Size

See "MDS Cache Size" for how to set the Metadata Service (MDS) instance cache size in b2b-config.xml.

B.3 Number of Threads

See "Number of Threads" for how to set the number of threads in b2b-config.xml.

B.4 Setting Up File, FTP, or Email in an HA Environment

To set up File, FTP, or Email transports in an HA environment, specify a unique name for each instance in b2b.HAInstance. If you use #ServerName# for the value, B2B retrieves the WebLogic Server name as the HAInstanceName.

B.5 Setting Internal Properties for a Functional Acknowledgment

To ensure that the ISA segment elements (1 - 4) of a 997 message generated by B2B are identical to the received 850, or any other transaction message, set the property FAInternalProperties to true.

B.6 Setting b2b.FAHandleByB2B for EDI EDIFACT and EDI X12

When the b2b.FAHandleByB2B property in b2b-config.xml is set to false, then for an inbound EDI message, B2B does not generate a functional acknowledgment (FA).

If the FA is marked as expected in an agreement, the message is placed into the MSG_WAIT_FA state and the back-end application is expected to generate the FA and push it to B2B as an outbound message back to the partner.

The following limitations apply when generating the FA from the back-end application:

  • The FA is correlated with the original message based on the ReferToMsgID value set in the enqueue properties. The FA is correlated based on control numbers also.

  • If the FA indicates that there was an error in the received message, the status of the correlated message is not updated to indicate an error. The correlated message is updated to MSG_COMPLETE.

These limitations are not present when the FA is generated by B2B (that is, when FAHandledByB2B is true).

B.7 Setting the b2b.outboundOneErrorAllError Parameter

When using the b2b.outboundOneErrorAllError parameter, inbound messages behave as if b2b.outboundOneErrorAllError is set to false; that is, if an error occurs during an inbound message process, then only that message is flagged with the error and other messages are passed. There is no option to flag every message as failed. For outbound messages, b2b.outboundOneErrorAllError can be set to true or false. The default is false. If the parameter is set to true, then for outbound messages, all outbound batch messages with errors are flagged.

To set the OneErrorAllError parameter:

Use either of the following methods:

  • In b2b-config.xml, add the following property:

    <property>
  <name>b2b.outboundOneErrorAllError</name>
  <value>true</value>
  <comment>error all outbound batch messages on one error</comment>
</property>

  • In Oracle Enterprise Manager Fusion Middleware Control, add the property to the b2b MBean by using the System MBean Browser. See Section 24.2, "Configuring B2B Operations" in Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite for how to access the System MBean Browser.