FIX: A hotfix is available that enables BizTalk Adapter for TIBCO EMS to support ordered message delivery and SSL connections in BizTalk Server 2006 R2 SP1 and BizTalk Server 2009

Ordered Delivery Option

When you set the Ordered Delivery option to True, the messages are expected to be polled from the Tibco server and to be submitted to BizTalk Server. The order in which BizTalk server receive messages is the same as the order in which messages are sent to Tibco server.

Note The messages that have higher priority in the Tibco queue are the messages that are expected to be polled and submitted to BizTalk ahead of the messages that have lower priority. You can change the priority of a message by using the transmitter configuration property of the Message Priority option.

StopPollingOnFailure option

This option is applicable only if the Ordered Delivery option is set to True. This option is used to decide whether to continue or to stop polling when the submission of a message to BizTalk fails. If the StopPollingOnFailure option is set to True and a message is not submitted to BizTalk, the receive port that uses the BizTalk Adapter for TIBCO EMS stops additional polling of the messages from the Tibco server, and then the port is disabled. If the StopPollingOnFailure option is set to False, then the polling is not stopped even if the submission of a message to BizTalk fails. In this case, failed messages are moved to a suspended queue.

Note When the StopPollingOnFailure option is set to False, the messages that cannot be submitted to BizTalk are moved to the suspended queue. This behavior causes a loss of order. Therefore, we recommend that you set this option to True.

UseSSL option

If the UseSSL option is set to False, the adapter connects to the Tibco Server on the TCP Port. If the UseSSL option is set to True, the adapter connects to the Tibco Server on the SSL port.

Note The Tibco Server is configured in the "Server Name" field under the server connection definition section. Both the TCP Port and the SSL Port are configured in the Port number field under the server connection definition section.

SSLTargetHostName option

Make sure that the trusted root certificate of the Tibco server is installed in the Trusted Root Certification Authorities store of the user whose account is configured for the BizTalk host instance.

SSL ClientSubjectDN option

This option is mandatory if two-way SSL is needed. For example, the Tibco server requires the client to present the certificate. The certificate can be enabled or disabled in the ssl_require_client_cert property of the Tibemsd.conf file. This value corresponds to the subject distinguished name of the client certificate. Make sure that the trusted root certificate of the Tibco server is installed in the Trusted Root Certification Authorities store of the user whose account is configured for the BizTalk host instance.

The following is a sample value for this option:

E=client@testcompany.com, CN=client, OU=client Unit, O=Test Company, L=us-english, S=California, C=US

Configuring One-way SSL

On the Tibco server, change the Tibemsd.conf file. To do this, follow these steps:

1. Disable the ssl_require_client_cert property. To do this, change this setting so that it appears as follows:
   ssl_require_client_cert = disable

2. Set the ssl_server_identity property to point to the server certificate, set the ssl_server_key property to use the correct SSL key, and set the ssl_password property to use the correct SSL password. To do this, change these setting so that they appear as follows:
   ssl_server_identity = server.cert.pem
   ssl_server_key = server.key.pem
   ssl_password =<password>
   
   Note Make sure that the .pem files are available in the path that you set.

3. Save the Tibemsd.conf file and start the Tibco EMS server.

On the BizTalk server, install the trusted root certificate of the Tibco server in the Trusted Root Certification Authorities store of the user whose account is configured for the BizTalk host instance. Then, try to connect to the Tibco server by using the Tibco adapter.

Configuring Two-way SSL

On the Tibco server, change the Tibemsd.conf file. To do this, follow these steps:

1. Enable the ssl_require_client_cert property. To do this, change this setting so that it appears as follows:
   ssl_require_client_cert = enable

2. Set the ssl_server_identity property to point to the server certificate, set the ssl_server_key property to use the correct SSL key, and set the ssl_password property to use the correct SSL password. To do this, change these setting so that they appears as follows:
   ssl_server_identity = server.cert.pem
   ssl_server_key = server.key.pem
   ssl_password =<password>
   
   Note Make sure that the .pem files are available in the path that you set.

3. Set the ssl_server_trusted property to point to the root certificate for the CA of the client certificate. To do this, change this setting so that it appears as follows:
   ssl_server_trusted = client.root.cert.pem
   
   Note Make sure that the .pem files are available in the path that you set.

4. Save the Tibemsd.conf file and start the Tibco EMS server

On the BizTalk server, install the trusted root certificate of the Tibco server in the Trusted Root Certification Authorities store of the user whose account is configured for the BizTalk host instance. Install the CA certificate of the client certificate in the Trusted Root Certification Authorities store of the current user. Install the client certificate in the Personal store of the current user. Then, try to connect to the server by using the Tibco adapter.

For BizTalk Server 2006 R2 SP1

The hotfix is included in cumulative update package 3 for BizTalk Server 2006 R2 SP1.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2286501Cumulative update package 3 for BizTalk Server 2006 R2 Service Pack 1

For more information about BizTalk Server 2006 R2 SP1 hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

974563List of Microsoft BizTalk Server hot fixes that are included in BizTalk Server 2006 R2 Service Pack 1

For BizTalk Server 2009

The hotfix that resolves this issue is included in cumulative update package 2 for BizTalk Server 2009.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2497794 Cumulative update package 2 for BizTalk Server 2009

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Microsoft BizTalk Server 2009 and Microsoft BizTalk Adapter for Enterprise Applications (also known as BizTalk LOB Adapter) installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply the hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.