DDTP Settings

bc.ib.channel.forc e.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.

bc.ib.channel.max Processor

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 ⁵. 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.

Table 22 TIBCO BusinessConnect Server Properties Overview (Sheet 9 of 12) Table

Section Field Explanation / Enter

Activated Protocol Plug-ins and Properties

|

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.

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 ³⁰⁰.

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.

Table 22 TIBCO BusinessConnect Server Properties Overview (Sheet 10 of 12) Table

Section Field Explanation / Enter

Inbox Transport Settings

bc.inbox.sendEma il

Send an Email to the Partner on successful Inbox storage when using Inbox Transport as the primary transport.

bc.inbox.notify.pa yload.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 ¹⁴⁴⁰. bc.inbox.response.

payload.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 ¹⁴⁴⁰. LDAP

Configuration

bc.ldap.rolebased n.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 72 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.

Table 22 TIBCO BusinessConnect Server Properties Overview (Sheet 11 of 12) Table

Section Field Explanation / Enter

Activated Protocol Plug-ins and Properties

|

JMS

Configuration

bc.jms.destination .cache

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.

Audit Log bc.auditlog.messa geInAsync

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.messa geInAsync.maxM essages

This property specifies the maximum number of messages in asynchronous message audit log queue.

The default value of this property is ²⁰⁰⁰. bc.auditlog.messa

geInAsync.maxTo talSize

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 ¹²⁸.

The limit for messages is controlled by both the ^maxMessage and maxTotalSize properties, the property that first reaches the limit Table 22 TIBCO BusinessConnect Server Properties Overview (Sheet 12 of 12)

Table

Section Field Explanation / Enter

Add 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.

3. 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.