15 Configuring B2B System Parameters

Configuration settings that were formerly accessible in oracle.tip properties files are now accessible in the Oracle B2B interface on the Configuration tab. Settings on the Configuration tab override property settings in b2b-config.xml. See Appendix B, "Properties of b2b-config.xml."

This chapter contains the following topics:

Setting Configuration Parameters

15.1 Setting Configuration Parameters

Figure 15-1 shows the configuration settings available in the Oracle B2B interface.

Figure 15-1 Configuration Parameters in the Oracle B2B Interface

Description of "Figure 15-1 Configuration Parameters in the Oracle B2B Interface"

Table 15-1 describes the configuration parameters.

Table 15-1 Configuration Settings

Field	Description
Acknowledgment Settings	-
Functional Ack Handled by B2B	If set to true, then B2B autogenerates the functional acknowledgment (FA) message for inbound EDI and HL7 messages. Inbound FA messages are consumed when this option is true. When this option is set to false, B2B does not autogenerate the FA document. The back-end application (middleware) must generate the FA and provide it to B2B as an outbound message. When option is set to false, inbound FA documents are passed back to the back-end application. If the document does not require an FA (as indicated by the agreement-level setting), then this option is ignored. The default value for this property is true. See "Setting b2b.FAHandleByB2B for EDI EDIFACT and EDI X12" for more information. When Functional Ack Handled by B2B is set to false, then Notify Inbound Functional Acks must be set to false also for the inbound FA to be sent to the back-end application. If Notify Inbound Functional Acks is set to true (while Functional Ack Handled by B2B is set to false), then the incoming 997 (FA doc) generates only a notification and the 997 document itself is not sent back to the back-end application.
Functional Ack Internal Properties	Generates the internal properties structure in the functional acknowledgment XML for EDI transactions. A document type 997 (for X12) or CONTRL (for EDIFACT) must exist. The default value is false, which means that the functional acknowledgment uses the original message-internal properties. If true, then the FA message autogenerated by B2B contains interchange/group envelope information from the original message.
Notify Inbound Receipt Acks	If set to true, B2B sends an acknowledgment notification to the application when an exchange acknowledgment is received.
Notify Inbound Functional Acks	If set to true, B2B sends an acknowledgment notification to the application when a functional acknowledgment is received. When Functional Ack Handled by B2B is set to false, then Notify Inbound Functional Acks must be set to false also for the inbound FA to be sent to the back-end application. If Notify Inbound Functional Acks is set to true (while Functional Ack Handled by B2B is set to false), then the incoming 997 (FA doc) generates only a notification and the 997 document itself is not sent back to the back-end application.
Generic Settings	-
Use JMS Queue	Set this option to true to use the default JMS queues (B2B_IN_QUEUE and B2B_OUT_QUEUE) as the default internal delivery channel.
Use B2B Queue	Set this option to true to use the default AQ queues (IP_IN_QUEUE and IP_OUT_QUEUE) as the default internal delivery channel.
Callout Directory	Specify a directory for the callout JAR file location if you do not use the default callout. The callout directory path cannot end with `/` or `\`.
Miscellaneous Settings	-
Default Trading Partner	Defaults to this trading partner if trading partner agreement identification fails. Used for HL7 documents.
Ignore Validation on Envelope Elements	When this property is set to true, the validation of look-up parameters is turned off Use this option to provide a list of envelope elements, separated by commas, to be ignored during look-up validation. The possible values are InterchangeSenderID, InterchangeReceiverID, GroupReceiverID, GroupSenderID, TransactionAssociationAssignedCode, InterchangeReceiverQual, InterchangeSenderQual, and InterchangeControlVersion.
Ignore Correlation	When an acknowledgment is received from a trading partner, it is correlated to the actual business message of the sender. If the correlation fails, an exception is generated and the acknowledgment processing stops. To ignore the correlation and process the acknowledgment, set this property to true.
Additional MIME Types	Use to specify attachments (additional MIME types) in addition to the default MIME types supported by B2B for ebxml exchanges. By default, B2B supports `application/xml : application/octet-stream : application/EDIFACT : application/EDI-X12 : application/jpg : image/jpeg : application/gzip : application/x-gzip: application/pkcs7-signature`.
Log Payload	If true, B2B logs the payload in a diagnostic log (also depends on log level setting). Error messages are logged by default. Payload logging is useful for diagnostic purposes, but may be undesirable for security reasons. The default value is false.
Reconnect on Error	If set to true, the AQ adapter retries the enqueue operation when the initial enqueue fails. This parameter is not available in this release.
HTTP Header Delimiter	A delimiter to separate the HTTP headers provided in the Additional Transport Headers field for HTTP delivery channel configuration.
Treat Reply to Message as Request	Used in ebMS to indicate that the conversation message is to be considered as a request message.
Miscellaneous (continued)	-
Generic Message Type	If this property is enabled (set to true), B2B finds the agreement for the specific message type first, and then the generic message type. The default value is false.
Outbound Dispatcher Count	The number of dispatchers used for handling the outbound messages. Used in message sequencing for MLLP. The default value is 0.
Inbound Dispatcher Count	The number of dispatchers used for handling the inbound messages. Used in message sequencing for MLLP. The default value is 0.
Auto Stack Handler	Used in stacking for MLLP. If true, the stack handler processes stacked messages in automatic mode. The default value is false.
Auto Stack Handler Interval	Used in stacking for MLLP. Enter comma-separated values for the time interval in seconds for the stack handler to process the stacked messages. The default value is 1.
Performance Settings	-
Large Payload Size	Specify a large payload size, in bytes. The default value is 2,000,000 (2MG).
Large Payload Directory	The default directory is `/tmp`. For Windows-based systems, change the directory to an appropriate directory, such as `C:\temp`.
UI Settings	-
Show Payload	Enables the payload to be displayed in reports accessible from the Reports tab. If set to true, the database is automatically searched with the default search parameters and the results are displayed.
Enable Auto Search	Enables automatic searching in reports accessible from the Reports tab. The default value is true. If set to false, a blank result table is displayed on the report pages until the Search button is clicked.
Payload Display Size	The default value is 1,048,576 KB. This parameter (in bytes) is used to display the payload only if its size is less than the value configured in the interface.

To set configuration parameters:

Click the Administration link.
Click the Configuration tab.
Provide values for the configuration parameters, as described in Table 15-1.
Click Save.