Hello Shawn, Which versions of BizTalk have you encountered? My experience is with 2004 versions and later. BizTalk is an implementation is best supported by development and support resources committed to the Microsoft .NET framework.
BizTalk can integrate very easily with Commerce Server and Sharepoint. It can be the interface between a companies back-end data system and the public facing web portal. It can coordinate activity between ERP, CRM and Accounting Systems. It has a robust Business Rules Engine that can be used in a variety of ways. In my opinion, however, it is not a good fit for an operation lacking .NET Framework development resources. Your experience has shown that. Dylan On Mon, Dec 27, 2010 at 8:08 PM, Shawn Aker <[email protected]> wrote: > Biztalk is much more of a custom solution when it comes to > it's communication/gateway(AS2) and EDI translations stuff. I've taken out > many home grown solutions "based" on biztalk because the implementer took > off and no one could figure out what the h*** they did. > > My guess is you already have Biztalk. Use it for integration between your > apps, webservices, SOA stuff etc. It's a great middle-ware tool. One thing > we've found is the license models that biztalk provides doesn't lend it self > well to large gateway and translation. > > Spend a few bucks and implement something in the cloud or behind your > firewall made for EDI. EDI is more then just an X12 definition. It's the > 997 acknowledgment, tracking, viability, key management, etc. > > Regards, > > Shawn Aker > [email protected] > > > On Mon, Dec 27, 2010 at 1:25 PM, Dylan Hall <[email protected]> wrote: > >> Hello Anne, >> >> Translators like GXS AI and Gentran are well suited for data translation >> right out of the box. When it comes to EDI translation, it is not that >> hard >> to learn the language of these translation tools and create applications. >> Many of us who worked with one or two translators find learning a new one >> not that difficult. >> >> BizTalk can handle any task that you throw at it. It is based on >> Microsoft's >> .NET framework, so you can use .NET code to customize any application you >> create. You can create code libraries, custom components, adapters for >> virtually anything.It can handle all of your communication needs - and you >> can extend or customize communications to suit your needs. In addition >> ,you >> can easily go to the Internet for sample code, problem solving and best >> practices. There is lots of free information available on Microsoft's >> websites. You can even download and run the Developer Edition of BizTalk >> for >> free (no time bomb). With the download you get compliant X12 and Edifact >> Schemas. >> However, development and maintenance of BizTalk requires some competency >> in >> C# .NET and SQL server. Although, these developers/consultants tend to be >> senior, their skill set is quite readily available. >> >> Having worked with both, I would say this: >> >> - traditional translators are quick and efficient. >> - BizTalk does require more resources, however it can reward the >> enterprise in other ways. >> >> >> Dylan >> >> On Mon, Dec 27, 2010 at 1:51 PM, anneco_2000 <[email protected]> >> wrote: >> >> > >> > >> > Is there anyone out there currently working with Biztalk? How does it >> stack >> > up against tradtional EDI translators like Gentran? >> > PLEASE no Sales Reps contact for any translator. I am just looking for >> user >> > opionions please. >> > >> > regards, >> > Anne >> > >> > >> > >> >> >> [Non-text portions of this message have been removed] >> >> >> >> ------------------------------------ >> >> ... >> >> Please use the following Message Identifiers as your subject prefix: >> <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> >> >> Job postings are welcome, but for job postings or requests for work: >> <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links >> >> >> >> > [Non-text portions of this message have been removed] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
