WebLogic Integration - Business Connect, the lightweight trading partner software for BEA WebLogic Integration, enables businesses to connect supply chains with demand chains, down to the smallest partners and suppliers. In a configuration in which a business uses BEA WebLogic Integration as a hub and its partners use WebLogic Integration - Business Connect as spokes, all participating trading partners can automate the sharing of information while lowering the costs and time-to-market of B2B commerce.
A potential security risk has been discovered which could affect customers using BEA WebLogic Integration - Business Connect 8.1. The vulnerability is caused by a third party application that is bundled in this product. This vulnerability could allow unintentional access to the machine's file system over a Web browser. A new version of the third party application has been bundled with WebLogic Integration - Business Connect 8.1.2 to resolve this issue.
When receiving documents inbound with synchronous MDNs requested, if the synchronous connection fails, WebLogic Integration - Business Connect will consider the transaction incomplete and wait for a resend.
For information on hardware and software requirements, see System Requirements in Using WebLogic Integration - Business Connect at the following location:
Although WebLogic Integration - Business Connect supports ebXML trading with bundled HTTP, bundled HTTPS, SMTP, or POP transport, only HTTP and HTTPS are supported with a WebLogic Integration trading partner.
Wherever the phrase "conversation definition defined in WebLogic Integration" is referenced in Using WebLogic Integration - Business Connect, users should substitute with "ebXML service name." In WebLogic Integration, the ebXML service name corresponds to the
ebxml-service-name in the process annotation (for participant process) or in the control annotation (for initiator process).
The "ebXML with File System Interface" section in Using WebLogic Integration - Business Connect mentions that "There are no WebLogic Integration requirements for the value of the action." This is correct if the WebLogic Integration side uses the "default" option for ebXML actions (expressed in the `ebxml-action-mode' attribute). However, if the "non-default" option is used, the value of the action does matter and must match the Client Request method name in the participant process. For more on ebXML action names, see "Introducing ebXML Solutions" at the following URL:
WebLogic Integration - Business Connect may send a duplicate ebXML acknowledgment after it is restarted. This does not affect the operation of ebXML messaging as the duplicate acknowledgement will be discarded by the receiving side.
WebLogic Integration trading partners do not support document encryption. Turn off document encryption by clearing the encrypt documents check box on the Security tab in the Partner Profile window. For secure transport, use the HTTPS transport protocol.
Do not manually delete files that begin with
md in the archive directory. Deleting such files can result in errors when reprocessing documents. These files are associated with conversations in trading using message control documents (MCDs). If it is necessary to delete the
md files, use File
InterchangeHttpsURL are not populated in the document that is attached to the event sent to API event listeners. These values should be populated. This forces the API user to use a document listener. Note that the values are populated in the
If you trade XML files larger than 100 megabytes, you may need to increase the memory on the computer that runs the server application. Processing such a large file can cause the packaging thread to pause and not be released. This situation is caused by a lack of resources.
If you want to reprocess an ebXML document for which you already have received an acknowledgment, be aware of the following. BEA WebLogic Integration - Business Connect repackages documents that are selected for reprocessing. When you reprocess an ebXML document, your partner re-sends the original acknowledgment. This causes your system to generate a message integrity check (MIC) error upon receiving the acknowledgment, because the hash of the outbound reprocessed document does not match the hash of the inbound acknowledgment. This only occurs when an MCD is used and when a
messageID element is present in the MCD.
If you upgrade from version 7.0 and you used a password in 7.0 to access the Server Monitor web page, the password does not work in 8.1. Set a new password in 8.1 on the Monitoring tab in Tools
When two or more partner profiles with similar IDs are present on the system, documents can be sent to the wrong partner. To prevent this, add the parameter
-enableStrictIdMatching at the end of the Windows
StartServer.bat file or the UNIX start server script.
installation_dir/profiles/Quickstart.xml file cannot be directly imported into WebLogic Integration 8.1. You can, however, import it into WebLogic Integration - Business Connect to quickly get started with trading partner configuration. If you subsequently export it from WebLogic Integration - Business Connect, you will then be able to import the information into WebLogic Integration 8.1.