- This topic has 1 reply, 1 voice, and was last updated 9 years ago by
.
-
Posts
-
-
Hello;
We recently bought filenet as our content mangement system and BPM solution and want to make calls from within the BPM to backoffice systems. Filenet support JMS and Webservices calls to interact with backoffice systems. We now do webservice calls from filenet to backoffice. But we have no message queing. Is it a good thing to implement a biztalk and let de calls from filenet go to biztalk and biztalk to the backoffice. Would biztalk provide the queing with the messagebox functionality or do we need to get a JMS connector and get the messages via JMS to biztalk and then to the backoffice with the use of webservices. Wat is the best path for performance reasons and will it be a good way ?
Please i don't know biztalk that well but hoped you guys could clear it out.
Thanks in advance.
Michael
-
Michael,
As I can understand by your description, you want a queing mechanism to queue call messages to back office, they are currently sent using the web services, so there is no queuing.
BizTalk comes with two queuing adapters out-of-the-box, namely MSMQ and WebSphere MQ (MQ Series), so you can use one of these two no problem, if filenet supports them, on the other side of it you can make a web service call from BizTalk to your back office. The queing inside biztalk is database (Sql Server) driven as far as I know, so it is not the traditional queing system. So you need to decide on first how do you reach BizTalk first, would you prefer to use a queue to reach BizTalk or some other mechanism like SOAP, File etc. then once your messages is inside biztalk, it gives you the safety of database driven queing.
By putting BizTalk in b/w you'd get the benefit of assured delivery of messages even if the back office system is down, Centrallized management of all the calls etc.
Regards,
Sajid
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.