Receive ports and Receive Locations
When we talk about receive ports we have to relate it to recevie location, mapping.
Given a scenario how you will do transformation on the received message to fit to your desired format?
How can we accomplish this?
There are two ways to accomplish this... hope most of you guys have guessed atleast one.
Option 1: With the help of mapping.
Option 2: With out mapping.
Receive Ports are static one-way and request-response port (eg : http , web service). there can be more than one receive
location for a receive port and each of them can be configured for differnet application or a protocols.There cannot be more
than one receive location for the same protocol or application at the same time.receive locations are physical entry point
for the messages.
Main four option that we run while configuring receive locations are General,receive handler,receive pipeline and service
window. we have the option for specifying the Physical Location.authentication,batching. receive handler is always the Host
application eg(Biztalk server). Service window option can be specified if we require to receive messages only during the
particualr time frames.
recevie Pipelines can be custom developed. we will learn more about in later tutorials.
Now that we have briefly outlined about receive ports. It time to ponder on send port too.
Note: last but not least Receive port are always static.
Send port
Send Ports are responsible for sending the processed message out of Biztalk to heterogenous systems. there is a slight
differnce in configuring send port on Biztalk explorer and Administration control.
Here we have both static and Dynamic Behaviour.
Statis one way, Static - solicit response where are the former is one way and acknowledgement is received on later.
Dynamic one-way and dynamic - solicit response.Here the port bindings are specified during runtime.
coming to the configuration we have three main categories like transport,send,Filters & map.
Transport is applicable only for static port types. we can specify primary as well as secondary transport. we have the
facilities like specifying the retry count , start and end time for activity of the port etc..
with the send property we can specify Tracking habit before or after message sent and also the priority for delivery with 1
being highest 10 being lowest and 5 as default.For secure transmit we can also have ceritification bound.
Note : Incase of solicit type we have the option for specifying the receive pipeline.
More about Filter with send port
Filters are specified when orchestration are not part of scenario.when send port are bound to orchestration no filters will
be used.In that case MAPs are used for tranform.Few basic requirements of send ports are Transport mechanism ,transport
location, Biztalk pipeline that process the message outbound from Biztalk. Hope this gives the clue to answer the option 2
mentioned above.
Summary
Now that we have seen in detail about each port characteristics next we will explore more about their mapping features. Ofcourse will give you the solution for Option 2 mentioned above.
Happy Learning
|
| Author: sreejith 21 Feb 2008 | Member Level: Silver Points : 0 |
its really nice to read the article.simple presentation. really good.
cheers
sreejith
MCAD
sreejithsql@gmail.com
|