|Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for HP-UX Itanium
Part Number E14773-06
This chapter describes issues associated with Oracle B2B. It includes the following topics:
This section describes general issues and workarounds. It includes the following topics:
Install the latest XEngine patch if you are using Oracle B2B with EDI and HL7. You can find the latest patch on My Oracle Support (formerly OracleMetalink), number 8604074.
The XEngine sets Interchange and Group header fields for the date and time using GMT instead of the date and time on the local server. This is so even in cases when you have local time configured in the
XERegistry.xml configuration file.
The default setting for the XEngine
Time attribute is
GMT, as shown in the following segment of the
<Product Name="XEngine"> <Category Name="Settings"> <Item Name="Time">GMT</Item> <Item Name="LimitEvents">Rejecting</Item> <!-- Rejecting | @ NonRejecting | All --> <Item Name="InputBufferSize">4096</Item> <Item Name="EnvCrtSeq">DSA</Item> <Item Name="UECLSupport">true</Item>
Local instead of
GMT for the
Time attribute has no effect.
Install the latest XEngine patch. After applying the patch, the default changes to
Local. Installing the latest XEngine patch is also recommended if you are using Oracle B2B with EDI and HL7 (the latest patch addresses this issue). You can find the latest patch on My Oracle Support (formerly OracleMetalink), number 8604074.
Although the Save button is not displayed on the Agreement screen for remote partner administrators, these users can update and save agreements by editing the agreement name on non-deployed agreements, and then updating and saving the agreements. Oracle B2B does not check the user authorization in this case.
Oracle B2B offers a notification of an Ack (AS2-MDN or EDI-FA) that is sent back to a composite or AQ (IP_IN_QUEUE) if configured using the Oracle B2B interface (Administration > Configuration page). The received Ack notification appears similar to the following:
<Acknowledgment xmlns="http://integration.oracle.com/B2B/Acknowledgment" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <replyToB2BMessageId>0AB1FE0211FE933570200000120666E0</replyToB2BMessageId> <replyToAppMessageId>0AB1FE0211FE933570200000120666E0</replyToAppMessageId> <ackB2BMessageId>0AB1FE0211FE9338CB80000012066930-1</ackB2BMessageId> </Acknowledgment>
Note, however, that the
replyToAppMessageId is always incorrectly set to be the same as the
In a batched message, if multiple documents batched as part of a single message have different settings for the FA in the agreement, Oracle B2B uses the FA setting for the first document and applies the setting to all other documents in the batch.
In the outbound case, documents that do not require functional acknowledgement wait on the FA with a status of MSG_WAIT_FA. In the inbound case, documents for which the FA need not be produced are generated and this can cause FA documents to transition to the MSG_ERROR state if there are no deployed agreements for the FA.
Note the following:
If an exception occurs during an outbound batch, the batch is not cleared from the repository. This is true even if a trigger has been fired. In this case, you must manually delete the scheduled batch entry using the Administration page in the Oracle B2B interface.
If you disable a single time invocation batch schedule, any messages set in WAIT_BATCH mode remain in this mode if the schedule is not re-enabled before the expiry time. Furthermore, a new batch schedule created for the same document will not process these messages. The workaround is to resend the message using the resubmit application message option.
Receipt notification does not occur for an Ack (AS2-MDN) received back for an EDI FA document that was sent.
In the Oracle Enterprise Manager B2B Infrastructure (SOA Binding) page, the Top 5 Active Document Types section displays inbound messages received using the AS2 exchange showing only the
DocumentTypeName instead of
For example, 850 may display instead of EDI_X12 4010 850.
After creating an EDI document definition, accessing and saving the document definition (when no updates have been made to the ecs file) can cause a FileNotFoundException message to be generated.
When delivering a receipt notification (AS2 MDN) to AQ, Oracle B2B incorrectly sets the user information to the document routing ID (if the outbound document has a document routing ID set) instead of b2backuser.
The Application Message report in the Oracle B2B interface incorrectly displays document types. Specifically, the Application Message report displays the following:
For receipt messages, the displayed document type is of the outbound message. This can be an issue if you need to collect metric data on the number of inbound application messages for a specific document type. In this case, the issue can cause queries to report incorrect data.
For FA messages, the displayed document type is the same as the FA message type.
In Sync AS2 mode, the generated MDN uses the AS2 Identifier set in the inbound agreement. If no AS2 Identifier is defined in the agreement, the generated MDN incorrectly uses the name identifier.
The workaround is to set the expected AS2 Identifier in the inbound agreement.
In AS2, a request for a signed MDN from the recipient can specify the algorithm to use for signing. Oracle B2B, however, incorrectly signs the MDN with the algorithm set in the agreement delivery channel. This algorithm may be different from the requested algorithm.
In the Oracle B2B interface, the default time to initiate an event in the Administration > Configuration > Schedule Batch screen is 10 minutes ahead of the current server time. However, if you launch the scheduler between 11:50 PM and midnight, then this default time setting does not work properly.
In cases when you have the Oracle B2B interface running in two Web browsers or Web browser windows (on the same or different computers), actions performed in one instance of the Oracle B2B interface may not be automatically reflected in the other running instance. For example, importing metadata in one instance of the Oracle B2B interface is not reflected in the other instance, even after performing a browser refresh.
Clicking on another tab in the Oracle B2B interface and then returning to the previous screen causes the information to refresh correctly.
When receiving an EDI document over an AS2 exchange, if Oracle B2B fails to identify the trading partner using the AS2 From Identifier, Oracle B2B tries to identify the partner using the EDI Interchange and Group ID. The failure to identify the partner by the AS2 Identifier is ignored.
The Sync MDN received by the host server in response to an AS2 message sent over SSL shows an incorrect URL in the wire message. Specifically, the URL indicates the HTTPS protocol while the port information is for the HTTP listen port.
Setting an invalid EDI Interchange ID Qualifier or an invalid Function Group Identifier (not part of the default ecs Qualifier Standard Code List_105 or Function Identifier Code Standard Code List_479 respectively) is not signalled as a MSG_ERROR in the outbound case. Oracle B2B instead delivers the message to the configured endpoint without error.
When a B2B channel is configured to retry following an error (such as a transport channel being unavailable) and the message is subsequently successfully delivered, Oracle Enterprise Manager fails to adjust the corresponding error count.
When validating an agreement, Oracle B2B validates the saved data. Oracle B2B does not validate any unsaved changes you make to an agreement.
In a clustered environment, the XEngine does not get installed on the second node when the node is on another computer. This is because the XEngine extraction occurs only when you run the Configuration Wizard (which is not run automatically on the second node). The workaround is to perform the XEngine extraction manually in this case. After completing the XEngine extraction, you must restart the server.
When you change the identification fields of a custom document (such as the XPath expression, value, start-position, or end-position, among others), you must retire and purge all agreements referring to the document definition before redeploying the agreements to have the changes take effect. Note that redeploying the agreements without purging does not ensure an update of the identification fields in-memory.
When sending EDI messages batched over the Applicability Statement 2 (AS2) exchange protocol, only one message transitions to the MSG_COMPLETE state after receiving an acknowledgment (MDN) back. All other messages remain in the MSG_WAIT_ACK state.
When Oracle B2B batches multiple messages into a single message, the system records the native message size for each business message as the size of all messages in the batch. This results in Oracle B2B reporting an incorrect average message size on the Metrics pages of the Oracle B2B interface.
When using the Administration > Configuration page in the Oracle B2B interface, after you enter a value for a property and save it, you cannot change the property value to null. Doing so causes the Oracle B2B interface to generate the following error:
The value must be of the following type: Type Name: non-empty-string Base Type: string Primitive Type: string With the following constraints: minimum length: 1 Value '' does not satisfy '' facet : minLength
Furthermore, after receiving this error, you will not be able to update any other values on the Administration > Configuration page. The workaround is to navigate to another page, return to the Administration > Configuration page, and update the values, as appropriate.
After deleting a user using Oracle WebLogic Administration Console, the user continues to appear in the Oracle B2B interface for approximately five minutes. This is because the user information remains cached in the managed server (Oracle B2B) for a user-configurable period of time. Performing certain operations, such as provisioning this user, can generate an error.
The workaround is to wait for longer than five minutes after deleting a user using Oracle WebLogic Administration Console.
Alternatively, you can specify the following system property in the setDomain.sh file to disable the cache:
In some cases, Oracle B2B may not pick up the batched messages when you update the batching schedule. If you see that batched messages are not being picked up, delete the batch and create a new batch schedule with the same name as the previous batch. The same name must be used so that Oracle B2B picks up the previous messages in WAIT_BATCH status.
Do not purge instance metadata (using the Purge Instance Metadata button on the Administration > Purge tab) when messages are being processed. Doing so can result in messages in progress being lost. Instead, use the
b2bpurge command line utility, which accepts a date range and message state as arguments. When using the
b2bpurge command, remove messages in the Completed state only (unless you have a specific reason for doing otherwise).
The test page for B2BMetadataWSPort results in a "404 Not Found" error. The workaround is to change the port number in the URL for the link from the managed server port to the admin server port (7001) and try again.
checkduplicateisacontrolnumber is not available in this release.
In a clustered environment, do not use the B2B command line utilities for purging data, importing data, exporting data, deploying agreements, and validating B2B metadata. Use the Oracle B2B interface for these functions.
For ebMS documents, negative acknowledgments for decryption and signature failures are sent as security severity errors. For all other negative ebMS acknowledgments, the error is set as UnknownError.
Under certain circumstances, resubmitting an asynchronous AS2 inbound wire message does not work as expected. For example, change the state of an inbound agreement to inactive. On receiving a message, a negative acknowledgment is generated and sent back. The sender sees the message state as MSG_ERROR on receipt of the negative acknowledgment. Resolve the issue on the inbound side by changing the agreement state from inactive to active. Now two scenarios for resubmitting the asynchronous message exist:
Scenario A: Resubmit the wire message at the sender's side. Because the message was already processed at the receiver's end, this results in a duplicate error message.
Scenario B: Resubmit the wire message at the receiver's end. This passes at the receiver's end and pushes back a positive acknowledgment message. However, the state of the message on the sender's side is not changed. Although scenario A can be expected, scenario B should have worked. However, because the state of the message is MSG_ERROR, the incoming positive acknowledgment is ignored. This results in inconsistency in reporting at the two ends. The inbound side passes the message to the back-end successfully, whereas the outbound side has the message in the MSG_ERROR state.
EDI X12 version 5020 is not supported in this release.
The Oracle B2B Instance Data Access Java API is not available in this release. The API will be available in a future release.
The predefined callout,
XSLTCallout, is not available in this release.
Note the following:
Allow pop-ups (disable the browser pop-up blocker) to use the Oracle B2B online help.
Oracle B2B online help is available in English only for this release.
Some links in the Contents and Index panes do not consistently display the correct section in the topic pane. The workaround is to click one of the top-level headings in Contents and use the internal links at the beginning of each topic to navigate within the topic. Use the search function to find an index term if the link does not work.
Based on the database load and the application server load, tune the transaction timeout setting in the Oracle Weblogic Administration Console. Select JTA from the home page and increase the default setting of 30 to a higher value.
Set the following properties in the
enqueue.properties file when enqueuing large payloads:
Because the full directory path must be provided, use the local computer for this operation.
If the Use JMS Queue flag is enabled, B2B starts to send all inbound messages to the JMS queue,
B2B_IN_QUEUE. However, error notifications for runtime message failures continue to be sent to
IP_IN_QUEUE, even with the Use JMS Queue flag enabled.
If you enable B2B to use the JMS queues by setting the flag Use JMS Queue to true on the Administration > Configuration tab of the Oracle B2B interface, then you must restart the SOA Server.
When the processing of an incoming RosettaNet message fails, as per the standards, an Exception signal should be sent back to the partner, but is not.
If a CONTRL message contains multiple document types and one document is in error, then one ORDERS message remains in the
Consider the following example:
A batch containing the following is sent from Acme to GlobalChips:
ORDERS (duplicate GUID)
ORDERS (new GUID)
The outbound message is sent with one ORDERS message in the
MSG_ERROR state, as expected. The other messages are in the
MSG_WAIT_FA state. The inbound FA (CONTRL) updates only the status of one ORDERS and one ORDRSP message. The result is that one ORDERS message remains in
Implicit SSL encryption is not supported in the transport layer.
%ACTIONNAME% filename format is not recognized when used with the File, FTP, and SFTP transport protocols.
Oracle B2B is unable to process an inbound RosettaNet message encoded as UTF-16. It gives a document protocol identification error.
The RosettaNet delivery channel security settings for an inbound agreement must be set as follows:
When sending back an unsigned receipt acknowledgment message, set both Message Signed and Ack Signed to false (do not select the boxes).
When sending back a signed receipt acknowledgment message, set both Message Signed and Ack Signed to true (select the boxes). Select the signature algorithm and certificate alias as required.
Save autogenerated agreements at least once before the agreements are deployed. The agreement parameter settings for translation/validation and FA are generated in the agreement only when you save an agreement and not when it is autogenerated. Although the interface may show the default values, they are not captured in the agreement metadata and are ignored at runtime; that is, the inbound EDI message may not be translated.
When creating a Minimum Lower Layer Protocol (MLLP) client delivery channel specified using a host name and a permanent connection, the permanent delivery channel can become transient when the in-flight message establishes the connection to the server. The workaround is to use an IP address instead of the host name when creating the client MLLP delivery channel. However, if the connection is pre-established (by enabling the client channel to establish the connection), then the connection works as a permanent connection.
See Section 3.1.1, "Patches Required to Address Specific Upgrade and Compatibility Requirements," for required patches.
An ecs file created in Oracle B2B Document Editor cannot be used for translation with the positional flat file document type. Therefore, the positional flat file document type is not available for this release. It will be available in the next release.
On the Listening Channel tab, some parameter fields that are displayed in the Channel Details area based on your protocol selection are not relevant to that protocol. Entering a value for these parameters has no effect. Table 15-1 lists the parameter fields that are not relevant.
Table 15-1 Fields That Display but Are Not Relevant for the Selected Protocol
|If you select this protocol...||Then you can ignore these parameter fields...|
Subject, Send as attachment, Ack Mode, Response Mode, Retry Count, Retry Interval, all fields on the Security tab
Retry Count, Retry Interval
Retry Count, Retry Interval
Use Proxy, Retry Count, Retry Interval
Retry Count, Retry Interval
Retry Count, Retry Interval
Subject, Send as attachment, Retry Count, Retry Interval
See Section 15.3.6, "Some Parameters Should Not Be Documented for Listening Channels" for related information.
Oracle JDeveloper hangs when you switch application server connections in the B2B Configuration Wizard. The workaround is to restart JDeveloper.
The Generic FTP-1.0 protocol for a listening channel does not have proxy support.
When using the
b2bpurge command line utility, if inactive channels exist, then those listening threads are not terminated. The workaround is to repeat the
b2bpurge call two or three times until the listening threads for the inactive channels are terminated.
If you encounter a "Method Not Found" error in the B2B interface (due to incorrect JSP compilation), use the following workaround to recompile the interface JSP files:
Go to your Fusion Middleware home.
_tpagreement_jspx.class location and remove all B2B interface JSP class files in the same directory.
For the admin server, the directory typically looks like this:
For the managed server, the directory typically looks like this:
Restart all servers, including every server in a clustered environment.
Accessing the B2B interface may be slow at first due to JSP compilation.
When using the B2B Configuration Wizard in Oracle JDeveloper, the SOA HTTP Port field on the Application Server Connection page does not accept an HTTPS port.
If you select multiple agreements to export (from Administration > Import/Export), and any of those agreement names are in a multibyte character language, then in the export ZIP file, which contains a separate ZIP file for each agreement, the ZIP file names for the agreement names with the multibyte characters are garbled. The ZIP files with the garbled names are corrupted and cannot be successfully imported. However, a single agreement name (or repository name) in a multibyte character language is exported correctly.
For an inbound agreement that uses an ebMS exchange with the Ack Mode parameter set to Async, an ebMS delivery channel is required.
Normally the default log level suppresses details in the log file. However, for RosettaNet deployments, log details are not suppressed even with the default log level setting.
If you use a custom icon for a trading partner (a PNG image file) and export the entire repository, then the icon image file is present in the exported configuration (ZIP file). However, if you import the ZIP file to another B2B server, then the custom icon for the trading partner does not appear in the B2B interface.
The workaround is to do the following:
Move the image file for the trading partner from the
images directory to the
images directory is located under the
b2bui directory. For example, the directory path looks something like
Rename the PNG image file to remove the prepended string,
The directory name is added to the image file name. To preserve the image file name, remove the prepended directory name. For example, if your original image file name is
TP_ICON_tp_dGL-8506012758410451620_mobile.png, then after moving it, rename it from
tpIconsTP_ICON_tp_dGL-8506012758410451620_mobile.png back to the original file name,
For documents using the XEngine, such as EDIFACT and HL7 documents, when you have a payload with multibyte characters that are not in the EDIFACT and HL7 document character set registry, you may see the error, "A data element contains characters not listed in the allowed character set."
To avoid this error, create a custom character set (CS) file in Oracle B2B Document Editor called
In Oracle B2B Document Editor, click Tools > Character Set Registry.
In the Character Set Registry window, select the character set you want to override.
For example, you may want to override EDIFACT UNOB CS or HL7 CS.
Click the Duplicate icon.
In the Duplicate Character Set Properties window, accept the defaults and add the specific multibyte characters at the end of the Charset blank; then click OK.
With the duplicated file still selected, click the Export icon.
Name the file
user.cs and save it.
Now documents such as EDIFACT and HL7 will use the
user.cs file instead of the default CS file to verify the payload file.
a01.xml payload for an HL7_2.3.1_ ADT_A01 XML document contains multibyte characters, then, to support multibyte characters, you must change the MSH.18 element in the payload from
<MSH.18>UNICODE</MSH.18>. If the
UNICODE value is not included, you will get the error "Sub-Component PID5-1-1 (family name) contains characters not listed in the allowed character set." You must also create
user.cs and modify it to contain the multibyte characters. See Section 15.1.62, "Enabling Multibyte Support for EDIFACT and HL7 Documents" for more information.
When working with document definition names with multibyte characters (MBCS-named document definitions) in the B2B Configuration Wizard in JDeveloper, you may see the error " Invalid UTF8 encoding" at the step where the document definitions are loading for you to select the document definition for the service. This occurs when JDeveloper is running in a non-UTF-8 environment (for example, in Windows, using Simplified Chinese Win2k3, or in a native encoding Linux OS, using zh_CN.gb18030). However, in a Linux environment with UTF-8 encoding, such as zh_CN.utf8, MBCS-named document definitions load correctly. After loading, the MBCS-named document definition becomes the name of the document XSD folder in JDeveloper.
To ensure that MBCS-named document definitions load and display correctly in the B2B Configuration Wizard, do the following:
When using JDeveloper in a Linux environment, first set the
LC_All environment variables to a locale with the UTF-8 character set. This enables the operating system to process any characters in Unicode. Then start JDeveloper.
When using JDeveloper in a Windows environment, start JDeveloper using UTF-8 encoding with
This section describes configuration issues and workarounds. It includes the following topics:
HL7 File/Batch Header Envelope support is not available directly from the seeded ecs files for HL7 version 2.6. However, as a workaround, you can override the File/Batch Header ecs file when creating the document protocol version. Note that while HL7 Batch and File envelopes are supported, batching is not supported in this release.
For HL7, setting the Functional Ack internal property (FAInternalProperty) to false using the Administration > Configuration page in the Oracle B2B interface causes Oracle B2B to nevertheless use the payload header FA internal properties instead of the design-time parameters.
When the FAInternalProperty is set to true and there are different payload and design-time parameter values, you may see an error in the Ack message. Therefore, it is recommended that you do not set the FAInternalProperty to true for HL7.
Although the metadata for a remote trading partner stores separate information for the sender and the receiver for the same document definition, you cannot specify these differences using the Oracle B2B interface.
The workaround is to create a new document definition and use the two definitions to specify the parameters for the sender and receiver separately.
The Oracle B2B interface does not offer the ability to set the Ack Requested field for Interchange.
When creating a host document, including specifying the version, type, and definition, Oracle B2B assigns default values to certain fields that can be overridden by the user. If you override one or more nonmandatory fields by making them blank and then add the definition to the remote trading partner, the default values that you intentionally left blank re-appear for the remote trading partner.
To resolve this issue, manually make the nonmandatory fields blank again for the remote trading partner.
When using any document protocol, the following exception appears in the seller's soa.log file:
oracle.toplink.exceptions.QueryException Exception Description: Query sent to an unactivated UnitOfWork.
The workaround is to increase the JTA timeout from 30 to a higher value using Oracle WebLogic Server Administration Console.
Increase the default tablespace configuration in production environments to prevent error conditions that can occur when processing a large number of messages.
You can specify the envelope elements, separated by commas, to be ignored during look-up validation for agreements. The possible values for ignore validation on envelope elements varies based on the identifiers used in the agreement. For example, for HL7 agreements, you can specify MessageSendingApp, MessageReceivingApp, MessageSendingFacility, and MessageReceivingFacility, among others.
For EDI agreements, the possible values are InterchangeSenderID, InterchangeReceiverID, GroupReceiverID, GroupSenderID, TransactionAssociationAssignedCode, InterchangeReceiverQual, InterchangeSenderQual, and InterchangeControlVersion, among others.
Changes to the Ignore Validation on Envelope Elements setting require you to restart the Oracle B2B server for the setting to take effect.
Use these parameters as follows:
Use JMS Queue
If this option is set to true, then
B2B starts to poll on
B2B_OUT_QUEUE, and along with
IP_OUT_QUEUE, for outbound messages
Inbound messages are delivered only to
B2B_IN_QUEUE and not to
If this option is set to false, then
B2B polls only on
IP_OUT_QUEUE for outbound messages
Inbound messages are delivered to
Use B2B Queue
Do not use this setting. Set Use JMS Queue to false to deliver inbound message to
In the Oracle B2B interface, the Enable Auto Search parameter (on the Administration > Configuration page) does not function in this release.
When the log level is set to trace for
oracle.soa.b2b.repository, the payload received by B2B is logged in plain text into the server's
In a high availability environment, B2B MDS notification occurs across nodes in a cluster when the following default values are set for these properties:
These default values cannot be updated in Oracle Enterprise Manager 11g Fusion Middleware Control.
This section describes documentation errata. It includes the following topics:
The description of the Retry Interval parameter in Table 5-3 of Oracle Fusion Middleware User's Guide for Oracle B2B is incorrect and should read as follows:
This is the interval, specified in minutes, after which B2B will attempt to resend a message. B2B tries to resend the message if the status of the message is not Complete. For a retry interval set to 2 minutes, the first retry may not be at the 120 second (2 minute) interval. This is because the first retry is done without considering the seconds at which the message was sent. For example, if the sent timestamp is 3:42:58 (3 hours, 42 minutes and 58 seconds), then 42 minutes is incremented by 2 minutes and the first retry is done at 3:44:00. Subsequent retries, if any, will follow at 3:46:00, then 3:48:00, and so on, with exact 2 minute intervals.
The description of JTA settings in Appendix A of Oracle Fusion Middleware User's Guide for Oracle B2B is incorrect. It should not state a setting of up to 350 seconds. The suggested setting is an increase to 90, and if required, to higher values.
The description of the
b2b.outboundOneErrorAllError parameter in Appendix B of Oracle Fusion Middleware User's Guide for Oracle B2B requires the following changes indicated in bold italics.
When using the
b2b.outboundOneErrorAllError parameter, inbound messages behave as if
b2b.outboundOneErrorAllError is set to false; that is, if an error occurs during an inbound message process, then only that message is flagged with the error and other messages are passed. There is no option to flag every message as failed.
For outbound messages,
b2b.outboundOneErrorAllError can be set to true or false. The default is false. If the parameter is set to true, then for outbound messages, even with a single message in error, all outbound batch messages are set to the error state. None of the batched messages are sent to the trading partner.
To set the OneErrorAllError parameter, use either of the following methods:
b2b-config.xml, add the following property:
<property> <name>b2b.outboundOneErrorAllError</name> <value>true</value> <comment>error all outbound batch messages on one error</comment></property>
In Oracle Enterprise Manager Fusion Middleware Control, add the property to the b2b MBean by using the System MBean Browser. For more information about how to access the System MBean Browser, see Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite.
The description of the polling interval parameter in Table 5-3 and Table 14-3 of Oracle Fusion Middleware User's Guide for Oracle B2B states that the time interval is milliseconds. This is incorrect. The time interval is seconds. The description should read as follows:
The time interval in seconds during which Oracle B2B polls the server for inbound messages.
The following statement in Appendix B, "Setting Internal Properties for a Functional Acknowledgment" of Oracle Fusion Middleware User's Guide for Oracle B2B is incorrect:
To ensure that the ISA segment elements (1 - 4) of a 997 message generated by B2B are identical to the received 850, or any other transaction message, set the property
The correct statement is as follows:
true, by default, will not map ISA segment elements (1-4). By default it will only swap the interchange and group IDs from the sender to the receiver and vice versa, in the generated FA. The test usage indicator parameter is also mapped; that is, an inbound message set as a test message will generate an FA with the flag set to test message.
Table 14-3 in Oracle Fusion Middleware User's Guide for Oracle B2B incorrectly includes the parameters listed in Table 15-2. These parameters are not relevant to listening channels. In addition, the Use proxy parameter in Table 14-3 incorrectly states that this parameter is used with the Generic FTP-1.0 protocol. Use proxy is used with the Generic SFTP-1.0 protocol only.
Table 15-2 Parameters Not Relevant to Listening Channels
|Protocol/Parameter||Description||Protocol Used With|
Send as attachment
If enabled, the message (payload) is sent as an e-mail attachment instead of the typical delivery in which the payload is the message body.
The subject header of the e-mail message.
Select Sync, Async, or None for the mode in which the trading partner receives messages. Select None for all generic exchanges.
Select Sync, Async, or None,
The number of times that Oracle B2B retries sending the message.
The time interval in seconds during which Oracle B2B attempts to resend the message. A time interval of 2 minutes increments the HH:MM:SS timestamp as follows: If the sent timestamp is 3:42:58, then 42 seconds is incremented by 2 minutes and the retry is sent at 3:44:00. The seconds are dropped in the retry increment. Subsequent retries are at 2 minute intervals.
For protocols with acknowledgments, B2B waits for the acknowledgment (formerly called the Time to Acknowledge parameter). If it is not received, the retry interval setting causes B2B to retry
Select this option to ensure that the responder acknowledges receipt of the messages; nothing needs to be provided.
If Message Signed is selected, then select one of the following:
SMIME 3.0 with MD5 - RSA
SMIME 3.0 with SHA1 - RSA
If Message Encrypted is selected, then select one of the following:
SMIME 3.0 with DES
SMIME 3.0 with 3DES
SMIME 3.0 with RC2 - 40
SMIME 3.0 with RC2 - 64
SMIME 3.0 with RC2 - 128
Select this option to enable message encryption. This option requires you to select an encryption schema in the Encryption field.
Select this option to provide one of the digital signatures in the Digital Signature field.
See Section 15.1.52, "Some Listening Channel Details Are Not Relevant for the Selected Protocol" for related information.
The security note in "Security Features of Oracle B2B" in Oracle Fusion Middleware User's Guide for Oracle B2B is incorrect.
The correct statement is as follows:
Note:Oracle B2B runtime does not support the CLIENT-CERT authentication method. Therefore, B2B is not able to post to OAM-SSO protected URLs.
The following information was omitted from Oracle Fusion Middleware User's Guide for Oracle B2B.
In outbound agreements, the following identifier types should be used with these exchange protocols:
|Exchange Protocol||Identifier Type|
|AS2-1.1||Name, AS2 Identifier|
|AS1-1.0||Name, AS1 Identifier|
|ebMS-1.0, ebMS-2.0||Name, ebMS Identifier|
|RosettaNet-V02.00, RosettaNet-01.10||Name, DUNS|
|MLLP exchange||Name, MLLP ID|
|Generic HTTP-1.0||Name, Generic Identifier|
|Generic Email-1.0||Name, Generic Identifier|
Note the following corrections to Oracle Fusion Middleware User's Guide for Oracle B2B:
Incorrect Repetition of Text
The following error (in italics) appears in Chapter 5, "Configuring Trading Partners":
For information on creating a document definition—required before you can you can add it to the trading partner profile—see Chapter 4, "Creating Document Definitions."
The correction (in italics) is as follows:
For information on creating a document definition—required before you can add it to the trading partner profile—see Chapter 4, "Creating Document Definitions."
Change JMS to JMS* To Indicate Preview Mode
In Table 1-2, "Protocols Supported in Oracle B2B," JMS should be asterisked—JMS*—to indicate that it is in preview mode for this release.
Secure Socket Layer
In "Security Features of Oracle B2B" in Chapter 1, secure socket layer should be Secure Socket Layer.
Directory Path for Finding Port Information
The correct directory path is as follows:
In "Creating Guideline Files: EDIFACT D98 Example" in Chapter 3 of Oracle Fusion Middleware User's Guide for Oracle B2B, step 5 inaccurately states that you can select this option if you require a variation from the standard. This is incorrect. Selecting the interchange envelope along with the transaction will cause validation errors for the inbound message. To override the default preseeded envelope information, create a separate ecs file with only the required envelope information (without the transaction details) and then upload it using the envelope override option available in the Document version.
In "Notes" in Appendix A of Oracle Fusion Middleware User's Guide for Oracle B2B, the following information should be included:
If an enqueue script is used when working with large payloads, add
The descriptive text (tooltip) that pops up when you place the cursor in the SOA HTTP Port field of the Application Server Connection page of the B2B Configuration Wizard in Oracle JDeveloper incorrectly refers to the property soa.oc4j.http-web-site. The correct description for SOA HTTP Port is as follows:
The HTTP port number for the application server.