Does anyone know if BizTalk 2006 MQSeries adapter (server version) supports MQ 7.0 on W2k3? I know R2 does but none of the documentation specifically mentions it.
From a purely WMQ perspective, the answer is "yes." IBM has published a support statement that WMQ Server V7 is compatible with all previous WMQ clients. Assuming the BizTalk 2006 client is either bundling the IBM client or at least is compatible with it, then it should work fine.
Related
I am in a middle of migrating a one classic Azure VM (hosting a web app using Signalr) to an Azure resource manager scale set having multiple VMS with os Windows Server 2016.
Looking at Signalr documentation (https://www.asp.net/signalr/overview/getting-started/supported-platforms) is seems that it support only Windows Server 2012.
I am using Signalr 2.2.0 .
I couldn't find any documentation saying that Signalr is supported on Windows Server 2016.
Does Windows Server 2016 supports Signalr?
Does Windows Server 2016 supports Signalr?
Yes, because you can run .Net 4.5(+) on Server 2016 (I would think this would be obvious). The following documentation was published in 2014, long before 2016 was released, so it's not going to mention future server versions explicitly. It seems the only requirement is the ability to enable Web Sockets.
(for example asp.net 2.0 was released in 2005 and can be run on Server 2016)
https://www.asp.net/signalr/overview/getting-started/supported-platforms
Excerpt:
Supported server operating systems
The SignalR server component can be hosted in the following server or client operating systems. Note that for SignalR to use WebSockets, Windows Server 2012 or Windows 8 is required (WebSocket can be used on Windows Azure Web Sites, as long as the site's .NET framework version is set to 4.5, and Web Sockets is enabled in the site's Configuration page).
Windows Server 2012
Windows Server 2008 r2
Windows 8
Windows 7
Windows Azure
Supported server .NET Framework version
SignalR 2 is only supported on .NET Famework 4.5. See the Recommended Updates section for updates that enhance reliability, compatibility, stability, and performance.
Supported server IIS versions
When SignalR is hosted in IIS, the following versions are supported. Note that if a client operating system is used, such as for development (Windows 8 or Windows 7), full versions of IIS or Cassini should not be used, since there will be a limit of 10 simultaneous connections imposed, which will be reached very quickly since connections are transient, frequently re-established, and are not disposed immediately upon no longer being used. IIS Express should be used on client operating systems.
Also note that for SignalR to use WebSocket, IIS 8 or IIS 8 Express must be used, the server must be using Windows 8, Windows Server 2012, or later, and WebSocket must be enabled in IIS. For information on how to enable WebSocket in IIS, see IIS 8.0 WebSocket Protocol Support.
IIS 8 or IIS 8 Express.
IIS 7 and 7.5. Support for extensionless URLs is required.
IIS must be running in integrated mode; classic mode is not supported. Message delays of up to 30 seconds may be experienced if IIS is run in classic mode using the Server-Sent Events transport.
The hosting application must be running in full trust mode.
I'm unable to find anywhere online where it states that BizTalk Server 2010 is supported/not supported fully by Windows 10.
No, not even BizTalk 2013 R2 is supported on Windows 10 as can be seen at Summary of 64-bit support, operating systems and SQL Server versions supported by BizTalk Server and also
Hardware and Software Requirements for BizTalk Server 2013 and 2013 R2 as it is not listed on either page as a supported operating system.
There is a related question about BizTalk 2013 R2 and windows 10 called BizTalk Server Configuration failing to create group. The conclusion for that is, yes you can run BizTalk 2013 R2 on Windows 10, but as per a answer and comments there it probably will not be supported by Microsoft for a Production environment and could break with updates and patches applied to the operating system.
No, not directly but that shouldn't matter because running BizTalk Server on any client OS is never the best option.
Yes, you can run BizTalk Server 2010 in a Windows Server 2008 R2 VM using Client Hyper-V. You need Windows 10 Professional or Enterprise but this would be the best way to do it even if the client OS supported it directly.
I'm trying to configure a BizTalk server in BizTalk Server 2013 R2. I'm using Windows 10 and a local DB.
I can create the Enterprise SSO and the Business Rule Engine but not the BizTalk Server Group and the BizTalk Runtime.
It gives me the following error:
Failed to read "Software\Microsoft\BizTalk Server\3.0\Administration" from the registry.
The network path was not found.
I've tried everything I could imagine, any ideas as why I can't create the group?
EDIT: After trying everything I could imagine, the problem was in the name of my machine that was too big. Because of that, BizTalk could not write in the registry.
BizTalk Server 2013 R2 is not supported on Windows 10.
You can look this up in the official BizTalk Server documentation, which you can find here: https://msdn.microsoft.com/en-us/library/jj248697.aspx
Supported for BizTalk Server 2013 R2 are: Windows Server 2012 R2, Windows Server 2012, Windows 8.1 and Windows 7 SP1.
Windows 10 is not supported.
After trying everything I've searched on the web, I finally managed to solved the problem.
Because my machine name was too long (15 characters), BizTalk could not edit the registry. After changing it to 4 characters long, I solved the problem and I was able configure the server.
Does the BizTalk 2010 BtsAsmExt.dll work with Server 2008 R2?
Followed the instructions at MSDN but the screen shots look to be Windows XP, as it talking about "My Computer"
The install by regsvr32 BtsAsmExt.dll worked Ok
Probably not. While BTAV is still shipped, it suffers from two significant deficiencies:
It is not supported on 64-bit systems.
It does not support the .Net 4.0 GAC.
BizTalk Server 2010 is .Net 4.0 based so because of item 2, any BizTalk 2010 Assemblies you build/deploy would not be visible to BTAV.
Is BizTalk Server 2013 compatible with the Dynamics AX 2009 AIF BizTalk Adapter?
I've searched but can't find any information to say either way.
I found that BizTalk Server 2010 is compatible with AX2009 SP1 RU7: http://blogs.msdn.com/b/emeadaxsupport/archive/2011/09/29/microsoft-biztalk-server-2010-passes-compatibility-testing-with-microsoft-dynamics-ax-2009-sp1.aspx
(Apologies if this is not the correct site for this question, as it's not directly programming related; however I couldn't find another Stack Exchange site which looked more suitable).
I did not find anything newer announced at Partner Source.
This does not imply that BizTalk 2013 is not compatible, only that it is not a tested scenario, and that if you choose to use, it is your own risk.
Unfortunately, the BizTalk+AX story has alwasy been a little mysterious in terms of what exactly is 'supported' and not.
However, the Adapter interface is unchanged from BizTalk Server 2010 to BizTalk Server 2013 so the '2010' Adapter should run without issue in 2013.
Worst case, PSS will only offer 'best effort' support, though it's highly unlikely you'd ever need it.