The BizTalk Mapper lives in the Visual Studio shell. A
portion of the usefulness in the BizTalk Mapper depends on the UI components of
the Visual Studio shell. For instance, you utilize the File, Edit, and View
menus similarly as you would for other advancement in Visual Studio. Data about
this normal usefulness is accessible from the Help menu.
The BizTalk Mapper ends up noticeably dynamic when you add
another guide to a BizTalk venture, when you open a current guide (a .btm
document), or when you reactivate a guide by clicking its tab in the primary
Visual Studio altering window.
Note: The BizTalk Mapper saves map
files using UTF-16 character encoding.
Note: When you add a current ancient rarity to a BizTalk
venture, the construct activity is constantly
set to BtsCompile.
Notwithstanding when you rename a current antique, its construct activity is
set to the default esteem BtsCompile. Subsequently, while including or renaming
a current antique, you have to set the fabricate activity suitably relying upon
whether you need to manufacture that specific relic or not.
Get the OnlineItGuru BizTalk Online
Training Course Certification!
The accompanying figure demonstrates
different parts of BizTalk Mapper inside Visual Studio.
The usefulness of each of the perspectives is as per the
following:
Visual Studio Mapper Utility Ribbon. The BizTalk Server
Mapper gives an utility lace to surface Mapper-related charges. The lace gives
source pattern data, flip catch for importance see for source and goal
outlines, flip catch to show or cover up absolutely out of degree joins, flip
change to turn auto-looking on or off, catch to container the Mapper surface,
controls to zoom in or zoom out, and the pursuit content box. The accompanying
figure demonstrates the utility lace you can see at the highest point of the
framework page.
Source pattern tree
see: This view shares the primary Visual Studio altering window with the
goal construction tree see and the network see.
As the name recommends, this view shows the blueprint that
depicts the case messages that are the wellspring of mapping. The connections
that characterize the mapping lead from the source diagram tree view to the
lattice see, and, at last, to the goal construction tree see.
For more data about how BizTalk patterns are spoken to in a
blueprint tree see, see BizTalk Representation of Schemas.
Destination schema
tree view: This view shares the primary Visual Studio altering window with
the source blueprint tree see and the network see.
As the name recommends, this view shows the pattern that
portrays the occasion messages that are the goal of the mapping. The
connections that characterize the mapping lead into the goal outline tree see
from the matrix see, and at last from the source composition tree see.
For more data about how BizTalk diagrams are spoken to in a
mapping tree see, see BizTalk Representation of Schemas.
Grid view: This
view shares the principle Visual Studio altering window with the source
blueprint tree see and the goal pattern tree see, with the source outline tree
view to one side and the goal construction tree view to one side.
As the name recommends, this view assumes a basic part in
the meaning of maps, containing the connections and functoids that control how
information in a source case message is changed into an occasion message that
fits in with the goal construction.
Interested in learning BizTalk Online
Training is a success for your career!
The matrix view can have various layers, called lattice
pages, enabling you to arrange complex maps into consistent subdivisions of
mappings. Lattice pages for the most part utilize more space than can be shown
at one time, and there are a few successful approaches to look inside a
framework page.
You effectively work in this view to build your guide.
Visual Studio Toolbox
window: You utilize this view to show the functoids accessible for use in
BizTalk maps, and as the wellspring of the simplified operations to put
functoids in a matrix page.
The functoids appeared in the Toolbox are sorted out as per
their classes. For more data about the accessible functoids, see Functoids in
Maps. Likewise observe Functoid Reference.
Visual Studio
Properties window: You utilize this view, and its related discourse boxes,
to look at and set the properties of the connections and functoids that you
make to characterize your guide.
When you select a connection or functoid in a matrix page in
the Grid see, select an outline hub in the source or goal pattern tree sees, or
select a guide in the Solution Explorer window; the comparing properties of
that connection, functoid, blueprint hub, or guide show up in the Properties window
utilizing the standard Visual Studio traditions. For instance, the properties
are assembled into classifications, and can be shown by these classes or
sequentially.
For definite data about the distinctive arrangements of
properties that are accessible for joins, functoids, construction hubs, or the
guide itself, see Map Property Reference. Additionally observe Schema Property
Reference.
Visual Studio Task List and Output windows: You utilize
these perspectives to analyze the consequences of approving, arranging, and
testing your BizTalk maps similarly that these perspectives are utilized when
incorporating source code and building different sorts of tasks.
In addition to these perspectives, you can connect with a
few exchange boxes. You generally open these exchange boxes when you are
altering a mind boggling property, for example, the info parameters to a
functoid.
You frequently utilize the Solution Explorer window in
conjunction with BizTalk Mapper. For instance, to make another guide, right-tap
the BizTalk venture in the Solution Explorer window, click Add, click Add New
Item, and after that utilization the Add New Item exchange box to name and make
another guide.
Read more at
Biztalk Online Training Hyderabad
