Table 20 lists plug-in properties for the TIBCO BusinessConnect server.
|
|
|
|
|
|
|
|
|
|
|
|
Note: This property cannot be changed dynamically: the TIBCO BusinessConnect server has to be restarted for this property to take effect.
|
|
|
|
|
|
Note: When session caching for outgoing HTTPS/FTPS transports is disabled, performance can be significantly degraded and this should be done only if there are known problems with the involved third party server application's handling of SSL session caching.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This property along with the property bc.tx.resend.pollingInterval makes it possible to fine tune resend behavior by limiting the maximum number of messages to be processed in one polling cycle.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The FTP get command terminates if it does not complete within the timeout period.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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, <, >, ?, :
|
|
|
The value of specified_filename is taken from the file name specified in the content disposition field of the message INITIATOR.REQUEST.
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, <, >, ?, :
|
|
|
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.
|
|
|
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 high performance is required and the data transfer security across the inner firewall is not a big concern.
This property is also added to the gsengine.tra file located in the BC_HOME/bin directory in each Gateway Server.
|
|
|
The default value of this property is 5. You can increase this value when high volumes or large payloads are processed.
|
|
|
Note: If you deploy TIBCO BusinessConnect in load balancing mode, you must set this property to the database-based lock.
|
|
|
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 performs 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.
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
Note: If this value is set too high, it might consume all the available memory and put the system at risk.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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 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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
The limit for messages is controlled by both the maxMessage and maxTotalSize properties, the property that first reaches the limit condition takes effect.
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note: This field is applicable only for TCM and PX.
|
|
|
Note: This field is applicable only for TCM and PX.
|