Home Page › Forums › BizTalk 2004 – BizTalk 2010 › BizTalk Orchestration – best practice.
- This topic has 3 replies, 1 voice, and was last updated 8 years, 4 months ago by
community-content.
-
AuthorPosts
-
-
August 6, 2010 at 8:48 AM #25556
Hello Gurus, I was wondering if anyone here can help me with BizTalk implementation,
I am integrating with Dynamics CRM, and have defined orchestration to handle the creation and updates of account and contact entities, I have implemented the solution and works fine but I want to refine the solution, below is what I have done
defined orchestration to handle account message
1) receive account message
2) perform lookup to see if contact exists (fetch request using crm adapter) if exists set action attribute to update else create
I have defined a seperate contact process orchestration to receive contact message
perform lookup to see if account exits
if account exists create contact, otherwise sleep for 5 min and repeat the process until account is created –> how can improve on this scenerio
i’m fairly new to Biztalk, but well versed in Tibco. I was thinking of sending a message to messagebox from the account orchestration and set some correlation id (account id) and instead of using timer define a receive shape which subscibes to the message published by account orchestration process.
your comment would be much appreciated
ambishan
-
August 6, 2010 at 9:44 PM #25562
Hi ambishan,
The extent of refining your solution really depends on how your business process handles the creation and update of account and contact entities. Is the account supposed to exist before a contact can be created/updated? If that’s the case, I would say there’s an opportunity for you can to change both your orchestrations to improve the design and workflow.
Daniel.
-
August 9, 2010 at 5:12 AM #25575
Daniel
Thanks for your prompt reply, yes account has to exists in order to create contacts, account messages are created seperate to the contact message assyncronously, is there a concept of wait notitfy from one orchestration to another in biztalk?
thanks
-
August 10, 2010 at 4:11 AM #25584
Hi
Using the sleep is like sending message to messagebox
because the message will be dehydrated which mean it will not stay in memory. but you need to put a counter
for it to stop it on after a specific retry after that a notification
email should be sent and finish the orchestration.
-
-
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.