Dev - org.ofbiz.odbc entities and datasource

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Dev - org.ofbiz.odbc entities and datasource

Si Chen-2
David, Andy -

Can you tell us what org.ofbiz.odc entities and datasource is used for?

How should it be configured?  I would imagined not to the regular
derby/postgresql/mysql database, or it wouldn't be odbc.

Can it be disabled?

Thanks,

Si
 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Dev - org.ofbiz.odbc entities and datasource

Jacques Le Roux
Administrator

----- Original Message -----
From: "Si Chen" <[hidden email]>


> David, Andy -
>
> Can you tell us what org.ofbiz.odc entities and datasource is used for?
>
> How should it be configured?  I would imagined not to the regular
> derby/postgresql/mysql database, or it wouldn't be odbc.
>
> Can it be disabled?
>
> Thanks,
>
> Si

That's an interesting question...

Jacques
 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Dev - org.ofbiz.odbc entities and datasource

Jacopo Cappellato
I think they are used for an interface between OFBiz and an external
shipping software... but I'm not sure.

Jacques Le Roux wrote:

> ----- Original Message -----
> From: "Si Chen" <[hidden email]>
>
>
>>David, Andy -
>>
>>Can you tell us what org.ofbiz.odc entities and datasource is used for?
>>
>>How should it be configured?  I would imagined not to the regular
>>derby/postgresql/mysql database, or it wouldn't be odbc.
>>
>>Can it be disabled?
>>
>>Thanks,
>>
>>Si
>
>
> That's an interesting question...
>
> Jacques
>  
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev
>

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Dev - org.ofbiz.odbc entities and datasource

Jacques Le Roux
Administrator
From: "Jacopo Cappellato" <[hidden email]>


> I think they are used for an interface between OFBiz and an external
> shipping software... but I'm not sure.

Yes I saw something like that also, but can't we know anymore ?

Jacques
 

> Jacques Le Roux wrote:
> > ----- Original Message -----
> > From: "Si Chen" <[hidden email]>
> >
> >
> >>David, Andy -
> >>
> >>Can you tell us what org.ofbiz.odc entities and datasource is used for?
> >>
> >>How should it be configured?  I would imagined not to the regular
> >>derby/postgresql/mysql database, or it wouldn't be odbc.
> >>
> >>Can it be disabled?
> >>
> >>Thanks,
> >>
> >>Si
> >
> >
> > That's an interesting question...
> >
> > Jacques
> >  
> > _______________________________________________
> > Dev mailing list
> > [hidden email]
> > http://lists.ofbiz.org/mailman/listinfo/dev
> >
>
>  
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev
 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Dev - org.ofbiz.odbc entities and datasource

Andrew Zeneski
They are staging tables to be used (as Jacopo said) to integrate with  
external shipping software like Worldship from UPS. The name ODBC is  
probably not the best; however the idea for this is to keep the  
tables being written to by an external application away from the  
primary tables in the database.

The reason for putting them in a different database was for security  
and speed. ODBC is very slow and trying to read ALL ofbiz tables in  
order to do world ship mapping was problematic. Since the joins  
required were too complex, keeping them in a staging table was  
preferred.

In addition, these tools write back to the database. So rather than  
having them write directly to the ofbiz tables, we have them write to  
a staging table and then an internal service checks these tables via  
a scheduled service. This service then takes the posted data and  
updates shipment information.

I named them ODBC only because I was integrating with Worldship and  
the connection was (windows based) via ODBC. They can be disabled as  
long as the ECA used to populate them is also disabled and the  
scheduled service which polls them is also disabled. They are moved  
into a new group so they can also be configured to be in the same  
database with everything else; or easily separated out.

Andy

On Dec 16, 2005, at 8:55 AM, Jacques Le Roux wrote:

> From: "Jacopo Cappellato" <[hidden email]>
>
>
>> I think they are used for an interface between OFBiz and an external
>> shipping software... but I'm not sure.
>
> Yes I saw something like that also, but can't we know anymore ?
>
> Jacques
>
>> Jacques Le Roux wrote:
>>> ----- Original Message -----
>>> From: "Si Chen" <[hidden email]>
>>>
>>>
>>>> David, Andy -
>>>>
>>>> Can you tell us what org.ofbiz.odc entities and datasource is  
>>>> used for?
>>>>
>>>> How should it be configured?  I would imagined not to the regular
>>>> derby/postgresql/mysql database, or it wouldn't be odbc.
>>>>
>>>> Can it be disabled?
>>>>
>>>> Thanks,
>>>>
>>>> Si
>>>
>>>
>>> That's an interesting question...
>>>
>>> Jacques
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> [hidden email]
>>> http://lists.ofbiz.org/mailman/listinfo/dev
>>>
>>
>>
>> _______________________________________________
>> Dev mailing list
>> [hidden email]
>> http://lists.ofbiz.org/mailman/listinfo/dev
>
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Dev - org.ofbiz.odbc entities and datasource

Jacques Le Roux
Administrator
----- Original Message -----
From: "A. Zeneski" <[hidden email]>


> They are staging tables to be used (as Jacopo said) to integrate with  
> external shipping software like Worldship from UPS. The name ODBC is  
> probably not the best; however the idea for this is to keep the  
> tables being written to by an external application away from the  
> primary tables in the database.
>
> The reason for putting them in a different database was for security  
> and speed. ODBC is very slow and trying to read ALL ofbiz tables in  
> order to do world ship mapping was problematic. Since the joins  
> required were too complex, keeping them in a staging table was  
> preferred.
>
> In addition, these tools write back to the database. So rather than  
> having them write directly to the ofbiz tables, we have them write to  
> a staging table and then an internal service checks these tables via  
> a scheduled service. This service then takes the posted data and  
> updates shipment information.
>
> I named them ODBC only because I was integrating with Worldship and  
> the connection was (windows based) via ODBC. They can be disabled as  
> long as the ECA used to populate them is also disabled and the  
> scheduled service which polls them is also disabled. They are moved  
> into a new group so they can also be configured to be in the same  
> database with everything else; or easily separated out.
>
> Andy

Thanks Andy, that's really clear now.

Jacques


> On Dec 16, 2005, at 8:55 AM, Jacques Le Roux wrote:
>
> > From: "Jacopo Cappellato" <[hidden email]>
> >
> >
> >> I think they are used for an interface between OFBiz and an external
> >> shipping software... but I'm not sure.
> >
> > Yes I saw something like that also, but can't we know anymore ?
> >
> > Jacques
> >
> >> Jacques Le Roux wrote:
> >>> ----- Original Message -----
> >>> From: "Si Chen" <[hidden email]>
> >>>
> >>>
> >>>> David, Andy -
> >>>>
> >>>> Can you tell us what org.ofbiz.odc entities and datasource is  
> >>>> used for?
> >>>>
> >>>> How should it be configured?  I would imagined not to the regular
> >>>> derby/postgresql/mysql database, or it wouldn't be odbc.
> >>>>
> >>>> Can it be disabled?
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Si
> >>>
> >>>
> >>> That's an interesting question...
> >>>
> >>> Jacques
> >>>
> >>> _______________________________________________
> >>> Dev mailing list
> >>> [hidden email]
> >>> http://lists.ofbiz.org/mailman/listinfo/dev
> >>>
> >>
> >>
> >> _______________________________________________
> >> Dev mailing list
> >> [hidden email]
> >> http://lists.ofbiz.org/mailman/listinfo/dev
> >
> > _______________________________________________
> > Dev mailing list
> > [hidden email]
> > http://lists.ofbiz.org/mailman/listinfo/dev
>
>  
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev
 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Dev - org.ofbiz.odbc entities and datasource

Si Chen-2
In reply to this post by Andrew Zeneski
Andy,

Thanks.  This does really help clear it up.

So is the idea during deployment to set "org.ofbiz" entity group to a
datasource like mysql or postgresql and then "org.ofbiz.odbc" to an odbc
link for worldship?  Or is the idea to set "org.ofbiz.odbc" to mysql and
postgresql as well, but in a separate database, which can then be
configured to be accessed from worldship?

Si

A. Zeneski wrote:

> They are staging tables to be used (as Jacopo said) to integrate with  
> external shipping software like Worldship from UPS. The name ODBC is  
> probably not the best; however the idea for this is to keep the  
> tables being written to by an external application away from the  
> primary tables in the database.
>
> The reason for putting them in a different database was for security  
> and speed. ODBC is very slow and trying to read ALL ofbiz tables in  
> order to do world ship mapping was problematic. Since the joins  
> required were too complex, keeping them in a staging table was  
> preferred.
>
> In addition, these tools write back to the database. So rather than  
> having them write directly to the ofbiz tables, we have them write to  
> a staging table and then an internal service checks these tables via  
> a scheduled service. This service then takes the posted data and  
> updates shipment information.
>
> I named them ODBC only because I was integrating with Worldship and  
> the connection was (windows based) via ODBC. They can be disabled as  
> long as the ECA used to populate them is also disabled and the  
> scheduled service which polls them is also disabled. They are moved  
> into a new group so they can also be configured to be in the same  
> database with everything else; or easily separated out.
>
> Andy
>
> On Dec 16, 2005, at 8:55 AM, Jacques Le Roux wrote:
>
>> From: "Jacopo Cappellato" <[hidden email]>
>>
>>
>>> I think they are used for an interface between OFBiz and an external
>>> shipping software... but I'm not sure.
>>
>>
>> Yes I saw something like that also, but can't we know anymore ?
>>
>> Jacques
>>
>>> Jacques Le Roux wrote:
>>>
>>>> ----- Original Message -----
>>>> From: "Si Chen" <[hidden email]>
>>>>
>>>>
>>>>> David, Andy -
>>>>>
>>>>> Can you tell us what org.ofbiz.odc entities and datasource is  
>>>>> used for?
>>>>>
>>>>> How should it be configured?  I would imagined not to the regular
>>>>> derby/postgresql/mysql database, or it wouldn't be odbc.
>>>>>
>>>>> Can it be disabled?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Si
>>>>
>>>>
>>>>
>>>> That's an interesting question...
>>>>
>>>> Jacques
>>>>
>>>> _______________________________________________
>>>> Dev mailing list
>>>> [hidden email]
>>>> http://lists.ofbiz.org/mailman/listinfo/dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> [hidden email]
>>> http://lists.ofbiz.org/mailman/listinfo/dev
>>
>>
>> _______________________________________________
>> Dev mailing list
>> [hidden email]
>> http://lists.ofbiz.org/mailman/listinfo/dev
>
>
>
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev
>
 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Dev - org.ofbiz.odbc entities and datasource

Jacques Le Roux
Administrator

----- Original Message -----
From: "Si Chen" <[hidden email]>


> Andy,
>
> Thanks.  This does really help clear it up.
>
> So is the idea during deployment to set "org.ofbiz" entity group to a
> datasource like mysql or postgresql and then "org.ofbiz.odbc" to an odbc
> link for worldship?  Or is the idea to set "org.ofbiz.odbc" to mysql and
> postgresql as well, but in a separate database, which can then be
> configured to be accessed from worldship?

Another interesting question :o)

Jacques
 

> Si
>
> A. Zeneski wrote:
>
> > They are staging tables to be used (as Jacopo said) to integrate with  
> > external shipping software like Worldship from UPS. The name ODBC is  
> > probably not the best; however the idea for this is to keep the  
> > tables being written to by an external application away from the  
> > primary tables in the database.
> >
> > The reason for putting them in a different database was for security  
> > and speed. ODBC is very slow and trying to read ALL ofbiz tables in  
> > order to do world ship mapping was problematic. Since the joins  
> > required were too complex, keeping them in a staging table was  
> > preferred.
> >
> > In addition, these tools write back to the database. So rather than  
> > having them write directly to the ofbiz tables, we have them write to  
> > a staging table and then an internal service checks these tables via  
> > a scheduled service. This service then takes the posted data and  
> > updates shipment information.
> >
> > I named them ODBC only because I was integrating with Worldship and  
> > the connection was (windows based) via ODBC. They can be disabled as  
> > long as the ECA used to populate them is also disabled and the  
> > scheduled service which polls them is also disabled. They are moved  
> > into a new group so they can also be configured to be in the same  
> > database with everything else; or easily separated out.
> >
> > Andy
> >
> > On Dec 16, 2005, at 8:55 AM, Jacques Le Roux wrote:
> >
> >> From: "Jacopo Cappellato" <[hidden email]>
> >>
> >>
> >>> I think they are used for an interface between OFBiz and an external
> >>> shipping software... but I'm not sure.
> >>
> >>
> >> Yes I saw something like that also, but can't we know anymore ?
> >>
> >> Jacques
> >>
> >>> Jacques Le Roux wrote:
> >>>
> >>>> ----- Original Message -----
> >>>> From: "Si Chen" <[hidden email]>
> >>>>
> >>>>
> >>>>> David, Andy -
> >>>>>
> >>>>> Can you tell us what org.ofbiz.odc entities and datasource is  
> >>>>> used for?
> >>>>>
> >>>>> How should it be configured?  I would imagined not to the regular
> >>>>> derby/postgresql/mysql database, or it wouldn't be odbc.
> >>>>>
> >>>>> Can it be disabled?
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> Si
> >>>>
> >>>>
> >>>>
> >>>> That's an interesting question...
> >>>>
> >>>> Jacques
> >>>>
> >>>> _______________________________________________
> >>>> Dev mailing list
> >>>> [hidden email]
> >>>> http://lists.ofbiz.org/mailman/listinfo/dev
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Dev mailing list
> >>> [hidden email]
> >>> http://lists.ofbiz.org/mailman/listinfo/dev
> >>
> >>
> >> _______________________________________________
> >> Dev mailing list
> >> [hidden email]
> >> http://lists.ofbiz.org/mailman/listinfo/dev
> >
> >
> >
> > _______________________________________________
> > Dev mailing list
> > [hidden email]
> > http://lists.ofbiz.org/mailman/listinfo/dev
> >
>  
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev
 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev