15 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 Setting B2B Configuration Properties in Fusion Middleware Control).

This chapter includes the following section:

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 follows
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

-

Notify Inbound Receipt Acks

If set to true, B2B sends an acknowledgment notification to the application when an exchange acknowledgment is received.

Miscellaneous

-

Default Trading Partner

Defaults to this trading partner if trading partner agreement identification fails.

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.

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. For more information, see Monitoring Instance Message Data With Oracle BAM.

BAM Polling Interval

Polling interval in minutes for Oracle BAM. For more information, see Monitoring Instance Message Data With Oracle BAM.

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 Securing Oracle B2B Web Services for more information about the use of this field.

SSL Private Key Password

When configuring in B2B SSL(with client authentication required) or signing, if private key password (keypassword) is different from keystore password, when doing handshake (SSL) or trying to encrypt message this error occurs: "Could not establish SSL due to java.security.UnrecoverableKeyException: Cannot recover key. So, B2B is not able to access its private key from a keystore if keypass is not the same as keystore password.

Therefore, if the private key password is different from the keystore password, the private key password can be configured using Administration->Configuration-> "SSL Private Key Password

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.

Session Timeout

Enables you to set when the session will timeout due to inactivity. It is measured in seconds. The default is 300 seconds. Any changes will take effect after you log out and log back in.

To set configuration parameters:

  1. Click the Administration link.

  2. Click the Configuration tab.

  3. Provide values for the configuration parameters, as described in Table 15-1.

  4. Click Save.