Difference between revisions of "Talk:Sponsored Development: Interface with OSCommerce"
| Line 41: | Line 41: | ||
Jitterbit is tempting, but, IMHO, it is not good for documents, like orders, because it bypasses all the Model rules that apply. You can take that risk by enforcing all the right rules in OSCommerce or in the ETL. But there remains the risk that you have to maintain business logic in two places. That's also a problem with making a generic jitterbit. An approach that works through the model layer, like posterita or the recently contributed webservices is appealing for consistency and reusability. | Jitterbit is tempting, but, IMHO, it is not good for documents, like orders, because it bypasses all the Model rules that apply. You can take that risk by enforcing all the right rules in OSCommerce or in the ETL. But there remains the risk that you have to maintain business logic in two places. That's also a problem with making a generic jitterbit. An approach that works through the model layer, like posterita or the recently contributed webservices is appealing for consistency and reusability. | ||
[[User:JsSolutions|jsSolutions]] 14:01, 4 July 2007 (EDT) | [[User:JsSolutions|jsSolutions]] 14:01, 4 July 2007 (EDT) | ||
| + | :: WebServices seem like best bet ok... But couldn't you use jitterbit to load the orders into the import table and process them from there? Wouldn't that then follow the business logic of the document in question? [[User:Croo|Croo]] 18:10, 4 July 2007 (EDT) | ||
Revision as of 15:10, 4 July 2007
About Jitterbit : this could be a nice way to achieve the objective. Would it be possible to create "templates" that would work for any OSCommerce / ADempiere ?
What would be the advantages / disadvantages of using Jitterbit ETL vs making the integration via webservices ?
--ALP 13:50, 3 July 2007 (EDT)
We haven't done the integration with oscommerce, but we have made several custom webstores and some of them may be close to your needs. In some cases, we inspired ourselves from the checkout process of oscommerce. Give me a call on skype or send me an email if you want to find out more about these.
We have a very basic webstore which has already been contributed under the contribution folder of Adempiere.
Fredtsang 15:38, 3 July 2007 (EDT)
Thanks, but in this case, the webstore is already online and the objective is to integrate it with ADempiere, the client will consider switching to an "embedded" webstore later.
--ALP 03:11, 4 July 2007 (EDT)
The advantage of webservice is that you dont have to change any adempiere code. you need to change xt/os-commerce checkout process to push the order into adempiere. additionally you need to pull out all the products from adempiere. you wouldnt need to play arround directly in the database as you would need to do if you use jitterbit
--Jab doa 03:58, 4 July 2007 (EDT)
OK, how do we move from here ? --ALP 04:40, 4 July 2007 (EDT)
Ok, you only have 2 solutions then:
1) Webservices. The problem is that the webservice hasn't been contributed yet to my knowledge. But we have seen a proof of concept in berlin, proposed by Lukasz and Maciej from 3E. They have done a great work with a VB integration over the webservice layer. They have a small article printed for more info go to Sponsored_Development:_WebService.
2) Jeff Davis has made a tutorial on jitterbit, you may want to contact him also to find out how difficult the integration would be.
Regards. Fredtsang 06:29, 4 July 2007 (EDT)
1) Webservices have been contributed. See Sponsored_Development:_WebService which I started yesterday. I got it running here.
Jab doa 08:49, 4 July 2007 (EDT)
Jitterbit is tempting, but, IMHO, it is not good for documents, like orders, because it bypasses all the Model rules that apply. You can take that risk by enforcing all the right rules in OSCommerce or in the ETL. But there remains the risk that you have to maintain business logic in two places. That's also a problem with making a generic jitterbit. An approach that works through the model layer, like posterita or the recently contributed webservices is appealing for consistency and reusability. jsSolutions 14:01, 4 July 2007 (EDT)
- WebServices seem like best bet ok... But couldn't you use jitterbit to load the orders into the import table and process them from there? Wouldn't that then follow the business logic of the document in question? Croo 18:10, 4 July 2007 (EDT)
