17 Configuring B2B System Parameters

This chapter describes how to access configuration settings that are available in the Oracle B2B interface on the Configuration tab.

Settings on the Configuration tab override property settings configured in the Oracle Enterprise Manager Fusion Middleware Control Console. See Appendix C, "Setting B2B Configuration Properties in Fusion Middleware Control" for information about properties set in Oracle Enterprise Manager Fusion Middleware Control Console.

This chapter contains the following topics:

Section 17.1, "Setting Configuration Parameters"

17.1 Setting Configuration Parameters

Table 17-1 shows the configuration settings available in the Oracle B2B interface.

Figure 17-1 Configuration Parameters in the Oracle B2B Interface

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

Table 17-1 describes the configuration parameters.

Table 17-1 Configuration Settings

Field	Description
Acknowledgment	-
Functional Ack Handled by B2B	To specify how a functional acknowledgment is handled, set this property to true or false. 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. If the FA is marked as expected in an agreement, then 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. See Section C.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. 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 this property is set to `true`).
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. To swap the interchange and group IDs in the generated FA from the sender to the receiver and vice versa, set this property to `true`. The test usage indicator parameter is also mapped; that is, an inbound message set as a test message generates an FA with the flag set to test message. Setting this property to `true`, by default, does not map ISA segment elements (1-4).
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 `text/plain : image/jpeg: text/xml : application/xml : application/octet-stream : application/EDIFACT : application/EDI-X12 : application/jpg : 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.
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.
Exception Queue	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 (`B2B_IN_QUEUE`) if Use JMS Queue as default is set to true or to the AQ queue (`IP_IN_QUEUE`) if Use JMS Queue as default is set to false. AQ queues are not supported for use as custom exception queues.
Enable BAM	Enables B2B to send runtime information to Oracle BAM. See Chapter 24, "Monitoring Instance Message Data With Oracle BAM" for more information.
BAM Polling Interval	Polling interval in minutes for Oracle BAM. See Chapter 24, "Monitoring Instance Message Data With Oracle BAM" for more information.
Non Purgeable	The nonpurgeable parameters retain their values even after a metadata repository purge is invoked.
Use JMS Queue as default	If this option is set to true, then B2B starts to poll on the JMS queue, `B2B_OUT_QUEUE` for outbound messages, and delivers all inbound messages to `B2B_IN_QUEUE`. Polling on `IP_OUT_QUEUE` is stopped. If this option is set to false (the default), then B2B starts to poll on the AQ queue, `IP_OUT_QUEUE` for outbound messages, and delivers all inbound messages to `IP_IN_QUEUE`. Polling on `B2B_OUT_QUEUE` is stopped. When a non-Oracle database is used and therefore no AQ queues are available, the JMS queues are used no matter how this option is set. 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 `/` or `\`. The default file location, `/MyCalloutDir`, is retained after purging the metadata repository.
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.
Webservice Policy	Specify a security policy to secure the Web service. Enter only a security policy URI or complete `<policy>` tag. For example: oracle/wss_username_token_service_policy See Section 21.5, "Securing Oracle B2B Web Services" for more information about the use of this field.
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 `/tmp`. For Windows-based systems, change the directory to an appropriate directory, such as `C:\temp`.
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 17-1.
Click Save.