Mapper

Data Analysis – BizTalk Mapper
www.alliedc.com www.
BizTalk Mapper
Allied Consultants
Stability: Dev | QA | Prod
Author: Muhammad Omer
Ref. Number:
Confidentiality Statement
ALL INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON THE
BASIS OF STRICT CONFIDENTIALITY AND IS GOVERNED BY THE
AGREEMENTS BETWEEN THE TWO PARTIES. IT MUST NOT BE DISCLOSED
IN WHOLE OR IN PART TO ANY OTHER PARTY AT ANY TIME WITHOUT THE
PRIOR CONSENT AND AUTHORITY IN WRITING FROM ALLIED CONSULTANTS
Process Analysis – Human Workflows Page 1 of 13
Copyright ã Allied Consultants, 2014 All rights reserved. Proprietary and Confidential.

Document Version and Control
Review History
Name Date
Version Control
Version Date Change Summary Updated by
Distribution
Version Date Parties

1. Table of Contents
1. TABLE OF CONTENTS...........................................................................................................................3
2. IDEAS..........................................................................................................................................................4
3. OVERVIEW...............................................................................................................................................4
4. VOCABULARY.........................................................................................................................................5
4.1 PRODUCT SPECIFIC (BIZTALK).........................................................................................................5
4.2 GENERIC ACRONYMS AND TERMINOLOGY.........................................................................................5
5. ANALYSIS .................................................................................................................................................6
6. PATTERNS OF THE DOMAIN..............................................................................................................6
7. TASKS.........................................................................................................................................................7
PRODUCT SPECIFIC AREA.....................................................................................................................8
8. GOOD TO HAVE FEATURES IN THE PRODUCT............................................................................8
9. HOW TO:....................................................................................................................................................9
9.1 GET A SAMPLE RUNNING..................................................................................................................9
9.1.1 Comments on Sample:....................................................................................................................9
9.2 PERFORM LOGGING AND EXCEPTION HANDLING...............................................................................9
9.3 HOW TO DEPLOY IT AUTOMATICALLY...............................................................................................9
9.4 RUNNING MAPS FROM EXTERNAL APPLICATIONS................................................................................9
10. HOW IT WORKS .................................................................................................................................10
11. BEST PRACTICES................................................................................................................................10
12. USEFUL REFERENCES......................................................................................................................11
13. USEFUL TOOLS...................................................................................................................................11
14. COMMON PROBLEMS.......................................................................................................................11
15. TODO/ NOT COVERED......................................................................................................................12
APPENDIX A: PLACEMENT OF INFORMATION ARCHITECTURE AS A COMPANY’S
STRATEGY..................................................................................................................................................13

2. Ideas
- Try and make a table out of every two pieces of information you feel are connected. This
tends to bring structure to thought.
- Imagine someone with no knowledge of your area is trying to become an expert by
reading this document. This will serve as a reference for when you revisit this topic after
a few months.
- Separate documents if the area is too large to fit reasonably in a document. Too large a
document is worse than one that is too small.
- Design the document so that someone looking at the “Document Map” can browse to his
required information easily. Use the outlining toolbar.
-
3. Overview
<<Mention which product areas you are covering in this document >> e.g. EDI, Flat files…

4. Vocabulary
<<What should one say to sounds like an expert. i.e. talk the talk>>
<<Fancy words you can think of>>
4.1 Product Specific (BizTalk)
Term Context Description
4.2 Generic Acronyms and terminology
Term Context Description
Semantic
Integration
Dissonance
Semantic
Information
Architecture
Area of architecture dealing with the analysis and design of
complicated information in EAI scenarios
Data Semantics Semantics captures the formal meaning of data. It is achieved
by mapping (or rationalizing) the data’s schema to the
Information Model.
Information
Model
A study of what exists in the enterprise. An ontology of the data.

5. Analysis
- Turn data into information by explicitly capturing the meaning and context of each data
element (Enterprise wide IT analysis)
- Semantic information architecture – core principles:
o Metadata – Know your data (Asset location, usage, origin, relationships to other
asets, rules associated with it, ownership
o Information Model – Know your business (See above)
o Data semantics – Understand your data
- Value preposition of Information Analysis includes (Higher quality BI [unambiguous,
valid, and consistent], Business agility, and Lower/more predictable IT costs.
- Analysis Methodology:
o Gather requirements > Catalog Metadata > Construct Information Model > Map
to Information Model (Rationalize) > Publish to relevant stakeholders > Utilize in
ongoing projects
o
<Consider making a template Excel out of this>
-
6. Patterns of the domain
<< Might want to go into how these are implemented. You might want to refer to a separate
document for this >>

7. Tasks
Task Name Input Document
(Embed it if needed)
Output
(Sample if
needed)
Likelihood of
occurrence
Simple Mapping
- Try to identify common tasks you think will be involved in a typical project in this area.
- Task
o Input required: Based on these the requirement gatherer will ensure he has all
the information that is needed to perform this task.
o Output of the task: Schema xsd…, orchestration odx…
- Be explicit. Try to make templates for the input you require. A good template would be
one which takes the minimum information from the user and derives the most from it.

Product Specific Area
8. Good to have features in the Product
Feature Description
Grouping of Shapes Grouping of functoids in the map
Connection between pages Ability to connect wires between pages of a map
<<add columns if you like>>

9. How to:
9.1 Get a sample running
1. <SDK Sample is pretty good>
9.1.1 Comments on Sample:
- Infopath sample is good for high level experience but hard to understand what is
going on underneath.
- Invocation through code helps more in terms of understand the underlying
process
9.2 Perform Logging and Exception handling
- Use the Testing Utility
- Custom Functoids
- Inline Functoids
- XSLT??
- Possible Exceptions
9.3 How to deploy it automatically
<<e.g. from a script or a setup wizard>>
9.4 Running maps from external applications

10. How it works
- Maps run top to bottom (From the input schema), left to right (in terms of
dependencies).
- If a functoids output is connected to two nodes in a target schema, the functoids
is executed TWICE!
- Mapper is DOM based. Limit the size of the input documents
-
11. Best Practices
1. Use the input template to gather requirements!!!!!
2. Try to identify independent sections in the mapping rules. Place each one in a separate
tab page. This helps greatly in large maps.
3. Use the Custom scripting functoid’s “label” property to keep a name or signature of the
method it is calling
4. Try to identify stages within the map.
5. Copy the rule description on top of any code that you write in a custom script.

12. Useful References
Make sure you have the latest SDK and documentation from the MS website:
Address Comments
Semantic
Information
Architecture
http://knowledgemanagement.ittoolbox.co
m/pub/ZS050903.pdf
Good article on the
architectural significance of
this work.
13. Useful Tools
Tool name Useful For Download Link Rate it
14. Common Problems
Symptoms Description Cause Resolution
Moving shapes is
dangerous as it is
very easy to get
OOTB functoids error
How is that done?
handling
Input = Repeating
node but one record
sent. Output = single
node… any functoids
connecting the two
are called twice, once
with correct
parameters once with
“”!!

15. TODO/ Not covered
<<Areas that should be explored to understand the area completely but are not covered in the
document>>
Area Reason for not covering it

Appendix A: Placement of Information Architecture as a
company’s strategy.

Mapper

Recommended

Recommended

More Related Content

Similar to Mapper

Similar to Mapper (20)

More from Allied Consultants

More from Allied Consultants (20)

Recently uploaded

Recently uploaded (20)

Mapper