Used to add the incoming ebMS message details of ACTION, SERVICE, SERVICE TYPE, CPAID, FROMROLE, and TOROLE to the ACTION_NAME header in AQ.

By default only the ACTION is passed as part of ACTION_NAME.

To specify an attachments directory location, set this property.

If enabled, this property allows users to specify a directory into which all of the attachments will be written.

Changes to this property require a server restart for the new value to take effect.

This property is used to enable or disable the validation of the certificate received on ebMS. For example, an expired certificate normally throws an error; however, if the property is set to false, it allows the certificate without throwing validation errors. The default value is true, indicating that by default, Oracle B2B validates the certificate.

To check for duplicate messages, set this property to true, which is the default.

If this property is set to false, a check for a duplicate of the incoming business message is not performed.

By default, Oracle B2B checks for duplicate messages based on the business message ID of the incoming message.

This property needs to be set to false to enable processing of duplicate RosettaNet messages.

All document protocols can use this feature. Note that this checking is based on business message ID only. An example on how to reproduce this is using the file name format in this PDF document, on page 6:

http://www.oracle.com/technetwork/middleware/b2b-integrations/learnmore/tnb2b11g002-326857.pdf

Inbound to Oracle B2B (Request): sending a message

Format:

%TO_PARTY%_

%DOCTYPE_NAME%_

%DOCTYPE_REVISION%_

%MSG_TYPE%_

%MSG_ID%

Filename example: SalesInc_850_4010_1_1234.dat

The business message ID is 1234. The first file consumed is fine. If the second file with the same name is used, B2B will mark the message state with MSG_ERROR if b2b.checkDuplicate is set to true; this is for inbound messages only. The property checking is not applicable to inbound wire message resubmitted from the UI or the command line utility.

When this property is set to true, duplicate messages with same message ID are not allowed in a batch. If such messages are sent, Oracle B2B changes the message ID of messages and sets the messages to ERROR state.

Also, in the Reports page, the following error is reported:

“Duplicate message with same message id found in a batch. Changing original message id <org_msg_id> to new message id <org_msg_id+timestamp) and rejecting the message."

The default value of this property is false.

Set this property to determine whether JMS objects or SOA datasource information is cached.

The value of the property is either true or false. By default, the value is true. If the property is set to true, then Oracle B2B looks up for the JMS objects or SOA datasource in the cache. If there is a cache hit, the cached value is returned, otherwise the lookup value is returned. This property may be used for incremental performance improvement.

The value is LogDir=<directory>, where the directory is a location to write the value of the b2b.batchMonitorStragglerBatchName and b2b.batchMonitorStragglerTimeLag in the files. The BatchStragglerKeySet_<unique_guid>.dat file contains the value of the b2b.batchMonitorStragglerBatchName and b2b.batchMonitorStragglerTimeLag. The BatchStragglerKeySet_<unique_guid>.dat file contains the key name of the b2b.batchMonitorStragglerBatchName during the batch processing time.

These files are created only if you specify a value for this property. To disable logging, remove this property.

To turn off validation during deployment, set this property to false.

This is useful when deploying a large number of agreements where you are certain that the data is valid.

When this property is set to true, then Protocol Message ID and Protocol Collaboration ID values are prefixed with the Host Trading Partner name. By default, this property is set to false.

For example:

When b2b.ebMS.ProtMsgId.prependHost is false, the values will be:

• Protocol Message Id: @0A261B4D13F33830161000006AB9B3F8

• Protocol Collaboration Id: @0A261B4D13F33830161000006AB9B3F8

When b2b.ebMS.ProtMsgId.prependHost is true, the values will be:

• Protocol Message Id: INDIGO@0A261B4D13F33830161000006AB9B3F8

• Protocol Collaboration Id: INDIGO@0A261B4D13F33830161000006AB9B3F8

wherein INDIGO is the Host Trading Partner name.

Set this property to 0 to specify that the MDS cache would be stored in memory forever. By default, the value for this property is 5, which means that the cache would be removed from memory after 5 minutes, if the objects are not used. You can set the value of the property to be 0 or any other non-zero value.

This property can be used to specify encoding other than default UTF-8.

To indicate whether reported errors are cumulative or not, set this property to true or false.

Set this property to true (the default) to report errors in a cumulative fashion.

If set to false, the error text and error description fields are not concatenated with the description starting on a new line.

This property is most useful with EDI batching error messages.

Set this property to true to enable the transport cache to cache the transport message objects between the transport layer and the engine.

To change the location of the failed application message that is written to the file system, when b2b.jmsRedeliveryLimit is reached, set this property. The location can be changed from the default to another location by setting this property to another folder.

Set this property to true to ensure only one node in a High Availability (HA) cluster starts a polling thread for the configured File, FTP, or Email channels. Without this property being set, each node starts its own polling thread and could pick the same file multiple times.

The default value of this property is false.

A restart of all the nodes in the cluster is required to ensure each node works in the expected HA Mode.

In cases of TCP-based exchange protocols, such as MLLP and Generic TCP, where the host name is masked, to enable Oracle B2B to determine the host name of each message, set this boolean property to true.

If set to true, then Oracle B2B retrieves the host name from the IP address of the host.

If set to false, then Oracle B2B does not lookup the host name from the IP address.

The default value for this property is true.

In cases where the B2B UI is configured with a generic identifier as a client IP address in the partner profile and the partner has provided a range of IP addresses in the form of a mask (for example, 120.12.23.*) from which they can send a document, then B2B cannot recognize the sender and fails with an Agreement Not Found Error. Set this boolean property to true to enable B2B to find the agreement.

The default value for this property is false.

This property specifies how many times retry of a failed message to fabric is attempted. For fabric, retry count is a global property and for non-fabric it is a channel retry count.

This property specifies the number of seconds between attempts to retry delivery of a message to fabric.

To enable a channel name or a trading partner name as a sequence target, set this property to true.

If a message has a sequence target as a part of the action name, then priority is be given to that message property. However, if there is no message level sequence target, and the property (b2b.TPBasedSeqTarget) is enabled, then the trading partner name is considered as the sequence target.

To enable sequencing in case of:

• TCP: If sequencing is enabled (in trading partner facing channel) and TARGET is not specified, use the trading partner name as the TARGET to query the cache. This happens at the entry point in 10.

• Non-TCP protocols: Because in non-TCP protocols, the channel is not bidirectional, use the TO-PARTY name as TARGET.

• Nonfabric: Use the sequencing flag in the channel of outbound listening internal channel.

For an encrypted RosettaNet message being exchanged, set this property to true for viewing Packed Message contents.

b2b.threads.LogStatusInterval

b2b.threads.LogStatusLevel

Use this feature to log the number of active inbound and outbound threads from the available pool of threads during a periodic interval. Oracle B2B publishes event thread information such as name, last active status at periodic intervals to DMS metrics and diagnostic logs. By default, thread information are published at a 30 minute interval and the log level is DEBUG.

Users can change the interval and log level using these properties.

Possible values for b2b.threads.LogStatusLevel are DEBUG, INFORMATION, WARNING, and ERROR.

For the feature to work:

• When b2b.threads.LogStatusLevel = DEBUG, the server log level needs to be set to TRACE.

  When b2b.threads.LogStatusLevel = INFORMATION, then the server log level needs to be set to NOTIFICATION.

Sample Output:

<Mar 3, 2011 11:37:01 PM PST> <Error> <oracle.soa.b2b.engine> <BEA-000000>

<B2B Thread Name :

weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@f6e5fd8 - Direction :

Default - Status : ACTIVE>

Set this property to false to stop adding unwanted or unset parameters in the import zip.

Set this property to false to make the value of Receive Time Stamp blank and Send Time Stamp to be automatically filled.

The default value is true.

Set this property to true indicate if there must be a retry by refreshing the cache in case of a failure (only for EBMS.) The property is required only in a cluster environment when the cache synchronization is not set up.

The default value is false.

Set this property to true to indicate whether the database transaction message should be (intermediate) committed while delivering the message to the back end. If this parameter is not set, the message is still delivered to the back end, but the database records are not committed.

b2b.inboundThreadCount

b2b.outboundThreadCount

b2b.defaultThreadCount

b2b.inboundSleepTime

b2b.outboundSleepTime

b2b.defaultSleepTime

Set these properties to set the number of threads and thread sleep time to improve message processing.

The recommended values for b2b.inboundThreadCount and b2b.outboundThreadCount depend on your system. For a 2 GB computer, a setting of 3 to 5 is recommended.

If Oracle B2B is running in a single thread mode (default), then a blocked outbound HTTP message could cause failure in Oracle B2B to process the subsequent message. The HTTP delivery has a default timeout of 60 seconds, and the timeout would push the message to error and unblock the processing. To avoid delays in processing, it is recommended that you increase the thread count property b2b.outboundThreadCount to 3 or 4 threads.

If b2b.inboundThreadCount and b2b.outboundThreadCount are set, then b2b.defaultThreadCount sets the number of threads to process events other than inbound messages or outbound messages. For example, events such as auto retry, manual resubmit, trading partner agreement deployment, batch messages together, and send batch out events are processed by b2b.defaultThreadCount threads. If b2b.inboundThreadCount and b2b.outboundThreadCount are not set, then b2b.defaultThreadCount threads will process all the events including inbound messages or outbound messages.

The b2b.inboundSleepTime, b2b.outboundSleepTime, and b2b.defaultSleepTime properties put a thread to sleep after message processing. A setting between 10 and 1000 (milliseconds) is recommended.

You can change the retry limit for reading messages from the JMS queue by setting this property, causing Oracle B2B to retry reading the message for the number of times specified there. The default retry limit is 5.

When the limit count expires, the message and the header contents are written into the file system (the default location is the /tmp folder). Oracle B2B also sends an exception message to the JMS - B2B_IN_QUEUE, reporting the error and providing the location of the saved message.

You can specify the location for failed messages by setting b2b.FailedMessagesDirectory.

Sometimes Oracle B2B creates multiple file monitor threads for a listening channel. Setting a longer interval using this property helps to avoid the race condition of threads during initialization.

Set this property to avoid an issue in which the autostack handler does not resume processing of messages after restart.

The time unit value of b2b.MaxTimeinAquiredState property is in minutes and 30 is the default value.

b2b.mdsCache cache_size

To set the Metadata Service (MDS) instance cache size, set this property.

A ratio of 5:1 is recommended for the xmx-to-mdsCache values. For example, if the xmx size is 1024, maintain mdsCache at 200 MB.

To control the delay between every cycle of dispatch, use this property. Set this property to specify the amount of time to wait (in milliseconds) between dispatching of sequenced messages.

If enabled, the property will control the delay between every cycle of dispatch. The property can be used along with Message Sequencing and Trading Partner Downtime Schedule features.

When auto stack handler is used, then Oracle B2B retries the outbound failed messages in sequence. after the endpoint is reached for delivery, all messages in the sequence will be eligible for delivery and this may cause an overload of message delivery at the endpoint. To reduce the load, this property can be used to set the interval between dispatch of messages in milliseconds.

To turn on payload obfuscation, set this property to true.

For more information, see Payload Obfuscation.

To use EDI ecs and xsd files from Oracle B2B 10g, set this property to true.

When using EDI ecs and xsd files in Oracle B2B 11g that were used in Oracle B2B 10g, the XEngine may generate dynamic namespace for the translated xml. For example,

To turn off dynamic namespace generation for inbound EDI messages, set this property to false.

When using callouts, to enable delivery of messages to the back-end message queue, set this property to true. To disable the message delivery, set this property to false. By default, this property is disabled (set to false). This property is case-sensitive.

Oracle B2B sets the LARGE_PAYLOAD header property to true only if the payload is large (as per configured size). In case the payload is small, the LARGE_PAYLOAD header property is not set. If you want to set the LARGE_PAYLOAD property for small payloads also, set the b2b.setisLargePayloadPropertyForSmallMsg property to true.

By default, the value of the property is false.

By default, if the resource server, such as SFTP or JMS is down, Oracle B2B tries to reconnect only a specified number of times. However, if Oracle B2B cannot reconnect within the specified retries, it simply stops the particular listening channel.

When this property is set to true, Oracle B2B makes continuous attempts to reconnect to resource server in downtime.

In case of SFTP, the resource server is an SFTP server, and in case of JMS, the resource server is an JMS server.

By default, the value of the property is false.

Set the value of this property to true to reuse HTTP connections. By default, the value of this property is false. When the default value is used, HTTP connections are opened and closed repeatedly when accessing the same URL consecutively.

However, this property depends on other property values to take effect. If you call HTTPClient.HTTPConnection.setCurrentProxy when reusing an HTTP connection, side effect changes (such as reusing HTTP connections, closing the socket) are invoked only if the proxy settings have actually changed for the obtained HTTP connection instance. If invoking setCurrentProxy applies values currently set in the HTTP connection instance, the setCurrentProxy call is ignored.

So you need to compare HTTPClient.HTTPConnection.getProxyHost and HTTPConnection.getProxyPort values against proposed new values, and call HTTPConnection.setCurrentProxy only if the values are different.

In ebMS, you can check the server state by using a set of messages called 'Ping and Pong'. Set the b2b.deliverPingPongToBackend property to true for enabling Oracle B2B to pass these messages to the back end applications on receipt of such messages.

By default, the value of the property is false, which forces Oracle B2B to consume these Ping and Pong messages on receipt.

In the case of an inbound MLLP HA, if the server crashes after wire message has been committed to the database but before the event gets enqueued to Event Queue, it is perpetually stuck in the Sequence Manager table and is not processed. This blocks the inbound message flow in the sequencing case.

Set the b2b.SingleTransactionAtInbound to true only in the case of MLLP HA to enable the JMS and database commit to take place in a single transaction. It is suitable only for the MLLP case where only one inbound message is received at a time.

The default value of the property is false.

When this value is set to true, @msgid is retained for the specific message ID, protocol message ID and collaboration ID during an Application Message resubmit.

If this value is set to false, @msgid is retained for the message ID, but a new ID is generated for the protocol message ID and the collaboration ID.

The default value for this property is false.

Use this property to enable or disable Trading Partner Agreement (TPA) layer processing cache. By default, this property is not enabled.

Limitation of the property: The TPA cache relies on agreement deployments to refresh the change in values. So, when this parameter is enabled, hot uptake of channel parameter changes does not work. It would require the agreements to be deployed. You need to restart the server for applying any changes to this parameter.

The valid value for this parameter is local.

Use this property to determine whether the storage of payloads would be optimized (shared) across Business, Wire, and Application instances, if applicable. Setting this property accordingly reduces the I/O load at the database layer due to persistence of payloads. You need to restart the server for applying any changes to this parameter.

The valid values for the parameter are true and false (default).

Use this property to enable or disable the Dispatcher processing cache. By default, this property is not enabled. You need to restart the server for applying any changes to this parameter.

The valid value for this parameter is local.

Use this property to spawn a separate thread for dispatching messages to the back-end application. Enable this property to improve the performance of the inbound dispatcher. You need to restart the server for applying any changes to this parameter.

The valid values for this property are true or false.

Use this property to define the batch size for sequencing fetches. The Inbound or outbound Dispatcher attempt to pick <batchsize> number of messages for a given sequence target in a single fetch. The default value for this property is 20. You need to restart the server for applying any changes to this property.

The valid value for this parameter is Integer.

If the HTTP From message header contains a value that can be mapped to an IP Address, then Oracle B2B converts the value to an IP Address. If the remote Trading Partner identifiers, specifically, Generic Identifier, does not contain that IP Address, then Oracle B2B fails to identify that the message came from which Trading Partner.

Use this property to specify a value for the header name so that when a message arrives, Oracle B2B does an exact match (no IP Address conversion) of the value extracted from the From message header with the Generic Identifier specified for the remote Trading Partner.

The value of this property is case-sensitive. So, the header must match exactly with the value that is provided in the message.

The value for this property takes the following format:

The value can contain multiple header names separated by #, such as sender_id#receiver_id.

Use b2b.auditFileLocation to retrieve the EM URL for Composite Flow Trace . The property takes a string value.

Example:

Use b2b.maxNumAuditFile to specify the maximum number of audit logs. The default value for this property is 10.

Format: audit-<managed server name>.log.<n>o where n=0,1,2,3

Example:

The audit file is stored in the CSV format.

Use this property to identify a RosettaNet document. If you set this property to true and the document is received through RNExchangePlugin, then the document is identified successfully.

If you set this property to false, then the document is identified based on the XPath expression and its value (just like a custom document.)

If an inbound AS2 message has requested the sign MDN, the outbound MDN needs to be signed. However, B2B does not have information about the private key that is needed to sign the MDN nor does it have the algorithm used. This is solved by using this property to handle signing of negative MDN for AS2 messages. The property takes its value in the following format:

Example:

This property only affects the AS2 Exchange protocol. The managed server does not need to be re-started for the property to take effect.

Use this property to include XPath from where the Trading Partner name has to be extracted from the payload.

When a message comes, Oracle B2B uses the XPath specified in the Enterprise Management console to extract the Trading Partner name from the payload, and then Oracle B2B compares that value to the value specified as a Generic Identifier to determine which Trading Partner has sent the message.

Note: Do not include /text() at the end of the XPath, otherwise Oracle B2B will not find the path.

Use this property to toggle correlation in Oracle B2B.

The default value for this property is true.

If you set this property to false, Oracle B2B does not to correlate the outbound enqueued message with an existing message having the ID that is specified in the replyToMsgID field.

Set this property to true enable Oracle B2B to send the protocol MsgID to the back end application.

The default value for this property is false.

b2b.sqldumpTimeRange

Set this property to get the time range for SQL dumps. This property is used during the Diagnostic Framework implementation. The time is specified in minutes.

When Oracle B2B is hosted in one domain and the Oracle SOA composite (Oracle B2B adapter with the JMS option) is deployed in a different domain (Oracle Enterprise Manager Fusion Middleware Control in a different domain), Oracle B2B needs a mechanism to provide the link to the domain where the composite is deployed.

Use this property to provide the domain URL details of the Oracle SOA composite for tracking the instance message flow based on the ECID.

The format for setting the value of this property is:

You can also specify this URL details at the Delivery Channel level by using the Oracle B2B console.

This URL is available as a Flow Trace link for individual messages in the Oracle B2B Application Message reports.

While creating the Flow Trace link, Oracle B2B first checks if the value is provided at the channel level. If the value is present, it is used to construct the URL link. If the value is not present, Oracle B2B checks whether b2b.flowTraceEMURL is set in Oracle Enterprise Manager Fusion Middleware Control. If it is set, then the property value is used to construct the URL link. If both values are not set, by default, Oracle B2B assumes that the composite is available in the local domain and constructs the URL link accordingly.

See Configuring Oracle B2B Logging Mode in Administering Oracle SOA Suite and Oracle Business Process Management Suite.

Set this property (along with b2b.flowTraceEMURL) on the domain where Oracle Enterprise Manager Fusion Middleware Control is hosted to construct the Flow Trace URL link in the reports of the Oracle B2B console.

The format for setting the value of this property is:

Note: Currently, Oracle SOA Suite supports tracking of multiple SOA domains and one Oracle B2B instance. This is because this property is set at the global level.

This property enables:

• Trading partner Identifier sent from Middleware or Trading partner is validated against the configured Identifiers in the Agreement for both inbound and outbound flow.

• Override the Identifiers configured in the Agreement using the Identifier sent from back-end application or from trading partner.

The default value is false.

If b2b.TPAbasedebMSIdValidateAndOverride= true:

• Agreement is configured with Identifier ID1, ID2 and inbound message has Identifier ID2, then ID2 would be sent to the back-end application.

  Note: This applies to outbound messages.

• Agreement is configured with Identifier ID1, ID2 and inbound message has Identifier ID3, even though the trading partner is configured with Identifier ID3, there is a failure in Agreement Identification.

• For any outbound message without a specific Identifier type, Name identifier is used in ebMS message header.

If b2b.TPAbasedebMSIdValidateAndOverride= false:

The Identification is done against the configured Identifier in the profile, and the configured Identifier in the Agreement is used in ebMS headers.

Set this property to true to enable resubmission of OUTBOUND ACK.

The default value is false.

When the payload comes in as inbound over AS2 delivery channel, B2B tries to identify the document protocol which is not possible because there is no identifier in the payload to look at. The payload can be any flat file or binary file payload. Set this to binary to define the protocol.

When the payload comes in as inbound over AS2 delivery channel, B2B tries to identify the document protocol which is not possible because there is no identifier in the payload to look at. The payload can be any flat file or binary file payload. Set this to generic to define the protocol.

If this property is set to true, then B2B uses the default .jks file to send for the https delivery channel.

Coherence system properties

coherence.b2bDispatcherCache.size

coherence.b2bDispatcherCache.expiry

coherence.b2bTPACache.size

coherence.b2bTPACache.expiry

These system properties help you to tune the cache size and expiry durations.

The following are the default values of the system properties:

coherence.b2bDispatcherCache.size - 20000

coherence.b2bDispatcherCache.expiry - 3 minutes

coherence.b2bTPACache.size - 20000

coherence.b2bTPACache.expiry - 30 minutes