Mapper

Data Analysis – BizTalk Mapperwww.alliedc.comwww.

BizTalk Mapper

Allied Consultants

Stability: Dev | QA | ProdAuthor: 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 of 14Copyright ã 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)....................................................................................................54.2 GENERIC ACRONYMS AND TERMINOLOGY...................................................................................5

5. PATTERNS OF THE DOMAIN....................................................................................................6

6. TASKS...............................................................................ERROR! BOOKMARK NOT DEFINED.

7. PRODUCT SPECIFIC AREA........................................................................................................8

7.1 COMPONENTS OF A WORKFLOW............................................ERROR! BOOKMARK NOT DEFINED.7.2 ACTIONS..............................................................................ERROR! BOOKMARK NOT DEFINED.7.3 TASKS..................................................................................ERROR! BOOKMARK NOT DEFINED.7.4 WORKFLOW GUIDANCE........................................................ERROR! BOOKMARK NOT DEFINED.7.5 WORKFLOW MONITORING....................................................ERROR! BOOKMARK NOT DEFINED.

7.5.1 Business Monitoring through BAM (not very appropriate for monitoring the workflow as such) Error! Bookmark not defined.7.5.2 Workflow monitoring............................................................Error! Bookmark not defined.

8. HOW TO:........................................................................................................................................ 9

8.1 GET A SAMPLE RUNNING............................................................................................................ 98.1.1 Comments on Sample:........................................................................................................ 9

8.2 PERFORM LOGGING IN HWS......................................................................................................9

9. HOW IT WORKS......................................................................................................................... 10

9.1 SCENARIO............................................................................ERROR! BOOKMARK NOT DEFINED.9.2 ACTIVITY MODELS, ACTIVITY BLOCKS, ACTIONS..................ERROR! BOOKMARK NOT DEFINED.

10. SOURCES OF INFORMATION/GOOD REFERENCES............ERROR! BOOKMARK NOT DEFINED.

11. TODO/ NOT COVERED.......................................................................................................... 12

APPENDIX A: UI ALTERNATIVES FOR HWS...............................................................................13

PROS AND CONS....................................................................ERROR! BOOKMARK NOT DEFINED.

EXCEL.............................................................................................ERROR! BOOKMARK NOT DEFINED.WORD.............................................................................................ERROR! BOOKMARK NOT DEFINED.OUTLOOK........................................................................................ERROR! BOOKMARK NOT DEFINED.



Appendix B :How to convert a workflow into a BizTalk HWF.....................Error! Bookmark not defined.



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 DescriptionSemantic Dissonance

Integration

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, ownershipo 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 DescriptionGrouping of Shapes Grouping of functoids in the mapConnection 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 Practices1. 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 calling4. 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 ReferencesMake sure you have the latest SDK and documentation from the MS website:

Address CommentsSemantic Information Architecture

http://knowledgemanagement.ittoolbox.com/pub/ZS050903.pdf

Good article on the architectural significance of this work.

13. Useful ToolsTool name Useful For Download Link Rate it

14. Common ProblemsSymptoms Description Cause ResolutionMoving shapes is dangerous as it is very easy to get OOTB functoids error handling

How is that done?

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

Technology

Transcript of Mapper