Point-to-point integration while simple and fast to implement, is
generally regarded as more costly on the long-term.
IMO, building an integration framework along the lines of
http://www.eaipatterns.com/toc.html into OpenERP would pay for itself.
I'm going to build a _very_ simple one for myself based on RabbitMQ. It
would need two modules:
a) one for "service enablement" of OpenERP. It would fire and receive
CRUD operations and actions as events that would be propagated through
RabbitMQ. I'm still thinking of how to do it without putting event
firing code all over...
b) an optional "router" module that would transform and route the
messages. It's optional because it could be replaced by Mule, or another
"enterprise" ESB for more complex scenarios or if you want pre-packaged
connectors.
Standard integration modules could be build as "adapters" and
"transformers" to external systems and benefit from a decoupled
architecture, reliability (if needed), monitoring, asynchronism, etc.
Cloves
Em 11/12/2012 06:08, Guewen Baconnier escreveu:
On 12/10/2012 08:18 PM, Maxime Chambreuil wrote:
Hello,
I think this was the list mentioned for discussions about project
creation.
We need to integrate OpenERP with:
* Redmine: http://www.redmine.org
* RT: http://www.bestpractical.com/rt/
* SugarCRM : http://www.sugarcrm.com
and I was thinking of creating new projects with their respective
team, based on openobject-extension:
* redminerpconnect
* rterpconnect
* sugarcrmerpconnect
As the import_sugarcrm module is discontinued , I plan to move it in
sugarcrmerpconnect until the new connector is stable enough.
Any comments ?
_______________________________________________
Mailing list: https://launchpad.net/~openerp-expert-framework
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-expert-framework
More help : https://help.launchpad.net/ListHelp
Hello Maxime,
Your new projects are very welcome in the *erpconnect world :-)
However, we wish to start a refactoring project on
'base_external_referentials' and 'base_sale_multichannels' (and
'magentoerpconnect') and if all goes well, a lot of things would
change (it would be far simpler to create new connectors). I hope
we'll able to give more details in a near future.
In any case, we'll try to not break the existing connectors
(deprecation of a part of the actual API), but one day or another you
would need to switch to the new API.
I don't have any conclusion, you may want to wait some time or already
start with the actual API, anyway you'll be informed in time about our
plans.
Best,
_______________________________________________
Mailing list: https://launchpad.net/~openerp-expert-framework
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-expert-framework
More help : https://help.launchpad.net/ListHelp