Known Issues
The table lists known issues in version 6.2.1 of TIBCO BusinessConnect.
Key Summary/Workaround
BC-8730 Summary: When you create an external user in TIBCO Administrator GUI under BusinessConnect > System Management > Users > External tab, if you enabled any gateway service permissions and set the authentication source to the LDAP server for external users, the "No Such Object" LDAP error is thrown, however the user is successfully created and stored in the LDAP server.
Workaround: Before creating the external user, ensure that you configure a valid value for the bc.ldap.rolebasedn.attribute property that is located under
BusinessConnect > System Settings > Activated Protocol Plug-ins and Properties >
BC.
BC-8729 Summary: The external users that are manually created in the LDAP server or are created by a previous version of TIBCO BusinessConnect are not displayed in TIBCO Administrator GUI under BusinessConnect > System Management > Users >
External tab.
Workaround:Log in to the LDAP server, and then add the o attribute and set the value of this attribute to the associated trading partner name for these external users.
BC-8725 Summary:When you used SSLv3 as the secure transport mode to establish a connection between TIBCO BusinessConnect Server and a business-to-business server, the connection was not established successfully because the SSLv3 handshake failed.
Workaround: You can issue the following steps to resolve this issue:
1. Delete the SSLv3 option from the values of jdk.tls.disabledAlgorithms
property in the java.security file that is located in the TIBCO_HOME\tibcojre64\1.7.0\lib\security directory.
2. Restart all TIBCO BusinessConnect engines.
BC-8307 Summary: When using the Email transport to send out a file as a compressed attachment, if this file comes from a TIBCO ActiveMatrix BusinessWorks private process and both the name and the fileName fields are specified but the content field is empty, error occurs when TIBCO BusinessConnect processes the inbound message if the characters in the fileName field are longer than the characters in the name field.
Workaround: Do not specify a value for the name field if the value in the fileName field is specified so that the file content comes from the file, in which case the value in the fileName field is used for the attachment header of the outbound Email message.
28
|
Release NotesBC-8302 Summary: There is a possibility that the sample certificate used to connect to the Gmail SMTP server can expire depending on the Gmail service.
Workaround: Download a new Gmail server certificate.
BC-8262 Summary: Audit log of UNPACKAGE_MSG state is not present for inbound PGP packaged files by using the SSHFTP transport, when a script is specified for retrieving and un-packaging the files.
Workaround: None.
BC-8141 Summary: Inbound messages sent by using FTPS, SSHFTP or TIBCO PartnerExpress plug-ins are not counted to the "InboundReceived" count in TIBCO Hawk monitoring of Gateway Servers. This can only be resolved in each plug-in new release.
Workaround: None.
BC-7903 Summary: If you use the TIBCO BCAppManage tool to create a deployment, the BusinessConnect tab is not displayed on the Application Management >
BusinessConnect > Configuration > BusinessConnect link > Edit Application Configuration page. You also see null pointer exceptions if you select
BusinessConnect in the left panel and click Manage in the installation section.
Workaround: Restart TIBCO Administrator server.
BC-7831 Summary: When using the TIBCO BCAppManage tool to import .csx configuration files, there is a possibility that Java class-loading errors are displayed after the import operation is completed in TIBCO Administrator.
Workaround: Restart TIBCO Administrator.
BC-7818 Summary: If you delete a tibbr subject in TIBCO BusinessConnect at the trading partner level, TIBCO BusinessConnect does not post messages to valid system level tibbr subjects. This behavior occurs because of the way TIBCO BusinessConnect interacts with the tibbr API.
Workaround: None.
BC-7776 Summary: Signed multiple attachments sent by using the AS1 email are not verified by TIBCO BusinessConnect.
Workaround: None.
Key Summary/Workaround
Known Issues
|
29BC-7742 Summary: If you attempt to save a tibbr subject that has been deleted in either BusinessConnect > System Settings > Visibility > tibbr or BusinessConnect >
Participants > Edit Participant > Visibility, an error message is displayed. This is because tibbr subject names must be unique. Once a subject has been created in tibbr, it cannot be re-created, even if you have deleted it. tibbr retains subjects internally to preserve old messages posted to that subject.
Workaround: Use a different subject name.
BC-7608 Summary: When the Host Logo field in the option Host Partner Type contains a file reference type to an image that is not reachable, then the imported host gets deactivated and disables the PartnerSelfService protocol if TIBCO
BusinessConnect Trading Community Management is installed and activated.
Workaround: Make sure that the Host Logo field has an image uploaded.
BC-7604 Summary: When TIBCO BusinessConnect Trading Community Management is installed in TIBCO BusinessConnect and there are changes to Property Metadata Editor to make protocol specific properties to be self-serviceable, these self-serviceable attributes are not exported.
Workaround: To make the properties self-serviceable, you must enable them explicitly after importing the configuration.
BC-7451 Summary: When you enable PGP signing, encryption, or compression for a trading partner for the FTP transport, no PGP processing is performed on messages received by that trading partner. Similarly, when you disable PGP signing, encryption, or compression for a trading partner for the FTP transport, PGP processing is performed on messages received by that trading partner.
Workaround: After enabling or disabling PGP processing for a trading partner for the FTP transport, restart Interior Server.
BC-7242 Summary: When the Email transport is configured under BusinessConnect > System Settings > Inbound Public Transport Types, the setup under Application
Management > BusinessConnect > Configuration must be changed and saved for the Email transport to work after redeployment.
Workaround: The setup under Application Management > BusinessConnect >
Configuration must be edited and saved.
Key Summary/Workaround
30
|
Release NotesBC-7233 Summary: Once the Gateway tokens are created and deployed, if the value in the Installation Name or Installation Prefix fields are changed under BusinessConnect >
System Settings > General, Gateway Server does not come up even after the tokens are re-exported from BusinessConnect > Gateway > Gateway Tokens.
Workaround: Delete the previously created Gateway tokens and create new ones for the changes to take place.
BC-7216 Summary: TIBCO BusinessConnect can send the AS2_HTTPS message to TIBCO BusinessConnect Remote only if the bc.securityVendor.sockets list is set to ENTRUST. The SUN and IBM providers are not supported in TIBCO BusinessConnect Remote.
Workaround: None.
BC-7165 Summary: Shadow credentials are not supported for the TIBCO BusinessConnect server keys; they are supported only for public certificates.
Workaround: None.
BC-7133 Summary: PGP credentials are not supported with the TIBCO BCAppManage tool.
Workaround: Only the TIBCO Administrator UI can be used for exporting and importing PGP credentials.
BC-7083 Summary: The exception "Session already closed" occurs in TIBCO Administrator logs when an installation .csx file is imported.
Workaround: None.
BC-6930 Summary: If any changes other than Email are made under BusinessConnect >
System Settings > Inbound Public Transport Types, then Interior Servers and Gateway Servers must be restarted. For the Email transport, a redeployment of Interior Servers is required.
Workaround: None.
Key Summary/Workaround