BizTalk Summit 2015

Hello BizTalk & Integration Fans,

If you are really excited about the Microsoft Integration Stack and of course Microsoft BizTalk Server, you should absolutely attend the BizTalk Summit 2015 !

Registration : http://www.biztalk360.com/Events/BizTalk-Summit-2015-London/

BizTalk Server vNext

BizTalk Server is Microsoft’s integration and connectivity server and is one of the most deployed integration servers in the industry. BizTalk Server 2010 was released just over a year ago.

BizTalk Server 2010 R2 will focus on three primary themes:

• Platform Support – Supporting new and current server and development platforms
• Improved B2B – Aligning with industry standards and continuing to invest in performance improvements
• Ready for the Cloud – Enabling customers to take advantage of the benefits of cloud computing

BizTalk Server 2010 R2 will be delivered approximately 6 months following the release of Windows Server 8. Release timing for Windows Server 8 is yet to be announced and will be disclosed by the Windows Server team in the future.

In addition to the investments they are making in BizTalk Server 2010 R2, they will continue the tradition of providing regular cumulative updates on a quarterly basis. These include updates to comply with Line-Of-Business (LOB) systems, schema changes, accelerator certifications, and bug fixes.

They believe that with this release we continue to deliver a mature, reliable and stable integration server that honors the trust of the thousands of customers who run their mission critical business processes on BizTalk Server.

Below is the detailed view of the features we are releasing: (Source : http://blogs.msdn.com/b/biztalk_server_team_blog/archive/2011/12/08/biztalk-server-2010-r2.aspx)

Platform Support	Improved B2B	Ready for the Cloud
New Platforms and Infrastructure Windows Server 8* SQL Server 2012* Increased Developer and IT Productivity Visual Studio 11* and Windows 8* to develop solutions In-place migration from BizTalk Server 2010 Extended Platform Integration DB2 client connectivity to SQL Server, conversion of commands to T-SQL, migration of packages to stored procedures Adapter connectivity to new data sources, including IBM Informix V11 and IBM IMS/DB V11	Agile Alignment to Industry Standards Regular updates to schemas, accelerators certifications and adapters. Highlights include: Healthcare: HIPPA 5010 extensions: 2777CA, 999, HL7 2.5.1 Finance: SWIFT SRG 2011 support, SWIFT SRG 2012, SWIFTNet 7.0 (new messaging platform) Improved Performance and Scalability HL7 MLLP adapter performance improvements Better performance with ordered send ports Enhanced scale out configuration with multiple hosts Expanded adapter options for faster batch processing	Extend on-premises solutions to the cloud Easily extend your on-premises BizTalk Server solution to the cloud in a secure manner Tighter integration of on-premises BizTalk Server applications with Windows Azure Service Bus Improved Licensing Adjustments to licensing that are geared towards cloud hosting, including: Purchase from a hoster on a monthly basis (SPLA) Register your existing license with a hoster (License Mobility)

Using IBM MQ Transactional Client with BizTalk

In order to get everything working correctly to use IBM MQ Transactional together with BizTalk, you need to purchase the IBM MQ Transactional Client. Please always download the latest version of the client.

After you install the IBM WebSphere MQ Extended Transactional Client on your BizTalk Server computer, the following additional configuration steps are necessary before you can implement transactional messaging with the BizTalk Adapter for WebSphere MQ.

• In the WebSphere MQ Server environment, give your Network Service account appropriate permissions, as described in the IBM Technote article 1223479. For security reasons, it is strongly recommended that you use the “Security Exit” so that you do not have to add “Network Service” account into the MQM group.
• On your BizTalk Server computer, add the MQSeries XA dll to the MSDTC registry. To the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\XADLL, add the string value amqmtsxatmc.dll in the Name column and add its path to the Data column. Provide the path in the form <WebSphere MQ Client installation folder>\bin\amqmtsxatmc.dll; for example, C:\Program Files\IBM\WebSphere MQ\bin\amqmtsxatmc.dll.
• On your BizTalk Server computer, if you are using WebSphere MQ 5.3, give your Network Service account read/write access to the @SYSTEM folder, contained in <WebSphere MQ Client installation folder>\qmgrs\@SYSTEM. (You do not have to do this if you are using WebSphere MQ 6.0 /7.0.)
• Make sure that MSDTC is enabled on the computer on which BizTalk Server is installed and that security is configured as described in the following procedure:

To enable MSDTC and configure security

---

1. Click Start, point to Programs, point to Administrative Tools, and then click Component Services.
2. In the Console Root of the Component Services Console, expand Component Services.
3. Expand Computers.
4. Right-click My Computer, and then click Start MSDTC.
5. Right-click My Computer, and then click Properties.
6. Click the MSDTC tab.
7. Under Transaction Configuration, click Security Configuration.
8. Under Security Settings, select the Network DTC Access and Enable XA Transactions check boxes.
9. Click OK.

If you are using Sysplex distributor with queue sharing groups, don’t forget to activate the GROUPUR attribute on your MQ Server. The GROUPUR attribute allows XA client applications to have any in-doubt transaction recovery that may be required, performed on any member of the QSG.If an XA client application connects to a queue-sharing group (QSG) through a Sysplex it cannot guarantee which specific queue manager it connects to. Use of the GROUPUR attribute by queue managers within the QSG can enable any in-doubt transaction recovery that may be necessary to occur on any member of the QSG. Even if the queue manager to which the application was initially connected is not available, transaction recovery can take place.This feature frees the XA client application from any dependency on specific members of the QSG and thus extends the availability of the queue manager. The QSG appears to the transactional application as a single entity providing all the WebSphere MQ features and without a single queue manager point of failure.