BizTalk 2009 MQ Series Adepater with WebSphere MQ 7.0 - biztalk

We are in the process of upgrading IBM Websphere MQ Series from V6.x to V7.x.
Currently our BizTalk application servers are integrated to IBM Websphere MQSeries server to read messages from remote queue through BizTalk 2009 MQSeries adapter.
We would like to know whether our current BizTalk 2009 MQSeries adapter needs any updates to connect to new 7.x version of IBM Websphere MQ Series server.
Below are our BizTalk and IBM MQ series Server configurations
BizTalk 2009 (Windows 2003 64 bit) with MQ Series Adapter.
IBM Websphere MQSeries Server (V6.0.2.7 with Windows 2003 32 bit)

In the Infocenter for each of the releases, there is a section on version-to-version changes. There are several related to Windows. Please see the Infocenter for the appropriate version:
V6.0 to V7.5 Changes
V6.0 to V7.1 Changes
There is a V7.0 Infocenter but at this point, everyone should be migrating to V7.5 preferably, or V7.1 at the earliest, due to the security enhancements and other features.

Related

in corda enterprise- can we use IBM MQ for standalone artemis server?

I have gone through https://docs.r3.com/en/platform/corda/4.7/enterprise/node/corda-firewall-component.html#standalone-artemis-server
but just need to check will IBM MQ work?

Unable to connect to BizTalk group after enabling TLS 1.2 and disabling lower versions of SSL and TLS

After diabling lower security protocol versions SSL3.0, TLS1.0, TLS1.1 and enabling TLS 1.2, I am not able to connect to BizTalk group or use BizTalk server. The BizTalk server version I am using is 2013R2. Following is the error:
An attempt to connect to "BizTalkMgmtDb" SQL Server database on server "XXXXXX" failed.
Internal Error from OLEDB provider: "[DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security error."
Also when I enable TLS 1.2 without disabling the lower versions I don't see any problems and everything seems working fine
Please suggest what can be done to make the server compatible while disabling lower versions
You need to install CU 8 and and also the prerequisite SQL Server 2012 Native Client version 11 as per Support for TLS 1.2 protocol in BizTalk Server
See also BizTalk: Configure TLS 1.2 on BizTalk Server
For BizTalk 2013 R2 we also installed .Net 4.6 and updated the BAM connection strings to use the SQL Server Native Client 11.
You will also have to ensure that any other endpoints that BizTalk communicates with or that communicates with BizTalk is capable of TLS 1.2, for anything using either HTTPS, FTPS or SQL.
So any SQL server you connect to also need to have SQL Server 2012 Native Client version 11 or above, and .NET 4.5 or greater.
Are you added this key on regedit?
Going to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319
then Add--> New DWORD --> SchUseStrongCrypto with value 1
Needing to do same operation on HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0.30319

Receive messages from IBM Websphere MQ using MQseries adapter in BizTalk 2016

I need to connect to IBM WebSphere MQ using BizTalk 2016.
Can this be done using out of the box MQSeries Adapter? Do we need anything else to get this working (For example IBM Websphere MQ client) or only out of the box MQSeries Adapter is enough?
I have read some document that we have to install the Adapter for WebSphere MQ which ships with HIS. Why do we need this?
If this can be achieved with both out of the box MQSeries Adapter and Adapter for WebSphere MQ which ships with HIS then what's the advantage or disadvantage of one with others.
IBM MQSeries product has been discontinued by IBM. MQSeries adapter in BizTalk is meant for MQSeries specifically. If you are looking to connect to IBM MQ recent versions, you need to install HIS. This gives you MQSC adapter and support for latest MQ version. With latest HIS, you have option to use IBM MQ client or Microsoft Client (built into HIS) to connect to IBM MQ.
IBM MQ, WebSphere MQ, and MQSeries product READMEs

TLS version support for BizTalk 2016

How can I check on which TLS version our BizTalk 2016 server is running
I want to know if TLS1.2 is not enabled how can I enable the same on BizTalk 2016 server.
As BizTalk 2016 is on .Net 4.6 this tries to use TLS 1.2 first but falls back to TLS 1.1 & TLS 1.0 unless they are disabled.
MS16-065: Description of the TLS/SSL protocol information disclosure vulnerability (CVE-2016-0149): May 10, 2016
Note The .NET Framework 4.6 and later versions use TLS 1.2, TLS 1.1, and TLS 1.0 as the protocol defaults. This is discussed in the Microsoft Security Advisory 2960358 topic on the Microsoft TechNet website.
If you want to make BizTalk use TLS 1.2 exclusively you need to make sure you have either Feature Pack 2 or Feature Pack 3 (I would recommend the latest always), or if not installing feature packs, install CU 5 for BizTalk 2016. You also need to ensure that any system BizTalk connects to, including the BizTalk database server support TLS 1.2
Note there is a prerequisite:
SQL Server 2012 Native Client version 11 should be installed on all BizTalk Server systems before you apply this update. If the SQL Native Client is not installed before you apply cumulative update, the installation may not complete.
Both of those articles then link you to Support for TLS 1.2 protocol in BizTalk Server and also links leading to MS16-065: Description of the TLS/SSL protocol information disclosure vulnerability (CVE-2016-0149): May 10, 2016

connection string for classic asp application using odbc 11 for sql server

We have a classic asp application, we lost connection with the database. In application server we are able to connect to database only through odbc driver 11 for sql server. Have tried other native client drivers to establish connection which remained unsuccessful. The only supported driver is odbc 11 for sql server.
Have tried following connection strings -
ODBC Driver 11 for SQL Server:
{"Driver={ODBC Driver 11 for SQL Server }; Data Source =servername; Initial Catalog= dbname; Uid=username ; Pwd=password; "}
DSN:
{" DSN=dsnname;Uid=username ; Pwd=password; Database=dbname"}
Still unable to establish connection.
Can you please suggest the connection strings for odbc driver 11 for sql server?
The is an MS fix for these symtoms here https://blogs.msdn.microsoft.com/sqlreleaseservices/tls-1-2-support-for-sql-server-2008-2008-r2-2012-and-2014/
Issue described as below. The list of items fixed includes SQL Native client and ODBC client.
SQL Server Management Studio (SSMS), Report Server, and Report Manager don’t connect to the database engine after you apply the fix for SQL Server 2008, 2008 R2, 2012, or 2014. Report Server and Report Manager fail and return the following error message:
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable)
This issue occurs because SSMS, Report Manager, and Reporting Services Configuration Manager use ADO.NET, and ADO.NET support for TLS 1.2 is available only in the .NET Framework 4.6. For earlier versions of the .NET Framework, you have to apply a Windows update so that ADO.NET can support TLS 1.2 communications for the client. The Windows updates that enable TLS 1.2 support in earlier versions of .NET framework are listed in the table in the “How to know whether you need this update” section of KB3135244.
Found as to[ Google hit searching for https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=oledb+tls1.2 - there are many more interesting-looking hits in the top ten there that should get you going.
Please come back and self-answer if this solves your issue and there were any other peculiar or unexpected mods you had to make.

Resources