Adding an Authentication Source
SSHFTP Settings
bc.sshftp.cache.tun nel
SSHFTP Tunnel Max Inactive Life, in minutes. Only one SSH tunnel (per transport) exists between a host and a participant. If this tunnel is inactive for a longer time than described by this parameter, BusinessConnect will destroy the tunnel and create a new one the next time the BusinessConnect engine needs to send or receive messages. If the tunnel is destroyed earlier because of other problems, such as the trading partner closed it or a disconnection occurred, BusinessConnect will try to create a new tunnel automatically and fall back to that if possible.
The default value is 120. EDIINT bc.ediint.streamSiz
e
A message size threshold. When reached, it will cause messages to be stored in temporary files on the file system while they are being processed, instead of being stored in memory. Consider setting this property to a low value when processing large messages, since it will help to conserve system memory.
The default value is 5000000. bc.ediint.suppress.f
oldedheader
Enabling this property removes any embedded CRLFs from the content-type header field of the following types of outbound HTTP messages: Signed messages and Message Disposition Notifications (receipts).
The resulting content-type header will be all on one line. This property can be set for a specific trading partner by creating a Boolean property with the following name format: bc.ediint.suppress.foldedheader.<tpName>
Any spaces in the trading partner name should be replaced with underscores (_) when specifying the name of the property.
By default, this property is enabled.
bc.ediint.as2.inbou nd.filename.preser vation
Enable file name preservation for the inbound AS2 Messages. When set to true, all inbound AS2 messages with a content disposition type of
“attachment” will be stored on the file system after unpackaging. Files are stored in the shared directory for BusinessConnect, under a subdirectory for the trading partner, and by date in the following way: If a file name has been specified in the content disposition header, it will be used when storing the message.
If the filename already exists for that trading partner and date, it will be generated based upon the filename specified in the content disposition header and will have the following form:
<specified filename base>_
<TP name>_<GUID>_<inbound file number>.<specified filename extension>
If a file name extension is not specified, none is used.
Note: Various operating systems restrict the characters used in filenames.
Therefore, TIBCO BusinessConnect does not allow use of the following characters in filenames: embedded quotes, <, >, ?, :
Table 22 TIBCO BusinessConnect Server Properties Overview (Sheet 7 of 12) Table
Section Field Explanation / Enter
Activated Protocol Plug-ins and Properties
|
77bc.ediint.as2.outbo und.filename.prese rvation
Enable file name preservation for the outbound AS2 Messages. When set to true, BusinessConnect will try to package all outbound AS2 messages as attachments with file names by including a content disposition header of the following form:
Content Disposition: attachment; filename=specified_filename
The value of specified_filename is taken from the file name specified in the content disposition field of the message INITIATOR.REQUEST.
If the outbound File poller is used to pass messages from the private process to BusinessConnect, the name of the file containing the message from the outbound File poller is used as the value of specified_filename in the content disposition header.
Note: Various operating systems restrict the characters used in file names.
Therefore, TIBCO BusinessConnect does not support the use of the following characters in file names: embedded quotes, <, >, ?, :
bc.ediint.digestAlgo rithmEnabled
Determines whether the AS1 and AS2 transports default to using the SHA1 message digest algorithm or pick up the digest algorithm setting from the Business Agreements/Document Security/Outbound Document Exchange/ Signing Info Settings/Digest Algorithm.
By default, bc.ediint.digestAlgorithmEnabled is false and the AS1 and AS2 handlers will always use SHA1 for the message digest algorithm as recommended by their respective specifications.
DDTP Settings
bc.ib.channel.force.
plain
TIBCO BusinessConnect Gateway Server and TIBCO BusinessConnect Interior Server can use plain HTTP connections for DMZ Data Transfer Protocol (DDTP) data transferring after you enable this property in TIBCO Administrator GUI and set the value of the java.property.bc.ib.channel.force.plain property in all gsengine.tra files to true separately. This implementation can reduce the communication time consumption between Gateway Server and Interior Server when highly performance is required and the data transfer security across the inner firewall is not a big concern.
By default, this property is disabled.
This property is also added to the gsengine.tra file located in the BC_HOME/bin directory in each Gateway Server.
Table 22 TIBCO BusinessConnect Server Properties Overview (Sheet 8 of 12) Table
Section Field Explanation / Enter
TIBCO BusinessConnect Trading Partner Administration 78
|
Chapter 4 System Settingsbc.ib.channel.maxP rocessor
This property applies to Interior Servers, and is used to specify the maximum number of threads that each Interior Server can use to handle DDTP data transferring between Interior Server and Gateway Servers using the data-tunneling. The data streaming can come from Gateway Server, or go to Gateway Server and eventually go to trading partners when trading partners download files using the PartnerExpress, SSHFTP or FTPS service.
The default value of this property is 5. You can increase this value when high volumes or large payloads are processed.
When you set a value for this property, it is good practice that the total value of this property in all Interior Servers is close to the total value of the java.property.gs.webengine.ddtp.maxProcessor property in all Gateway Servers.
Others bc.useFLock Two options are available in the list: File and Database.
In TIBCO BusinessConnect, some functions use locks to achieve synchronization among TIBCO BusinessConnect Servers.
If you install TIBCO BusinessConnect on a Linux platform, it is good practice to use the database-based lock instead of the file-based lock because the file-based lock is not stable.
Note: If you deploy TIBCO BusinessConnect in load balancing mode, you must set this property to the database-based lock.
bc.securityLevel Security Level when connecting to an HTTPS server. Select from menu:
HIGH or LOW. All leaf certificates need to be checked and this value dictates how this will be done. This property is checked only on the client side and has the following values:
• LOW Used when testing with sample certificates. When the value is LOW, the host name authentication is not done.
• HIGH Default setting. BusinessConnect preforms a very strict validation on the remote server certificate to ensure that the host registered with that certificate is the same one receiving the POST: the certificate CN (common name) must match the URL host name.
bc.securityVendor.
sockets
Security vendor for inbound and outbound socket operations. Select SUN, ENTRUST, or IBM.
bc.security.restrict Version
Security level restrict to the specified version or later. Select All, SSLv3, TLSv1, TLSv1.1, or TLSv1.2.
Note: If you select TLS version 1.1 or 1.2, you have to select SUN or IBM as the security vendor for inbound and outbound socket operations.
Table 22 TIBCO BusinessConnect Server Properties Overview (Sheet 9 of 12) Table
Section Field Explanation / Enter
Activated Protocol Plug-ins and Properties
|
79bc.security.sslv2hel lo.enabled
Select this check box to enable SSL agreement authentication between trading partners.
bc.maxAuditLog.E ntriesPerView
Maximum Log Viewer entries per view. You can set this value to control how many rows of data should be returned from the audit/non-repudiation database for viewing.
Note: If this value is set too high, it might consume all the available memory and put the system at risk.
The default value is 300.
bc.repo.fetch.limit This property is used to limit how many configuration items are fetched and displayed initially when you open certain configuration pages. In systems with a large amount of configuration items, such as a large amount of users, participants, or business agreements and other items, the page response time is improved.
The default value of this property is 500.
Because only a limited amount of configuration items are fetched from the configuration store and displayed on the configuration page, you cannot paginate the displayed items outside of the limit. If a large amount of items are stored in the configuration store, you have to use the Search function to fetch the items you want.
Inbox Transport Settings
bc.inbox.sendEmail Send an Email to the Partner on successful Inbox storage when using Inbox Transport as the primary transport.
bc.inbox.notify.payl oad.Timeout
Default time for the Notify transaction payload to reside in Inbox before it is purged (in minutes).
BusinessConnect honors Asynchronous Request timeout when uploading a request to Inbox TIBCO BusinessConnect storage to be retrieved by TIBCO PartnerExpress.
For Notify operations uploaded into the Inbox TIBCO BusinessConnect storage, the timeout value specified here will be used.
The default value of this property is 1440. Table 22 TIBCO BusinessConnect Server Properties Overview (Sheet 10 of 12)
Table
Section Field Explanation / Enter
TIBCO BusinessConnect Trading Partner Administration 80
|
Chapter 4 System Settingsbc.inbox.response.p ayload.Timeout
Default time for the Response transaction payload to reside in Inbox before it is purged (in minutes).
BusinessConnect honors Asynchronous Request timeout when uploading a request to Inbox TIBCO BusinessConnect storage to be retrieved by TIBCO PartnerExpress™.
For Response operations uploaded into the Inbox TIBCO BusinessConnect storage, the timeout value specified here will be used.
The default value of this property is 1440. LDAP
Configuration
bc.ldap.rolebasedn.
attribute
The distinguished name of an LDAP entry that contains role entries. For example, the following information can be a roleBaseDN:
CN=Users,DC=adldap,DC=com
The parts DC=adldap and DC=com are optional for the baseDN entry. the part CN=Users is mandatory, unless a role entry is created in baseDN.
See Adding an Authentication Source on page 66 for more information about User Authentication and LDAP server configuration.
Note: Ensure that an entry is created under the Base DN, which is specified in the Base DN field in the LDAP server configuration, on the LDAP server before you specify a value cn=entry_name for this property. The entry must have the object class organizationalRole on the Open LDAP server or IBM Tivoli Directory LDAP server, Container on the Microsoft Active Directory LDAP server, and nsContainer on the Sun ONE LDAP server.
JMS
Configuration
bc.jms.destination.c ache
A JMS destination cache is created after you enable this property.
By using the cache, TIBCO BusinessConnect Interior Server does not have to discover the JMS destinations every time when it sends messages to a private process by using the JMS transport. This implementation improves the communication performance between Interior Server and the JMS server, and it is effective if the related EMS destinations used by the JMS server are not updated frequently.
By default, this property is enabled.
Table 22 TIBCO BusinessConnect Server Properties Overview (Sheet 11 of 12) Table
Section Field Explanation / Enter
Activated Protocol Plug-ins and Properties
|
81Add a Property
To add a property to any of the listed protocol plug-ins:
1. In the Edit Plug-in Properties: plug-in_name dialog, click Add.
2. In the Property Name field, enter the name for the new property.
Audit Log bc.auditlog.messag eInAsync
This property specifies whether to save transaction messages in audit log asynchronously.
By default, this property is disabled.
Note: With the properties of bc.auditlog.messageInAsync,
bc.auditlog.messageInAsync.maxMessages, bc.auditlog.messageInAsync.maxTotalSize, and bc.auditlog.messageInAsync.threadpool.size, you can save transaction messages in audit logs asynchronously. This function is useful when the message size is large and the database connection is not good, but fast delivery or quick response is required. When using this function, you must be cautious with the system memory consumption because more memory is consumed as a cache to temporarily store messages before the messages are written to the database.
bc.auditlog.messag eInAsync.maxMess ages
This property specifies the maximum number of messages in asynchronous message audit log queue.
The default value of this property is 2000. bc.auditlog.messag
eInAsync.maxTotal Size
This property specifies the maximum size of memory in MB that can be used for asynchronous message audit log.
The default value of this property is 128.
The limit for messages is controlled by both the maxMessage and maxTotalSize properties, the property that first reaches the limit condition takes effect.
bc.auditlog.messag eInAsync.threadpo ol.size
This property specifies the size of thread pool that can be used for consuming the messages stored in memory temporarily and writing the messages to the database.
The default value of this property is 10. You can increase this value if the memory occupied by the messages grows up, however more database writing bandwidth is available.
Table 22 TIBCO BusinessConnect Server Properties Overview (Sheet 12 of 12) Table
Section Field Explanation / Enter
TIBCO BusinessConnect Trading Partner Administration 82
|
Chapter 4 System Settings3. Enter or select information as explained in Table 23.
4. Click Save.
Delete a Property To remove a property:
1. In the screen Edit Plug-in Properties: plug-in_name, click Delete.
2. In the Delete Property dialog, enter the name of the property to be deleted.
3. Click OK.
Table 23 Adding New Property
Field Description
Property Name Type a name for the property (required)
Property Type Select a data type from the list: boolean, string, or integer Description Type a description of the new property in the Description field
You can remove only user defined properties; default properties cannot be removed.
Metadata Type Configuration
|
83Metadata Type Configuration
The functionality in this area is protocol-specific:
• Roles Supported by RosettaNet.
Roles display in the Roles tab for a host and trading partner and the Activity tab in the operations editor.
Roles are explained in TIBCO BusinessConnect RosettaNet Protocol User’s Guide.
• Domains Supported by TIBCO BusinessConnect Services Plug-in, TIBCO BusinessConnect™ RosettaNet Protocol, and TIBCO BusinessConnect™ EDI Protocol powered by Instream®.
Each trading partner involved in the exchange of documents has a domain. Look in the User’s Guides for each of these protocols for more information.
• Partner Classification Codes Supported by RosettaNet. Example: Buyer.
Partner Classification Codes are explained in TIBCO BusinessConnect RosettaNet Protocol User’s Guide.
• Supply Chain Codes Supported by RosettaNet. Example: Electronic Components.
Supply Chain Codes are explained in TIBCO BusinessConnect RosettaNet Protocol User’s Guide.