Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

BizTalk 2009 : Host Integration Server 2009 - BizTalk Adapter for Host Applications

- How To Install Windows Server 2012 On VirtualBox
- How To Bypass Torrent Connection Blocking By Your ISP
- How To Install Actual Facebook App On Kindle Fire
6/14/2011 9:09:14 AM
BizTalk Adapter for Host Applications (BAHA) is a subset of the BizTalk Adapter for Host Systems. BAHA provides BizTalk Server with the extensibility needed to access legacy systems. It leverages the Transaction Integrator capabilities by supporting Windows-initiated processing scenarios and therefore supports all the programming models for mainframe and AS/400 access. From a BizTalk configuration perspective, it provides a solicit-response adapter that targets remote environments defined in the TI Manager. Every time the BAHA receives an XML instance to be sent to a mainframe, the BAHA Runtime compares the received instance against its corresponding BizTalk schema and transfers the data to Transaction Integrator. From there, Transaction Integrator is responsible for sending the data to the mainframe, receiving the response, and then returning the data to the BAHA.

The BAHA Runtime maps the mainframe datatypes and data back to .NET datatypes, creates the XML response document, and passes the data back to the Messagebox through its corresponding port. From a send port configuration perspective, the Host Type property allows you to select a TI remote environment—your mainframe region. The Allow Advanced Override and Allow Security Overrides properties allow you to manipulate the TI Client Context object. The Persistent Connections property allows you to create persistent connections when working with batches of messages. We recommend the use of persistent connections to improve the performance and also to maintain the state in the server. The SSO Affiliate Application property allows you to use either a specific SSO Affiliate Application or the settings of the TI remote environment selected in the Host Type property. Figure 1 shows the available properties for the BAHA solicit-response port.

Figure 1. BizTalk Adapter for HostApps Transport Properties window

As we pointed out earlier, BAHA relies on the Transaction Integrator to access legacy systems. The setting that you need to set up in the Transaction Integrator object to generate a BizTalk schema is its Type Restrictions property. You have to set its value to BizTalk Adapter for Host Applications. The purpose of this Type Restriction is to prevent the TI client application from using conventions unsupported by BizTalk Server. However, it doesn't stop the client application from calling the assembly directly from any other Windows application. Figure 2 shows the TI Assembly Properties window highlighting the type restrictions available.

Figure 2. Transaction Integrator Assembly properties window

Once you have saved your TI changes in the Visual Studio project, an XML Schema Definition (XSD) file with the definitions for the request and response messages that BAHA will use will be generated. Afterward, you will need to import the XSD file into your BizTalk Server project. By doing so, when you deploy your BizTalk application, you will have the new BizTalk schema available in the schemas directory in the BizTalk application. One of the benefits of this approach is that you if you need to populate fields in a TI object that has a large amount of fields, you can use a BizTalk Server map and populate the input fields easily from an orchestration. Nonetheless, I recommend you ensure that you handle the TI object versions properly, so the XSD definitions you use in your BizTalk Server project always reflects the latest changes/updates you may have performed to your TI object definition and deployed to TI Manager. Figure 3 shows a sample TI XSD file imported in a BizTalk Server project.

Figure 4 shows two BAHA nodes connected to an enterprise SNA Gateway. Remember that every BAHA node should have installed and configured Transaction Integrator to access the SNA Gateway. A SQL Server is required to work with Transaction Integrator, so port 1433 should be opened, and remote access should be enabled as well.

Figure 3. BizTalk schema definition for a TI object

Figure 4. BAHA systems providing mainframe transactional access
Other -----------------
- BizTalk 2009 : Host Integration Server 2009 - Session Integrator
- SQL Server 2008 : Database Mail (part 2) - Configuring, Sending, Cleanup Procedures Database Mail Using T-SQL
- SQL Server 2008 : Database Mail (part 1) - Database Mail Configuration Wizard
- SQL Server 2008 : Monitoring Your Server - Using Server-Side Tracing
- BizTalk 2009 : Host Integration Server 2009 - Security
- Microsoft Dynamics CRM 2011 : Attaching Files to Accounts and Contacts
- Upgrading to SharePoint 2010 : Performing Post-Upgrade Configurations
- Upgrading to SharePoint 2010 : Performing an In-Place Upgrade (part 2) - Configuring the In-Place Upgrade
- Upgrading to SharePoint 2010 : Performing an In-Place Upgrade (part 1) - Installing the In-Place Upgrade
- Upgrading to SharePoint 2010 : Performing a Database Attach Upgrade
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
- First look: Apple Watch

- 3 Tips for Maintaining Your Cell Phone Battery (part 1)

- 3 Tips for Maintaining Your Cell Phone Battery (part 2)
programming4us programming4us
Popular tags
Microsoft Access Microsoft Excel Microsoft OneNote Microsoft PowerPoint Microsoft Project Microsoft Visio Microsoft Word Active Directory Biztalk Exchange Server Microsoft LynC Server Microsoft Dynamic Sharepoint Sql Server Windows Server 2008 Windows Server 2012 Windows 7 Windows 8 windows Phone 7 windows Phone 8
programming4us programming4us
 
programming4us
Natural Miscarriage
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Game Trailer