How should I prepare a roadmap to conduct a training on biztalk administration to train people going to work on a support project?

What and how much in detail to cover?

• Edited by ssimon11 Monday, March 02, 2015 10:07 PM

Training Resources for BizTalk Administrators Technet article published by Sandro covers all what you require to conduct training sessions on BizTalk Administration.

Rachit

First define/understand what level of administrative knowledge your people need to have for your support project. For example if your people are going to do first-level support then a operator-level access and admin knowledge may be enough. Getting into more detail about the database table details like Spool table may not require for them.

Try to map the level of support your people are going to do to the level of administration knowledge/training they need.

For example, a high-level traning could invole topics as following:

Introduction to BizTalk Server What Is BizTalk Server?

• Whats New in BizTalk Server 2010?
• Examining the BizTalk Server Architecture
• BizTalk Server Administration Tools and Tasks

Deploying BizTalk Applications

• Introduction to BizTalk Applications
• Deploying BizTalk Applications
• Binding BizTalk Applications
• Managing MSI Packages

Managing BizTalk Hosts and Applications

• Introduction to BizTalk Adapters
• Configuring BizTalk Endpoints
• Configuring Hosts and Host Instances

Tracking and Troubleshooting a BizTalk Application

• About Troubleshooting Tools -Admin console, eventlog etc

Evaluating the Performance of a BizTalk Environment

• Performance Testing Performance Tuning

For advanced support group, your road map could contain things like following:

Introduction to BizTalk Server

• What Is BizTalk Server?
• The BizTalk Server Development Environment

Deploying BizTalk Applications

• Deployment Fundamentals
• Deploying Manually
• Working with Bindings Files
• Deploying using MSI Packages

Configuring BizTalk Applications

• The BizTalk Publish Subscribe Model
• Introduction to Adapters
• Creating Receive and Send Ports
• Logical Port Bindings
• Lab: Configuring a BizTalk Application

Tracking and Troubleshooting BizTalk Applications

• Troubleshooting using the Group Hub
• Lab: Troubleshooting BizTalk Server Applications
• Enabling Tracking
• Viewing Tracked Information

Setting up BizTalk Environments

• Planning a BizTalk Installation
• Pre-Installation Tasks
• Installing and Configuring BizTalk Server
• Post Configuration Tasks

Creating Highly-Available BizTalk Environments

• BizTalk Hosts and Host Instances
• Creating Hosts and Host Instances
• Isolated Hosts and Web Services
• Lab: Creating Hosts and Host Instances

Securing Passwords using ESSO

• ESSO Fundamentals

Business Activity Monitoring for Administrators

• BAM Fundamentals
• Administration of BAM Components

Business Rules Engine for Administrators

• BRE Fundamentals
• BRE Administration Tasks

BizTalk Message Security

• Securing Messages using Pipelines
• Encrypting and Decrypting Messages
• Applying and Verifying Digital Signatures

Business to Business Integration using EDI

• Role-Based Integration
• What is EDI?
• Enabling EDI-Based Messaging

3rd Party Utilities

• BizTalk Server Community Tools, BizTalk 360, Codeplex, Messagebox viwer

The above road map details are referenced from : http://www.quicklearn.com/class.aspx?class=BTAF

Hi,

I want to add a little bit more in M.R. Ashwin answer that its totally depends on your project means how complex and large project your company have.
To administrating a BizTalk application not a easy task comparative to development. Well I do both administration and development and truely i found administration take more effort because sometime crucial error occur and its difficult to find out the actual cause of the error if solution have IDOC/EDI/DB/complex orchestration/Custom Pipeline.

So I think,first u should give some POC development task to your people so that they could understand the BizTalk flow and that time they will go through the basic error occur in BizTalk and its solutions.
And last don't forget to appreciate your Support team because those keep your application working not developers after developed.