Proposal: sending the specialpurpose/oagis component to Attic

[Jacopo Cappellato-5]

Hi all,

my proposal is to remove the "oagis" specialpurpose component from the
trunk and record the event in our Attic page [*].
If we will do this, the consequence will be that the component will no more
be available in future releases: if you are using it, or plan to use it,
speak up now! :-)
Otherwise, its source code and interesting concepts will be always
available in our source repository and interested parties could easily
retrieve its sources following the instructions in our Attic page.
The main motivation for this proposal is because of the tricky license of
the XML schema files under specialpurpose/oagis/dtd/
These files are an old and unmaintained version and we could not upgrade
them because since their inclusion in OFBiz the newer versions have been
re-licensed under an incompatible license. Even in they current license,
they require special handling and mention in our LICENSE file and,
considering the complexity of the subject, and the fact that the component
has never attracted much attention (based on the questions or contributions
received in the years), I think it would be safer if we remove it from the
trunk.

Kind regards,

Jacopo

[*] https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Attic

[Jacques Le Roux]

+1

Jacques


Le 23/09/2016 à 10:44, Jacopo Cappellato a écrit :

> Hi all,
>
> my proposal is to remove the "oagis" specialpurpose component from the
> trunk and record the event in our Attic page [*].
> If we will do this, the consequence will be that the component will no more
> be available in future releases: if you are using it, or plan to use it,
> speak up now! :-)
> Otherwise, its source code and interesting concepts will be always
> available in our source repository and interested parties could easily
> retrieve its sources following the instructions in our Attic page.
> The main motivation for this proposal is because of the tricky license of
> the XML schema files under specialpurpose/oagis/dtd/
> These files are an old and unmaintained version and we could not upgrade
> them because since their inclusion in OFBiz the newer versions have been
> re-licensed under an incompatible license. Even in they current license,
> they require special handling and mention in our LICENSE file and,
> considering the complexity of the subject, and the fact that the component
> has never attracted much attention (based on the questions or contributions
> received in the years), I think it would be safer if we remove it from the
> trunk.
>
> Kind regards,
>
> Jacopo
>
> [*] https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Attic
>

[Ashish Vijaywargiya-4]

+1

Kind Regards
Ashish Vijaywargiya
HotWax Systems - est. 1997


On Fri, Sep 23, 2016 at 2:14 PM, Jacopo Cappellato <
[hidden email]> wrote:

> Hi all,
>
> my proposal is to remove the "oagis" specialpurpose component from the
> trunk and record the event in our Attic page [*].
> If we will do this, the consequence will be that the component will no more
> be available in future releases: if you are using it, or plan to use it,
> speak up now! :-)
> Otherwise, its source code and interesting concepts will be always
> available in our source repository and interested parties could easily
> retrieve its sources following the instructions in our Attic page.
> The main motivation for this proposal is because of the tricky license of
> the XML schema files under specialpurpose/oagis/dtd/
> These files are an old and unmaintained version and we could not upgrade
> them because since their inclusion in OFBiz the newer versions have been
> re-licensed under an incompatible license. Even in they current license,
> they require special handling and mention in our LICENSE file and,
> considering the complexity of the subject, and the fact that the component
> has never attracted much attention (based on the questions or contributions
> received in the years), I think it would be safer if we remove it from the
> trunk.
>
> Kind regards,
>
> Jacopo
>
> [*] https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Attic
>

[taher]

+1

On Fri, Sep 23, 2016 at 12:32 PM, Ashish Vijaywargiya <
[hidden email]> wrote:

> +1
>
> Kind Regards
> Ashish Vijaywargiya
> HotWax Systems - est. 1997
>
>
> On Fri, Sep 23, 2016 at 2:14 PM, Jacopo Cappellato <
> [hidden email]> wrote:
>
> > Hi all,
> >
> > my proposal is to remove the "oagis" specialpurpose component from the
> > trunk and record the event in our Attic page [*].
> > If we will do this, the consequence will be that the component will no
> more
> > be available in future releases: if you are using it, or plan to use it,
> > speak up now! :-)
> > Otherwise, its source code and interesting concepts will be always
> > available in our source repository and interested parties could easily
> > retrieve its sources following the instructions in our Attic page.
> > The main motivation for this proposal is because of the tricky license of
> > the XML schema files under specialpurpose/oagis/dtd/
> > These files are an old and unmaintained version and we could not upgrade
> > them because since their inclusion in OFBiz the newer versions have been
> > re-licensed under an incompatible license. Even in they current license,
> > they require special handling and mention in our LICENSE file and,
> > considering the complexity of the subject, and the fact that the
> component
> > has never attracted much attention (based on the questions or
> contributions
> > received in the years), I think it would be safer if we remove it from
> the
> > trunk.
> >
> > Kind regards,
> >
> > Jacopo
> >
> > [*] https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Attic
> >
>

[Michael Brohl-3]

+1

Thanks,

Michael

Am 23.09.16 um 10:44 schrieb Jacopo Cappellato:

> Hi all,
>
> my proposal is to remove the "oagis" specialpurpose component from the
> trunk and record the event in our Attic page [*].
> If we will do this, the consequence will be that the component will no more
> be available in future releases: if you are using it, or plan to use it,
> speak up now! :-)
> Otherwise, its source code and interesting concepts will be always
> available in our source repository and interested parties could easily
> retrieve its sources following the instructions in our Attic page.
> The main motivation for this proposal is because of the tricky license of
> the XML schema files under specialpurpose/oagis/dtd/
> These files are an old and unmaintained version and we could not upgrade
> them because since their inclusion in OFBiz the newer versions have been
> re-licensed under an incompatible license. Even in they current license,
> they require special handling and mention in our LICENSE file and,
> considering the complexity of the subject, and the fact that the component
> has never attracted much attention (based on the questions or contributions
> received in the years), I think it would be safer if we remove it from the
> trunk.
>
> Kind regards,
>
> Jacopo
>
> [*] https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Attic
>

[Sharan-F]

+1

Thanks Jacopo for detailing the current status and problems as it makes it a lot easier to make a decision.

Thanks
Sharan

On 2016-09-23 10:44 (+0200), Jacopo Cappellato <[hidden email]> wrote:

> Hi all,
>
> my proposal is to remove the "oagis" specialpurpose component from the
> trunk and record the event in our Attic page [*].
> If we will do this, the consequence will be that the component will no more
> be available in future releases: if you are using it, or plan to use it,
> speak up now! :-)
> Otherwise, its source code and interesting concepts will be always
> available in our source repository and interested parties could easily
> retrieve its sources following the instructions in our Attic page.
> The main motivation for this proposal is because of the tricky license of
> the XML schema files under specialpurpose/oagis/dtd/
> These files are an old and unmaintained version and we could not upgrade
> them because since their inclusion in OFBiz the newer versions have been
> re-licensed under an incompatible license. Even in they current license,
> they require special handling and mention in our LICENSE file and,
> considering the complexity of the subject, and the fact that the component
> has never attracted much attention (based on the questions or contributions
> received in the years), I think it would be safer if we remove it from the
> trunk.
>
> Kind regards,
>
> Jacopo
>
> [*] https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Attic
>

[Pranay Pandey-3]

+1

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Fri, Sep 23, 2016 at 2:14 PM, Jacopo Cappellato <
[hidden email]> wrote:

> Hi all,
>
> my proposal is to remove the "oagis" specialpurpose component from the
> trunk and record the event in our Attic page [*].
> If we will do this, the consequence will be that the component will no more
> be available in future releases: if you are using it, or plan to use it,
> speak up now! :-)
> Otherwise, its source code and interesting concepts will be always
> available in our source repository and interested parties could easily
> retrieve its sources following the instructions in our Attic page.
> The main motivation for this proposal is because of the tricky license of
> the XML schema files under specialpurpose/oagis/dtd/
> These files are an old and unmaintained version and we could not upgrade
> them because since their inclusion in OFBiz the newer versions have been
> re-licensed under an incompatible license. Even in they current license,
> they require special handling and mention in our LICENSE file and,
> considering the complexity of the subject, and the fact that the component
> has never attracted much attention (based on the questions or contributions
> received in the years), I think it would be safer if we remove it from the
> trunk.
>
> Kind regards,
>
> Jacopo
>
> [*] https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Attic
>

[Paul Foxworthy]

+1


> On Fri, Sep 23, 2016 at 2:14 PM, Jacopo Cappellato <
> [hidden email]> wrote:
>
> > my proposal is to remove the "oagis" specialpurpose component from the
> > trunk and record the event in our Attic page [*].
>

[Mike Z]

Great.  So everyone seems to agree to dump oagis.  Obviously someone took
the time to create this component.  My understanding it is used for
automating B2B communication for purchase orders, inventory, etc.  If you
want ofbiz to play with the big boys, you need this TYPE of Electronic Data
Interchange (EDI) functionality.

So:  If you want to dump oagis, please propose alternatives to make ofbiz
integrate with EDI.  All ERPs have this.

On Tue, Sep 27, 2016 at 9:39 PM, Paul Foxworthy <[hidden email]> wrote:

> +1
>
>
> > On Fri, Sep 23, 2016 at 2:14 PM, Jacopo Cappellato <
> > [hidden email]> wrote:
> >
> > > my proposal is to remove the "oagis" specialpurpose component from the
> > > trunk and record the event in our Attic page [*].
> >
>

[Todd Thorner]

I did a quick search for a dog food solution within the ASF, and found
this page:

https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=92973

It points toward a project hosted outside the ASF, and codehaus.org
appears to be temporarily unresponsive (at least on my end), but that
Smooks thing might represent an alternative.


On 16-09-28 10:52 AM, Mike wrote:

> Great.  So everyone seems to agree to dump oagis.  Obviously someone took
> the time to create this component.  My understanding it is used for
> automating B2B communication for purchase orders, inventory, etc.  If you
> want ofbiz to play with the big boys, you need this TYPE of Electronic Data
> Interchange (EDI) functionality.
>
> So:  If you want to dump oagis, please propose alternatives to make ofbiz
> integrate with EDI.  All ERPs have this.
>
> On Tue, Sep 27, 2016 at 9:39 PM, Paul Foxworthy <[hidden email]> wrote:
>
>> +1
>>
>>
>>> On Fri, Sep 23, 2016 at 2:14 PM, Jacopo Cappellato <
>>> [hidden email]> wrote:
>>>
>>>> my proposal is to remove the "oagis" specialpurpose component from the
>>>> trunk and record the event in our Attic page [*].

[Jacopo Cappellato-5]

On Wed, Sep 28, 2016 at 11:22 PM, Mike <[hidden email]> wrote:

> Great.  So everyone seems to agree to dump oagis.  Obviously someone took
> the time to create this component.  My understanding it is used for
> automating B2B communication for purchase orders, inventory, etc.  If you
> want ofbiz to play with the big boys, you need this TYPE of Electronic Data
> Interchange (EDI) functionality.
>
> So:  If you want to dump oagis, please propose alternatives to make ofbiz
> integrate with EDI.  All ERPs have this.
>
>

Thank you for the feedback Mike.
I do agree that providing some EDI functionality out of the box is very
important for an ERP system. OFBiz already has a few mechanisms for data
exchange that can be leveraged to implement specific or custom
integrations. The concept of an universal data interchange standard is
great, but, as far as I know, OAGIS has never reached the critical mass to
make it a viable solution for all integration needs. By experience I have
noticed that such standards tend to gain more tractions when they address
specific industries (e.g. parts interchange formats for the auto parts
aftermarket industry etc...).
Most importantly, when it was adopted by OFBiz, the OAGIS license allowed
us to include its xsd files; but after that, they have been relicensed
under an incompatible license: as a consequence this component is stuck to
an years old and unmaintained version making even more difficult to be used
to integrate with an external system.

Kind regards,

Jacopo

[Jacopo Cappellato-5]

The component has been removed in rev. 1763454

Thanks,

Jacopo

On Wed, Oct 5, 2016 at 11:16 AM, Jacopo Cappellato <
[hidden email]> wrote:

> On Wed, Sep 28, 2016 at 11:22 PM, Mike <[hidden email]> wrote:
>
>> Great.  So everyone seems to agree to dump oagis.  Obviously someone took
>> the time to create this component.  My understanding it is used for
>> automating B2B communication for purchase orders, inventory, etc.  If you
>> want ofbiz to play with the big boys, you need this TYPE of Electronic
>> Data
>> Interchange (EDI) functionality.
>>
>> So:  If you want to dump oagis, please propose alternatives to make ofbiz
>> integrate with EDI.  All ERPs have this.
>>
>>
> Thank you for the feedback Mike.
> I do agree that providing some EDI functionality out of the box is very
> important for an ERP system. OFBiz already has a few mechanisms for data
> exchange that can be leveraged to implement specific or custom
> integrations. The concept of an universal data interchange standard is
> great, but, as far as I know, OAGIS has never reached the critical mass to
> make it a viable solution for all integration needs. By experience I have
> noticed that such standards tend to gain more tractions when they address
> specific industries (e.g. parts interchange formats for the auto parts
> aftermarket industry etc...).
> Most importantly, when it was adopted by OFBiz, the OAGIS license allowed
> us to include its xsd files; but after that, they have been relicensed
> under an incompatible license: as a consequence this component is stuck to
> an years old and unmaintained version making even more difficult to be used
> to integrate with an external system.
>
> Kind regards,
>
> Jacopo
>
>
>

[Mike Z]

> "Thank you for the feedback Mike. I do agree that providing some EDI
functionality out of the box is very important for an ERP system. OFBiz
already has a few mechanisms for data exchange that can be leveraged to
implement specific or custom integrations."

I remember looking in the oagis code and didn't really see anywhere how it
was connected to the code.  Still, you mention that ofbiz has "some EDI
functionality"?  Can you clarify this?

If HotWax integrated ofbiz with EDI, how did you do it?  In real life, a PO
is created, and transmitted to/from a supplier via EDI.

A while ago I was looking at BOTS (
http://bots.sourceforge.net/en/index.shtml) and it looked like a better
solution.

On Wed, Oct 5, 2016 at 7:14 AM, Jacopo Cappellato <
[hidden email]> wrote:

> The component has been removed in rev. 1763454
>
> Thanks,
>
> Jacopo
>
> On Wed, Oct 5, 2016 at 11:16 AM, Jacopo Cappellato <
> [hidden email]> wrote:
>
> > On Wed, Sep 28, 2016 at 11:22 PM, Mike <[hidden email]> wrote:
> >
> >> Great.  So everyone seems to agree to dump oagis.  Obviously someone
> took
> >> the time to create this component.  My understanding it is used for
> >> automating B2B communication for purchase orders, inventory, etc.  If
> you
> >> want ofbiz to play with the big boys, you need this TYPE of Electronic
> >> Data
> >> Interchange (EDI) functionality.
> >>
> >> So:  If you want to dump oagis, please propose alternatives to make
> ofbiz
> >> integrate with EDI.  All ERPs have this.
> >>
> >>
> > Thank you for the feedback Mike.
> > I do agree that providing some EDI functionality out of the box is very
> > important for an ERP system. OFBiz already has a few mechanisms for data
> > exchange that can be leveraged to implement specific or custom
> > integrations. The concept of an universal data interchange standard is
> > great, but, as far as I know, OAGIS has never reached the critical mass
> to
> > make it a viable solution for all integration needs. By experience I have
> > noticed that such standards tend to gain more tractions when they address
> > specific industries (e.g. parts interchange formats for the auto parts
> > aftermarket industry etc...).
> > Most importantly, when it was adopted by OFBiz, the OAGIS license allowed
> > us to include its xsd files; but after that, they have been relicensed
> > under an incompatible license: as a consequence this component is stuck
> to
> > an years old and unmaintained version making even more difficult to be
> used
> > to integrate with an external system.
> >
> > Kind regards,
> >
> > Jacopo
> >
> >
> >
>

[Craig Parker]

Is there a doc somewhere on starting with a fresh DB? I'm still tooling
with the data that comes with a default install, but I'm going to want
another "squeaky clean" DB to be playing with also.

There's nothing saying I can't have two instances of ofbiz running on
the same server is there, or is there a better way to swap back and
forth between the "test" DB that I'm currently running and what will
eventually be my live DB in a hurry?

[taher]

Hi Craig,

Take a look at the data loading tasks in README.md as it shows you
different data loading scenarios for different environments.

You can switch between two databases, but not the way you might recognize
it in Ruby on Rails or so. If the two databases are both embedded (Derby)
then you have to switch their folders manually in between restarts. If they
are standalone like postgres then you have to update entityengine.xml in
between restarts.

I hope that helps, good luck OFBizzing.

Taher Alkhateeb

On Oct 11, 2016 6:21 AM, "Craig Parker" <[hidden email]> wrote:

> Is there a doc somewhere on starting with a fresh DB? I'm still tooling
> with the data that comes with a default install, but I'm going to want
> another "squeaky clean" DB to be playing with also.
>
> There's nothing saying I can't have two instances of ofbiz running on the
> same server is there, or is there a better way to swap back and forth
> between the "test" DB that I'm currently running and what will eventually
> be my live DB in a hurry?
>
>

[Jacques Le Roux]

Le 11/10/2016 à 05:20, Craig Parker a écrit :
> Is there a doc somewhere on starting with a fresh DB? I'm still tooling with the data that comes with a default install, but I'm going to want
> another "squeaky clean" DB to be playing with also.
>
> There's nothing saying I can't have two instances of ofbiz running on the same server is there, or is there a better way to swap back and forth
> between the "test" DB that I'm currently running and what will eventually be my live DB in a hurry?
>
>
Hi Craig,

You might start 2 (or more) OFBiz instances at the same time by using the portoffset option, hence using simultaneously 2 DBs. As its name says it
will offset all ports internally used by OFBiz.
The syntax can be known using "gradlew "ofbiz -help" if you use the trunk or "ant -p" if you use a released package.

Jacques

[Craig Parker]

I was initially thinking of having two xml files (test.xml and
clean.xml) with appropriate settings in each, and just running cat
test.xml > entityengine.xml (or cat clean.xml --whicever one I'm going
to run) but will this mean I have to sit for a few minutes after each
switch while OFBiz loads? Not sure if this is a better or worse idea
than two instances of OFBiz running. Six of one, a half-dozen of the other?


On 10/10/2016 11:35 PM, Taher Alkhateeb wrote:

> Hi Craig,
>
> Take a look at the data loading tasks in README.md as it shows you
> different data loading scenarios for different environments.
>
> You can switch between two databases, but not the way you might recognize
> it in Ruby on Rails or so. If the two databases are both embedded (Derby)
> then you have to switch their folders manually in between restarts. If they
> are standalone like postgres then you have to update entityengine.xml in
> between restarts.
>
> I hope that helps, good luck OFBizzing.
>
> Taher Alkhateeb
>
> On Oct 11, 2016 6:21 AM, "Craig Parker" <[hidden email]> wrote:
>
>> Is there a doc somewhere on starting with a fresh DB? I'm still tooling
>> with the data that comes with a default install, but I'm going to want
>> another "squeaky clean" DB to be playing with also.
>>
>> There's nothing saying I can't have two instances of ofbiz running on the
>> same server is there, or is there a better way to swap back and forth
>> between the "test" DB that I'm currently running and what will eventually
>> be my live DB in a hurry?
>>
>>

[Scott Gray-3]

Another possible option (which I've never tried), is to use the multi
tenancy functionality to allow two different sets of data without needing
to restart OFBiz or run multiple instances.

Regards
Scott

On 12 October 2016 at 07:40, Craig Parker <[hidden email]> wrote:

> I was initially thinking of having two xml files (test.xml and clean.xml)
> with appropriate settings in each, and just running cat test.xml >
> entityengine.xml (or cat clean.xml --whicever one I'm going to run) but
> will this mean I have to sit for a few minutes after each switch while
> OFBiz loads? Not sure if this is a better or worse idea than two instances
> of OFBiz running. Six of one, a half-dozen of the other?
>
>
>
> On 10/10/2016 11:35 PM, Taher Alkhateeb wrote:
>
>> Hi Craig,
>>
>> Take a look at the data loading tasks in README.md as it shows you
>> different data loading scenarios for different environments.
>>
>> You can switch between two databases, but not the way you might recognize
>> it in Ruby on Rails or so. If the two databases are both embedded (Derby)
>> then you have to switch their folders manually in between restarts. If
>> they
>> are standalone like postgres then you have to update entityengine.xml in
>> between restarts.
>>
>> I hope that helps, good luck OFBizzing.
>>
>> Taher Alkhateeb
>>
>> On Oct 11, 2016 6:21 AM, "Craig Parker" <[hidden email]> wrote:
>>
>> Is there a doc somewhere on starting with a fresh DB? I'm still tooling
>>> with the data that comes with a default install, but I'm going to want
>>> another "squeaky clean" DB to be playing with also.
>>>
>>> There's nothing saying I can't have two instances of ofbiz running on the
>>> same server is there, or is there a better way to swap back and forth
>>> between the "test" DB that I'm currently running and what will eventually
>>> be my live DB in a hurry?
>>>
>>>
>>>
>

[brajeshpatel]

Hi All,

I am working on a project where I need to implement EDI thing.

Found this old thread, is there any component or services that having EDI
implementation in latest release?



On Thu, Oct 6, 2016 at 4:33 AM Mike <[hidden email]> wrote:

> > "Thank you for the feedback Mike. I do agree that providing some EDI
> functionality out of the box is very important for an ERP system. OFBiz
> already has a few mechanisms for data exchange that can be leveraged to
> implement specific or custom integrations."
>
> I remember looking in the oagis code and didn't really see anywhere how it
> was connected to the code.  Still, you mention that ofbiz has "some EDI
> functionality"?  Can you clarify this?
>
> If HotWax integrated ofbiz with EDI, how did you do it?  In real life, a PO
> is created, and transmitted to/from a supplier via EDI.
>
> A while ago I was looking at BOTS (
> http://bots.sourceforge.net/en/index.shtml) and it looked like a better
> solution.
>
> On Wed, Oct 5, 2016 at 7:14 AM, Jacopo Cappellato <
> [hidden email]> wrote:
>
> > The component has been removed in rev. 1763454
> >
> > Thanks,
> >
> > Jacopo
> >
> > On Wed, Oct 5, 2016 at 11:16 AM, Jacopo Cappellato <
> > [hidden email]> wrote:
> >
> > > On Wed, Sep 28, 2016 at 11:22 PM, Mike <[hidden email]> wrote:
> > >
> > >> Great.  So everyone seems to agree to dump oagis.  Obviously someone
> > took
> > >> the time to create this component.  My understanding it is used for
> > >> automating B2B communication for purchase orders, inventory, etc.  If
> > you
> > >> want ofbiz to play with the big boys, you need this TYPE of Electronic
> > >> Data
> > >> Interchange (EDI) functionality.
> > >>
> > >> So:  If you want to dump oagis, please propose alternatives to make
> > ofbiz
> > >> integrate with EDI.  All ERPs have this.
> > >>
> > >>
> > > Thank you for the feedback Mike.
> > > I do agree that providing some EDI functionality out of the box is very
> > > important for an ERP system. OFBiz already has a few mechanisms for
> data
> > > exchange that can be leveraged to implement specific or custom
> > > integrations. The concept of an universal data interchange standard is
> > > great, but, as far as I know, OAGIS has never reached the critical mass
> > to
> > > make it a viable solution for all integration needs. By experience I
> have
> > > noticed that such standards tend to gain more tractions when they
> address
> > > specific industries (e.g. parts interchange formats for the auto parts
> > > aftermarket industry etc...).
> > > Most importantly, when it was adopted by OFBiz, the OAGIS license
> allowed
> > > us to include its xsd files; but after that, they have been relicensed
> > > under an incompatible license: as a consequence this component is stuck
> > to
> > > an years old and unmaintained version making even more difficult to be
> > used
> > > to integrate with an external system.
> > >
> > > Kind regards,
> > >
> > > Jacopo
> > >
> > >
> > >
> >
>

--
Thanks
Brajesh Patel
skype: brajesh.patel11
Cell :- [phone]

[Arun Patidar-3]

Hello Brajesh,

EDI support is not available in OFBiz till now. You will need to implement
services for parsing EDI files and creating new EDI files for different
processes. You can refer 'Smooks[1]' for EDI parsing.

[1]: http://www.smooks.org/guide





Kind Regards,

Arun Patidar
Director of Information Systems

*HotWax CommerceReal OmniChannel. Real Results.*
m: [phone]
w: www.hotwax.co

 <https://www.linkedin.com/company/hotwaxcommerce/>
<https://www.facebook.com/HotWaxCommerce/>
<https://twitter.com/hotwaxcommerce>



On Sat, Sep 8, 2018 at 10:11 PM Brajesh Patel <[hidden email]>
wrote:

> Hi All,
>
> I am working on a project where I need to implement EDI thing.
>
> Found this old thread, is there any component or services that having EDI
> implementation in latest release?
>
>
>
> On Thu, Oct 6, 2016 at 4:33 AM Mike <[hidden email]> wrote:
>
> > > "Thank you for the feedback Mike. I do agree that providing some EDI
> > functionality out of the box is very important for an ERP system. OFBiz
> > already has a few mechanisms for data exchange that can be leveraged to
> > implement specific or custom integrations."
> >
> > I remember looking in the oagis code and didn't really see anywhere how
> it
> > was connected to the code.  Still, you mention that ofbiz has "some EDI
> > functionality"?  Can you clarify this?
> >
> > If HotWax integrated ofbiz with EDI, how did you do it?  In real life, a
> PO
> > is created, and transmitted to/from a supplier via EDI.
> >
> > A while ago I was looking at BOTS (
> > http://bots.sourceforge.net/en/index.shtml) and it looked like a better
> > solution.
> >
> > On Wed, Oct 5, 2016 at 7:14 AM, Jacopo Cappellato <
> > [hidden email]> wrote:
> >
> > > The component has been removed in rev. 1763454
> > >
> > > Thanks,
> > >
> > > Jacopo
> > >
> > > On Wed, Oct 5, 2016 at 11:16 AM, Jacopo Cappellato <
> > > [hidden email]> wrote:
> > >
> > > > On Wed, Sep 28, 2016 at 11:22 PM, Mike <[hidden email]> wrote:
> > > >
> > > >> Great.  So everyone seems to agree to dump oagis.  Obviously someone
> > > took
> > > >> the time to create this component.  My understanding it is used for
> > > >> automating B2B communication for purchase orders, inventory, etc.
> If
> > > you
> > > >> want ofbiz to play with the big boys, you need this TYPE of
> Electronic
> > > >> Data
> > > >> Interchange (EDI) functionality.
> > > >>
> > > >> So:  If you want to dump oagis, please propose alternatives to make
> > > ofbiz
> > > >> integrate with EDI.  All ERPs have this.
> > > >>
> > > >>
> > > > Thank you for the feedback Mike.
> > > > I do agree that providing some EDI functionality out of the box is
> very
> > > > important for an ERP system. OFBiz already has a few mechanisms for
> > data
> > > > exchange that can be leveraged to implement specific or custom
> > > > integrations. The concept of an universal data interchange standard
> is
> > > > great, but, as far as I know, OAGIS has never reached the critical
> mass
> > > to
> > > > make it a viable solution for all integration needs. By experience I
> > have
> > > > noticed that such standards tend to gain more tractions when they
> > address
> > > > specific industries (e.g. parts interchange formats for the auto
> parts
> > > > aftermarket industry etc...).
> > > > Most importantly, when it was adopted by OFBiz, the OAGIS license
> > allowed
> > > > us to include its xsd files; but after that, they have been
> relicensed
> > > > under an incompatible license: as a consequence this component is
> stuck
> > > to
> > > > an years old and unmaintained version making even more difficult to
> be
> > > used
> > > > to integrate with an external system.
> > > >
> > > > Kind regards,
> > > >
> > > > Jacopo
> > > >
> > > >
> > > >
> > >
> >
>
>
> --
> Thanks
> Brajesh Patel
> skype: brajesh.patel11
> Cell :- [phone]
>