15 Configuring B2B System Parameters
Configuration settings are accessible in the Oracle B2B interface on the Configuration tab. Settings on the Configuration tab override property settings using the Oracle Enterprise Manager Fusion Middleware Control Console. See Appendix B, "Setting B2B Configuration Properties in Fusion Middleware Control."
This chapter contains the following topics:
15.1 Setting Configuration Parameters
Table 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 |
- |
|
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 Section B.1, "Properties To Set in Fusion Middleware Control," 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. |
|
Miscellaneous |
- |
|
Default Trading Partner |
Defaults to this trading partner if trading partner agreement identification fails. Used for HL7 documents. |
|
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 |
|
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. |
|
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. |
|
Miscellaneous (continued) |
- |
|
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. |
|
Partial Batch Commit Size |
Used while debatching an EDI message that has large transaction sets. Instead of using a single commit, which is prone to errors in case of failure, this feature enables specifying a partial batch commit size. For example, if Partial Batch Commit Size=10, then, for an envelope with more than 10 transactions, B2B calls a separate commit for every 10 transaction sets. |
|
Select a JMS internal delivery channel for the host trading partner to use as the exception queue. A null default value for this parameter means that exceptions are sent to the JMS queue ( AQ queues are not supported for use as custom exception queues. |
|
|
Non Purgeable |
The nonpurgeable parameters—Use JMS Queue as default and Callout Directory—retain their values even after a metadata repository purge is invoked. |
|
If this option is set to true, then B2B starts to poll on the JMS queue, If this option is set to false (the default), then B2B starts to poll on the AQ queue, If you select a queue from Exception Queue, then exception messages are sent to that configured queue. The default queues continue to be valid for other messages, depending on the setting for Use JMS Queue as default. If the value of Use JMS Queue as default is set to true before purging the metadata repository, then after a purge, the value continues to be true and does not revert back to the default value, false. |
|
|
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 The default file location, |
|
SMTP Host |
Specify the host name of the SMTP server in the enterprise to send the negative MDN to the trading partner for an AS1 exchange. |
|
Performance |
- |
|
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 |
|
UI |
- |
|
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.