Oracle® Fusion Middleware User's Guide for Oracle B2B 11g Release 1 (11.1.1.6.2) Part Number E10229-09 |
|
|
PDF · Mobi · ePub |
This appendix describes how to use Oracle Enterprise Manager Fusion Middleware Control to set B2B configuration properties for properties that are not set on the Configuration tab of the Oracle B2B interface (see Chapter 17, "Configuring B2B System Parameters"). It also discusses how to set B2B properties by using the configmbeanutil
utility.
The appendix contains the following topics:
The following properties can be set in Oracle Enterprise Manager Fusion Middleware Control. See Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite for how to set the properties.
Note:
Restarting the SOA Server is required for changes to B2B properties.
Table C-1 Oracle B2B Properties in Oracle Enterprise Manager Fusion Middleware Control
Property | Description |
---|---|
b2b.addebMSHeaders |
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. |
b2b.attachments.dir |
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. |
b2b.certificatevalidation |
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 |
b2b.checkDuplicate |
To check for duplicate messages, set this property to If this property is set to By default, Oracle B2B checks for duplicate messages based on the business message ID of the incoming message. |
To turn off validation during deployment, set this property to This is useful when deploying a large number of agreements where you are certain that the data is valid. |
|
b2b.docPluginList |
Using this property, document plugins are loaded as per the order specified in this property. For example, b2b.docPluginList=Custom,EDI_X12,EDI_EDIFACT,HL7,RosettaNet ensures that document plugins are loaded as per the specified order. If no value is provided for this property, then all document plugins from the system ( |
b2b.edi.enablePreprocess |
Set this property to The default value is Changes to this property require a server restart for the new value to take effect. |
oracle.tip.b2b.edi.binaryDocType |
This property is used by Oracle B2B to handle the BIN segment of EDI payloads. You need to specify a comma-separated list of document types that can have BIN segments as the following: oracle.tip.b2b.edi.binaryDocType=841 Setting this property ensures that Oracle B2B processes the corrupt BIN segment content by treating the content as binary. |
b2b.edi.identifyToTP |
To identify the toTP from the TP information present in the incoming message, use this property. This property is used for inbound message processing. If it is set to |
b2b.edi.ignoreValidation |
To turn off the EDI envelope validation and ignore interchange validation errors for EDI messages, you can set comma separated envelope header with this property. For example: b2b.edi.ignoreValidation=InterchangeSenderID, InterchangeReceiverID or use the value Note: If you add or update this flag, a server restart is not needed. However, if you remove the flag, the server must be restarted for the change to take effect. |
b2b.encoding |
This property can be used to specify encoding other than default UTF-8. |
b2b.errorsCumulativeReported |
To indicate whether reported errors are cumulative or not, set this property to Set this property to 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. |
b2b.fa.inbound.validation b2b.fa.outbound.validation |
Use these properties to control inbound and outbound FA validation. To turn off the outbound FA validation, set the To turn off the inbound FA validation, set the |
b2b.FACorrelatedByInterchangeId |
To correlate inbound and outbound FAs correctly if the same control numbers are used between the same trading partners, set this property to By default Oracle B2B does not correlate inbound and outbound FAs correctly if the same control numbers are used between the same trading partners. Set this property to |
b2b.FailedMessagesDirectory |
To change the location of the failed application message that is written to the file system, when |
Set this property to The default value of this property is 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 If set to If set to The default value for this property is |
|
To enable a channel name or a trading partner name as a sequence target, set this property to 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 ( To enable sequencing in case of:
|
To turn off the hl7 envelope validation, you can set comma separated envelope header with this property. For example: b2b.hl7.ignoreValidation = MessageReceivingFacility, MessageSendingApp or set it to |
|
To set the number of threads and thread sleep time to improve message processing, set these properties. The recommended values for 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 The |
|
b2b.jmsRedeliveryLimit |
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 You can specify the location for failed messages by setting |
b2b.listening.channel.restart.wait |
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. |
b2b.MaxTimeinAquiredState |
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 |
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. |
|
b2b.OutboundDispatchInterval |
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. Once 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. |
b2b.outboundOneErrorAllError |
To specify how errors are flagged, set this parameter to For outbound messages, When using the |
b2b.payloadObfuscation |
To turn on payload obfuscation, set this property to true. See Section 1.4.1, "Payload Obfuscation," for more information. |
b2b.rowLockingForCorrelation |
To enable row level locking, set this property to When Oracle B2B receives an EDI FA message and an AS2 MDN message (Acknowledgment message) simultaneously, a race condition can occur which causes the outbound EDI message to remain in the MSG_WAIT_FA state (although FA was successfully processed). Use this row level locking parameter so that the original EDI message can be accessed sequentially when the correlated FA and Acknowledgment messages are processed concurrently. It avoids a racing condition when Oracle B2B updates the original message. |
b2b.setDynamicNameSpace |
To use EDI ecs and xsd files from Oracle B2B 10g version, set this property to When using EDI ecs and xsd files in Oracle B2B 11g which were used in Oracle B2B 10g, the XEngine may generate dynamic namespace for the translated xml. For example, xmlns="NS_31CA8D0F33324F95A0BF15D85539C27E20060518215520" To turn off dynamic namespace generation for inbound EDI messages, set this property to |
b2b.SyncAppDelivery |
When using callouts, to enable delivery of messages to the back-end message queue, set this property to |
b2b.setisLargePayloadPropertyForSmallMsg |
By default Oracle B2B sets the By default, the value of the property is |
b2b.listening_channels.continue_reconnect |
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 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 |
b2b.reuseHttpConnections |
Set the value of this property to However, this property depends on other property values to take effect. If you call So you need to compare |
b2b.deliverPingPongToBackend |
In ebMS, you can check the server state by using a set of messages called 'Ping and Pong'. Set the b2b.deliverPingPongToBackend property to By default, the value of the property is |
b2b.trackInboundCtlNum |
By default, the value of this property is |
b2b.SingleTransactionAtInbound |
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 The default value of the property is |
b2b.retainmsgid |
When this value is set to If this value is set to The default value for this property is |
b2b.TPACache |
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 |
b2b.DispatcherCache |
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 |
b2b.enableDeliveryHelper |
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 |
b2b.sequencingFetchSize |
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 The valid value for this parameter is |
Coherence system properties
|
These system properties help you to tune the cache size and expiry durations. The following are the default values of the system properties:
|
You can also use the configmbeanutil utility to set properties.
To use the configmbeanutil utility:
Set the MW_HOME
environment variable to point to the Fusion Middleware installation directory. For example,
setenv MW_HOME /scratch/$user/fmwhome
Note:
To access the Fusion Middleware directory, you must provide an mbean property file (mbeanutil.properties
) that contains host, port, user, and password information. For example,
host=myfmw.com port=7001 user=weblogic password=mypwd
Set the JAVA_HOME
environment variable. For example,
setenv JAVA_HOME ${MW_HOME}/jdk160_14_R27.6.4-18
Add the Java bin directory to the PATH
environment variable. For example,
setenv PATH ${JAVA_HOME}/bin:${PATH}
Example C-1, Example C-2, Example C-3, and Example C-4 show uses for this utility.
Example C-1 To Print All Properties to the Console
java -cp $MW_HOME/AS11gR1SOA/soa/modules/oracle.soa.b2b_11.1.1/b2b.jar:$MW_HOME/ wlserver_10.3/server/lib/wljmxclient.jar:$MW_HOME/modules/ glassfish.jaxb_1.2.0.0_2-1-7.jar oracle.tip.b2b.utility.ConfigMBeanUtility
Example C-2 To Add a Property
java -cp $MW_HOME/AS11gR1SOA/soa/modules/oracle.soa.b2b_11.1.1/b2b.jar:$MW_HOME/ wlserver_10.3/server/lib/wljmxclient.jar:$MW_HOME/modules/ glassfish.jaxb_1.2.0.0_2-1-7.jar oracle.tip.b2b.utility.ConfigMBeanUtility add b2b.test cool ok